Mailman 3 April 2012 - Mailman-coders

[Bug 975700] [NEW] On password change, trigger an event
by Barry Warsaw Sept. 8, 2012

Sept. 8, 2012

Public bug reported: When a user changes her password (e.g. via the email API), a zope.event should be triggered. This could be used to inform Postorius of the event. ** Affects: mailman Importance: High Status: Confirmed ** Tags: easy 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/975700 Title: On password change, trigger an event To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/975700/+subscriptions

1 2

[Bug 987563] [NEW] List-Post should be NO when posting is not allowed
by Barry Warsaw Sept. 8, 2012

Sept. 8, 2012

Public bug reported: >From RFC 2369: 3.4. List-Post The List-Post field describes the method for posting to the list. This is typically the address of the list, but MAY be a moderator, or potentially some other form of submission. For the special case of a list that does not allow posting (e.g., an announcements list), the List-Post field may contain the special value "NO". Mailman currently prevents adding the List-Post header for announce-only lists. Instead it should include it with the value of NO. ** Affects: mailman Importance: High Status: Confirmed ** Tags: easy 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/987563 Title: List-Post should be NO when posting is not allowed To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/987563/+subscriptions

1 2

[Bug 953497] [NEW] Unused variable in loop
by Andrea Crotti Sept. 8, 2012

Sept. 8, 2012

Public bug reported: in mailman/src/mailman/config/config.py the property header_matches for match in matches: yield (matches.header, matches.pattern, matches.chain) has a probable typo in the loop, and the variablel looping over is not used. ** Affects: mailman Importance: Undecided Status: New ** 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/953497 Title: Unused variable in loop To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/953497/+subscriptions

2 5

[Bug 963612] [NEW] ArchiveRunner has Pipermail artifacts
by Barry Warsaw Sept. 8, 2012

Sept. 8, 2012

Public bug reported: When the original message has a Date header, ArchiveRunner._dispose() will check to see if the date should be trusted or clobbered. This code still references the out of date [archiver.pipermail]clobber_date_policy value. The config var needs to be moved or renamed and the functionality re-implemented (and tested!). For now, I'm going to disable this bit of code but it should be re-addressed for beta2. ** Affects: mailman Importance: Medium Status: Confirmed ** 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/963612 Title: ArchiveRunner has Pipermail artifacts To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/963612/+subscriptions

1 2

[Bug 967409] [NEW] NewsRunner needs to be ported to Mailman 3
by Barry Warsaw Sept. 8, 2012

Sept. 8, 2012

Public bug reported: In src/mailman/runners/news.py, prepare_message() is ported to mm3 and tested, however ArchiveRunner is not. We also need some unittests, and this probably means that we'll pull in mock as a test dependency. It beats requiring a real NNTP server. ** Affects: mailman Importance: Undecided 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/967409 Title: NewsRunner needs to be ported to Mailman 3 To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/967409/+subscriptions

1 3

[Bug 887610] [NEW] RFC 1153 digests should not work around VM bug
by Barry Warsaw Sept. 8, 2012

Sept. 8, 2012

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 987020] [NEW] remove mail-archive.dev from configs
by Jeff Breidenbach Sept. 6, 2012

Sept. 6, 2012

Public bug reported: The URL mail-archive.dev is in the mailman code. Time to use the real thing. ** Affects: mailman Importance: Undecided Status: New ** Tags: mailman3 ** Tags added: 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/987020 Title: remove mail-archive.dev from configs To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/987020/+subscriptions

2 1

[Bug 899344] [NEW] Ability to set nomail on initial subscription
by Josh Triplett Sept. 4, 2012

Sept. 4, 2012

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 Aug. 31, 2012

Aug. 31, 2012

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 984765] [NEW] MM3: Expected unicode, found <type 'datetime.datetime'>:
by Bernhard Schmidt Aug. 19, 2012

Aug. 19, 2012

Public bug reported: Mailman 3.0.0b1+ (hg checkout of two days ago) throws the following error in the log Apr 18 12:53:57 2012 (23857) Uncaught runner exception: Expected unicode, found <type 'datetime.datetime'>: datetime.datetime(2012, 4, 18, 10, 53, 56, 403336) Apr 18 12:53:58 2012 (23857) Traceback (most recent call last): File "/usr/local/mailman/src/mailman/core/runner.py", line 138, in _one_iteration self._process_one_file(msg, msgdata) File "/usr/local/mailman/src/mailman/core/runner.py", line 220, in _process_one_file keepqueued = self._dispose(mlist, msg, msgdata) File "/usr/local/mailman/src/mailman/runners/incoming.py", line 67, in _dispose process(mlist, msg, msgdata, start_chain) File "/usr/local/mailman/src/mailman/core/chains.py", line 90, in process link.function(mlist, msg, msgdata) File "/usr/local/mailman/src/mailman/chains/hold.py", line 146, in _process request_id = hold_message(mlist, msg, msgdata, None) File "/usr/local/mailman/src/mailman/app/moderator.py", line 105, in hold_message RequestType.held_message, message_id, msgdata) File "/usr/local/mailman/src/mailman/model/requests.py", line 87, in hold_request token = getUtility(IPendings).add(pendable, timedelta(days=5000)) File "/usr/local/mailman/src/mailman/model/pending.py", line 130, in add keyval = PendedKeyValue(key=key, value=value) File "/usr/local/mailman/src/mailman/model/pending.py", line 54, in __init__ self.value = value File "/usr/lib/python2.7/dist-packages/storm/properties.py", line 67, in __set__ obj_info.variables[column].set(value) File "/usr/lib/python2.7/dist-packages/storm/variables.py", line 396, in parse_set % (type(value), value)) TypeError: Expected unicode, found <type 'datetime.datetime'>: datetime.datetime(2012, 4, 18, 10, 53, 56, 403336) Apr 18 12:53:58 2012 (23857) SHUNTING: 1334746438.043432+d81b75cc8924fd572477ebc0358bde18bf755fd9 ** 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/984765 Title: MM3: Expected unicode, found <type 'datetime.datetime'>: To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/984765/+subscriptions

2 2