Mailman 3 November 2014 - Mailman-coders

[Bug 1382150] [NEW] feature request: add option for list owner to receive copies of all bounce mail
by Stephen Mats Mats Jan. 30, 2015

Jan. 30, 2015

Public bug reported: Here at U of Wa we've had one request to add the feature to Mailman. As a list owner I want to know about each and every bounce my list gets. thanks, steve (sorry if this is the wrong place for feature requests, I didn't see anywere else) ** 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/1382150 Title: feature request: add option for list owner to receive copies of all bounce mail To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1382150/+subscriptions

3 4

[Bug 1397170] [NEW] admin CGI throws UnicodeDecodeError when certain list text attrubutes are unicodes
by Mark Sapiro Jan. 30, 2015

Jan. 30, 2015

Public bug reported: It is possible for the text values of various list attributes such as info, welcome_msg, msg_footer and topics names and descriptions to be unicodes. One way this may happen is if they are set via bin/config_list from an input file with a # -*- coding: utf-8 -*- line. There may be other ways. It is not completely clear exactly how this happens. If these attributes are unicodes, attempts to display them in the lists admin GUI result in UnicodeDecodeError exceptions. This will be fixed to avoid the exception by displaying the representation of the attribute rather than the attribute in cases of text attributes whose value is not a string. ** 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/1397170 Title: admin CGI throws UnicodeDecodeError when certain list text attrubutes are unicodes To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1397170/+subscriptions

2 4

[Bug 1390653] [NEW] If a user is unsubscribed after retrieving her options page and before submitting an unsub, an uncaught exception is thrown
by Mark Sapiro Jan. 30, 2015

Jan. 30, 2015

Public bug reported: Scenario 1: User logs in and retrieve her options page. Another process unsubscribes the user. User submits an unsub from the options page. NotAMemberError is thrown and not caught. Scenario 2 User logs in and retrieve her options page. User unsubscribes. User goes back a page in her browser and unsubscribes again. NotAMemberError is thrown and not caught. The options CGI should catch and ignore NotAMemberError. ** 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/1390653 Title: If a user is unsubscribed after retrieving her options page and before submitting an unsub, an uncaught exception is thrown To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1390653/+subscriptions

2 3

[Bug 1379813] [NEW] Documentation error
by Lindsay Jan. 30, 2015

Jan. 30, 2015

Public bug reported: Section 7 of the Mailman Installation Manual makes reference to the HOME_DIR or MAILMAN_DIR variables. These are not to be found in Defaults.py, nor in mm_cfg.py as installed (v2.1.18). Variations on the PREFIX variable contain this same information. Perhaps it would be good to qualify the statement in the Installation Manual, or change it to reference the PREFIX variable. ** 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/1379813 Title: Documentation error To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1379813/+subscriptions

3 6

[Bug 1371678] [NEW] The list poster password should be accepted in an Urgent: header.
by Mark Sapiro Jan. 30, 2015

Jan. 30, 2015

Public bug reported: The summary says it all. ** 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/1371678 Title: The list poster password should be accepted in an Urgent: header. To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1371678/+subscriptions

2 3

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

Jan. 30, 2015

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 Jan. 30, 2015

Jan. 30, 2015

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 Jan. 30, 2015

Jan. 30, 2015

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 1388614] [NEW] archive problem when an email got not subject
by Bersam Karbasion Jan. 30, 2015

Jan. 30, 2015

Public bug reported: Hey everybody, In one mailing list that use Mailman software, somebody send an empty email subject to mailing list. and this conversation completed without any problem, but seems links in archive pages got problem because that dude didn't use a subject for his email. you can see it here: http://lists.isfahanlug.org/pipermail/supervisors/2014-November/thread.html As i can see they use Mailman2 "version 2.1.15" on debian server. ** Affects: mailman Importance: Undecided Status: New ** Tags: archive mailman2 subject -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1388614 Title: archive problem when an email got not subject To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1388614/+subscriptions

3 7

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

Jan. 30, 2015

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