Mailman 3 December 2011 - Mailman-coders

[Bug 886296] [NEW] Improve DSN handling for google 'inactive' accounts
by Kevin Fenzi 30 May '13

30 May '13

Public bug reported: The DSN bouncer handler can't seem to parse out when a bounce is generated due to an inactive google account. See attached bounce file for example. ** 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/886296 Title: Improve DSN handling for google 'inactive' accounts To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/886296/+subscriptions

3 8

[Bug 887610] [NEW] RFC 1153 digests should not work around VM bug
by Barry Warsaw 08 Sep '12

08 Sep '12

Public bug reported: In RFC1153Digester.finish(), we have this comment: # This is not strictly conformant RFC 1153. The trailer is only # supposed to contain two lines, i.e. the "End of ... Digest" line # and the row of asterisks. If this screws up MUAs, the solution # is to add the footer as the last message in the RFC 1153 digest. # I just hate the way that VM does that and I think it's confusing # to users, so don't do it unless there's a clamor. It is bogus that Mailman works around VM this way, so the code should be fixed to fully conform to RFC 1153. While this bug report is specifically targeted to Mailman 3, it also affects MM2.1, but I'll let Mark decide the priority of that bugtask. ** Affects: mailman Importance: Medium Status: Triaged ** Tags: mailman3 -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/887610 Title: RFC 1153 digests should not work around VM bug To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/887610/+subscriptions

3 8

[Bug 899344] [NEW] Ability to set nomail on initial subscription
by Josh Triplett 04 Sep '12

04 Sep '12

Public bug reported: I frequently find myself subscribing to a list for the sole purpose of ensuring I can post to that list, since it only allows posting from members. I often read those (high-volume) lists via the archives only, as well as threads that CC me. Thus, I want to set the nomail flag. Often I end up doing so for multiple subscriptions to the same list with a few different email addresses. Currently, the process for doing that looks something like this: Type in my name and email address, hit subscribe, wait for confirmation mail, confirm subscription, wait for subscription confirmation mail, go back to web form, copy/paste password, log in, check nomail, delete the handful of unwanted emails that arrived in the meantime. Repeat for every list I want to subscribe to, and every email address I want to post from. I'd like to have a way to set the "nomail" flag right from the subscription form. That would simplify the process significantly; I'd still have to confirm the subscription, but I wouldn't need to bother logging in and setting the flag, and I wouldn't receive unwanted emails from high-volume lists. ** 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/899344 Title: Ability to set nomail on initial subscription To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/899344/+subscriptions

2 2

[Bug 736849] [NEW] Sender header change to improve Outlook
by Joseph Brennan 31 Aug '12

31 Aug '12

Public bug reported: FAQ 2.3 describes problems with Outlook's ugly display of Sender "on behalf of" From, giving the example as "From listname- bounces(a)mailman.server.com On behalf of fred(a)poster.domain.com". But Outlook prefers to show the real name and hide the Internet address, when a real name is present. Most commonly the From would be "From: Fred Example <fred(a)poster.domain.com>" and as a result Outlook would display "From listname-bounces(a)mailman.server.com On behalf of Fred Example". If Mailman wrote the Sender header with a real name Outlook would show the name there too. For example, if the list name (local part) were inserted, thus "Sender: listname <listname-bounces(a)mailman.server.com>", then Outlook would display "From listname on behalf of Fred Example" which is much better in appearance and still complies with using a Sender header. RFC 2822 allows Sender to contain a real name. sender = "Sender:" mailbox CRLF mailbox = name-addr / addr-spec name-addr = [display-name] angle-addr ** 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/736849 Title: Sender header change to improve Outlook

3 7

[Bug 815444] [NEW] typo in german invite.txt 'einzutragenn'
by Thijs Kinkhorst 16 Jun '12

16 Jun '12

Public bug reported: There is a misspelled word in the german translation file of the invitation text. Fix: sed -i 's/einzutragenn/einzutragen/' /usr/share/mailman/de/invite.txt ** Affects: mailman Importance: Undecided Status: New ** Affects: mailman (Debian) Importance: Unknown Status: Unknown ** Bug watch added: Debian Bug tracker #627429 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=627429 ** Also affects: mailman (Debian) via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=627429 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/815444 Title: typo in german invite.txt 'einzutragenn' To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/815444/+subscriptions

3 4

[Bug 500955] [NEW] Templates for AST use inconsistent DOCTYPE
by Matt Selsky 15 Jun '12

15 Jun '12

Public bug reported: Most of the templates use a DOCTYPE of HTML 4.01 Transitional, but the AST templates use HTML 3.2. The patch updates the DOCTYPES for the AST templates. ** Affects: mailman Importance: Undecided Status: New -- Templates for AST use inconsistent DOCTYPE https://bugs.launchpad.net/bugs/500955 You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman.

2 3

[Bug 500952] [NEW] Extra escape characters in DOCTYPE
by Matt Selsky 15 Jun '12

15 Jun '12

Public bug reported: The DOCTYPE header for 2 files in the sk templates contain extra escape characters around the quote marks. ** Affects: mailman Importance: Undecided Status: New -- Extra escape characters in DOCTYPE https://bugs.launchpad.net/bugs/500952 You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman.

2 3

[Bug 770581] [NEW] The list admin or moderator password can be compromised by sending in an Approved: header
by Mark Sapiro 15 Jun '12

15 Jun '12

Public bug reported: If posting to a list is secured by requiring an Approved: or X-Approved: header for a post to be accepted without moderation, the list admin or moderator password can be compromised by sending it in the headers of an email message. There should be a 'poster' password for this purpose only so the consequences of compromise would be less severe. ** Affects: mailman Importance: Wishlist 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/770581 Title: The list admin or moderator password can be compromised by sending in an Approved: header

1 2

[Bug 637652] [NEW] mailman should respect LDFLAGS
by Hanno Böck 15 Jun '12

15 Jun '12

Public bug reported: mailman Makefile should respect the LDFLAGS variable. See attached patch. ** Affects: mailman Importance: Undecided Status: New -- mailman should respect LDFLAGS https://bugs.launchpad.net/bugs/637652 You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman.

4 6

[Bug 901957] [NEW] Mailman.Mailbox.Mailbox.AppendMessage method can add null bytes to mailbox.
by Mark Sapiro 15 Jun '12

15 Jun '12

Public bug reported: The Mailman.Mailbox.Mailbox.AppendMessage method has an invalid seek to position the file to the end of the mailbox. It contains . # Seek to the last char of the mailbox . self.fp.seek(1, 2) This actually should be self.fp.seek(0, 2). There is no actual ill effect in Mailman itself from this bug as Mailman always opens mailbox files to be written to in 'a+' mode and seeks before writes are ignored for files opened in append mode, but if someone creates a process which opens a file in 'w+' mode and then uses the Mailman.Mailbox.Mailbox.AppendMessage method to add messages to it, each added message's UnixFrom is preceded by a null byte. ** Affects: mailman Importance: Low Assignee: Mark Sapiro (msapiro) Status: Confirmed -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/901957 Title: Mailman.Mailbox.Mailbox.AppendMessage method can add null bytes to mailbox. To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/901957/+subscriptions

1 2

Mailman-coders December 2011