My list owners are getting Sobig files bounced to them through the administrative addresses. One of their ISPs has decided to reject those relayed messages with a 550 User Unknown because they contain Sobig. The mailman-owner gets this bounce back and kicks them off all the lists. She's asked her admins to change it to a 554 Service Unavailable
Ask him to silently discard them (>/dev/null) because the bounce address is also a victim.
Yes, but it is doing a 550 in its conversation with the server (in this case a Sobig instance) so for actual Sobig connections, the message would be silently discarded by both the Sobig instance and their mail server without annoying the owner of the forged address. Not a bad way to do things overall, I just need to get around it somehow.
-- Rob Carlson [EMAIL PROTECTED] http://vees.net/
------------------------------------------------------ Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
