Mailman 3 November 2016 - Mailman-coders

[Bug 1643210] [NEW] 'from_is_list' does not RFC2047 encode correctly when translation contains non-ascii char
by Yasuhito FUTATSUKI＠POEM June 2, 2017

June 2, 2017

Public bug reported: If from_is_list feature is used, From: header's `realname' field is composed by original realname and translation of '%(realname)s via %(lrn)s' which may contain non-ascii character. The realname field is encoded before compose if nessesary, but translation part is not. So From header may contain raw non-ascii character. To fix this, do RFC 2047 encode after compose. (There is another bug..., if servers language setting and mail list preferred language is differ, translation has taken from servers language, not from mail list one. Attached patch contains fix of it) ** Affects: mailman Importance: Undecided Status: New ** Attachment added: "CookHeaders.py.diff.txt" https://bugs.launchpad.net/bugs/1643210/+attachment/4780159/+files/CookHead… ** 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/1643210 Title: 'from_is_list' does not RFC2047 encode correctly when translation contains non-ascii char To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1643210/+subscriptions

2 16

[Bug 1602779] [NEW] Some German language templates are utf-8 encoded
by Mark Sapiro May 3, 2017

May 3, 2017

Public bug reported: The templates/de files adminaddrchgack.txt masthead.txt nomoretoday.txt probe.txt refuse.txt subauth.txt are incorrectly encoded as utf-8 instead of iso-8859.1. ** Affects: mailman Importance: Medium Assignee: Mark Sapiro (msapiro) Status: Fix Committed -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1602779 Title: Some German language templates are utf-8 encoded To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1602779/+subscriptions

2 4

[Bug 1539384] [NEW] Non-blocking DMARC mitigations should also be done for p=none
by Jakob Bohm Dec. 29, 2016

Dec. 29, 2016

Public bug reported: If you read the DMARC informational RFC (no longer just a draft), you will see that there are 3 possible policies a mail domain (of a poster) can set p=reject All recipients should reject/drop mails with From: ...<at ourdomain> that have neither DKIM not SPF pass for our ourdomain. Send automatic reports of this to our postmaster at the specified rua address. p=quarantine All recipient spam filters should penalize ditto. Send the same automatic reports. p=none Recipients should act as if this policy was not there, but send the automatic reports so we can decide if our policy needs fine tuning before switching to a tougher p value. Currently Mailman 2.1.20+ has code that applies reasonable adjustments to avoid failures with posters from p=reject domains (such as Yahoo). Mailman 2.1.20+ also has an option to do the same for p=quarantine. But when a domain is set to p=none because the postmaster is trying to figure out what will break if he/she/they turn on quarantine, Mailman will continue sending mail in a way which causes all the backscatter reports from everybody except the list owner. As a postmaster I find this very annoying as it makes it hard to find actual problems in the flurry of backscatter noise from making even a few posts to a single Mailman list. Especially annoying is reports that some servers received mails with failed DKIM from a 4th party IP, as it is impossible to tell if those 4th parties were forwarding mails that were broken by Mailman munging the Subject header or were handling mails of some other kind needing a different correction. I would therefore suggest the following change to the 2.1 branch (since 3.x is still not in a usable state): * If dmarc_moderation_action is set to a value other than Reject or Discard, the specified mitigation should be applied to domains with any valid DMARC policy, not just reject. The effect of this would be: + List admins need to do nothing extra, since this works with the existing Mailman settings. + Domains that use p=none with a user posting to a list with action other than Reject/Discard will see the true effects that setting p=reject would have, and their users will see any change in the Mailing list behavior and be able to complain to the local postmaster before the domain goes to p=reject. Which is exactly the intended purpose of p=none. + Domains that use p=none with a user posting to a list with action set to Reject/Discard will receive a flurry of error reports reflecting how badly things will break if they go to p=reject, but the users will not loose their ability to post (because the reject/discard action is not applied to domains with p=none). Again this is consistent with the intended purpose of p=none. + Domains that use p=quarantine with a user posting to a list that has not set dmarc_quarantine_moderation_action will see the same effects as domains that use p=none (see above). + Domains that use p=quarantine with a user posting to a list that has set dmarc_quarantine_moderation_action will see the same behavior as for the current 2.1.20 code. + Domains that use p=reject will see the same behavior as for the current 2.1.20 code. ** Affects: mailman Importance: Undecided Status: New ** Tags: dmarc -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1539384 Title: Non-blocking DMARC mitigations should also be done for p=none To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1539384/+subscriptions

5 14

[Bug 1643215] [NEW] Some Handlers get translation of language unsupposed
by Yasuhito FUTATSUKI＠POEM Nov. 24, 2016

Nov. 24, 2016

Public bug reported: Take a look at Mailman/Handlers/*.py, some of handlers seems to get translation of server language when mail list preferred language or user preferred language context is needed, for lack of set_language() (or set_translation). (Some handlers like Hold.py seems to switch language context correctly.) I found it in CookHeaders.py at first, while I try to fix bug #1643210 (and patch for fix attached there). I cannot determine which of those is correct and is incorrect, so I report it incompletely, sorry. ** Affects: mailman Importance: Undecided Status: New ** 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/1643215 Title: Some Handlers get translation of language unsupposed To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1643215/+subscriptions

2 4

[Bug 266464] Re: Subscriber "disappears" after subscription
by Mark Sapiro Nov. 17, 2016

Nov. 17, 2016

Thanks for the report. Fixed at http://bazaar.launchpad.net/~mailman- coders/mailman/2.1/revision/1683 ** Changed in: mailman Status: Fix Released => Fix Committed ** Changed in: mailman Milestone: 2.1.15 => 2.1.24 -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/266464 Title: Subscriber "disappears" after subscription To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/266464/+subscriptions

1 0

[Bug 266464] Re: Subscriber "disappears" after subscription
by Uli Nov. 16, 2016

Nov. 16, 2016

The bug was not completly fixed in Mailman 2.1.15. self.__timestamp is set after the loading AND parsing of the file. With large files the parsing may need 1-2 seconds and in the meantime a new file, but older then the self.__timestamp set after the parsing ist written: (1) Nov 16 21:02:54 2016 (57765) Try-Load config file /var/lib/mailman/lists/XY/config.pck -> Load (2) Nov 16 21:02:54 2016 (57765) 1479326518 mtime(/var/lib/mailman/lists/XY/config.pck) -> Check mtime (3) Nov 16 21:02:54 2016 (57765) 0 (self.__timestamp) -> self.__timestamp is not set -> Load-File (4) Nov 16 21:02:54 2016 (57765) 1479326574 (Time before Load of config.pck) -> Timestamp int(time.time()) before the loading of the pickle file. (5) Nov 16 21:02:55 2016 (57765) 1479326575 (Time after Loading unpickling File = self.__timestamp) -> Timestamp after the Loading of the pickle file. The unpickling needs some time due to large List with 200.000 subscribers The parsing needs 1 second, timestamps differ. (6) Nov 16 21:02:55 2016 (57765) Try-Loaded config file /var/lib/mailman/lists/neuerscheinungen/config.pck -> Reload/Check Pickle-File (7) Nov 16 21:02:55 2016 (57765) 1479326574 mtime(/var/lib/mailman/lists/XY/config.pck) -> Check mtime (file is older than self.__timestamp), but nervertheless changed after the Loading in (5) (8) Nov 16 21:02:55 2016 (57765) 1479326575 SelfTimestamp -> Wrong Data saved -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/266464 Title: Subscriber "disappears" after subscription To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/266464/+subscriptions

1 0