[Mailman-Developers] [ mailman-Patches-665569 ] make Postfix bounce detection work withnewer postfix
Patches item #665569, was opened at 2003-01-10 17:33 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=665569&group_id=103 Category: bounce processing Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: James Henstridge (jhenstridge) Assigned to: Nobody/Anonymous (nobody) Summary: make Postfix bounce detection work with newer postfix Initial Comment: Mailman does not recognise bounce messages from newer versions of Postfix. The content-type header on bounce messages looks like this: Content-Type: multipart/report; report-type=delivery-status; boundary="2892E4C0CF.1042189077/quoll.daa.com.au" Mailman only looks for bounce messages with type multipart/mixed, so skips them. The simple solution is to check for both content types (which should allow mailman to continue to work with old postfixes. The attached patch is against 2.0.x (haven't upgraded to MM2.1 yet), but the code is almost identical for 2.1 so the patch should be easy to apply. -- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=665569&group_id=103 ___ Mailman-Developers mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-developers
[Mailman-Developers] [ mailman-Patches-665569 ] make Postfix bounce detection work withnewer postfix
Patches item #665569, was opened at 2003-01-10 17:33 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=665569&group_id=103 Category: bounce processing Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: James Henstridge (jhenstridge) Assigned to: Nobody/Anonymous (nobody) Summary: make Postfix bounce detection work with newer postfix Initial Comment: Mailman does not recognise bounce messages from newer versions of Postfix. The content-type header on bounce messages looks like this: Content-Type: multipart/report; report-type=delivery-status; boundary="2892E4C0CF.1042189077/quoll.daa.com.au" Mailman only looks for bounce messages with type multipart/mixed, so skips them. The simple solution is to check for both content types (which should allow mailman to continue to work with old postfixes. The attached patch is against 2.0.x (haven't upgraded to MM2.1 yet), but the code is almost identical for 2.1 so the patch should be easy to apply. -- >Comment By: James Henstridge (jhenstridge) Date: 2003-01-10 17:36 Message: Logged In: YES user_id=146903 Hmm. It seems to have lost the attachment -- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=665569&group_id=103 ___ Mailman-Developers mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-developers
[Mailman-Developers] [ mailman-Bugs-665732 ] List-Id should be oneline.
Bugs item #665732, was opened at 2003-01-10 15:05 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=665732&group_id=103 Category: mail delivery Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Bernhard Reiter (ber) Assigned to: Nobody/Anonymous (nobody) Summary: List-Id should be one line. Initial Comment: If the List-Id: header gets splitted into several lines, which I could observe on lists I'm on which switched to mailman 2.1 now, it is getting harder to filter the list based on the fixed part of the list id. Filtering would need to look at more than one line. So a procmail pattern (procmail uses egrep an basically work on one line) like :0: *^List-Id:.* $ kmail-incoming would not work anymore reliably when the description of the mailinglist is getting longer. Before mailman 2.1 the above pattern was save against the changes in the description. I know that headers longer than one line are allowed, still I consider is a design bug at mailman does not necessrily need to make filtering harder at this point. -- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=665732&group_id=103 ___ Mailman-Developers mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-developers
[Mailman-Developers] [ mailman-Bugs-665791 ] Hiding e-mail addresses breaks mbox archives
Bugs item #665791, was opened at 2003-01-10 10:12 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=665791&group_id=103 Category: Pipermail Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: A.M. Kuchling (akuchling) Assigned to: Nobody/Anonymous (nobody) Summary: Hiding e-mail addresses breaks mbox archives Initial Comment: (Noticed in the archives for the pycon-organizers list) The archiver will generate mbox separator lines that look like this: >From sholden at holdenweb.com Fri Jan 3 03:53:20 2003 This breaks at least mutt's mbox parsing. The line should use unaltered e-mail address. -- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=665791&group_id=103 ___ Mailman-Developers mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-developers
[Mailman-Developers] Re: [Mailman-Users] What's wrong with the mailman-users archive?
We had some problems with mail delivery on python.org/zope.org. We now believe it was a SpamAssassin process that was hanging Exim delivery. We've got a stop gap measure in place which is getting mail flowing again. Looks like the hosage affected the archives. I'll attempt to rebuild them. -Barry ___ Mailman-Developers mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-developers
