Hi,
Somebody used our majordomos address as sending address for his spamrun.
Now we are drowning in MAJORDOMO ABORT messages, because majordomo gets
hit by thousands of Bounces.
I know I can filter my personal mail with procmail, but I would like to
do this globally.
Is there a way to get majordomo not to send out these messages (but
only for the mailerdaemon case, otherwise these alerts are often
useful)?
I have tried to actually block mail from <> to majordomo using
sendmail/AccessDB/check_compat-Feature. However, there seems to be a
syntax-problem.
Check_Compat-Ruleset needs the fully expanded aliases and majordomo
expands to "|/usr/local/lib/mail/majordomo-current/wrapper majordomo",
putting this into a Compat: entry does not work (The AccessDB is
processed without error, but the rule does not work).
Compat:<><@>"|/usr/local/lib/mail/majordomo-current/wrapper majordomo"
ERROR: 550 Leave our majordomo alone
(I have tested Compat:<><@>user@domain and it works, it is only the
majordomo part that goes wrong.)
Does anyone know, what the right syntax is?
thanks for your input
Susan
(Did I mention, that I hate spammers. There are millions of other
addresses they could steal from our namespace, but no - it has to be
the listservers, just to annoy us.)
Follow-Ups:
|
|
