Mailman-coders November 2019

mailman-coders@python.org

5 participants
17 discussions

[Bug 1851442] [NEW] MailList.AddMember crashes in a certain condition
by Yasuhito FUTATSUKI＠POEM 12 Jan '20

12 Jan '20

Public bug reported: MailList.AddMember crashes with UnicodeDecodeError if all conditions below are satisfied. * subscribe_policy of the lists is 1 or 3 (user confirmaion required) * charset of preferred_language of the list is other than us-ascii * translation for ' from %(remote)s' in the language contains other than us-ascii character the patch attached may fix it. ** Affects: mailman Importance: Undecided Status: New ** Patch added: "fix_AddMember_patch.txt" https://bugs.launchpad.net/bugs/1851442/+attachment/5303123/+files/fix_AddM… ** Branch linked: lp:mailman/2.1 -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1851442 Title: MailList.AddMember crashes in a certain condition To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1851442/+subscriptions

2 2

[Bug 1785854] [NEW] TypeError from confirm CGI.
by Mark Sapiro 12 Jan '20

12 Jan '20

Public bug reported: We have seen some massive, robotic subscribes and confirmations. In rare cases a TypeError can be thrown. This occurs because in processing, the CGI script retrieves the pending entry more than once. If the initial retrieval returns None, an appropriate message is returned, but if two clients confirm the same token at the same time, both initial retrievals may succeed, but then subsequent processing locks the list and retrieves the data again. The first client to get there processes the confirmation which removes the token. Then when the list is unlocked, the second client gets None for the pending data and throws TypeError when retrieving things from None. ** Affects: mailman Importance: Undecided Status: New -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1785854 Title: TypeError from confirm CGI. To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1785854/+subscriptions

2 3

[Bug 1805137] [NEW] Bounces sent from opensmtpd not parsed
by Cristiano de Paula Costa 12 Jan '20

12 Jan '20

Public bug reported: Hi, We have updated our external MTA to use OpenBSD(6.4) and opensmptd. After we updated, mailman started to send "bounce message w/no discernable addresses" messages to us (list admins). It seems that mailman is not able to parse bounce messages sent from opensmtpd. Please check an example of a bounce message from opensmtpd: Hi! This is the MAILER-DAEMON, please DO NOT REPLY to this email. An error has occurred while attempting to deliver a message for the following list of recipients: XXXXXXXXX(a)live.com: 550 5.5.0 Requested action not taken: mailbox unavailable. [VE1EUR02FT047.eop-EUR02.prod.protection.outlook.com] Below is a copy of the original message: We are using mailman 2.1.11 and I could not test the issue on version 2.1.17. But, reading the code, it seem that the problem is still there. We managed to fix the problem by editing the file 'mailman/Mailman/Bouncers/SimpleMatch.py' and including the following lines: 191,194d190 < # opensmtpd < (_c('An error has occurred while attempting to deliver a message for'), < _c('Below is a copy of the original message'), < _c('^\s*(?P<addr>[^\s@]+@[^\s@]+)')), patch follows attached Regards, Cristiano ** Affects: mailman Importance: Undecided Status: New ** Patch added: "SimpleMatch.py.patch" https://bugs.launchpad.net/bugs/1805137/+attachment/5216458/+files/SimpleMa… -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1805137 Title: Bounces sent from opensmtpd not parsed To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1805137/+subscriptions

3 7

[Bug 1818872] [NEW] Trailing spaces in the email address cause login failures.
by Mark Sapiro 12 Jan '20

12 Jan '20

Public bug reported: Login to the user options page and private archives authentication fails if the email address has trailing spaces. ** Affects: mailman Importance: Low Assignee: Mark Sapiro (msapiro) Status: In Progress -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1818872 Title: Trailing spaces in the email address cause login failures. To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1818872/+subscriptions

2 3

[Bug 1831321] [NEW] the List-Id field is filled without < and > around the list-id if the description contains unsupported characters
by Florian Schlegel 12 Jan '20

12 Jan '20

Public bug reported: According to rfc2919 the List-Id field should be formated like this: list-id-header = "List-ID:" [phrase] "<" list-id ">" CRLF This works as long as description is left blank or contains supported characters. In my case the description was as follows: �ffentliche Supportliste As you can see the umlaut "Ö" got broken while importing the list from an old server. Unfortunately I don't know how the import was done. The field is still present but < and > around the list-id are missing. This is problematic with procmail and other mail filters. ** Affects: mailman Importance: Undecided Status: New -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1831321 Title: the List-Id field is filled without < and > around the list-id if the description contains unsupported characters To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1831321/+subscriptions

3 6

[Bug 1845751] [NEW] cc modification due to nodup setting breaks DKIM & thus DMARC
by Ian Kelling 12 Jan '20

12 Jan '20

Public bug reported: Keeping DKIM signature intact allows passing DMARC without from munging (I have references all about this if needed). However, mailman modifies the cc header when a subscriber has the nodup setting and someone sends to the list with that subscriber cced. Mailman doesn't email them and removes them from the cc, presumably so for further replies mailman can email them without it being a duplicate and they get all the good mailman headers instead of a plain email from the cc. Anyways, best if Mailman just not modify the cc if we are in the situation where it matters for passing DMARC. The attached patch does that. Note, I'm sending this as an employee of the Free Software Foundation and my copyright is already going to them. ** Affects: mailman Importance: Undecided Status: New ** Patch added: "nodup-dkim.patch" https://bugs.launchpad.net/bugs/1845751/+attachment/5292024/+files/nodup-dk… -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1845751 Title: cc modification due to nodup setting breaks DKIM & thus DMARC To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1845751/+subscriptions

4 10

[Merge] lp:~futatuki/mailman/2.1-ja-translation into lp:mailman/2.1
by Yasuhito FUTATSUKI＠POEM 12 Nov '19

12 Nov '19

Yasuhito FUTATSUKI at POEM has proposed merging lp:~futatuki/mailman/2.1-ja-translation into lp:mailman/2.1. Commit message: update Japanese translation for lp:mailman/2.1 rev 1825-1826 Requested reviews: Mailman Coders (mailman-coders) For more details, see: https://code.launchpad.net/~futatuki/mailman/2.1-ja-translation/+merge/3753… -- Your team Mailman Coders is requested to review the proposed merge of lp:~futatuki/mailman/2.1-ja-translation into lp:mailman/2.1.

2 1

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

Mailman-coders November 2019