From mark at msapiro.net Mon Jun 3 02:49:38 2013 From: mark at msapiro.net (Mark Sapiro) Date: Mon, 03 Jun 2013 00:49:38 -0000 Subject: [Bug 693134] Re: Uncaught bounce from Dovecot when Quota Exceeded References: <20101221185325.20409.19945.malonedeb@soybean.canonical.com> Message-ID: <20130603004939.6067.28427.launchpad@chaenomeles.canonical.com> ** Also affects: flufl.bounce Importance: Undecided Status: New ** Changed in: flufl.bounce Status: New => In Progress ** Changed in: flufl.bounce Importance: Undecided => Low ** Changed in: flufl.bounce 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/693134 Title: Uncaught bounce from Dovecot when Quota Exceeded To manage notifications about this bug go to: https://bugs.launchpad.net/flufl.bounce/+bug/693134/+subscriptions From 693134 at bugs.launchpad.net Mon Jun 3 03:44:29 2013 From: 693134 at bugs.launchpad.net (Launchpad Bug Tracker) Date: Mon, 03 Jun 2013 01:44:29 -0000 Subject: [Bug 693134] Re: Uncaught bounce from Dovecot when Quota Exceeded References: <20101221185325.20409.19945.malonedeb@soybean.canonical.com> Message-ID: <20130603014429.10011.52664.launchpad@ackee.canonical.com> ** Branch linked: lp:flufl.bounce -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/693134 Title: Uncaught bounce from Dovecot when Quota Exceeded To manage notifications about this bug go to: https://bugs.launchpad.net/flufl.bounce/+bug/693134/+subscriptions From mark at msapiro.net Mon Jun 3 03:45:41 2013 From: mark at msapiro.net (Mark Sapiro) Date: Mon, 03 Jun 2013 01:45:41 -0000 Subject: [Bug 693134] Re: Uncaught bounce from Dovecot when Quota Exceeded References: <20101221185325.20409.19945.malonedeb@soybean.canonical.com> Message-ID: <20130603014542.5854.27717.launchpad@chaenomeles.canonical.com> ** Changed in: flufl.bounce Status: In Progress => Fix Committed ** Changed in: flufl.bounce Milestone: None => 2.2 -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/693134 Title: Uncaught bounce from Dovecot when Quota Exceeded To manage notifications about this bug go to: https://bugs.launchpad.net/flufl.bounce/+bug/693134/+subscriptions From aurelien at bompard.org Mon Jun 3 09:19:51 2013 From: aurelien at bompard.org (=?utf-8?q?Aur=C3=A9lien_Bompard?=) Date: Mon, 03 Jun 2013 07:19:51 -0000 Subject: [Bug 1184376] Re: REST server crashes on "reopen" References: <20130526163258.7720.51480.malonedeb@chaenomeles.canonical.com> Message-ID: <20130603071951.6067.31781.malone@chaenomeles.canonical.com> OK, now I know why you added this flag. Removing it does not work, the REST server still exits on reopen (I don't know how I missed this, it used to work). But it's an exit, not a crash. In the logs I get "REST server exiting", because the server gets an interrupted system call error. This is very probably linked to http://bugs.python.org/issue7978. In python upstream they suggested to simply restart the select call, so I'll prepare a patch to restart the serve_forever() call. Can you think of a reason where we would really want the REST server to exit on an interrupted system call ? ** Bug watch added: Python Roundup #7978 http://bugs.python.org/issue7978 ** Changed in: mailman Status: Fix Committed => 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/1184376 Title: REST server crashes on "reopen" To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1184376/+subscriptions From aurelien at bompard.org Mon Jun 3 10:55:11 2013 From: aurelien at bompard.org (=?utf-8?q?Aur=C3=A9lien_Bompard?=) Date: Mon, 03 Jun 2013 08:55:11 -0000 Subject: [Bug 1184376] Re: REST server crashes on "reopen" References: <20130526163258.7720.51480.malonedeb@chaenomeles.canonical.com> Message-ID: <20130603085511.4809.32050.malone@soybean.canonical.com> Here's the patch to restart the REST server on an interrupted system call. I tried to make use of the existing runner infrastructure so it's a short patch, but it may not be a good idea (I don't want to hijack something not designed for this purpose). ** Patch added: "mailman-1184376.patch" https://bugs.launchpad.net/mailman/+bug/1184376/+attachment/3693446/+files/mailman-1184376.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/1184376 Title: REST server crashes on "reopen" To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1184376/+subscriptions From mark at msapiro.net Tue Jun 4 01:46:47 2013 From: mark at msapiro.net (Mark Sapiro) Date: Mon, 03 Jun 2013 23:46:47 -0000 Subject: [Bug 1187201] [NEW] It is possible to add addresses to *_these_nonmembers from the admindb interface that cause later problems. References: <20130603234648.6184.7616.malonedeb@chaenomeles.canonical.com> Message-ID: <20130603234648.6184.7616.malonedeb@chaenomeles.canonical.com> Public bug reported: The admindb summary page has a checkbox and radio buttons to add the sender address of a held non-member post to one of the *_these_nonmembers filters. Sometimes the sender address will fail Mailman's syntactic address validation, e.g. because it doesn't have a qualified domain name. This addition is accepted and causes no real problem until the next time an admin tries to modify the filter via the admin web UI, at which point all the addresses are checked and the change rejected. ** 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/1187201 Title: It is possible to add addresses to *_these_nonmembers from the admindb interface that cause later problems. To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1187201/+subscriptions From noreply at launchpad.net Tue Jun 4 12:26:14 2013 From: noreply at launchpad.net (noreply at launchpad.net) Date: Tue, 04 Jun 2013 10:26:14 -0000 Subject: [Merge] lp:~wacky/postorius/GSoC2012 into lp:postorius In-Reply-To: <20130531023127.16308.6928.launchpad@ackee.canonical.com> Message-ID: <20130604102614.20271.97096.launchpad@ackee.canonical.com> The proposal to merge lp:~wacky/postorius/GSoC2012 into lp:postorius has been updated. Status: Needs review => Merged For more details, see: https://code.launchpad.net/~wacky/postorius/GSoC2012/+merge/166629 -- https://code.launchpad.net/~wacky/postorius/GSoC2012/+merge/166629 Your team Mailman Coders is subscribed to branch lp:postorius. From flo.fuchs at gmail.com Tue Jun 4 12:32:16 2013 From: flo.fuchs at gmail.com (Florian Fuchs) Date: Tue, 04 Jun 2013 10:32:16 -0000 Subject: [Merge] lp:~wacky/postorius/GSoC2012 into lp:postorius In-Reply-To: <20130531023127.16308.6928.launchpad@ackee.canonical.com> Message-ID: <20130604102503.10862.70256.codereview@wampee.canonical.com> Review: Approve Hi Richard, thanks for these changes! Everything merged into trunk... Florian -- https://code.launchpad.net/~wacky/postorius/GSoC2012/+merge/166629 Your team Mailman Coders is subscribed to branch lp:postorius. From flo.fuchs at gmail.com Tue Jun 4 12:32:20 2013 From: flo.fuchs at gmail.com (Florian Fuchs) Date: Tue, 04 Jun 2013 10:32:20 -0000 Subject: [Merge] lp:~stephen-xemacs/postorius/domain-not-list into lp:postorius In-Reply-To: <20130321001324.6948.42866.launchpad@ackee.canonical.com> Message-ID: <20130604102706.5557.59183.codereview@chaenomeles.canonical.com> Hi Steve, thanks for these changes! They're included in Rev. 141: http://bazaar.launchpad.net/~mailman-coders/postorius/trunk/revision/141 Florian -- https://code.launchpad.net/~stephen-xemacs/postorius/domain-not-list/+merge/154558 Your team Mailman Coders is requested to review the proposed merge of lp:~stephen-xemacs/postorius/domain-not-list into lp:postorius. From philipp at dreimann.net Tue Jun 4 20:21:25 2013 From: philipp at dreimann.net (Philipp Dreimann) Date: Tue, 04 Jun 2013 18:21:25 -0000 Subject: [Merge] lp:~philipp-dreimann/mailman/2.1-UnixMailbox-Fix into lp:mailman/2.1 Message-ID: <20130604182124.26204.96330.launchpad@ackee.canonical.com> Philipp Dreimann has proposed merging lp:~philipp-dreimann/mailman/2.1-UnixMailbox-Fix into lp:mailman/2.1. Requested reviews: Mailman Coders (mailman-coders) For more details, see: https://code.launchpad.net/~philipp-dreimann/mailman/2.1-UnixMailbox-Fix/+merge/167361 -- https://code.launchpad.net/~philipp-dreimann/mailman/2.1-UnixMailbox-Fix/+merge/167361 Your team Mailman Coders is requested to review the proposed merge of lp:~philipp-dreimann/mailman/2.1-UnixMailbox-Fix into lp:mailman/2.1. -------------- next part -------------- A non-text attachment was scrubbed... Name: review-diff.txt Type: text/x-diff Size: 795 bytes Desc: not available URL: From mark at msapiro.net Thu Jun 6 03:37:37 2013 From: mark at msapiro.net (Mark Sapiro) Date: Thu, 06 Jun 2013 01:37:37 -0000 Subject: [Bug 558106] Re: A MemberAdaptor for LDAP-based membership References: <20100408090607.1687.22727.launchpad@loganberry.canonical.com> Message-ID: <20130606013737.21597.63891.malone@chaenomeles.canonical.com> The LDAP_Memberships.py, version 0.63 which was attached to Comment #14 has been deleted. It is replaced with this one which corrects a serious typo in the prior version. ** Attachment removed: "LDAP_Memberships.py, version 0.63" https://bugs.launchpad.net/mailman/+bug/558106/+attachment/2188740/+files/LDAP_Memberships.py ** Attachment added: "LDAP_Memberships.py, version 0.63-1" https://bugs.launchpad.net/mailman/+bug/558106/+attachment/3695834/+files/LDAP_Memberships.py -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/558106 Title: A MemberAdaptor for LDAP-based membership To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/558106/+subscriptions From 1184376 at bugs.launchpad.net Fri Jun 7 22:42:34 2013 From: 1184376 at bugs.launchpad.net (Barry Warsaw) Date: Fri, 07 Jun 2013 20:42:34 -0000 Subject: [Bug 1184376] Re: REST server crashes on "reopen" References: <20130526163258.7720.51480.malonedeb@chaenomeles.canonical.com> Message-ID: <20130607204235.7769.49295.malone@gac.canonical.com> I generally like that you're using the runner infrastructure for this. Is there any chance you can come up with a unittest case for this? (I'm still working on one but haven't gotten it working yet.) -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1184376 Title: REST server crashes on "reopen" To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1184376/+subscriptions From 1187201 at bugs.launchpad.net Fri Jun 7 22:55:11 2013 From: 1187201 at bugs.launchpad.net (Launchpad Bug Tracker) Date: Fri, 07 Jun 2013 20:55:11 -0000 Subject: [Bug 1187201] Re: It is possible to add addresses to *_these_nonmembers from the admindb interface that cause later problems. References: <20130603234648.6184.7616.malonedeb@chaenomeles.canonical.com> Message-ID: <20130607205515.8852.47366.launchpad@ackee.canonical.com> ** 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/1187201 Title: It is possible to add addresses to *_these_nonmembers from the admindb interface that cause later problems. To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1187201/+subscriptions From mark at msapiro.net Fri Jun 7 23:05:11 2013 From: mark at msapiro.net (Mark Sapiro) Date: Fri, 07 Jun 2013 21:05:11 -0000 Subject: [Bug 1187201] Re: It is possible to add addresses to *_these_nonmembers from the admindb interface that cause later problems. References: <20130603234648.6184.7616.malonedeb@chaenomeles.canonical.com> Message-ID: <20130607210512.7738.95119.launchpad@gac.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/1187201 Title: It is possible to add addresses to *_these_nonmembers from the admindb interface that cause later problems. To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1187201/+subscriptions From aurelien at bompard.org Mon Jun 10 15:10:24 2013 From: aurelien at bompard.org (=?utf-8?q?Aur=C3=A9lien_Bompard?=) Date: Mon, 10 Jun 2013 13:10:24 -0000 Subject: [Bug 1184376] Re: REST server crashes on "reopen" References: <20130526163258.7720.51480.malonedeb@chaenomeles.canonical.com> Message-ID: <20130610131024.14031.78566.malone@soybean.canonical.com> Here's a testcase that I finally managed to get working. Download the attached file to src/mailman/runners/tests/test_rest.py. I'm not sure it's the best way to test for such a case, but at least it works (it fails without my patch and passes with it). ** Attachment added: "test_rest.py" https://bugs.launchpad.net/mailman/+bug/1184376/+attachment/3699803/+files/test_rest.py -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1184376 Title: REST server crashes on "reopen" To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1184376/+subscriptions From mark at msapiro.net Mon Jun 10 19:24:48 2013 From: mark at msapiro.net (Mark Sapiro) Date: Mon, 10 Jun 2013 17:24:48 -0000 Subject: [Bug 1189558] [NEW] mailmanctl -s will remove non-stale locks References: <20130610172448.8067.63533.malonedeb@gac.canonical.com> Message-ID: <20130610172448.8067.63533.malonedeb@gac.canonical.com> Public bug reported: The help for the -s option says it will remove a lock from another 'start' if the lock is determined to be stale. In fact it does no check and just removes any lock found. This can result in various issues from multiple qrunners attempting to process the same messages. ** 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/1189558 Title: mailmanctl -s will remove non-stale locks To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1189558/+subscriptions From 1189558 at bugs.launchpad.net Mon Jun 10 23:39:41 2013 From: 1189558 at bugs.launchpad.net (Launchpad Bug Tracker) Date: Mon, 10 Jun 2013 21:39:41 -0000 Subject: [Bug 1189558] Re: mailmanctl -s will remove non-stale locks References: <20130610172448.8067.63533.malonedeb@gac.canonical.com> Message-ID: <20130610213942.16824.38935.launchpad@ackee.canonical.com> ** 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/1189558 Title: mailmanctl -s will remove non-stale locks To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1189558/+subscriptions From mark at msapiro.net Mon Jun 10 23:39:56 2013 From: mark at msapiro.net (Mark Sapiro) Date: Mon, 10 Jun 2013 21:39:56 -0000 Subject: [Bug 1189558] Re: mailmanctl -s will remove non-stale locks References: <20130610172448.8067.63533.malonedeb@gac.canonical.com> Message-ID: <20130610213957.13962.95679.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/1189558 Title: mailmanctl -s will remove non-stale locks To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1189558/+subscriptions From 1190582 at bugs.launchpad.net Thu Jun 13 14:21:31 2013 From: 1190582 at bugs.launchpad.net (Florian Fuchs) Date: Thu, 13 Jun 2013 12:21:31 -0000 Subject: [Bug 1190582] [NEW] Add some common filters to REST API resources that expose collections References: <20130613122132.14706.13325.malonedeb@soybean.canonical.com> Message-ID: <20130613122132.14706.13325.malonedeb@soybean.canonical.com> Public bug reported: When Postorius GETs a collection of lists from the REST API, it will in most situations only use a subset (the ones that are set to "advertise in list index"). This is a minor issue as long as the request isn't paginated, but can lead to incorrect item counts when it is. Example: GET /lists/test at example.com?page=1&count=10 will return all lists within the range [:10] from the database. If there are x unadvertised lists in the result, the page will only show 10 - x results. I guess the most common way to solve this is for the REST API to accept a number of common filter params which are used in the WHERE clause of the database query. In this case: GET /lists/test at example.com?page=1&count=10&advertised=(0|1|2) 0 - only non-advertised 1 - only advertised 2 - both ** Affects: mailman Importance: Undecided Status: New ** Tags: mailman3 rest ** Description changed: When Postorius GETs a collection of lists from the REST API, it will in most situations only use a subset (the ones that are set to "advertise in list index"). This is a minor issue as long as the request isn't paginated, but can lead to incorrect item counts when it is. Example: GET /lists/test at example.com?page=1&count=10 will return all lists within the range [:10] from the database. If there are x unadvertised list in the result, the page will only show 10 - x results. I guess the most common way to solve this is for the REST API to accept - a number of common filter params which are used for the WHERE clause of + a number of common filter params which are used in the WHERE clause of the database query. In this case: GET /lists/test at example.com?page=1&count=10&advertised=(0|1|2) 0 - only non-advertised 1 - only advertised 2 - both ** Description changed: When Postorius GETs a collection of lists from the REST API, it will in most situations only use a subset (the ones that are set to "advertise in list index"). This is a minor issue as long as the request isn't paginated, but can lead to incorrect item counts when it is. Example: GET /lists/test at example.com?page=1&count=10 will return all lists within the range [:10] from the database. If there - are x unadvertised list in the result, the page will only show 10 - x + are x unadvertised lists in the result, the page will only show 10 - x results. I guess the most common way to solve this is for the REST API to accept a number of common filter params which are used in the WHERE clause of the database query. In this case: GET /lists/test at example.com?page=1&count=10&advertised=(0|1|2) 0 - only non-advertised 1 - only advertised 2 - both -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1190582 Title: Add some common filters to REST API resources that expose collections To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1190582/+subscriptions From mark at msapiro.net Fri Jun 14 02:40:15 2013 From: mark at msapiro.net (Mark Sapiro) Date: Fri, 14 Jun 2013 00:40:15 -0000 Subject: [Bug 1190802] [NEW] admin interface CSRF check fails if listname contains '+' References: <20130614004015.14031.57814.malonedeb@soybean.canonical.com> Message-ID: <20130614004015.14031.57814.malonedeb@soybean.canonical.com> Public bug reported: The hardening of the web admin interface against CSRF attacks which was introduced in Mailman 2.1.15 did not take into account listnames that contain a '+' character and confuses it with a derlimiter causing the check to fail. ** Affects: mailman Importance: High 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/1190802 Title: admin interface CSRF check fails if listname contains '+' To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1190802/+subscriptions From 1190802 at bugs.launchpad.net Fri Jun 14 02:55:09 2013 From: 1190802 at bugs.launchpad.net (Launchpad Bug Tracker) Date: Fri, 14 Jun 2013 00:55:09 -0000 Subject: [Bug 1190802] Re: admin interface CSRF check fails if listname contains '+' References: <20130614004015.14031.57814.malonedeb@soybean.canonical.com> Message-ID: <20130614005510.27959.6969.launchpad@ackee.canonical.com> ** 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/1190802 Title: admin interface CSRF check fails if listname contains '+' To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1190802/+subscriptions From mark at msapiro.net Fri Jun 14 02:55:15 2013 From: mark at msapiro.net (Mark Sapiro) Date: Fri, 14 Jun 2013 00:55:15 -0000 Subject: [Bug 1190802] Re: admin interface CSRF check fails if listname contains '+' References: <20130614004015.14031.57814.malonedeb@soybean.canonical.com> Message-ID: <20130614005516.7769.70236.launchpad@gac.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/1190802 Title: admin interface CSRF check fails if listname contains '+' To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1190802/+subscriptions From robin at jeffries.org Sat Jun 15 00:53:04 2013 From: robin at jeffries.org (Robin J) Date: Fri, 14 Jun 2013 22:53:04 -0000 Subject: [Bug 1094696] Re: Event notifications on postings References: <20121230162347.15671.27720.malonedeb@wampee.canonical.com> Message-ID: <20130614225304.8067.15122.malone@gac.canonical.com> I'm working on this. -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1094696 Title: Event notifications on postings To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1094696/+subscriptions From 1191796 at bugs.launchpad.net Mon Jun 17 15:38:21 2013 From: 1191796 at bugs.launchpad.net (Barry Warsaw) Date: Mon, 17 Jun 2013 13:38:21 -0000 Subject: [Bug 1191796] [NEW] ScriptOptions class can be removed References: <20130617133821.29265.63780.malonedeb@wampee.canonical.com> Message-ID: <20130617133821.29265.63780.malonedeb@wampee.canonical.com> Public bug reported: This convenience class is used in fewer places and can probably be removed for use of standard argparse. ** Affects: mailman Importance: Low Status: Triaged ** 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/1191796 Title: ScriptOptions class can be removed To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1191796/+subscriptions From 1184376 at bugs.launchpad.net Mon Jun 17 15:47:18 2013 From: 1184376 at bugs.launchpad.net (Barry Warsaw) Date: Mon, 17 Jun 2013 13:47:18 -0000 Subject: [Bug 1184376] Re: REST server crashes on "reopen" References: <20130526163258.7720.51480.malonedeb@chaenomeles.canonical.com> Message-ID: <20130617134718.22199.87084.malone@gac.canonical.com> This turned out to be a more extensive branch than anticipated because of weirdness in three competing constraints. To properly shutdown the WSGI server, the .shutdown() method must be called in a separate thread from the server. But because of SQLite constraints, the server must run in the main thread, and because of Python signal handling semantics, the signal handlers must run in the main thread. I solved this, by running a subthread that just waits on an Event and then calls the .shutdown(). The signal handler fires the Event. I also greatly simplified the bin/runner implementation and removed some command line options that weren't really being used. Thanks for the test code! I did a little bit of refactoring, but it was very helpful. ** 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/1184376 Title: REST server crashes on "reopen" To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1184376/+subscriptions From alexander.adolf at condition-alpha.com Mon Jun 17 20:59:53 2013 From: alexander.adolf at condition-alpha.com (Alexander Adolf) Date: Mon, 17 Jun 2013 18:59:53 -0000 Subject: [Bug 1191911] [NEW] [feature-request] calendar appointments support References: <20130617185953.3610.87411.malonedeb@soybean.canonical.com> Message-ID: <20130617185953.3610.87411.malonedeb@soybean.canonical.com> Public bug reported: This is an feature proposal/enhancement request. I am running standardisation groups, and often schedule conference calls, Web meetings, etc. To invite the working group members, I add a mailman list as an invitee to the calendar appointment on my calendar. That way, everybody on the list gets and invitation, and also update emails are delivered when I drag the appointment around on my calendar. Everyone stays in sync. Nice. I don't care who of the list members actually accepts the appointment, because the dates are fixed by other means beforehand (e.g. doodle.com). But of course I never see any accept/decline responses. This causes my calendaring app to consider the appointments as "unconfirmed" since none of the invitees has confirmed their participation. I hence have to manually edit such appointments in order to make them show up as "confirmed, busy". To alleviate this. it would be awesome if mailman could optionally be configured to automatically respond to the sender of an email containing a calendar appointment, and accept the invitation. Maybe this could fit in the content filtering section? That way, mailman operated lists would confirm their attendance on behalf of their members, and the calendar appointment on the organiser's calendar would have the proper status. ** Affects: mailman Importance: Undecided Status: New ** Tags: feature-request -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1191911 Title: [feature-request] calendar appointments support To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1191911/+subscriptions From 1191911 at bugs.launchpad.net Mon Jun 17 21:10:10 2013 From: 1191911 at bugs.launchpad.net (Barry Warsaw) Date: Mon, 17 Jun 2013 19:10:10 -0000 Subject: [Bug 1191911] Re: [feature-request] calendar appointments support References: <20130617185953.3610.87411.malonedeb@soybean.canonical.com> Message-ID: <20130617191010.3769.37999.malone@soybean.canonical.com> This can probably be done as a plugin to the commands processor. I.e. a new command that would be something like 'accept-invite'. Probably would be relatively easy to implement in Mailman 3. ** Changed in: mailman Status: New => Triaged ** Changed in: mailman Importance: Undecided => Wishlist ** 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/1191911 Title: [feature-request] calendar appointments support To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1191911/+subscriptions From alexander.adolf at condition-alpha.com Tue Jun 18 16:34:50 2013 From: alexander.adolf at condition-alpha.com (Alexander Adolf) Date: Tue, 18 Jun 2013 14:34:50 -0000 Subject: [Bug 1191911] Re: [feature-request] calendar appointments support References: <20130617185953.3610.87411.malonedeb@soybean.canonical.com> Message-ID: <20130618143450.22497.81853.malone@gac.canonical.com> Hm, the commands processor is only invoked for mails that go to the -requests address? So I should invite both, the normal list address, and the -requests address? Also, my calendar application does not allow me to edit the message before sending (in fact the mail is sent by a remote calendar server I have no control over), so putting in the new 'accept- invite' command would seem close to impossible in my case. To me it seems that a new archiver would look more promising? That would be presented all messages to the regular list address, and I don't need to remember inviting the -requests address. I presume I should be looking at /src/mailman/archiving? From what I saw it seemed that all archivers are invoked in turn on each message? -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1191911 Title: [feature-request] calendar appointments support To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1191911/+subscriptions From barry at canonical.com Wed Jun 19 04:51:29 2013 From: barry at canonical.com (Barry Warsaw) Date: Wed, 19 Jun 2013 02:51:29 -0000 Subject: [Merge] lp:~barry/mailman/pep435 into lp:mailman Message-ID: <20130619025126.15249.62338.launchpad@ackee.canonical.com> Barry Warsaw has proposed merging lp:~barry/mailman/pep435 into lp:mailman. Requested reviews: Mailman Coders (mailman-coders) For more details, see: https://code.launchpad.net/~barry/mailman/pep435/+merge/170232 Convert from flufl.enums to PEP 435 enums. -- https://code.launchpad.net/~barry/mailman/pep435/+merge/170232 Your team Mailman Coders is requested to review the proposed merge of lp:~barry/mailman/pep435 into lp:mailman. -------------- next part -------------- A non-text attachment was scrubbed... Name: review-diff.txt Type: text/x-diff Size: 15265 bytes Desc: not available URL: From 1157961 at bugs.launchpad.net Fri Jun 21 00:52:07 2013 From: 1157961 at bugs.launchpad.net (Barry Warsaw) Date: Thu, 20 Jun 2013 22:52:07 -0000 Subject: [Bug 1157961] Re: Bounce processing fails to recognize a particular Yahoo bounce References: <20130320202331.18190.73043.malonedeb@gac.canonical.com> Message-ID: <20130620225208.19591.42651.launchpad@gac.canonical.com> ** Changed in: flufl.bounce Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1157961 Title: Bounce processing fails to recognize a particular Yahoo bounce To manage notifications about this bug go to: https://bugs.launchpad.net/flufl.bounce/+bug/1157961/+subscriptions From 1079249 at bugs.launchpad.net Fri Jun 21 00:52:19 2013 From: 1079249 at bugs.launchpad.net (Barry Warsaw) Date: Thu, 20 Jun 2013 22:52:19 -0000 Subject: [Bug 1079249] Re: mail.ru bounces support References: <20121115153334.5140.47622.malonedeb@soybean.canonical.com> Message-ID: <20130620225220.19447.57056.launchpad@gac.canonical.com> ** Changed in: flufl.bounce Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1079249 Title: mail.ru bounces support To manage notifications about this bug go to: https://bugs.launchpad.net/flufl.bounce/+bug/1079249/+subscriptions From 1074592 at bugs.launchpad.net Fri Jun 21 00:52:14 2013 From: 1074592 at bugs.launchpad.net (Barry Warsaw) Date: Thu, 20 Jun 2013 22:52:14 -0000 Subject: [Bug 1074592] Re: Qmail detector fails on non-ASCII messages References: <20121103083426.19132.72322.malonedeb@soybean.canonical.com> Message-ID: <20130620225215.5800.89590.launchpad@soybean.canonical.com> ** Changed in: flufl.bounce Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1074592 Title: Qmail detector fails on non-ASCII messages To manage notifications about this bug go to: https://bugs.launchpad.net/flufl.bounce/+bug/1074592/+subscriptions From 1079254 at bugs.launchpad.net Fri Jun 21 00:52:43 2013 From: 1079254 at bugs.launchpad.net (Barry Warsaw) Date: Thu, 20 Jun 2013 22:52:43 -0000 Subject: [Bug 1079254] Re: Doesn't handle sendmail bounces properly References: <20121115154529.17370.55566.malonedeb@wampee.canonical.com> Message-ID: <20130620225244.14903.61065.launchpad@chaenomeles.canonical.com> ** Changed in: flufl.bounce Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1079254 Title: Doesn't handle sendmail bounces properly To manage notifications about this bug go to: https://bugs.launchpad.net/flufl.bounce/+bug/1079254/+subscriptions From 693134 at bugs.launchpad.net Fri Jun 21 00:52:25 2013 From: 693134 at bugs.launchpad.net (Barry Warsaw) Date: Thu, 20 Jun 2013 22:52:25 -0000 Subject: [Bug 693134] Re: Uncaught bounce from Dovecot when Quota Exceeded References: <20101221185325.20409.19945.malonedeb@soybean.canonical.com> Message-ID: <20130620225226.15089.42012.launchpad@chaenomeles.canonical.com> ** Changed in: flufl.bounce Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/693134 Title: Uncaught bounce from Dovecot when Quota Exceeded To manage notifications about this bug go to: https://bugs.launchpad.net/flufl.bounce/+bug/693134/+subscriptions From abe at debian.org Wed Jun 26 13:31:09 2013 From: abe at debian.org (Axel Beckert) Date: Wed, 26 Jun 2013 11:31:09 -0000 Subject: [Bug 975702] Re: Implement a pipeline in other runners References: <20120407033610.2126.15077.malonedeb@chaenomeles.canonical.com> Message-ID: <20130626113109.26266.32457.malone@soybean.canonical.com> This would be very useful to use SpamAssassin.py together with spam directed to the -bounces@ addresses which seems to rise currently. Those spams are currently always forwarded to the list owner as "Uncaught bounces" and due to new, usually local mail headers usually not filtered at the owner's mail account. -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/975702 Title: Implement a pipeline in other runners To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/975702/+subscriptions