Mailman-coders January 2016

mailman-coders@python.org

8 participants
49 discussions

[Bug 1496620] [NEW] Mailman sometimes fails to remove redundant Re: when prefixing subject.
by Mark Sapiro 03 Feb '16

03 Feb '16

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 03 Feb '16

03 Feb '16

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

[Bug 1486263] [NEW] cron/gate_news doesn't catch EOFError on opening the newsgroup.
by Mark Sapiro 03 Feb '16

03 Feb '16

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/1486263 Title: cron/gate_news doesn't catch EOFError on opening the newsgroup. To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1486263/+subscriptions

2 3

[Bug 1476298] [NEW] User-options available for digest despite this option unavailable
by Mla 03 Feb '16

03 Feb '16

Public bug reported: When message digests are disabled by the administrator ("Edit_digestable") the user option page for turning digests on is still available. It should be removed when it's no longer available to avoid any confusion. ** 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/1476298 Title: User-options available for digest despite this option unavailable To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1476298/+subscriptions

3 4

[Bug 1450826] [NEW] DMARC entries in the vette log don't include the list name.
by Mark Sapiro 03 Feb '16

03 Feb '16

Public bug reported: The list name should be included along with the result of the DMARC lookup in the vette log entry from checking dmarc_moderation_action. ** 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/1450826 Title: DMARC entries in the vette log don't include the list name. To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1450826/+subscriptions

2 3

[Bug 1532504] [NEW] Galician language templates are encoded in the wrong Character set.
by Mark Sapiro 03 Feb '16

03 Feb '16

Public bug reported: Mailman's Character set for Galician is utf-8 but many templates are iso-8859-1 encoded. The html templates should all use html entities where possible and everything should be properly utf-8 encoded. ** 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/1532504 Title: Galician language templates are encoded in the wrong Character set. To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1532504/+subscriptions

2 3

[Bug 1525733] [NEW] Banned subscription log entries should include the source.
by Mark Sapiro 03 Feb '16

03 Feb '16

Public bug reported: Attempts to subscribe a banned address to a list log the attempt to the vette log. The log message should include the source email address or IP address of the request. ** 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/1525733 Title: Banned subscription log entries should include the source. To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1525733/+subscriptions

2 3

[Bug 1519062] [NEW] Unshunting a shunted message can skip the original shunting handler.
by Mark Sapiro 03 Feb '16

03 Feb '16

Public bug reported: At least sometimes, when a message is shunted because an exception is thrown in IncomingRunner the pipeline saved in the msgdata of the shunted message can start with the handler following the one being handled when the exception is thrown. This has been observed when Moderate attempted to reject a message and raised Errors.RejectMessage. IncomingRunner then called BounceMessage to send a reject notice and BounceMessage threw an IOError exception. The message was shunted with a pipeline starting with the handler following Moderate which had already been successfully popped from the pipeline. When the message was unshunted, Moderate was skipped and the message which should have been rejected was delivered to the list. ** 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/1519062 Title: Unshunting a shunted message can skip the original shunting handler. To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1519062/+subscriptions

2 3

[Bug 1518084] [NEW] documentation: reply-to munging "useful" link now points to a spam domain
by Sander 03 Feb '16

03 Feb '16

Public bug reported: http://bazaar.launchpad.net/~mailman-coders/mailman/2.1/annotate/head:/doc/… line 86 includes a link, "Reply-To Munging Considered Useful", pointing to metasystema.org/essays/reply-to-useful.mhtml archive.org shows this document disappeared sometime between late 2013 and mid-2014, and if it's currently visited, your browser gets redirected through a large number of what I can only assume to be spam domains. I don't know if there's any policy for what to do with dead links in documentation, but a faithful reproduction of the document seems to live on http://marc.merlins.org/netrants/reply-to-useful.html (unchanged for the last 11 years based on a swift visual inspection via archive.org), so updating the link to point there seems to make sense. ** 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/1518084 Title: documentation: reply-to munging "useful" link now points to a spam domain To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1518084/+subscriptions

2 3

[Bug 1512866] [NEW] Some news servers reject some posts from the mail<->news gateway
by Mark Sapiro 03 Feb '16

03 Feb '16

Public bug reported: NewsRunner, when gating a list post to usenet, will append the appropriate usenet group name to any existing Newsgroups: header in the post that doesn't already contain the name. If the existing names in the header are a group or groups that don't exist on the gated news server, at least one server has been observed to reject the post. In some cases with the python-list(a)python.org list, we have seen 441 No valid newsgroups in "gmane.comp.python.general, comp.lang.python" This would actually seem to be a bug in the news server, but I will try prepending rather than appending the group name to see if that helps. ** 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/1512866 Title: Some news servers reject some posts from the mail<->news gateway To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1512866/+subscriptions

2 4

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

Mailman-coders January 2016