On Thu, 2004-06-17 at 14:36, Greg Stark wrote: > It is using messages posted to the list -- the content and format of which it > does not control -- to detect bouncing email addresses. Because of this it > cannot tell if the bounces it's receiving are caused by a broken email address > or caused by some particularity of the posted message.
> Really Mailman should simply not trust outside data for any purpose. It should > treat the bounces received from mailing list messages purely as hints. It > should then send its *own* message with content not subject to any control > from outside to the user. Only if that known inoffensive message bounces > should it consider removing the user. Upgrade to Mailman 2.1.5, which sends out probe messages after the bounce threshold is reached. Members will only get disabled if the probe message bounces, it should be computationally infeasible to forge a probe bounce, and bogus probes bounces are simply ignored. When a probe is sent, the member's bounce score is reset to zero, since it's impossible to tell whether the probe actually reached its destination -- all you know is that it hasn't bounced... yet. -Barry
signature.asc
Description: This is a digitally signed message part
_______________________________________________ Mailman-Developers mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-developers Unsubscribe: http://mail.python.org/mailman/options/mailman-developers/archive%40jab.org
