Spams are causing "ping pongs"
Hi everyone, I have a problem where if we get some type of spam cause emails to 'ping pong' back and forth. Instead an email going to me (ie the list owner) they appear to go back to the list, and get held again (because the list owner alias isn't on the list) and back and forth it goes about 40 times.
the -owner@ messages do go to me (I tested it :) so I'm not sure why they don't get forwarded to me in this case.
I have an archive of the messages in mbox format (depickled heldmsg-*) available at http://www.gsoft.com.au/~doconnor/ping-pong.tbz
I am running MIMEDefang which calls Spam Assassin to mark incoming messages with X- headers and Mailman is configured to hold messages with those headers (if it matters). This list is configured to hold messages from non-subscribers and to not send "your message is held" emails.
Any suggestions muchly appreciated! Let me know if you need more info :)
Thanks for your time.
-- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C
Daniel O'Connor wrote:
I am running MIMEDefang which calls Spam Assassin to mark incoming messages with X- headers and Mailman is configured to hold messages with those headers (if it matters). This list is configured to hold messages from non-subscribers and to not send "your message is held" emails.
There is a recent thread on this in the archives. See the entire thread starting at http://mail.python.org/pipermail/mailman-users/2005-June/045186.html
If (one of) the regexp(s) in header_filter_rules matches the subject of the owner notification - "%(listname)s post from %(sender)s requires approval" - the owner notification is held again, thus the loop.
If you have something like [spam] in your regexp(s), make sure the brackets are escaped - \[spam\]
There may be a problem matching the X- headers as well. in 2.1.6, header_filter_rules matches the sub-part headers too. It shouldn't match an X- header that only existest in the content of a message/rfc822 sub-part, but maybe there's a problem here.
Also, does the message to the -owner address go through Spam Assassin again? If so, you may have to arrange for it not to.
-- Mark Sapiro <msapiro@value.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
On Sat, 2 Jul 2005 23:23, Mark Sapiro wrote:
There is a recent thread on this in the archives. See the entire thread starting at http://mail.python.org/pipermail/mailman-users/2005-June/045186.html
I put the following in mm_cfg.py and it appears to have fixed it..
# Don't spam detect on owner messages or we'll get a loop OWNER_PIPELINE = [ # 'SpamDetect', 'Replybot', 'OwnerRecips', 'ToOutgoing', ]
It seems strange that this isn't the default to be honest, I submitted an RFE :)
-- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C
participants (2)
-
Daniel O'Connor
-
Mark Sapiro