On Jun 3, 2009, at 12:50 AM, Mark Sapiro wrote:
XXX We used to classify bounces to the site list as bounce events for every list, but this caused severe problems. Here's the scenario: [email protected] is a member of 4 lists, and a list owner of the foo list. example.com has an aggressive spam filter which rejects any message that is spam or contains spam as an attachment. Now, a spambot sends a piece of spam to the foo list, but since that spambot is not a member, the list holds the message for approval, and sends a notification to [email protected] as list owner. That notification contains a copy of the spam. Now example.com rejects the message, causing a bounce to be sent to the site list's bounce address. The bounce runner would then dutifully register a bounce for all 4 lists that [email protected] was a member of, and eventually that person would get disabled on all their lists. So now we ignore site list bounces. Ce La Vie for password reminder bounces.
I hope we've all learned by now never to bounce spam back to the "original" sender!
-Barry
PGP.sig
Description: This is a digitally signed message part
_______________________________________________ Mailman-Developers mailing list [email protected] http://mail.python.org/mailman/listinfo/mailman-developers Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-developers%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-developers/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
