Mailman 3 October 2014 - Mailman-coders

[Bug 1360616] [NEW] mailman: case-sensitivity issue in tarball for 2.18.1-1
by Thomas Klausner 30 Jan '15

30 Jan '15

Public bug reported: The tarball contains readme.sr, but the installation scripts check for the existence of README.sr. This test works on case-insensitive file systems but not on case-sensitive ones. Please rename it to README.sr so the behaviour is the same across file systems. ** 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/1360616 Title: mailman: case-sensitivity issue in tarball for 2.18.1-1 To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1360616/+subscriptions

3 4

[Bug 1331194] [NEW] French translation on main Mailman page
by Emmanuel Décarie 30 Jan '15

30 Jan '15

Public bug reported: Mailman version 2.1.15 On the main page of a list: /cgi-bin/mailman/listinfo/mylist.org the french translation is: "Vous recevrez un courriel de requête de confirmation, cela empêche que d'autres personnes vous abonnement impunément. " but should be: "Vous recevrez un courriel de requête de confirmation, cela empêche que d'autres personnes vous abonne impunément. " ** Affects: mailman Importance: Undecided Status: New ** Tags: french translation -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1331194 Title: French translation on main Mailman page To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1331194/+subscriptions

3 5

[Bug 1318025] [NEW] The DMARC mitigatation actions do not include a Reply-To: header in rare cases.
by Mark Sapiro 30 Jan '15

30 Jan '15

Public bug reported: If the incoming message contains no From: header or it's From: header can't be parsed into a display name and email address, the DMARC mitigation actions that try to put the From: address in Reply-To: fail to do so. In these cases and also in the non-compliant case where there are multiple From: addresses, just take the sender address from Mailman's get_sender() message method and use that in liu of the From address. ** 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/1318025 Title: The DMARC mitigatation actions do not include a Reply-To: header in rare cases. To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1318025/+subscriptions

2 4

[Bug 1372199] [NEW] in emails, unsubscribe links should not react to HTTP HEAD requests
by Stephane Martin 30 Jan '15

30 Jan '15

Public bug reported: Welcome emails from mailman include a URL to perform unsubscribing. ex: https://lists.schneier.com/cgi-bin/mailman/options/crypto- gram/XXX%40XXX?login-unsub=Unsubscribe If you perform a HTTP HEAD request on that URL, it triggers the unsubscribe process, and an unsubscribe confirmation email is sent to the user. This shouldnt happen: HTTP HEAD method is not HTTP GET. Its supposed to only return headers, not to trigger an action on web server. I have anti-malware software that checks every HTTP link in received emails. When such a link is found by antimalware, it does a HTTP HEAD request on the URL to check the mimetype (if mimetype show a windows executable, an alert is sent). But this HEAD request in understood by mailman as a *real* unsubscribe request, so mailman sends a confirmation to the actual user (who is lost). (Strictly speaking, the behaviour is wrong even with a HTTP GET request: GET should not trigger a webserver action too...) ** 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/1372199 Title: in emails, unsubscribe links should not react to HTTP HEAD requests To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1372199/+subscriptions

3 5

[Bug 1363278] [NEW] REMOVE_DKIM_HEADERS value 2 not reacted to
by Ian Johannesen 30 Jan '15

30 Jan '15

Public bug reported: When using the value 2 for REMOVE_DKIM_HEADERS in mm_cfg - it does not respond to it at all. After doing through the code, I've noticed that quite simply someone forgot to add this to the code itself. I've attached a patch for this, as I needed to remove ALL DKIM headers for all my lists. ** Affects: mailman Importance: Undecided Status: New ** Patch added: "mailman-2.1.18-1.allowdkimalwaysremove.patch" https://bugs.launchpad.net/bugs/1363278/+attachment/4190499/+files/mailman-… -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1363278 Title: REMOVE_DKIM_HEADERS value 2 not reacted to To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1363278/+subscriptions

3 4

[Bug 1327404] [NEW] Mailman's log files are world readable
by Mark Sapiro 30 Jan '15

30 Jan '15

Public bug reported: Mailman creates log files with permissions -rw-rw-r--. This allows possibly untrusted local users to read those logs and possibly find sensitive information therein. The same is true of lists/LISTNAME/request.pck files. ** Affects: mailman Importance: Medium 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/1327404 Title: Mailman's log files are world readable To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1327404/+subscriptions

2 4

[Bug 1334450] [NEW] If a message is held for header_filter_rules and subsequently approved, dmarc_moderation_action is bypassed.
by Mark Sapiro 30 Jan '15

30 Jan '15

Public bug reported: Messages which are pre-approved with an Approved: header or held by a pipeline handler earlier than Moderate and accepted by a moderator will bypass the dmarc_moderation_action test and applicable action. Clearly Munge From or Wrap Message actions should be done in this case. What to do in a case of a dmarc_moderation_action of Reject or Discard is not so clear, but either they should be honored or at least the Wrap Message action should be applied. Given that a moderator likely approved the message based on content without considering DMARC, probably Reject and Discard actions should be honored. ** Affects: mailman Importance: High 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/1334450 Title: If a message is held for header_filter_rules and subsequently approved, dmarc_moderation_action is bypassed. To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1334450/+subscriptions

3 5

[Bug 1324541] [NEW] If the dnspython package is not available and dmarc_moderation_action is not accept, nothing is logged.
by Mark Sapiro 30 Jan '15

30 Jan '15

Public bug reported: dmarc_moderation_action other than accept relies on DNS lookups via the dnspython package to check DMARC policy of the From: domain, but if the package is not available, the check silently returns no DMARC policy. It should at least log the fact that the package isn't there. ** Affects: mailman Importance: High 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/1324541 Title: If the dnspython package is not available and dmarc_moderation_action is not accept, nothing is logged. To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1324541/+subscriptions

2 3

[Merge] lp:~rajeevs1992/postorius/postorius into lp:postorius
by Rajeev S 10 Jan '15

10 Jan '15

Rajeev S has proposed merging lp:~rajeevs1992/postorius/postorius into lp:postorius. Requested reviews: Mailman Coders (mailman-coders) For more details, see: https://code.launchpad.net/~rajeevs1992/postorius/postorius/+merge/207826 Added a file upload feature to add Mass subscriptions.Also changed email validator to django builtin validator.(DRY) -- https://code.launchpad.net/~rajeevs1992/postorius/postorius/+merge/207826 Your team Mailman Coders is requested to review the proposed merge of lp:~rajeevs1992/postorius/postorius into lp:postorius.

2 2

[Bug 1158721] [NEW] Emails without a text/plain part crash the Approved rule
by Aurélien Bompard 30 Dec '14

30 Dec '14

Public bug reported: If an email has no plain text part, the Approved rule will crash with the following message: AttributeError: 'NoneType' object has no attribute 'get_payload' The attached patch fixes the bug and adds a unit test for it. It's been generated from the current bzr branch. ** Affects: mailman Importance: Undecided Status: New ** Patch added: "mailman-notextpart.patch" https://bugs.launchpad.net/bugs/1158721/+attachment/3590081/+files/mailman-… -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1158721 Title: Emails without a text/plain part crash the Approved rule To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1158721/+subscriptions

2 5