Mailman 3 November 2012 - Mailman-coders

[Bug 975692] [NEW] Allow style assignments when creating a list through REST
by Barry Warsaw Dec. 31, 2012

Dec. 31, 2012

Public bug reported: You should be able to query the available list styles through the REST API, and choose an available style when creating the mailing list through REST. ** Affects: mailman Importance: Low Status: Confirmed ** Tags: api easy mailman3 ** Tags removed: rest ** Tags added: api -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/975692 Title: Allow style assignments when creating a list through REST To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/975692/+subscriptions

1 4

[Merge] lp:~sunu0000/postorius/newuser_hint into lp:postorius
by Tarashish Mishra Dec. 15, 2012

Dec. 15, 2012

Tarashish Mishra has proposed merging lp:~sunu0000/postorius/newuser_hint into lp:postorius. Requested reviews: Terri (terriko) Related bugs: Bug #1062856 in Postorius: "It is not clear how to log in if you do not already have an account." https://bugs.launchpad.net/postorius/+bug/1062856 For more details, see: https://code.launchpad.net/~sunu0000/postorius/newuser_hint/+merge/132263 Added hint for new users to sign in. -- https://code.launchpad.net/~sunu0000/postorius/newuser_hint/+merge/132263 Your team Mailman Coders is subscribed to branch lp:postorius.

3 2

[Bug 1077908] [NEW] MailList configuration race condition between qrunners
by Jan Kaluza Nov. 15, 2012

Nov. 15, 2012

Public bug reported: Hi, If two qrunner processes access list configuration file in the same second, second qrunner proces does not reload the configuration file, because it thinks that it has not changed. The decision is made according to config file's modification time, which is always in seconds (not in miliseconds) on older systems. This breaks mlist.post_id incrementation if the first process is IncomingRunner and second process ArchRunner and leads to situation where two emails have the same sequence number. The flow is following (everything happens in the same second): AR (ArchRunner) loads config file with post_id=1 AR saves config file with post_id=1 IR (IncomingRunner) loads config file with post_id=1 IR increments post_id and saves config file with post_id=2 AR loads config file, but mlist.__timestamp == mtime, so it thinks it has the latest config file AR uses post_id=1 (instead of post_id=2) AR saves config file with post_id=1 (the bug happens - post_id=2 is replaced with post_id=1 in config file) Second problem is that during the GENERAL_PIPELINE, in some cases the lock file is unlocked and next mlist.Save() fails. The patch checks for this case and try to Lock() the mailing list again. ** 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/1077908 Title: MailList configuration race condition between qrunners To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1077908/+subscriptions

2 11

[Bug 1074542] [NEW] ban_list: addresses which begin with caret ("^")
by /dev/rob0 Nov. 3, 2012

Nov. 3, 2012

Public bug reported: This is very minor, but probably deserves a note in the documentation. In the ban_list (and probably other places) a regular expression requires the leading end anchor "^". Thus one without that as first character would be interpreted as an email address. With the "^", the entry will be read as a regular expression. How would you handle an email address where the localpart begins with "^"? Granted, this is a very rare thing, but it is possible. Escape it with backslash? It could be done as a regular expression also, but that fact might be worth noting. Thanks. FYI, I discussed this with Terri in IRC, and she suggested filing a bug. ** 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/1074542 Title: ban_list: addresses which begin with caret ("^") To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1074542/+subscriptions

2 1

[Branch ~mailman-coders/mailman.client/trunk] Rev 37: added _User.delete() method
by noreply＠launchpad.net Nov. 2, 2012

Nov. 2, 2012

Merge authors: Florian Fuchs (flo-fuchs) ------------------------------------------------------------ revno: 37 [merge] committer: Florian Fuchs <flo.fuchs(a)gmail.com> branch nick: mailman.client timestamp: Fri 2012-11-02 15:51:30 +0100 message: added _User.delete() method modified: src/mailmanclient/_client.py -- lp:mailman.client https://code.launchpad.net/~mailman-coders/mailman.client/trunk Your team Mailman Coders is subscribed to branch lp:mailman.client. To unsubscribe from this branch go to https://code.launchpad.net/~mailman-coders/mailman.client/trunk/+edit-subsc…

1 0

[Bug 558240] Re: Make password mailing RFC 3834 compliant
by Barry Warsaw Nov. 2, 2012

Nov. 2, 2012

** Also affects: mailman/2.1 Importance: Undecided Status: New ** Also affects: mailman/2.2 Importance: Undecided Status: New ** Also affects: mailman/3.0 Importance: Medium Assignee: Mark Sapiro (msapiro) Status: Fix Committed ** Changed in: mailman/2.1 Milestone: None => 2.1.16 ** Changed in: mailman/2.1 Assignee: (unassigned) => Mark Sapiro (msapiro) ** Changed in: mailman/2.1 Importance: Undecided => Medium ** Changed in: mailman/2.1 Status: New => Fix Committed ** Changed in: mailman/2.2 Assignee: (unassigned) => Mark Sapiro (msapiro) ** Changed in: mailman/2.2 Importance: Undecided => Medium ** Changed in: mailman/3.0 Status: Fix Committed => New ** Changed in: mailman/3.0 Importance: Medium => Low ** Changed in: mailman/3.0 Assignee: Mark Sapiro (msapiro) => Barry Warsaw (barry) ** Changed in: mailman/3.0 Milestone: 2.1.16 => None ** Changed in: mailman/2.2 Status: New => Fix Committed ** No longer affects: mailman/3.0 -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/558240 Title: Make password mailing RFC 3834 compliant To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/558240/+subscriptions

2 1

[Bug 558240] Re: Make password mailing RFC 3834 compliant
by Mark Sapiro Nov. 2, 2012

Nov. 2, 2012

I fixed this as suggested in the patch attached to comment #1. It should really be addressed in the send() method of the Message.UserNotification() class, except that it may not be possible to correctly decide there whether the appropriate value is auto-generated vs. auto-replied, thus it may require modifying all the callers anyway. Invitations and (un)subscription confirmations have already been fixed per LP:265831. ** Changed in: mailman Importance: Undecided => Medium ** Changed in: mailman Status: New => Fix Committed ** Changed in: mailman Milestone: None => 2.1.16 ** Changed in: mailman Assignee: (unassigned) => Mark Sapiro (msapiro) -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/558240 Title: Make password mailing RFC 3834 compliant To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/558240/+subscriptions

1 0

[Bug 558240] Re: Make password mailing RFC 3834 compliant
by Launchpad Bug Tracker Nov. 2, 2012

Nov. 2, 2012

** Branch linked: lp:mailman/2.2 ** Branch linked: lp:mailman/2.1 -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/558240 Title: Make password mailing RFC 3834 compliant To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/558240/+subscriptions

1 0