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
You do want to verify that DNS and /etc/hosts files do not have
You need to verify that during your "too many hops" loop, your own
default route out of your local network was funtional.
"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
> # 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