Do you understand what a mail loop is, and how to track one down?
Most of us get lazy about this, but it really is required so we can help you
with a problem that is not on our own machine.
What linux/unix are you running your mail server on? What MTA does your mail
server run? Include version numbers. Is your majordomo installed on the same
or a separate host? What version of majordomo are you running? Did you install
majordomo yourself? Was it from an rpm, pkg, zip, or other archive? What was
the output result of executing `./wrapper config-test`?
Now that introductions are out of the way, is your mail loop caused by DNS mx
records, a misconfiguration of your MTA or aliases, or your majordomo config?
What does your majordomo/Log say? What does your mail.log say? Are all of the
permissions and ownerships for your majordomo configuration and the mailing lists
themselves and the work directories for archives and digests compatible with both
majordomo and your MTA?
If your MTA is piping to a majordomo tool/utility, but does not have permission
to execute it, you might see this kind of error. Also, if the majordomo-owner
alias points to or evaluates to anything but a "REAL" user, you could get similar
results. The same is true for each list's -owner or -approval address/alias.
Dan Liston
Caldwell, Cedric wrote:
Got the majordomo tool working.. that's all that responded.
Now, I have an issue with the nasty messages filling up disk space:
MAJORDOMO ABORT (mj_majordomo)!!
<mailto:Majordomo @
hoppipolla .
net> Majordomo @
hoppipolla .
net punting to avoid
mail loop.
I only seem to get these messages after I restart sendmail and then send a
message to one of the lists.
Any resolution have a resolution to this?
References:
|
|
