----- Original Message ----- > From: "Mark Sapiro" <[email protected]> > To: "Franck Martin" <[email protected]> > Sent: Monday, July 8, 2013 10:37:01 AM > Subject: Re: [Mailman-Developers] Adding DMARC support for Mailman 3 > > On 07/08/2013 08:34 AM, Franck Martin wrote: > > > > I suspect this process has been improved in MM3, but I have not had a look > > at the code. The purpose is for mailman to recognize 5.7.x bounces and not > > count them against the recipient (or as soft bounce). Hard bounce is the > > default for any non recognized bounce. > > > MM3 uses flufl.bounce <https://launchpad.net/flufl.bounce> for bounce > processing. The process, algorithms and heuristics are essentially > identical to MM2.1 > > In the case of an RFC 3464 compliant DSN, MM does not look at the Status > field at all. It only looks at the Action field. Actions beginning with > 'fail' result in a 'permanent failure' determination. Actions beginning > with 'delayed' result in a 'temporary failure' determination. All other > actions result in the bounce being ignored. >
I see in MM2 that regex are used to classify the bounces: http://bazaar.launchpad.net/~mailman-coders/mailman/2.1/files/head:/Mailman/Bouncers/ which is described in broad terms here: http://www.esosoft.com/support/mailinglist/mailman/bounce.html It seems flufl has the same structure http://bazaar.launchpad.net/~mailman-coders/flufl.bounce/trunk/files/head:/flufl/bounce/_detectors/ but I just read the code quickly... _______________________________________________ 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
