Mailman 3 February 2016 - Mailman-coders

[Merge] lp:~rajeevs1992/mailman.client/mailmancli into lp:mailman.client
by Rajeev S Feb. 3, 2016

Feb. 3, 2016

Rajeev S has proposed merging lp:~rajeevs1992/mailman.client/mailmancli into lp:mailman.client. Requested reviews: Mailman Coders (mailman-coders) For more details, see: https://code.launchpad.net/~rajeevs1992/mailman.client/mailmancli/+merge/23… GSoC project "Mailman CLI" The branch contains the Mailman CLI shell as well as the command line tools built as a part of the GSoC 2014, Under the mentors Stephen J Turnbull, Abhilash Raj and Barry Warsaw. -- https://code.launchpad.net/~rajeevs1992/mailman.client/mailmancli/+merge/23… Your team Mailman Coders is requested to review the proposed merge of lp:~rajeevs1992/mailman.client/mailmancli into lp:mailman.client.

1 3

[Bug 1491187] [NEW] mailmanctl check_privs should check effective uid, not real uid
by Mark Sapiro Feb. 3, 2016

Feb. 3, 2016

Public bug reported: Situations can arise where mailmanctl is running with an effective uid of 'mailman' and a real uid of 'root'. Such a situation is if logrotate does 'su mailman mailman' to rotate mailman's logs and then invokes 'mailmanctl reopen' in a postrotate script. In this case, mailmanctl gets its real uid which is 'root' and then tries to do os.setgroups, but the effective uid is 'mailman' which doesn't have permission to set groups. ** 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/1491187 Title: mailmanctl check_privs should check effective uid, not real uid To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1491187/+subscriptions

2 2

[Bug 1526550] [NEW] Posts to a list with regular_exclude_lists can be delivered to excluded list members.
by Mark Sapiro Feb. 3, 2016

Feb. 3, 2016

Public bug reported: If a post is addressed to multiple lists, say list1 and list2, and list2 is in list1's regular_exclude_lists, and list1's regular_exclude_ignore is Yes, and the poster is not a member of list2 but the post will be accepted by list2 because of list2's equivalent_domains setting, the regular members of list1 and list2 will receive the post from both lists. For a more concrete example, consider a post to list1 and list2 from user(a)mac.com. user(a)mac.com is not a member of list2, but user(a)me.com is a member of list2 and list2's equivalent_domains includes "mac.com,me.com", In this case, if list2 is in list1's regular_exclude_lists, and list1's regular_exclude_ignore is Yes, regular members of both lists will receive the post from both lists and not be excluded from receiving the post from list1 ** 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/1526550 Title: Posts to a list with regular_exclude_lists can be delivered to excluded list members. To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1526550/+subscriptions

2 3

[Bug 1523273] [NEW] Posting to the options page for a non-member can throw an uncaught exception
by Mark Sapiro Feb. 3, 2016

Feb. 3, 2016

Public bug reported: Various post data or query fragments sent to the user options CGI for a non-member can throw NotAMemberError. This can occur for example if a user's options page has been retrieved and the user is asynchronously unsubscribed and then the form is posted. ** 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/1523273 Title: Posting to the options page for a non-member can throw an uncaught exception To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1523273/+subscriptions

2 3

[Bug 1507241] [NEW] Bad regexps in *_these_nonmembers, subscribe_auto_approval and ban_list should be logged
by Mark Sapiro Feb. 3, 2016

Feb. 3, 2016

Public bug reported: The list attributes *_these_nonmembers, subscribe_auto_approval and ban_list accept lists of email addresses and regexps (beginning with '^') matching email addresses. Currently, if the regexp is invalid, it is silently ignored. The GUI does not accept invalid regexp entries, but there are other ways they could be introduced. An invalid regexp should at least be logged. ** 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/1507241 Title: Bad regexps in *_these_nonmembers, subscribe_auto_approval and ban_list should be logged To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1507241/+subscriptions

2 3

[Bug 1505878] [NEW] Mailman can cause extraneous tabs to be displayed in Subject: headers
by Mark Sapiro Feb. 3, 2016

Feb. 3, 2016

Public bug reported: The genesis of this problem is that the header folding and unfolding algorithms specified in RFC822 could introduce extraneous white space in headers which have been folded and unfolded. RFC822 says when folding, "a CRLF immediately followed by AT LEAST one LWSP-char" may be inserted where linear-white-space is allowed, and unfolding "is accomplished by regarding CRLF immediately followed by a LWSP-char as equivalent to the LWSP-char." Thus, one can insert "AT LEAST one LWSP-char" when folding but not remove any when unfolding. The later RFCs 2822 and 5322 clarify the situation by specifying folding as inserting CRLF preceding existing white-space and unfolding as removing any CRLF which is immediately followed by white-space. Various MUAs and supporting libraries including the Python 2 email library used by Mailman still follow the RFC822 method of folding and can fold by inserting CRLF followed by TAB and the TAB then doesn't get removed in unfolding. There is actually control in the Python email library to use TAB or SPACE, and Mailman attempts to determine what character has been used and uses that, but in the case where a Subject: header is not folded but becomes long enough to be folded because of the insertion of a subject_prefix for example, Mailman defaults to a TAB which doesn't get removed in unfolding. The situation will never be perfect as long as there are MUAs that fold per RFC822 and MUAs that attempt to compensate by removing some white- space following CRLF, but it will be improved somewhat by defaulting to folding with SPACE rather than TAB. ** 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/1505878 Title: Mailman can cause extraneous tabs to be displayed in Subject: headers To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1505878/+subscriptions

2 3

[Bug 1503422] [NEW] Mailman's provided init.d script may not work with systemctl.
by Mark Sapiro Feb. 3, 2016

Feb. 3, 2016

Public bug reported: The provided misc/mailman.in script contains the line # pidfile: @prefix@/data/master-qrunner.pid While this is a comment, it may be used by chkconfig, etc. and it's wrong. It should be # pidfile: @VAR_PREFIX@/data/master-qrunner.pid ** Affects: mailman Importance: Low 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/1503422 Title: Mailman's provided init.d script may not work with systemctl. To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1503422/+subscriptions

2 3

[Bug 1496632] [NEW] visiting the user options page with crafted post data or query fragments can produce "we hit a bug"
by Mark Sapiro Feb. 3, 2016

Feb. 3, 2016

Public bug reported: If one visits the user options page with a hand crafted query fragment or post data containing for example language=en&email=&email=test&password=&login-remind=Remind the fact that the options CGI sees 'email' as a list rather than a string throws an exception in Utils.websafe(). We will defend against this by testing in Utils.websafe() for a sequence argument and if so, returning only websafe of the first element. ** Affects: mailman Importance: Low Assignee: Mark Sapiro (msapiro) 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/1496632 Title: visiting the user options page with crafted post data or query fragments can produce "we hit a bug" To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1496632/+subscriptions

2 3

[Bug 1496620] [NEW] Mailman sometimes fails to remove redundant Re: when prefixing subject.
by Mark Sapiro Feb. 3, 2016

Feb. 3, 2016

Public bug reported: When processing the subject_prefix for list mail, Mailman attempts to remove all the redundant Re: bits in the Subject. Under some circumstances this can fail resulting in messages being delivered to the list with subjects like, e.g., Subject: [prefix] Re: Re: Re: Re: some message subject Of course, it was a user's MUA that created a subject with multiple Re: to begin with, but it may not have been so blatant before prefixing manipulations. ** Affects: mailman Importance: Low Assignee: Mark Sapiro (msapiro) 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/1496620 Title: Mailman sometimes fails to remove redundant Re: when prefixing subject. To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1496620/+subscriptions

2 3

[Bug 1536816] [NEW] Mailman can create a non-ascii or improperly RFC 2047encoded From: header.
by Mark Sapiro Feb. 3, 2016

Feb. 3, 2016

Public bug reported: When creating the new From: header for a message with from_is_list or dmarc_moderation_action set to Munge From or Wrap Message, if the incoming From: has no display name so Mailman gets the display name from the poster's list member data, and that name contains non-ascii, Mailman puts the non-ascii display name in the new From: header and subsequent processing can see the non-ascii and attempt to RFC 2047 encode it, but do that improperly. ** Affects: mailman Importance: Medium Assignee: Mark Sapiro (msapiro) Status: Fix Committed ** Summary changed: - Mailman can create a non-ascii or improperly RFC 2047encoded From" header. + Mailman can create a non-ascii or improperly RFC 2047encoded From: header. -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1536816 Title: Mailman can create a non-ascii or improperly RFC 2047encoded From: header. To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1536816/+subscriptions

2 3