You missed the final argument on the first alias. It needs to know where
to "resend" TO. Most likely, oregoncares-outgoing?
Your reply_to (not reply-to, assuming typo here) of $SENDER could imply
that your <list> will not get much traffic. On the other hand, $SENDER
is the default for digested lists. You have to be careful here too. If
the $SENDER happens to be an alias that resolves to majordomo-owner or
root, or postmaster, you might have a loop.
The error message you are receiving after making changes to the aliases,
is solved by my first comment above. Your original "loop" problem is
not. That must be solved by close scrutinization of the messages that
bounce back, looking first at the bounce comment itself, then the content
of the bounced message's Received: headers to see which 2 or more
servers are creating the loop. If the looping is happening within your
own network, look for sendmail.cf and/or DNS MX record errors, as well
as the possibility of the reply_to or sender = in your .config files.
"Christopher A. Adams" wrote:
> Thanks for your reply. I had completely overlooked the use of the resend
> arguments in the list.config file, though I'm not sure that is the source
> of the problem.
> So, if I clean up my aliases and end up with a first line like this:
> oregoncares: "|/usr/local/majordomo/wrapper resend -l oregoncares
> Then, in the oregoncares.config file, I specify:
> reply-to: $SENDER (replaces -r)
> resend_host: sparkie.osl.state.or.us (replaces -h)
> sender: (defaults to list-name-request) (replaces -f)
> Then, when I post a message to the list, I get this result:
> <firstname.lastname@example.org>: Command died with status 2:
> "/usr/local/majordomo/wrapper resend -l oregoncares"
> Note: I have been administering over 200 Majordomo lists for quite awhile,
> using arguments in the aliases file. So, I realize that I shouldn't be
> doing it, but I just want you to know that I am not a novice and my lists
> are working for the most part. I would like to do it the right way.
> Thanks for your help.
> Christopher Adams
> On Tue, 23 Oct 2001, Daniel Liston wrote:
> > Note the last 3 lines quoted from the majordomo/resend file.
> > # Okay, resend accepts many command line arguments, as revealed by the
> > # Getopts call:
> > # &Getopts("Aa:df:h:I:l:M:p:Rr:s") || die("resend: Getopts() failed: $!");
> > # Most of these are defined via the list config file, so in general,
> > # it's a really bad idea to hardcode them in the alias definition.
> > # In a future version of majordomo, these will likely all be removed.
> > I would get rid of all but the "-l oregoncares" argument from the alias
> > and use the settings in your oregoncares.config file.
> > As for the snippet you provided from your aliases file;
> > Without knowing what MTA you using and how it is configured, or how well
> > connected your network and DNS resolver are connected, or any firewall
> > rules that may be preventing connections, it is impossible to provide a
> > simple answer to your question.
> > You might want to check the majordomo/lists/oregoncares file for any
> > addresses that may be pointing back to one of your aliases.
> > You might want to view the log files for your MTA and for majordomo for
> > any clues.
> > You do want to verify that DNS and /etc/hosts files do not have
> > conflicting entries.
> > You need to verify that during your "too many hops" loop, your own
> > default route out of your local network was funtional.
> > Dan Liston
> > "Christopher A. Adams" wrote:
> > >
> > > A list has recently developed a problem that I cannot figure out. I get
> > > messages that users can't be reached because of "too many hops- mail
> > > forwarding loop". From what I have read, many times that is caused by an
> > > aliases entry being forwarded to itself. I submit below the standard
> > > format that I use and wonder if anyone can comment on any obvious
> > > problems.
> > >
> > > #
> > > # oregoncares
> > > #
> > > oregoncares: "|/usr/local/majordomo/wrapper resend -l oregoncares -f oregoncares-Owner -h sparkie.osl.state.or.us -r oregoncares oregoncares-outgoing"
> > > owner-oregoncares: oregoncares-owner
> > > oregoncares-outgoing: :include:/usr/local/majordomo/lists/oregoncares
> > > owner-oregoncares-outgoing: oregoncares-owner
> > > owner-oregoncares-archive: oregoncares-owner
> > > oregoncares-request: "|/usr/local/majordomo/wrapper request-answer oregoncares"
> > > owner-oregoncares-request: oregoncares-owner
> > > oregoncares-approval: oregoncares-owner
> > > oregoncares-owner: email@example.com
> > > owner-oregoncares-owner: oregoncares-owner