From 558240 at bugs.launchpad.net Fri Nov 2 04:22:49 2012 From: 558240 at bugs.launchpad.net (Launchpad Bug Tracker) Date: Fri, 02 Nov 2012 03:22:49 -0000 Subject: [Bug 558240] Re: Make password mailing RFC 3834 compliant References: <20100408090825.1687.22542.launchpad@loganberry.canonical.com> Message-ID: <20121102032253.7380.21713.launchpad@ackee.canonical.com> ** 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 From mark at msapiro.net Fri Nov 2 04:33:36 2012 From: mark at msapiro.net (Mark Sapiro) Date: Fri, 02 Nov 2012 03:33:36 -0000 Subject: [Bug 558240] Re: Make password mailing RFC 3834 compliant References: <20100408090825.1687.22542.launchpad@loganberry.canonical.com> Message-ID: <20121102033337.4847.56268.malone@gac.canonical.com> 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 From 558240 at bugs.launchpad.net Fri Nov 2 06:57:59 2012 From: 558240 at bugs.launchpad.net (Barry Warsaw) Date: Fri, 02 Nov 2012 05:57:59 -0000 Subject: [Bug 558240] Re: Make password mailing RFC 3834 compliant References: <20100408090825.1687.22542.launchpad@loganberry.canonical.com> Message-ID: <20121102055800.10205.31838.launchpad@wampee.canonical.com> ** 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 From 558240 at bugs.launchpad.net Fri Nov 2 12:52:44 2012 From: 558240 at bugs.launchpad.net (John M. Whitney) Date: Fri, 02 Nov 2012 11:52:44 -0000 Subject: [Bug 558240] Re: Make password mailing RFC 3834 compliant References: <20100408090825.1687.22542.launchpad@loganberry.canonical.com> <20121102055800.10205.31838.launchpad@wampee.canonical.com> Message-ID: unsubscribe On Fri, Nov 2, 2012 at 1:57 AM, Barry Warsaw <558240 at bugs.launchpad.net>wrote: > ** 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 subscribed to 3.0. > https://bugs.launchpad.net/bugs/558240 > > Title: > Make password mailing RFC 3834 compliant > > Status in GNU Mailman: > New > Status in GNU Mailman 2.1 series: > Fix Committed > Status in GNU Mailman 2.2 series: > Fix Committed > > Bug description: > RFC 3834 specifies that messages generated > automatically by periodic automatic jobs should contain > an Auto-Submitted header with a 'auto-generated' value; > a 1-line patch does this for the cron'ed month > membership reminder. > > This helps avoid loops and potential "sorcerers > apprentice mode" when hitting well mannered vaction > programs that recognize RFC 3834 headers. There is > probably more work to do in mailman related to this > RFC, as well. > > To manage notifications about this bug go to: > https://bugs.launchpad.net/mailman/+bug/558240/+subscriptions > -- 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 From 1074374 at bugs.launchpad.net Fri Nov 2 15:20:00 2012 From: 1074374 at bugs.launchpad.net (Florian Fuchs) Date: Fri, 02 Nov 2012 14:20:00 -0000 Subject: [Bug 1074374] [NEW] REST API: Problems with addresses and memberships after deleting a user. References: <20121102142001.26084.19542.malonedeb@chaenomeles.canonical.com> Message-ID: <20121102142001.26084.19542.malonedeb@chaenomeles.canonical.com> Public bug reported: Hi Barry, I ran into some trouble after deleting a user account via the rest API. Apparently the user's address records were kept, which lead to two problems: - Memberships cannot be retrieved via rest any more. - The deleted user cannot be created again using any of their previous addresses. Steps to reproduce: 1) Create a user through the REST API 2) Delete that user through the REST API 3) Repeat step 1) (possibly because a person wants to register again after leaving) => 500 status code is returned through the REST -- ExistingAddressError is raised. 4) Access /3.0/addresses => Result still contains the email address used in 1). 5) Access /3.0/members => 500 status code is returned As a workaround, I tried to delete all the user's addresses through the API, but doing that returned 405 (Method not allowed). Wouldn't it be best to delete all address/membership records from the db when a user record is deleted? Cheers Florian ** Affects: mailman Importance: Undecided Assignee: Barry Warsaw (barry) Status: New ** Tags: mailman3 rest-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/1074374 Title: REST API: Problems with addresses and memberships after deleting a user. To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1074374/+subscriptions From noreply at launchpad.net Fri Nov 2 15:53:11 2012 From: noreply at launchpad.net (noreply at launchpad.net) Date: Fri, 02 Nov 2012 14:53:11 -0000 Subject: [Branch ~mailman-coders/mailman.client/trunk] Rev 37: added _User.delete() method Message-ID: <20121102145311.19516.63292.launchpad@ackee.canonical.com> Merge authors: Florian Fuchs (flo-fuchs) ------------------------------------------------------------ revno: 37 [merge] committer: Florian Fuchs 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-subscription -------------- next part -------------- A non-text attachment was scrubbed... Name: revision-diff.txt Type: text/x-diff Size: 509 bytes Desc: not available URL: From rob0-lpad at nodns4.us Sat Nov 3 02:16:09 2012 From: rob0-lpad at nodns4.us (/dev/rob0) Date: Sat, 03 Nov 2012 01:16:09 -0000 Subject: [Bug 1074542] [NEW] ban_list: addresses which begin with caret ("^") References: <20121103011610.25947.84494.malonedeb@chaenomeles.canonical.com> Message-ID: <20121103011610.25947.84494.malonedeb@chaenomeles.canonical.com> 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 From mark at msapiro.net Sat Nov 3 02:54:59 2012 From: mark at msapiro.net (Mark Sapiro) Date: Sat, 03 Nov 2012 01:54:59 -0000 Subject: [Bug 1074542] Re: ban_list: addresses which begin with caret ("^") References: <20121103011610.25947.84494.malonedeb@chaenomeles.canonical.com> Message-ID: <20121103015500.19252.43449.malone@soybean.canonical.com> Assuming there actually is such an address, it could be represented as you suggest with a regexp that would match only the literal address. E.g. if the address were "^some.name at example.com", the regexp would be "^\^some\.name at example\.com$". Escaping the leading ^ with a backslash wouldn't work without changes to Mailman. Non-regexp matches on addresses are done by simple string comparison which would treat the backslash as any other character. I'm not convinced that this is a valid bug, but I'm marking it "Won't Fix" so it can serve as documentation of how to deal with such an address. ** Changed in: mailman Importance: Undecided => Low ** Changed in: mailman Status: New => Won't Fix -- 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 From 1074374 at bugs.launchpad.net Mon Nov 5 16:27:02 2012 From: 1074374 at bugs.launchpad.net (Barry Warsaw) Date: Mon, 05 Nov 2012 15:27:02 -0000 Subject: [Bug 1074374] Re: REST API: Problems with addresses and memberships after deleting a user. References: <20121102142001.26084.19542.malonedeb@chaenomeles.canonical.com> Message-ID: <20121105152704.6457.96212.launchpad@chaenomeles.canonical.com> ** Changed in: mailman Status: New => In Progress ** Changed in: mailman Importance: Undecided => High ** Changed in: mailman Milestone: None => 3.0.0b3 -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1074374 Title: REST API: Problems with addresses and memberships after deleting a user. To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1074374/+subscriptions From 1074374 at bugs.launchpad.net Mon Nov 5 17:02:13 2012 From: 1074374 at bugs.launchpad.net (Barry Warsaw) Date: Mon, 05 Nov 2012 16:02:13 -0000 Subject: [Bug 1074374] Re: REST API: Problems with addresses and memberships after deleting a user. References: <20121102142001.26084.19542.malonedeb@chaenomeles.canonical.com> Message-ID: <20121105160214.17852.66618.launchpad@soybean.canonical.com> ** Changed in: mailman Status: In Progress => 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/1074374 Title: REST API: Problems with addresses and memberships after deleting a user. To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1074374/+subscriptions From 1076152 at bugs.launchpad.net Wed Nov 7 22:47:40 2012 From: 1076152 at bugs.launchpad.net (Barry Warsaw) Date: Wed, 07 Nov 2012 21:47:40 -0000 Subject: [Bug 1076152] [NEW] Review RFC 6783 for any needed changes References: <20121107214740.30333.84052.malonedeb@gac.canonical.com> Message-ID: <20121107214740.30333.84052.malonedeb@gac.canonical.com> Public bug reported: http://www.rfc-editor.org/rfc/rfc6783.txt Mailing Lists and Non-ASCII Addresses This needs to be reviewed for relevance to Mailman 3, likely with separate bugs for any needed changes. ** Affects: mailman Importance: Low 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/1076152 Title: Review RFC 6783 for any needed changes To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1076152/+subscriptions From jkaluza at redhat.com Mon Nov 12 13:22:48 2012 From: jkaluza at redhat.com (Jan Kaluza) Date: Mon, 12 Nov 2012 12:22:48 -0000 Subject: [Bug 1077908] [NEW] MailList configuration race condition between qrunners References: <20121112122248.30565.17723.malonedeb@wampee.canonical.com> Message-ID: <20121112122248.30565.17723.malonedeb@wampee.canonical.com> 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 From jkaluza at redhat.com Mon Nov 12 13:41:30 2012 From: jkaluza at redhat.com (Jan Kaluza) Date: Mon, 12 Nov 2012 12:41:30 -0000 Subject: [Bug 1077908] Re: MailList configuration race condition between qrunners References: <20121112122248.30565.17723.malonedeb@wampee.canonical.com> Message-ID: <20121112124130.16689.37210.malone@chaenomeles.canonical.com> Hm, when thinking about it, my patch wasn't the best thing for the race- condition. It will load config file everytime now, I think. But I think you got the idea what's wrong there. -- 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 From jkaluza at redhat.com Mon Nov 12 13:24:02 2012 From: jkaluza at redhat.com (Jan Kaluza) Date: Mon, 12 Nov 2012 12:24:02 -0000 Subject: [Bug 1077908] Re: MailList configuration race condition between qrunners References: <20121112122248.30565.17723.malonedeb@wampee.canonical.com> Message-ID: <20121112122402.31690.22927.malone@soybean.canonical.com> ** Patch added: "mailman-lock-race.patch" https://bugs.launchpad.net/mailman/+bug/1077908/+attachment/3431197/+files/mailman-lock-race.patch -- 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 From mark at msapiro.net Tue Nov 13 06:27:22 2012 From: mark at msapiro.net (Mark Sapiro) Date: Tue, 13 Nov 2012 05:27:22 -0000 Subject: [Bug 1077908] Re: MailList configuration race condition between qrunners References: <20121112122248.30565.17723.malonedeb@wampee.canonical.com> Message-ID: <20121113052722.26872.3234.malone@gac.canonical.com> *** This bug is a duplicate of bug 266464 *** https://bugs.launchpad.net/bugs/266464 What mailman version are you running? I think this duplicates LP:266464 which was fixed in Mailman 2.1.15. Please confirm. ** Changed in: mailman Importance: Undecided => Medium ** Changed in: mailman Status: New => Fix Committed ** Changed in: mailman Milestone: None => 2.1.15 ** Changed in: mailman Assignee: (unassigned) => Mark Sapiro (msapiro) ** This bug has been marked a duplicate of bug 266464 Subscriber "disappears" after subscription -- 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 From mark at msapiro.net Tue Nov 13 06:36:27 2012 From: mark at msapiro.net (Mark Sapiro) Date: Tue, 13 Nov 2012 05:36:27 -0000 Subject: [Bug 1077908] Re: MailList configuration race condition between qrunners References: <20121112122248.30565.17723.malonedeb@wampee.canonical.com> Message-ID: <20121113053628.17152.35296.malone@chaenomeles.canonical.com> *** This bug is a duplicate of bug 266464 *** https://bugs.launchpad.net/bugs/266464 Regarding your second problem of the list being unlocked by a handler during processing of the pipeline (I assume you mean GLOBAL_PIPELINE, not GENERAL_PIPELINE), I have never seen a report of this. Can you say which handler or under what circumstance this happens? -- 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 From mark at msapiro.net Tue Nov 13 06:41:18 2012 From: mark at msapiro.net (Mark Sapiro) Date: Tue, 13 Nov 2012 05:41:18 -0000 Subject: [Bug 1077908] Re: MailList configuration race condition between qrunners References: <20121112122248.30565.17723.malonedeb@wampee.canonical.com> Message-ID: <20121113054118.32028.60.malone@soybean.canonical.com> *** This bug is a duplicate of bug 266464 *** https://bugs.launchpad.net/bugs/266464 Also see the post at and other posts linked therefrom. -- 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 From jkaluza at redhat.com Tue Nov 13 08:44:47 2012 From: jkaluza at redhat.com (Jan Kaluza) Date: Tue, 13 Nov 2012 07:44:47 -0000 Subject: [Bug 1077908] Re: MailList configuration race condition between qrunners References: <20121112122248.30565.17723.malonedeb@wampee.canonical.com> Message-ID: <20121113074447.16541.1391.malone@chaenomeles.canonical.com> *** This bug is a duplicate of bug 266464 *** https://bugs.launchpad.net/bugs/266464 Sorry, this is mailman-2.1.9 and mailman-2.1.12. You are right it's fixed in 2.1.15, thanks. This is my debugging log showing the second problem. I reproduced it only once and my test case was sending lot of emails per second (I basically sent 10000 emails using more threads). It prints "SAVE post_id" or "LOAD post_id" in the end of mlist.Save() and mlist.Load() methods followed by traceback (to find out what called those methods - it was useful to debug the first problem). You can see the lock problem in the end. Oct 15 06:47:27 2012 (20378) SAVE 9345 [' File "/usr/lib/mailman/bin/qrunner", line 278, in ?\n main()\n', ' File "/usr/lib/mailman/bin/qrunner", line 238, in main\n qrunner.run()\n', ' File "/usr/lib/mailman/Mailman/Queue/Runner.py", line 71, in run\n filecnt = s elf._oneloop()\n', ' File "/usr/lib/mailman/Mailman/Queue/Runner.py", line 113, in _oneloop\n self._onefile(msg, msgdata)\n', ' File "/usr/lib/mailman/Mailman/Queue/Runner.py", line 176, in _onefile\n keepqueued = self._dispose(m list, msg, msgdata)\n', ' File "/usr/lib/mailman/Mailman/Queue/IncomingRunner.py", line 133, in _dispose\n mlist.Save()\n', ' File "/usr/lib/mailman/Mailman/MailList.py", line 561, in Save\n syslog(\'error\', \'SAVE %d\\n%s\\n\', self.post_id, repr(traceback.format_stack()))\n'] Oct 15 06:47:28 2012 (20378) SAVE 9346 [' File "/usr/lib/mailman/bin/qrunner", line 278, in ?\n main()\n', ' File "/usr/lib/mailman/bin/qrunner", line 238, in main\n qrunner.run()\n', ' File "/usr/lib/mailman/Mailman/Queue/Runner.py", line 71, in run\n filecnt = s elf._oneloop()\n', ' File "/usr/lib/mailman/Mailman/Queue/Runner.py", line 113, in _oneloop\n self._onefile(msg, msgdata)\n', ' File "/usr/lib/mailman/Mailman/Queue/Runner.py", line 176, in _onefile\n keepqueued = self._dispose(m list, msg, msgdata)\n', ' File "/usr/lib/mailman/Mailman/Queue/IncomingRunner.py", line 133, in _dispose\n mlist.Save()\n', ' File "/usr/lib/mailman/Mailman/MailList.py", line 561, in Save\n syslog(\'error\', \'SAVE %d\\n%s\\n\', self.post_id, repr(traceback.format_stack()))\n'] Oct 15 06:47:28 2012 (20380) LOAD 9346 [' File "/usr/lib/mailman/bin/qrunner", line 278, in ?\n main()\n', ' File "/usr/lib/mailman/bin/qrunner", line 238, in main\n qrunner.run()\n', ' File "/usr/lib/mailman/Mailman/Queue/Runner.py", line 71, in run\n filecnt = s elf._oneloop()\n', ' File "/usr/lib/mailman/Mailman/Queue/Runner.py", line 113, in _oneloop\n self._onefile(msg, msgdata)\n', ' File "/usr/lib/mailman/Mailman/Queue/Runner.py", line 176, in _onefile\n keepqueued = self._dispose(m list, msg, msgdata)\n', ' File "/usr/lib/mailman/Mailman/Queue/OutgoingRunner.py", line 70, in _dispose\n mlist.Load()\n', ' File "/usr/lib/mailman/Mailman/MailList.py", line 666, in Load\n syslog(\'error\', \'LOAD %d\\n%s\\n\', self.post_id, repr(traceback.format_stack()))\n'] Oct 15 06:47:28 2012 (20378) Uncaught runner exception: : None Oct 15 06:47:28 2012 (20378) Traceback (most recent call last): File "/usr/lib/mailman/Mailman/Queue/Runner.py", line 113, in _oneloop self._onefile(msg, msgdata) File "/usr/lib/mailman/Mailman/Queue/Runner.py", line 176, in _onefile keepqueued = self._dispose(mlist, msg, msgdata) File "/usr/lib/mailman/Mailman/Queue/IncomingRunner.py", line 133, in _dispose mlist.Save() File "/usr/lib/mailman/Mailman/MailList.py", line 551, in Save self.__lock.refresh() File "/usr/lib/mailman/Mailman/LockFile.py", line 229, in refresh raise NotLockedError, '%s: %s' % (repr(self), self.__read()) NotLockedError: : None Oct 15 06:47:28 2012 (20378) SHUNTING: 1350273953.9130599+e82f3657cfb0be0aae0be15565a31e333d37324b -- 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 From mark at msapiro.net Tue Nov 13 14:03:46 2012 From: mark at msapiro.net (Mark Sapiro) Date: Tue, 13 Nov 2012 13:03:46 -0000 Subject: [Bug 1077908] Re: MailList configuration race condition between qrunners References: <20121112122248.30565.17723.malonedeb@wampee.canonical.com> Message-ID: <20121113130347.32345.74489.malone@soybean.canonical.com> Reopening this bug for the second issue only. The first issue is a duplicate of LP:266464. The second issue requires further study. ** Changed in: mailman Milestone: 2.1.15 => None -- 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 From mark at msapiro.net Tue Nov 13 13:57:48 2012 From: mark at msapiro.net (Mark Sapiro) Date: Tue, 13 Nov 2012 12:57:48 -0000 Subject: [Bug 1077908] Re: MailList configuration race condition between qrunners References: <20121112122248.30565.17723.malonedeb@wampee.canonical.com> Message-ID: <20121113125749.26872.27148.launchpad@gac.canonical.com> ** This bug is no longer a duplicate of bug 266464 Subscriber "disappears" after subscription ** Changed in: mailman Status: Fix Committed => Triaged ** Changed in: mailman Status: Triaged => Incomplete -- 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 From mark at msapiro.net Wed Nov 14 19:54:23 2012 From: mark at msapiro.net (Mark Sapiro) Date: Wed, 14 Nov 2012 18:54:23 -0000 Subject: [Bug 1077908] Re: MailList configuration race condition between qrunners References: <20121112122248.30565.17723.malonedeb@wampee.canonical.com> Message-ID: <20121114185423.10565.18562.malone@gac.canonical.com> It seems that what happened is the NotLockedError and traceback at the end of comment #6 occurred when IncomingRunner attempted to Save() the list (two log messages earlier in comment #6) and found it not locked, or possibly this was the Save() after the next message which wasn't yet logged. In either case, this may have only occurred because of LP:266464. Pending further information and evidence that this can occur with the fix for LP:266464 installed, I'm leaving this 'incomplete'. -- 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 From jkaluza at redhat.com Thu Nov 15 07:51:30 2012 From: jkaluza at redhat.com (Jan Kaluza) Date: Thu, 15 Nov 2012 06:51:30 -0000 Subject: [Bug 1077908] Re: MailList configuration race condition between qrunners References: <20121112122248.30565.17723.malonedeb@wampee.canonical.com> Message-ID: <20121115065130.31839.94796.malone@chaenomeles.canonical.com> When I reproduced this second bug, my fix for the first bug had not been applied yet. I was not able to reproduce the second bug with your patch for LP:266464. I think you can close this bug. Thank you for all the information and help. -- 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 From mark at msapiro.net Thu Nov 15 15:13:39 2012 From: mark at msapiro.net (Mark Sapiro) Date: Thu, 15 Nov 2012 14:13:39 -0000 Subject: [Bug 1077908] Re: MailList configuration race condition between qrunners References: <20121112122248.30565.17723.malonedeb@wampee.canonical.com> Message-ID: <20121115141341.16874.34406.launchpad@gac.canonical.com> *** This bug is a duplicate of bug 266464 *** https://bugs.launchpad.net/bugs/266464 ** This bug has been marked a duplicate of bug 266464 Subscriber "disappears" after subscription -- 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 From davidw at axis.com Fri Nov 23 11:28:09 2012 From: davidw at axis.com (David Westlund) Date: Fri, 23 Nov 2012 10:28:09 -0000 Subject: [Bug 1082308] [NEW] The qrunner-master lock file causes issues when running clustered References: <20121123102809.19447.75468.malonedeb@wampee.canonical.com> Message-ID: <20121123102809.19447.75468.malonedeb@wampee.canonical.com> Public bug reported: Hi It is possible to run mailman in a failover or load balancing cluster, see: http://wiki.list.org/pages/viewpage.action?pageId=4030621 When running a cluster, it is crucial to use: * a shared directory for archive data * a shared directory for locks * separate directories for each qrunner This is possible to implement by setting the directories in mm_cfg.py, for example like this (where is a host name): VAR_PREFIX = '' LIST_DATA_DIR = os.path.join(VAR_PREFIX, 'lists') LOCK_DIR = os.path.join(VAR_PREFIX, 'locks') DATA_DIR = os.path.join(VAR_PREFIX, 'data') SPAM_DIR = os.path.join(VAR_PREFIX, 'spam') LOG_DIR = os.path.join(VAR_PREFIX, 'logs-') PUBLIC_ARCHIVE_FILE_DIR = os.path.join(VAR_PREFIX, 'archives', 'public') PRIVATE_ARCHIVE_FILE_DIR = os.path.join(VAR_PREFIX, 'archives', 'private') # For qfiles and logs, - is used to avoid conflicts QUEUE_DIR = os.path.join(VAR_PREFIX, 'qfiles-') INQUEUE_DIR = os.path.join(QUEUE_DIR, 'in') OUTQUEUE_DIR = os.path.join(QUEUE_DIR, 'out') CMDQUEUE_DIR = os.path.join(QUEUE_DIR, 'commands') BOUNCEQUEUE_DIR = os.path.join(QUEUE_DIR, 'bounces') NEWSQUEUE_DIR = os.path.join(QUEUE_DIR, 'news') ARCHQUEUE_DIR = os.path.join(QUEUE_DIR, 'archive') SHUNTQUEUE_DIR = os.path.join(QUEUE_DIR, 'shunt') VIRGINQUEUE_DIR = os.path.join(QUEUE_DIR, 'virgin') BADQUEUE_DIR = os.path.join(QUEUE_DIR, 'bad') RETRYQUEUE_DIR = os.path.join(QUEUE_DIR, 'retry') MAILDIR_DIR = os.path.join(QUEUE_DIR, 'maildir') Unfortunately, the master-qrunner lock causes problem with this setup. mailmanctl -s starts even if there is a master-qrunner file (provided that there is no running mailmanctl on the host), making it possible to get the service up and running on more than one host. Once a day however, mailmanctl controls the lock. If it does not have it, it shuts down. If you are running a cluster, at least one of the nodes will not have the lock, and the service will be shut down on that node. To solve this, I propose that the the LOCKFILE name in mailmanctl becomes configurable, so instead of having: LOCKFILE = os.path.join(mm_cfg.LOCK_DIR, 'master-qrunner') Have: LOCKFILE = os.path.join(mm_cfg.LOCK_DIR, mm_cfg.QRUNNER_LOCK_FILE) Then add LOCKFILE = 'master-qrunner' in Defaults.py. This would make it easy to have individual qrunner master lock files for each node in a cluster. ** Affects: mailman Importance: Undecided Status: New ** Tags: cluster -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1082308 Title: The qrunner-master lock file causes issues when running clustered To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1082308/+subscriptions From gphemsley at gmail.com Fri Nov 23 21:12:08 2012 From: gphemsley at gmail.com (Gordon P. Hemsley) Date: Fri, 23 Nov 2012 20:12:08 -0000 Subject: [Bug 1082495] [NEW] Support bracketed prefixes in subject as filters References: <20121123201208.21130.88112.malonedeb@gac.canonical.com> Message-ID: <20121123201208.21130.88112.malonedeb@gac.canonical.com> Public bug reported: Many large mailing lists use bracketed prefixes in subjects as a way to filter messages into smaller buckets, allowing some subscribers to read all mail sent to the list while allowing others to filter messages (in their mail client) to read only the messages they are interested in. For example, the W3C's www-style mailing list uses these tags to filter messages based on which CSS spec they refer to. Thus, a subject line that begins "[css3-fonts]" will be assumed to be about only the css3-fonts spec, with a target audience of only those interested in that particular spec and not, say, the css3-flexbox spec (whose subject lines would be prefixed with "[css3-flexbox]"). To handle this, the Mailman archive interface would provide an option to filter only on particular prefixes (as well as messages that don't have any prefixes), allowing a user of the archive to use it as they otherwise would, but filtering the output such that they only see the messages they want to see, instead of the whole archive. In addition, it would be helpful to allow mailing lists to automatically prefix subject lines when the message is sent to an e-mail address using a plus alias. For example, sending mail to www-style+css3-fonts at w3.org would prefix the subject line of the message with "[css3-fonts]" in the message sent to subscribers and in the archive, whereas sending mail to www- style+css3-flexbox at w3.org would prefix the message with "[css3-flexbox]". It should also be allowed to have multiple prefixes on a message, and having such messages be treated as if they had any prefix individually. In terms of plus aliasing, there are two ways to handle it: (1) allow aliases to specify multiple prefixes in a plus alias using some separator (e.g. a comma: www-style+css3-fonts,css3-flexbox at w3.org); or (2) detecting and intercepting when a single message was sent to multiple e-mail addresses with different plus aliases for a single mailing list (e.g. sending the same e-mail to both www- style+css3-fonts at w3.org and www-style+css3-flexbox at w3.org), treating it as a single message with multiple subject prefixes when sent to subscribers or stored in the archive. Now, I understand that this is likely a huge undertaking, but I think it would go a long way to helping users with large and diverse mailing 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/1082495 Title: Support bracketed prefixes in subject as filters To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1082495/+subscriptions From 1082495 at bugs.launchpad.net Fri Nov 23 21:27:37 2012 From: 1082495 at bugs.launchpad.net (Barry Warsaw) Date: Fri, 23 Nov 2012 20:27:37 -0000 Subject: [Bug 1082495] Re: Support bracketed prefixes in subject as filters References: <20121123201208.21130.88112.malonedeb@gac.canonical.com> Message-ID: <20121123202737.6115.94390.malone@chaenomeles.canonical.com> Many similar ideas are being explored on the mailman-developers mailing list, under the 'dlist' thread. I suggest engaging in that thread to put forth these ideas. ** 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/1082495 Title: Support bracketed prefixes in subject as filters To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1082495/+subscriptions From gphemsley at gmail.com Fri Nov 23 21:27:57 2012 From: gphemsley at gmail.com (Gordon P. Hemsley) Date: Fri, 23 Nov 2012 20:27:57 -0000 Subject: [Bug 1082495] Re: Support bracketed prefixes in subject as filters References: <20121123201208.21130.88112.malonedeb@gac.canonical.com> Message-ID: <20121123202757.2330.80990.launchpad@soybean.canonical.com> ** Description changed: Many large mailing lists use bracketed prefixes in subjects as a way to filter messages into smaller buckets, allowing some subscribers to read all mail sent to the list while allowing others to filter messages (in their mail client) to read only the messages they are interested in. For example, the W3C's www-style mailing list uses these tags to filter messages based on which CSS spec they refer to. Thus, a subject line that begins "[css3-fonts]" will be assumed to be about only the css3-fonts spec, with a target audience of only those interested in that particular spec and not, say, the css3-flexbox spec (whose subject lines would be prefixed with "[css3-flexbox]"). To handle this, the Mailman archive interface would provide an option to filter only on particular prefixes (as well as messages that don't have any prefixes), allowing a user of the archive to use it as they otherwise would, but filtering the output such that they only see the messages they want to see, instead of the whole archive. In addition, it would be helpful to allow mailing lists to automatically prefix subject lines when the message is sent to an e-mail address using a plus alias. For example, sending mail to www-style+css3-fonts at w3.org would prefix the subject line of the message with "[css3-fonts]" in the message sent to subscribers and in the archive, whereas sending mail to www- style+css3-flexbox at w3.org would prefix the message with "[css3-flexbox]". It should also be allowed to have multiple prefixes on a message, and having such messages be treated as if they had any prefix individually. In terms of plus aliasing, there are two ways to handle it: (1) allow aliases to specify multiple prefixes in a plus alias using some separator (e.g. a comma: www-style+css3-fonts,css3-flexbox at w3.org); or (2) detecting and intercepting when a single message was sent to multiple e-mail addresses with different plus aliases for a single mailing list (e.g. sending the same e-mail to both www- style+css3-fonts at w3.org and www-style+css3-flexbox at w3.org), treating it as a single message with multiple subject prefixes when sent to subscribers or stored in the archive. Now, I understand that this is likely a huge undertaking, but I think it would go a long way to helping users with large and diverse mailing lists. + + [EDIT: It appears the W3C may not actually use Mailman. But my point is + still the same, so take my usage of W3C e-mails as a hypothetical + example, if necessary.] -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1082495 Title: Support bracketed prefixes in subject as filters To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1082495/+subscriptions From 1082495 at bugs.launchpad.net Sat Nov 24 01:13:59 2012 From: 1082495 at bugs.launchpad.net (Barry Warsaw) Date: Sat, 24 Nov 2012 00:13:59 -0000 Subject: [Bug 1082495] Re: Support bracketed prefixes in subject as filters References: <20121123201208.21130.88112.malonedeb@gac.canonical.com> Message-ID: <20121124001400.19413.2319.launchpad@wampee.canonical.com> ** Changed in: mailman Importance: Undecided => Wishlist -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1082495 Title: Support bracketed prefixes in subject as filters To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1082495/+subscriptions From gphemsley at gmail.com Sat Nov 24 02:34:09 2012 From: gphemsley at gmail.com (Gordon P. Hemsley) Date: Sat, 24 Nov 2012 01:34:09 -0000 Subject: [Bug 1082495] Re: Support bracketed prefixes in subject as filters References: <20121123201208.21130.88112.malonedeb@gac.canonical.com> Message-ID: <20121124013409.2258.63788.malone@soybean.canonical.com> I sent an e-mail to the list a few hours ago, but it doesn't appear in the archive. Can you check on that? -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1082495 Title: Support bracketed prefixes in subject as filters To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1082495/+subscriptions From mark at msapiro.net Sat Nov 24 03:25:06 2012 From: mark at msapiro.net (Mark Sapiro) Date: Sat, 24 Nov 2012 02:25:06 -0000 Subject: [Bug 1082495] Re: Support bracketed prefixes in subject as filters References: <20121123201208.21130.88112.malonedeb@gac.canonical.com> Message-ID: <20121124022506.2854.47224.malone@soybean.canonical.com> As it says at "We have set the mailman-developers list to moderate all new users because of a recent problem with some people subscribing to this list and then posting messages that belong elsewhere, often messages that belong on mailman-users instead." Moderators are not online 24-7. Your post has now been accepted and your moderated bit cleared. -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1082495 Title: Support bracketed prefixes in subject as filters To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1082495/+subscriptions From mark at msapiro.net Sat Nov 24 19:43:33 2012 From: mark at msapiro.net (Mark Sapiro) Date: Sat, 24 Nov 2012 18:43:33 -0000 Subject: [Bug 1082711] [NEW] bin/list_lists needs an option for listing only lists with public archives. References: <20121124184333.21511.73908.malonedeb@gac.canonical.com> Message-ID: <20121124184333.21511.73908.malonedeb@gac.canonical.com> Public bug reported: For example, if one wants to create a list of pages for public search engines to index, one can make a list of all the *.html files in the archives/private// directory, but one probably only wants to do this for lists with public archives. With an option for listing only lists with public archives, 'bin/list_lists --bare --public_archive' can easily create a list of those lists. ** 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/1082711 Title: bin/list_lists needs an option for listing only lists with public archives. To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1082711/+subscriptions From mark at msapiro.net Sat Nov 24 23:39:07 2012 From: mark at msapiro.net (Mark Sapiro) Date: Sat, 24 Nov 2012 22:39:07 -0000 Subject: [Bug 1082746] [NEW] Automated processes can swamp a list with web subscription requests. References: <20121124223907.2772.33004.malonedeb@soybean.canonical.com> Message-ID: <20121124223907.2772.33004.malonedeb@soybean.canonical.com> Public bug reported: There are discussions of this in threads at , and . The Mailman developers do not think there is any way to prevent this other that disabling web subscribe entirely, as by definition, subscription requests come from unauthenticated users. However, an attempt will be made to mitigate this by making a site option to include a dynamically generated hidden hash in the subscribe form which will at least require an automated process to first GET and parse the listinfo form immediately prior to POSTing it. ** 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/1082746 Title: Automated processes can swamp a list with web subscription requests. To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1082746/+subscriptions From 1082746 at bugs.launchpad.net Sat Nov 24 23:49:56 2012 From: 1082746 at bugs.launchpad.net (Launchpad Bug Tracker) Date: Sat, 24 Nov 2012 22:49:56 -0000 Subject: [Bug 1082746] Re: Automated processes can swamp a list with web subscription requests. References: <20121124223907.2772.33004.malonedeb@soybean.canonical.com> Message-ID: <20121124224957.32462.9865.launchpad@ackee.canonical.com> ** 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/1082746 Title: Automated processes can swamp a list with web subscription requests. To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1082746/+subscriptions From mark at msapiro.net Sat Nov 24 23:53:38 2012 From: mark at msapiro.net (Mark Sapiro) Date: Sat, 24 Nov 2012 22:53:38 -0000 Subject: [Bug 1082308] Re: The qrunner-master lock file causes issues when running clustered References: <20121123102809.19447.75468.malonedeb@wampee.canonical.com> Message-ID: <20121124225339.6499.69214.launchpad@chaenomeles.canonical.com> ** Changed in: mailman Importance: Undecided => Low ** 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/1082308 Title: The qrunner-master lock file causes issues when running clustered To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1082308/+subscriptions From mark at msapiro.net Sat Nov 24 23:52:53 2012 From: mark at msapiro.net (Mark Sapiro) Date: Sat, 24 Nov 2012 22:52:53 -0000 Subject: [Bug 1082711] Re: bin/list_lists needs an option for listing only lists with public archives. References: <20121124184333.21511.73908.malonedeb@gac.canonical.com> Message-ID: <20121124225254.2854.23876.launchpad@soybean.canonical.com> ** Changed in: mailman Status: In Progress => 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/1082711 Title: bin/list_lists needs an option for listing only lists with public archives. To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1082711/+subscriptions From 1082308 at bugs.launchpad.net Sat Nov 24 23:49:56 2012 From: 1082308 at bugs.launchpad.net (Launchpad Bug Tracker) Date: Sat, 24 Nov 2012 22:49:56 -0000 Subject: [Bug 1082308] Re: The qrunner-master lock file causes issues when running clustered References: <20121123102809.19447.75468.malonedeb@wampee.canonical.com> Message-ID: <20121124224957.32462.49996.launchpad@ackee.canonical.com> ** 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/1082308 Title: The qrunner-master lock file causes issues when running clustered To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1082308/+subscriptions From mark at msapiro.net Sat Nov 24 23:52:35 2012 From: mark at msapiro.net (Mark Sapiro) Date: Sat, 24 Nov 2012 22:52:35 -0000 Subject: [Bug 1082746] Re: Automated processes can swamp a list with web subscription requests. References: <20121124223907.2772.33004.malonedeb@soybean.canonical.com> Message-ID: <20121124225236.6115.83887.launchpad@chaenomeles.canonical.com> ** Changed in: mailman Status: In Progress => 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/1082746 Title: Automated processes can swamp a list with web subscription requests. To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1082746/+subscriptions From 1082711 at bugs.launchpad.net Sat Nov 24 23:49:56 2012 From: 1082711 at bugs.launchpad.net (Launchpad Bug Tracker) Date: Sat, 24 Nov 2012 22:49:56 -0000 Subject: [Bug 1082711] Re: bin/list_lists needs an option for listing only lists with public archives. References: <20121124184333.21511.73908.malonedeb@gac.canonical.com> Message-ID: <20121124224957.32462.80915.launchpad@ackee.canonical.com> ** 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/1082711 Title: bin/list_lists needs an option for listing only lists with public archives. To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1082711/+subscriptions From gphemsley at gmail.com Thu Nov 29 18:48:14 2012 From: gphemsley at gmail.com (Gordon P. Hemsley) Date: Thu, 29 Nov 2012 17:48:14 -0000 Subject: [Bug 1082495] Re: Support bracketed prefixes in subject as filters References: <20121123201208.21130.88112.malonedeb@gac.canonical.com> Message-ID: <20121129174814.13667.80119.malone@soybean.canonical.com> Oh, sorry. I admit I didn't read that. I just assumed that I would get a notification if my message was moderated. -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1082495 Title: Support bracketed prefixes in subject as filters To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1082495/+subscriptions