From sakuag333 at gmail.com Sun Dec 9 15:30:20 2012 From: sakuag333 at gmail.com (Sandesh Kumar Agrawal) Date: Sun, 09 Dec 2012 14:30:20 -0000 Subject: [Bug 1082495] Re: Support bracketed prefixes in subject as filters References: <20121123201208.21130.88112.malonedeb@gac.canonical.com> Message-ID: <20121209143020.24715.52294.malone@wampee.canonical.com> I have coded such things in C++, so i am really interested in adding this feature... But i am new to mailman and don't know how to proceed with it. Can u please help me out regarding where should i start ? Thanks -- 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 sakuag333 at gmail.com Sun Dec 9 18:42:13 2012 From: sakuag333 at gmail.com (Sandesh Kumar Agrawal) Date: Sun, 09 Dec 2012 17:42:13 -0000 Subject: [Bug 799689] Re: Add API call >>>delete_domain("example.net") References: <20110620112749.26476.62275.malonedeb@gac.canonical.com> Message-ID: <20121209174213.17130.41349.launchpad@chaenomeles.canonical.com> ** Branch unlinked: lp:mailman.client -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/799689 Title: Add API call >>>delete_domain("example.net") To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/799689/+subscriptions From 1088506 at bugs.launchpad.net Mon Dec 10 16:04:37 2012 From: 1088506 at bugs.launchpad.net (dimytch) Date: Mon, 10 Dec 2012 15:04:37 -0000 Subject: [Bug 1088506] [NEW] The messages of console utilities have wrong encoding References: <20121210150438.16799.53349.malonedeb@chaenomeles.canonical.com> Message-ID: <20121210150438.16799.53349.malonedeb@chaenomeles.canonical.com> Public bug reported: When using LANG=ru_RU.utf8 console utilities are writing me with koi8-r encoding wich is unreadable. I can view help with redirecting 2>&1 | iconv -f koi8-r -t utf-8 but when using utilities they are completely unusable. Archlinux, Linux kserv 3.6.8-1-ARCH #1 SMP PREEMPT Mon Nov 26 22:10:40 CET 2012 x86_64 GNU/Linux mailman 2.1.15-2 Python 2.7.3 Feel free to contact me if more information needed. Also: I don`t know how to program in python. ** Affects: mailman Importance: Undecided Status: New ** Tags: console koi8-r utf-8 ** Attachment added: "I can view help with redirecting 2>&1 | iconv -f koi8-r -t utf-8" https://bugs.launchpad.net/bugs/1088506/+attachment/3456299/+files/mailman-console-0.png -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1088506 Title: The messages of console utilities have wrong encoding To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1088506/+subscriptions From 1082495 at bugs.launchpad.net Tue Dec 11 02:04:02 2012 From: 1082495 at bugs.launchpad.net (Terri) Date: Tue, 11 Dec 2012 01:04:02 -0000 Subject: [Bug 1082495] Re: Support bracketed prefixes in subject as filters References: <20121123201208.21130.88112.malonedeb@gac.canonical.com> Message-ID: <20121211010403.2229.29035.malone@soybean.canonical.com> I'm currently working on adding dynamic sublists (dlists) to mailman 3. It's a feature that Systers wrote for Mailman 2.1 that allows dynamic creation of "sublists" that people can subscribe or unsubscribe from within a list. Currently it uses the email address to do the filtering much like you described, but doesn't do the prefixes. Robin and I hoping to have the port of the dlist code done soon, probably in January, with the goal to have the code be part of the Mailman 3.1 release. Once it's in I think it wouldn't be too much more work to add the bracketed prefixes, perhaps as a configurable option for dlist enabled lists. It might even be a feasible project for a Google Summer of Code student at that point. So, in short, some of the necessary code already exists for Mailman 2.1, it's actively being ported (as in, Robin and I are trying to get together biweekly and hack on it), and it's probably not as huge an undertaking as you imagined as a result. Horray! -- 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 Tue Dec 11 06:58:33 2012 From: mark at msapiro.net (Mark Sapiro) Date: Tue, 11 Dec 2012 05:58:33 -0000 Subject: [Bug 1088506] Re: The messages of console utilities have wrong encoding References: <20121210150438.16799.53349.malonedeb@chaenomeles.canonical.com> Message-ID: <20121211055833.14185.57832.malone@wampee.canonical.com> Mailman's character set for Russian is koi8-r. This means that everything which is displayed in Russian is in the koi8-r character set. You can change this to utf-8 as follows: 1) put add_language('ru', 'Russian', 'utf-8', 'ltr') in mm_cfg.py. 2) run iconv to transliterate all the templates in Mailman's templates/ru/ directory from koi8-r to utf-8. 3) also, run iconv to transliterate Mailman's messages/ru/LC_MESSAGES/mailman.po to utf-8 and then edit the file to replace the line "Content-Type: text/plain; charset=koi8-r\n" near the beginning with "Content-Type: text/plain; charset=utf-8\n" 4) run Mailman's bin/msgfmt.py or the system's msgfmt command to compile messages/ru/LC_MESSAGES/mailman.po into the binary messages/ru/LC_MESSAGES/mailman.mo. Mailman's msgfmt.py is more forgiving of some anomalies which may or may not be present in the Russian message catalog. -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1088506 Title: The messages of console utilities have wrong encoding To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1088506/+subscriptions From 1090753 at bugs.launchpad.net Sat Dec 15 18:10:57 2012 From: 1090753 at bugs.launchpad.net (Barry Warsaw) Date: Sat, 15 Dec 2012 17:10:57 -0000 Subject: [Bug 1090753] [NEW] REST API for subscription moderation References: <20121215171057.12453.26512.malonedeb@wampee.canonical.com> Message-ID: <20121215171057.12453.26512.malonedeb@wampee.canonical.com> Public bug reported: >From IRC: a simple api lookup of subscription attempts would be very nice for now, so moderators can subscribe or ignore them. ** Affects: mailman Importance: High Status: Triaged ** Tags: mailman3 rest -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1090753 Title: REST API for subscription moderation To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1090753/+subscriptions From 1062893 at bugs.launchpad.net Sat Dec 15 21:05:06 2012 From: 1062893 at bugs.launchpad.net (Terri) Date: Sat, 15 Dec 2012 20:05:06 -0000 Subject: [Bug 1062893] Re: No ability to add prefix on subject line References: <20121006153824.15101.97308.malonedeb@chaenomeles.canonical.com> Message-ID: <20121215200506.23838.86189.malone@soybean.canonical.com> subject_prefix exists in Mailman, but we'll need it exposed in the api before postorius can use it. ** Also 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/1062893 Title: No ability to add prefix on subject line To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1062893/+subscriptions From 1062893 at bugs.launchpad.net Sat Dec 15 21:19:00 2012 From: 1062893 at bugs.launchpad.net (Terri) Date: Sat, 15 Dec 2012 20:19:00 -0000 Subject: [Bug 1062893] Re: No ability to add prefix on subject line References: <20121006153824.15101.97308.malonedeb@chaenomeles.canonical.com> Message-ID: <20121215201901.25224.57938.launchpad@gac.canonical.com> ** Tags added: mailman3 ** Tags added: rest -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1062893 Title: No ability to add prefix on subject line To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1062893/+subscriptions From terri at zone12.com Sat Dec 15 22:11:21 2012 From: terri at zone12.com (Terri) Date: Sat, 15 Dec 2012 21:11:21 -0000 Subject: [Merge] lp:~terriko/postorius/ghc12 into lp:postorius Message-ID: <20121215211120.26259.37448.launchpad@ackee.canonical.com> Terri has proposed merging lp:~terriko/postorius/ghc12 into lp:postorius. Requested reviews: Terri (terriko) For more details, see: https://code.launchpad.net/~terriko/postorius/ghc12/+merge/140078 Assorted bug fixes from GHC12 -- https://code.launchpad.net/~terriko/postorius/ghc12/+merge/140078 Your team Mailman Coders is subscribed to branch lp:postorius. -------------- next part -------------- A non-text attachment was scrubbed... Name: review-diff.txt Type: text/x-diff Size: 8680 bytes Desc: not available URL: From terri at zone12.com Sat Dec 15 22:21:19 2012 From: terri at zone12.com (Terri) Date: Sat, 15 Dec 2012 21:21:19 -0000 Subject: [Merge] lp:~terriko/postorius/ghc12 into lp:postorius In-Reply-To: <20121215211120.26259.37448.launchpad@ackee.canonical.com> Message-ID: <20121215212022.24140.44674.codereview@soybean.canonical.com> Review: Approve -- https://code.launchpad.net/~terriko/postorius/ghc12/+merge/140078 Your team Mailman Coders is subscribed to branch lp:postorius. From noreply at launchpad.net Sat Dec 15 22:26:23 2012 From: noreply at launchpad.net (noreply at launchpad.net) Date: Sat, 15 Dec 2012 21:26:23 -0000 Subject: [Merge] lp:~terriko/postorius/ghc12 into lp:postorius In-Reply-To: <20121215211120.26259.37448.launchpad@ackee.canonical.com> Message-ID: <20121215212623.29817.46961.launchpad@ackee.canonical.com> The proposal to merge lp:~terriko/postorius/ghc12 into lp:postorius has been updated. Status: Needs review => Merged For more details, see: https://code.launchpad.net/~terriko/postorius/ghc12/+merge/140078 -- https://code.launchpad.net/~terriko/postorius/ghc12/+merge/140078 Your team Mailman Coders is subscribed to branch lp:postorius. From noreply at launchpad.net Sat Dec 15 22:37:20 2012 From: noreply at launchpad.net (noreply at launchpad.net) Date: Sat, 15 Dec 2012 21:37:20 -0000 Subject: [Merge] lp:~sunu0000/postorius/newuser_hint into lp:postorius In-Reply-To: <20121031090721.10097.6460.launchpad@ackee.canonical.com> Message-ID: <20121215213720.1903.77209.launchpad@ackee.canonical.com> The proposal to merge lp:~sunu0000/postorius/newuser_hint into lp:postorius has been updated. Status: Needs review => Merged For more details, see: https://code.launchpad.net/~sunu0000/postorius/newuser_hint/+merge/132263 -- https://code.launchpad.net/~sunu0000/postorius/newuser_hint/+merge/132263 Your team Mailman Coders is subscribed to branch lp:postorius. From 1062893 at bugs.launchpad.net Sat Dec 15 22:46:45 2012 From: 1062893 at bugs.launchpad.net (Terri) Date: Sat, 15 Dec 2012 21:46:45 -0000 Subject: [Bug 1062893] Re: No ability to add prefix on subject line References: <20121006153824.15101.97308.malonedeb@chaenomeles.canonical.com> Message-ID: <20121215214646.12415.60266.launchpad@wampee.canonical.com> ** Changed in: postorius Status: Triaged => 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/1062893 Title: No ability to add prefix on subject line To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1062893/+subscriptions From terri at zone12.com Sat Dec 15 22:35:23 2012 From: terri at zone12.com (Terri) Date: Sat, 15 Dec 2012 21:35:23 -0000 Subject: [Merge] lp:~sunu0000/postorius/newuser_hint into lp:postorius In-Reply-To: <20121031090721.10097.6460.launchpad@ackee.canonical.com> Message-ID: <20121215213444.25796.77936.codereview@chaenomeles.canonical.com> Review: Approve -- https://code.launchpad.net/~sunu0000/postorius/newuser_hint/+merge/132263 Your team Mailman Coders is subscribed to branch lp:postorius. From 967954 at bugs.launchpad.net Sat Dec 15 23:19:00 2012 From: 967954 at bugs.launchpad.net (Barry Warsaw) Date: Sat, 15 Dec 2012 22:19:00 -0000 Subject: [Bug 967954] Re: IMessageStore should be exposed as a top level REST resource References: <20120329031151.18797.20416.malonedeb@chaenomeles.canonical.com> Message-ID: <20121215221900.25751.13524.malone@chaenomeles.canonical.com> When we do this, lists/foo at example.com/held/1 should not return the message text in its resource under the 'msg' key. That should just be a link to the IMessageStore resource. See HeldMessage.details() in rest/moderation.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/967954 Title: IMessageStore should be exposed as a top level REST resource To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/967954/+subscriptions From 1090753 at bugs.launchpad.net Sun Dec 16 15:51:21 2012 From: 1090753 at bugs.launchpad.net (Launchpad Bug Tracker) Date: Sun, 16 Dec 2012 14:51:21 -0000 Subject: [Bug 1090753] Re: REST API for subscription moderation References: <20121215171057.12453.26512.malonedeb@wampee.canonical.com> Message-ID: <20121216145134.13496.84683.launchpad@ackee.canonical.com> ** Branch linked: lp:~barry/mailman/lp1090753 -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1090753 Title: REST API for subscription moderation To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1090753/+subscriptions From 1091321 at bugs.launchpad.net Mon Dec 17 17:38:14 2012 From: 1091321 at bugs.launchpad.net (Barry Warsaw) Date: Mon, 17 Dec 2012 16:38:14 -0000 Subject: [Bug 1091321] [NEW] send_goodbye_message() is broken References: <20121217163814.24179.91633.malonedeb@soybean.canonical.com> Message-ID: <20121217163814.24179.91633.malonedeb@soybean.canonical.com> Public bug reported: in app/notifications.py This function is broken because it references mlist.goodbye_msg. That attribute no longer exists and besides it should be using the ITemplateLoader scheme just like send_welcome_message(). ** Affects: mailman Importance: Undecided Status: Triaged ** Tags: mailman3 -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1091321 Title: send_goodbye_message() is broken To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1091321/+subscriptions From 1062893 at bugs.launchpad.net Tue Dec 18 01:26:04 2012 From: 1062893 at bugs.launchpad.net (Barry Warsaw) Date: Tue, 18 Dec 2012 00:26:04 -0000 Subject: [Bug 1062893] Re: No ability to add prefix on subject line References: <20121006153824.15101.97308.malonedeb@chaenomeles.canonical.com> Message-ID: <20121218002605.23169.58254.launchpad@soybean.canonical.com> ** Branch linked: lp:~terriko/mailman/subject_prefix ** Changed in: mailman Assignee: (unassigned) => Terri (terriko) ** Changed in: mailman Importance: Undecided => High ** Changed in: mailman Status: New => In Progress ** Changed in: mailman Milestone: None => 3.0.0b3 ** 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/1062893 Title: No ability to add prefix on subject line To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1062893/+subscriptions From 1091321 at bugs.launchpad.net Tue Dec 18 04:28:31 2012 From: 1091321 at bugs.launchpad.net (Barry Warsaw) Date: Tue, 18 Dec 2012 03:28:31 -0000 Subject: [Bug 1091321] Re: send_goodbye_message() is broken References: <20121217163814.24179.91633.malonedeb@soybean.canonical.com> Message-ID: <20121218032831.25503.39234.launchpad@chaenomeles.canonical.com> ** Branch linked: lp:~barry/mailman/lp1090753 ** Changed in: mailman Status: Triaged => In Progress ** Changed in: mailman Importance: Undecided => High ** Changed in: mailman Assignee: (unassigned) => Barry Warsaw (barry) -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1091321 Title: send_goodbye_message() is broken To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1091321/+subscriptions From 1090753 at bugs.launchpad.net Tue Dec 18 04:29:02 2012 From: 1090753 at bugs.launchpad.net (Barry Warsaw) Date: Tue, 18 Dec 2012 03:29:02 -0000 Subject: [Bug 1090753] Re: REST API for subscription moderation References: <20121215171057.12453.26512.malonedeb@wampee.canonical.com> Message-ID: <20121218032903.12987.9473.launchpad@wampee.canonical.com> ** Changed in: mailman Assignee: (unassigned) => Barry Warsaw (barry) -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1090753 Title: REST API for subscription moderation To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1090753/+subscriptions From 1091321 at bugs.launchpad.net Tue Dec 18 05:05:53 2012 From: 1091321 at bugs.launchpad.net (Barry Warsaw) Date: Tue, 18 Dec 2012 04:05:53 -0000 Subject: [Bug 1091321] Re: send_goodbye_message() is broken References: <20121217163814.24179.91633.malonedeb@soybean.canonical.com> Message-ID: <20121218040554.24823.26366.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/1091321 Title: send_goodbye_message() is broken To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1091321/+subscriptions From 1090753 at bugs.launchpad.net Tue Dec 18 05:07:05 2012 From: 1090753 at bugs.launchpad.net (Barry Warsaw) Date: Tue, 18 Dec 2012 04:07:05 -0000 Subject: [Bug 1090753] Re: REST API for subscription moderation References: <20121215171057.12453.26512.malonedeb@wampee.canonical.com> Message-ID: <20121218040705.25189.43521.malone@chaenomeles.canonical.com> Please note that this includes the change to the held message JSON representation we chatted about on IRC. Specifically, the `data` key is flatted into the top-level JSON representation, and the _mod_* keys that mailman.client uses are inserted without their "_mod_" prefix. ** Changed in: mailman Status: Triaged => 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/1090753 Title: REST API for subscription moderation To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1090753/+subscriptions From aurelien at bompard.org Tue Dec 18 10:34:59 2012 From: aurelien at bompard.org (=?utf-8?q?Aur=C3=A9lien_Bompard?=) Date: Tue, 18 Dec 2012 09:34:59 -0000 Subject: [Bug 1091586] [NEW] Frequent OperationalError: database is locked with sqlite References: <20121218093500.12946.57302.malonedeb@wampee.canonical.com> Message-ID: <20121218093500.12946.57302.malonedeb@wampee.canonical.com> Public bug reported: I'm seeing frequent locking errors with SQLite on the current version of mailman3 from bzr. Here's an example traceback : Traceback (most recent call last): File "/srv/dev/mailman/bin/runner", line 9, in load_entry_point('mailman==3.0.0b2-', 'console_scripts', 'runner')() File "/srv/dev/mailman/mailman3/mailman/src/mailman/bin/runner.py", line 253, in main runner.run() File "/srv/dev/mailman/mailman3/mailman/src/mailman/core/runner.py", line 96, in run filecnt = self._one_iteration() File "/srv/dev/mailman/mailman3/mailman/src/mailman/core/runner.py", line 173, in _one_iteration config.db.commit() File "/srv/dev/mailman/mailman3/mailman/src/mailman/database/base.py", line 77, in commit self.store.commit() File "/srv/dev/mailman/lib/python2.6/site-packages/storm-0.19-py2.6-linux-x86_64.egg/storm/store.py", line 122, in commit self._connection.commit() File "/srv/dev/mailman/lib/python2.6/site-packages/storm-0.19-py2.6-linux-x86_64.egg/storm/databases/sqlite.py", line 126, in commit self.raw_execute("COMMIT", _end=True) File "/srv/dev/mailman/lib/python2.6/site-packages/storm-0.19-py2.6-linux-x86_64.egg/storm/databases/sqlite.py", line 154, in raw_execute return Connection.raw_execute(self, statement, params) File "/srv/dev/mailman/lib/python2.6/site-packages/storm-0.19-py2.6-linux-x86_64.egg/storm/database.py", line 322, in raw_execute self._check_disconnect(raw_cursor.execute, *args) File "/srv/dev/mailman/lib/python2.6/site-packages/storm-0.19-py2.6-linux-x86_64.egg/storm/database.py", line 371, in _check_disconnect return function(*args, **kwargs) sqlite3.OperationalError: database is locked It happens during the normal processing of Mailman, not while using the API (to my knowledge), so it seems different from bug #856004. I can reproduce this easily by letting Mailman work for some time. After the locking error, new messages are stuck in var/queue/pipeline: $ ls var/queue/* var/queue/archive: var/queue/bad: var/queue/bounces: var/queue/command: var/queue/digest: var/queue/in: var/queue/lmtp: var/queue/nntp: var/queue/out: var/queue/pipeline: 1355781960.9870529+18f0acdf07aab616f793ecf76acfa1994e62b3a9.pck 1355799347.787621+213f3a6a971717ad1ba27f3d56b65767747a45da.pck 1355814973.8623891+4e66eeadef9b8c9ae99e4ed022c6c93f5af75c05.pck 1355782349.546113+ee14cb323574b647d9014f742e3f505e388d553e.pck 1355800543.460628+c455625c1ad86a5a77c9c515fcb6d555ba439b19.pck 1355815808.8860879+ca3fb5f45999e47c92756489daa951672ba4304d.pck 1355792739.8787439+19973fbcf763f036655aa0a7d477231246afdfbd.pck 1355802301.7830889+7989a3199c7eb491b65176937c0c1658cca9d46d.pck 1355820018.1813829+5005ded04da3574a7f3cd7472c9d635c577b6c32.pck 1355794764.597765+6cf379ad16c948117bb65f0aed0b3c230268ffd2.pck 1355803681.7455051+52d185cdcaecaf883bd43f375f5253567f5cd568.pck 1355822188.0491021+6a3cab9831d03b4f94475f745fa508c5126116b4.pck 1355794889.8323901+e14e25e342ec59709266040d830d7e12be2a1261.pck 1355805362.052228+422e573a6117edb7aae1acf9150ac58c210cedba.pck 1355822293.2363911+627f13dd2121bcb0f1916bc0448cc3b8adc9ad1f.pck 1355795937.2442579+62193d05ee80c6a22213cf2ff211c135fb7d38d9.pck 1355807374.9844501+8de57ab53819fac59d64705bcc56f86899d22634.pck 1355798662.8335559+554da4e7690e116e6fabee5764ac69829dc25685.pck 1355808273.143533+ed1acbf580c596ed921e062ece575877f0c9304b.pck var/queue/rest: var/queue/retry: var/queue/shunt: 1355776302.1302171+c657867b33bf6e37554ff83ee26f4096a77c1114.pck var/queue/virgin: And I need to restart mailman to make it process them again. The locked caused the message to be shunted. I'll attach the mailman.log file, where you'll see many "database is locked" errors, happening on different requests. ** 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/1091586 Title: Frequent OperationalError: database is locked with sqlite To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1091586/+subscriptions From aurelien at bompard.org Tue Dec 18 10:36:27 2012 From: aurelien at bompard.org (=?utf-8?q?Aur=C3=A9lien_Bompard?=) Date: Tue, 18 Dec 2012 09:36:27 -0000 Subject: [Bug 1091586] Re: Frequent OperationalError: database is locked with sqlite References: <20121218093500.12946.57302.malonedeb@wampee.canonical.com> Message-ID: <20121218093627.12573.86005.malone@wampee.canonical.com> ** Attachment added: "The log file with errors" https://bugs.launchpad.net/mailman/+bug/1091586/+attachment/3462818/+files/mailman.log.gz -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1091586 Title: Frequent OperationalError: database is locked with sqlite To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1091586/+subscriptions From aurelien at bompard.org Tue Dec 18 12:10:05 2012 From: aurelien at bompard.org (=?utf-8?q?Aur=C3=A9lien_Bompard?=) Date: Tue, 18 Dec 2012 11:10:05 -0000 Subject: [Bug 1091586] Re: Frequent OperationalError: database is locked with sqlite References: <20121218093500.12946.57302.malonedeb@wampee.canonical.com> Message-ID: <20121218111005.25412.63813.malone@gac.canonical.com> I just restarted Mailman and got two tracebacks at exactly the same time, from two different processes (the PID number is logged too). Could Mailman be unqueuing from the pipeline queue in parallel processes ? Could that cause the SQLite lock ? For reference, the two tracebacks in the log : Dec 18 05:05:38 2012 (31146) Uncaught runner archive exception: database is locked Dec 18 05:05:38 2012 (31146) Traceback (most recent call last): File "/srv/dev/mailman/mailman3/mailman/src/mailman/core/runner.py", line 138, in _one_iteration self._process_one_file(msg, msgdata) File "/srv/dev/mailman/mailman3/mailman/src/mailman/core/runner.py", line 194, in _process_one_file else getUtility(IListManager).get(unicode(listname))) File "/srv/dev/mailman/mailman3/mailman/src/mailman/database/transaction.py", line 78, in wrapper return function(args[0], config.db.store, *args[1:], **kws) File "/srv/dev/mailman/mailman3/mailman/src/mailman/model/listmanager.py", line 69, in get return store.find(MailingList, MailingList._list_id == list_id).one() File "/srv/dev/mailman/lib/python2.6/site-packages/storm-0.19-py2.6-linux-x86_64.egg/storm/store.py", line 1142, in one result = self._store._connection.execute(select) File "/srv/dev/mailman/lib/python2.6/site-packages/storm-0.19-py2.6-linux-x86_64.egg/storm/database.py", line 238, in execute raw_cursor = self.raw_execute(statement, params) File "/srv/dev/mailman/lib/python2.6/site-packages/storm-0.19-py2.6-linux-x86_64.egg/storm/databases/sqlite.py", line 154, in raw_execute return Connection.raw_execute(self, statement, params) File "/srv/dev/mailman/lib/python2.6/site-packages/storm-0.19-py2.6-linux-x86_64.egg/storm/database.py", line 322, in raw_execute self._check_disconnect(raw_cursor.execute, *args) File "/srv/dev/mailman/lib/python2.6/site-packages/storm-0.19-py2.6-linux-x86_64.egg/storm/database.py", line 371, in _check_disconnect return function(*args, **kwargs) OperationalError: database is locked Dec 18 05:05:38 2012 (31146) SHUNTING: 1355828738.0138969+0a282d3d40cc1528e1d41b992b070b492449a641 Dec 18 11:05:38 2012 (31144) Uncaught runner digest exception: database is locked Dec 18 11:05:38 2012 (31144) Traceback (most recent call last): File "/srv/dev/mailman/mailman3/mailman/src/mailman/core/runner.py", line 138, in _one_iteration self._process_one_file(msg, msgdata) File "/srv/dev/mailman/mailman3/mailman/src/mailman/core/runner.py", line 222, in _process_one_file keepqueued = self._dispose(mlist, msg, msgdata) File "/srv/dev/mailman/mailman3/mailman/src/mailman/runners/digest.py", line 373, in _dispose for address, delivery_mode in mlist.last_digest_recipients: File "/srv/dev/mailman/mailman3/mailman/src/mailman/model/mailinglist.py", line 347, in last_digest_recipients results.remove() File "/srv/dev/mailman/lib/python2.6/site-packages/storm-0.19-py2.6-linux-x86_64.egg/storm/store.py", line 1183, in remove Delete(self._where, self._find_spec.default_cls_info.table)) File "/srv/dev/mailman/lib/python2.6/site-packages/storm-0.19-py2.6-linux-x86_64.egg/storm/database.py", line 238, in execute raw_cursor = self.raw_execute(statement, params) File "/srv/dev/mailman/lib/python2.6/site-packages/storm-0.19-py2.6-linux-x86_64.egg/storm/databases/sqlite.py", line 154, in raw_execute return Connection.raw_execute(self, statement, params) File "/srv/dev/mailman/lib/python2.6/site-packages/storm-0.19-py2.6-linux-x86_64.egg/storm/database.py", line 322, in raw_execute self._check_disconnect(raw_cursor.execute, *args) File "/srv/dev/mailman/lib/python2.6/site-packages/storm-0.19-py2.6-linux-x86_64.egg/storm/database.py", line 371, in _check_disconnect return function(*args, **kwargs) OperationalError: database is locked Dec 18 11:05:38 2012 (31144) SHUNTING: 1355828738.035006+8f81ee5185d05d54c65181474667db62072a6756 About 7 messages have been unqueued from the pipeline queue before the locking error happened. -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1091586 Title: Frequent OperationalError: database is locked with sqlite To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1091586/+subscriptions From 1091586 at bugs.launchpad.net Wed Dec 19 21:56:55 2012 From: 1091586 at bugs.launchpad.net (Barry Warsaw) Date: Wed, 19 Dec 2012 20:56:55 -0000 Subject: [Bug 1091586] Re: Frequent OperationalError: database is locked with sqlite References: <20121218093500.12946.57302.malonedeb@wampee.canonical.com> Message-ID: <20121219205656.15513.62947.launchpad@wampee.canonical.com> ** 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/1091586 Title: Frequent OperationalError: database is locked with sqlite To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1091586/+subscriptions From 1092973 at bugs.launchpad.net Fri Dec 21 21:15:47 2012 From: 1092973 at bugs.launchpad.net (=?utf-8?q?Carn=C3=AB_Draug?=) Date: Fri, 21 Dec 2012 20:15:47 -0000 Subject: [Bug 1092973] [NEW] implement flame-retardant option References: <20121221201547.26483.59478.malonedeb@soybean.canonical.com> Message-ID: <20121221201547.26483.59478.malonedeb@soybean.canonical.com> Public bug reported: This is more of a feature request than a bug. I have added it to my todo list but it's been there long enough to know that I probably will never get around to do it. I'm posting it here as an idea in case anyone also finds it good and wishes to pick it up. I had read about the idea the first time on this post (http://www.shirky.com/writings/group_user.html) which does mention mailman. It's a bit long post but near the end, on the "Novel Operations on Social Facts" section proposes some ideas for mailing lists. There's other worthy ideas there but the one I was planning to implement was the flame retardant in which basically if a user has been too active, its e-mails would be sent with a delay. I think that's pretty neat. Recently the mailing list where I am now is facing such problems. This could be set to the whole mailing list or as an alternative to place an user under moderation (for those that are actual helpful members of the mailing list but have a tendency to get too much involved in flame wars). ** 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/1092973 Title: implement flame-retardant option To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1092973/+subscriptions From 1091586 at bugs.launchpad.net Sun Dec 23 19:16:04 2012 From: 1091586 at bugs.launchpad.net (Barry Warsaw) Date: Sun, 23 Dec 2012 18:16:04 -0000 Subject: [Bug 1091586] Re: Frequent OperationalError: database is locked with sqlite References: <20121218093500.12946.57302.malonedeb@wampee.canonical.com> Message-ID: <20121223181605.2476.40274.malone@chaenomeles.canonical.com> A couple of thoughts: - Could you try again with the latest bzr head? Or perhaps with 3.0b3 which I'll be releasing soon? You'll have to switch to Python 2.7 though. - I'm seeing lots of errors in HyperKitty before the database locked error. I wonder if one of those errors is causing a transaction to stay open too long? If one process gets the error and doesn't abort the current transaction, it'll cause this database lock error in another process. Because of the way Storm is used, just about anything, including reading data, will open a transaction (you see this often in REST test cases). - Perhaps you can disable HyperKitty and run your tests again? -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1091586 Title: Frequent OperationalError: database is locked with sqlite To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1091586/+subscriptions From 1062963 at bugs.launchpad.net Sun Dec 23 19:30:47 2012 From: 1062963 at bugs.launchpad.net (Barry Warsaw) Date: Sun, 23 Dec 2012 18:30:47 -0000 Subject: [Bug 1062963] Re: Admin notification not received References: <20121006182248.14546.68625.malonedeb@gac.canonical.com> Message-ID: <20121223183047.15388.98526.malone@wampee.canonical.com> OP: Can you provide more information? What changes do you expect to get notified on? Do you have a way to reproduce the problem? There are two attributes which control admin notifications. admin_immed_notify controls whether the admin is notified when a subscription (or unsubscription) request is held for moderator approval. admin_notify_mchanges controls whether the administrator gets a notification when a user is subscribed to the mailing list. ** Changed in: mailman Status: New => 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/1062963 Title: Admin notification not received To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1062963/+subscriptions From 1047286 at bugs.launchpad.net Sun Dec 23 20:48:58 2012 From: 1047286 at bugs.launchpad.net (Barry Warsaw) Date: Sun, 23 Dec 2012 19:48:58 -0000 Subject: [Bug 1047286] Re: Notifications for core events References: <20120907111418.9617.11504.malonedeb@wampee.canonical.com> Message-ID: <20121223194858.15306.79689.malone@wampee.canonical.com> I added events for subscriptions and unsubscriptions. I don't think it's possible right now to add an event for a new thread, since this isn't something that Mailman itself tracks. An archiver would have to send that notification, but that may in fact be impossible for remote archivers. Actually, I don't think the core currently sends event notifications on postings. Please open a separate issue for that. ** Changed in: mailman Milestone: None => 3.0.0b3 ** Changed in: mailman Assignee: (unassigned) => Barry Warsaw (barry) ** Changed in: mailman Importance: Low => High ** Changed in: mailman Status: Confirmed => 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/1047286 Title: Notifications for core events To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1047286/+subscriptions From 1035033 at bugs.launchpad.net Sun Dec 23 21:08:02 2012 From: 1035033 at bugs.launchpad.net (Barry Warsaw) Date: Sun, 23 Dec 2012 20:08:02 -0000 Subject: [Bug 1035033] Re: bin/mailman --help could be improved References: <20120809185744.5261.62768.malonedeb@gac.canonical.com> Message-ID: <20121223200802.15347.30645.malone@wampee.canonical.com> I'm going to take a strict approach to this bug, and will attempt to improve the documentation. ** Changed in: mailman Status: Confirmed => In Progress ** Changed in: mailman Milestone: None => 3.0.0b3 ** Changed in: mailman Assignee: Stephen Turnbull (stephen-xemacs) => Barry Warsaw (barry) ** Changed in: mailman Importance: Wishlist => High ** 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/1035033 Title: bin/mailman --help could be improved To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1035033/+subscriptions From 1065447 at bugs.launchpad.net Wed Dec 26 05:41:40 2012 From: 1065447 at bugs.launchpad.net (Launchpad Bug Tracker) Date: Wed, 26 Dec 2012 04:41:40 -0000 Subject: [Bug 1065447] Re: Feature request: REST api to verify password References: <20121011100315.8642.7986.malonedeb@gac.canonical.com> Message-ID: <20121226044159.9669.66712.launchpad@ackee.canonical.com> ** Branch linked: lp:~barry/mailman/lp1065447 -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1065447 Title: Feature request: REST api to verify password To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1065447/+subscriptions From 1065447 at bugs.launchpad.net Thu Dec 27 00:51:19 2012 From: 1065447 at bugs.launchpad.net (Barry Warsaw) Date: Wed, 26 Dec 2012 23:51:19 -0000 Subject: [Bug 1065447] Re: Feature request: REST api to verify password References: <20121011100315.8642.7986.malonedeb@gac.canonical.com> Message-ID: <20121226235119.15180.300.malone@wampee.canonical.com> Here's how I'm going to do this. You post to http://.../users/{id}/login and the form data must contain exactly one parameter `cleartext_password`. If the value matches the stored, hashed password, an HTTP 204 (No Content) is returned. If they do not match, an HTTP 403 (Forbidden) is returned. There is no content body in either case, and thus the POST creates no addressable resource. The nice thing is that this will support hash migration as per passlib. ** Changed in: mailman Milestone: None => 3.0.0b3 ** Changed in: mailman Assignee: (unassigned) => Barry Warsaw (barry) ** Changed in: mailman Importance: Undecided => High ** Changed in: mailman Status: New => 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/1065447 Title: Feature request: REST api to verify password To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1065447/+subscriptions From 1065447 at bugs.launchpad.net Thu Dec 27 01:01:36 2012 From: 1065447 at bugs.launchpad.net (Barry Warsaw) Date: Thu, 27 Dec 2012 00:01:36 -0000 Subject: [Bug 1065447] Re: Feature request: REST api to verify password References: <20121011100315.8642.7986.malonedeb@gac.canonical.com> Message-ID: <20121227000137.26057.9798.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/1065447 Title: Feature request: REST api to verify password To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1065447/+subscriptions From sophron at latthi.com Sun Dec 30 17:23:47 2012 From: sophron at latthi.com (George Chatzisofroniou) Date: Sun, 30 Dec 2012 16:23:47 -0000 Subject: [Bug 1094696] [NEW] Event notifications on postings References: <20121230162347.15671.27720.malonedeb@wampee.canonical.com> Message-ID: <20121230162347.15671.27720.malonedeb@wampee.canonical.com> Public bug reported: It looks like there is no way for a MM3 plugin to be signaled for a new posting. It would be great if core could provide a notification to the plugins that have subscribed to this event when a new post occurs. This notification should carry some interesting information, like the number of recipients and the message size. This request is also essential for the MM3-Metrics module (https://launchpad.net/mm3-metrics). ** Affects: mailman Importance: Undecided Status: New ** Tags: events mailman3 metrics modules notification plugins post -- 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 sophron at latthi.com Sun Dec 30 17:36:07 2012 From: sophron at latthi.com (George Chatzisofroniou) Date: Sun, 30 Dec 2012 16:36:07 -0000 Subject: [Bug 1047286] Re: Notifications for core events References: <20120907111418.9617.11504.malonedeb@wampee.canonical.com> Message-ID: <20121230163607.15671.17348.malone@wampee.canonical.com> Thanks for adding this. Yes, i guess that threads is a complex issue and i probably need to get with the HK guys on that one. I think that determining threads should be a common service though. I just requested notifications on postings: https://bugs.launchpad.net/mailman/+bug/1094696 -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1047286 Title: Notifications for core events To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1047286/+subscriptions From sophron at latthi.com Sun Dec 30 18:09:12 2012 From: sophron at latthi.com (George Chatzisofroniou) Date: Sun, 30 Dec 2012 17:09:12 -0000 Subject: [Bug 1094696] Re: Event notifications on postings References: <20121230162347.15671.27720.malonedeb@wampee.canonical.com> Message-ID: <20121230170913.14994.78490.launchpad@wampee.canonical.com> ** Description changed: It looks like there is no way for a MM3 plugin to be signaled for a new posting. It would be great if core could provide a notification to the plugins that have subscribed to this event when a new post occurs. This notification should carry some interesting information, like the number of recipients and the message size. - This request is also essential for the MM3-Metrics module + This feature is also essential for the MM3-Metrics module (https://launchpad.net/mm3-metrics). -- 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 975692 at bugs.launchpad.net Sun Dec 30 19:35:22 2012 From: 975692 at bugs.launchpad.net (Barry Warsaw) Date: Sun, 30 Dec 2012 18:35:22 -0000 Subject: [Bug 975692] Re: Allow style assignments when creating a list through REST References: <20120407032203.3836.46652.malonedeb@gac.canonical.com> Message-ID: <20121230183523.23216.55192.launchpad@gac.canonical.com> ** Changed in: mailman Milestone: None => 3.0.0b3 ** Changed in: mailman Assignee: (unassigned) => Barry Warsaw (barry) ** Changed in: mailman Importance: Low => High ** Changed in: mailman Status: Confirmed => 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/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 From 975692 at bugs.launchpad.net Sun Dec 30 20:53:20 2012 From: 975692 at bugs.launchpad.net (Barry Warsaw) Date: Sun, 30 Dec 2012 19:53:20 -0000 Subject: [Bug 975692] Re: Allow style assignments when creating a list through REST References: <20120407032203.3836.46652.malonedeb@gac.canonical.com> Message-ID: <20121230195322.26525.60996.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/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 From 1090753 at bugs.launchpad.net Mon Dec 31 19:10:24 2012 From: 1090753 at bugs.launchpad.net (Barry Warsaw) Date: Mon, 31 Dec 2012 18:10:24 -0000 Subject: [Bug 1090753] Re: REST API for subscription moderation References: <20121215171057.12453.26512.malonedeb@wampee.canonical.com> Message-ID: <20121231181025.23876.76043.launchpad@gac.canonical.com> ** Changed in: mailman 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/1090753 Title: REST API for subscription moderation To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1090753/+subscriptions From 1074374 at bugs.launchpad.net Mon Dec 31 19:10:14 2012 From: 1074374 at bugs.launchpad.net (Barry Warsaw) Date: Mon, 31 Dec 2012 18:10:14 -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: <20121231181016.2435.40176.launchpad@chaenomeles.canonical.com> ** Changed in: mailman 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/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 1073506 at bugs.launchpad.net Mon Dec 31 19:10:07 2012 From: 1073506 at bugs.launchpad.net (Barry Warsaw) Date: Mon, 31 Dec 2012 18:10:07 -0000 Subject: [Bug 1073506] Re: Drop support for Python 2.6 References: <20121031101923.19289.16392.malonedeb@soybean.canonical.com> Message-ID: <20121231181008.26184.46713.launchpad@soybean.canonical.com> ** Changed in: mailman 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/1073506 Title: Drop support for Python 2.6 To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1073506/+subscriptions From 1047286 at bugs.launchpad.net Mon Dec 31 19:09:32 2012 From: 1047286 at bugs.launchpad.net (Barry Warsaw) Date: Mon, 31 Dec 2012 18:09:32 -0000 Subject: [Bug 1047286] Re: Notifications for core events References: <20120907111418.9617.11504.malonedeb@wampee.canonical.com> Message-ID: <20121231180933.23461.84575.launchpad@gac.canonical.com> ** Changed in: mailman 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/1047286 Title: Notifications for core events To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1047286/+subscriptions From 1065447 at bugs.launchpad.net Mon Dec 31 19:10:00 2012 From: 1065447 at bugs.launchpad.net (Barry Warsaw) Date: Mon, 31 Dec 2012 18:10:00 -0000 Subject: [Bug 1065447] Re: Feature request: REST api to verify password References: <20121011100315.8642.7986.malonedeb@gac.canonical.com> Message-ID: <20121231181001.23839.30110.launchpad@gac.canonical.com> ** Changed in: mailman 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/1065447 Title: Feature request: REST api to verify password To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1065447/+subscriptions From 1054730 at bugs.launchpad.net Mon Dec 31 19:09:40 2012 From: 1054730 at bugs.launchpad.net (Barry Warsaw) Date: Mon, 31 Dec 2012 18:09:40 -0000 Subject: [Bug 1054730] Re: Set the verified_on flag for IAddress through the REST API References: <20120922201416.22633.99405.malonedeb@chaenomeles.canonical.com> Message-ID: <20121231180941.2558.80955.launchpad@chaenomeles.canonical.com> ** Changed in: mailman 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/1054730 Title: Set the verified_on flag for IAddress through the REST API To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1054730/+subscriptions From 1035033 at bugs.launchpad.net Mon Dec 31 19:09:07 2012 From: 1035033 at bugs.launchpad.net (Barry Warsaw) Date: Mon, 31 Dec 2012 18:09:07 -0000 Subject: [Bug 1035033] Re: bin/mailman --help could be improved References: <20120809185744.5261.62768.malonedeb@gac.canonical.com> Message-ID: <20121231180908.23712.69423.launchpad@gac.canonical.com> ** Changed in: mailman 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/1035033 Title: bin/mailman --help could be improved To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1035033/+subscriptions From 982551 at bugs.launchpad.net Mon Dec 31 19:09:00 2012 From: 982551 at bugs.launchpad.net (Barry Warsaw) Date: Mon, 31 Dec 2012 18:09:00 -0000 Subject: [Bug 982551] Re: Relative paths in 'mailman start -C' are broken References: <20120415194535.4165.41414.malonedeb@gac.canonical.com> Message-ID: <20121231180901.23502.90473.launchpad@gac.canonical.com> ** Changed in: mailman 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/982551 Title: Relative paths in 'mailman start -C' are broken To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/982551/+subscriptions From 975692 at bugs.launchpad.net Mon Dec 31 19:08:50 2012 From: 975692 at bugs.launchpad.net (Barry Warsaw) Date: Mon, 31 Dec 2012 18:08:50 -0000 Subject: [Bug 975692] Re: Allow style assignments when creating a list through REST References: <20120407032203.3836.46652.malonedeb@gac.canonical.com> Message-ID: <20121231180851.23338.95933.launchpad@gac.canonical.com> ** Changed in: mailman 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/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 From 1091321 at bugs.launchpad.net Mon Dec 31 19:10:31 2012 From: 1091321 at bugs.launchpad.net (Barry Warsaw) Date: Mon, 31 Dec 2012 18:10:31 -0000 Subject: [Bug 1091321] Re: send_goodbye_message() is broken References: <20121217163814.24179.91633.malonedeb@soybean.canonical.com> Message-ID: <20121231181032.2640.3970.launchpad@chaenomeles.canonical.com> ** Changed in: mailman 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/1091321 Title: send_goodbye_message() is broken To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1091321/+subscriptions From 1042828 at bugs.launchpad.net Mon Dec 31 19:14:54 2012 From: 1042828 at bugs.launchpad.net (Barry Warsaw) Date: Mon, 31 Dec 2012 18:14:54 -0000 Subject: [Bug 1042828] Re: UI web URLs should be per-mailinglist References: <20120828161430.6858.57270.malonedeb@gac.canonical.com> Message-ID: <20121231181456.23921.14333.launchpad@gac.canonical.com> ** Changed in: mailman Milestone: 3.0.0b3 => 3.0.0b4 -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1042828 Title: UI web URLs should be per-mailinglist To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1042828/+subscriptions From 965532 at bugs.launchpad.net Mon Dec 31 19:15:03 2012 From: 965532 at bugs.launchpad.net (Barry Warsaw) Date: Mon, 31 Dec 2012 18:15:03 -0000 Subject: [Bug 965532] Re: Need a script to upgrade from MM2 to MM3 References: <20120326174611.5464.44688.malonedeb@chaenomeles.canonical.com> Message-ID: <20121231181504.26649.40771.launchpad@soybean.canonical.com> ** Changed in: mailman Milestone: 3.0.0b3 => 3.0.0b4 -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/965532 Title: Need a script to upgrade from MM2 to MM3 To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/965532/+subscriptions From 757062 at bugs.launchpad.net Mon Dec 31 19:13:49 2012 From: 757062 at bugs.launchpad.net (Barry Warsaw) Date: Mon, 31 Dec 2012 18:13:49 -0000 Subject: [Bug 757062] Re: Content filtering can remove the headers from a message/rfc822 part. References: <20110411032649.25540.48269.malonedeb@soybean.canonical.com> Message-ID: <20121231181351.7178.58318.launchpad@chaenomeles.canonical.com> ** Changed in: mailman/3.0 Milestone: 3.0.0b3 => 3.0.0b4 -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/757062 Title: Content filtering can remove the headers from a message/rfc822 part. To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/757062/+subscriptions From 1062893 at bugs.launchpad.net Mon Dec 31 19:09:50 2012 From: 1062893 at bugs.launchpad.net (Barry Warsaw) Date: Mon, 31 Dec 2012 18:09:50 -0000 Subject: [Bug 1062893] Re: No ability to add prefix on subject line References: <20121006153824.15101.97308.malonedeb@chaenomeles.canonical.com> Message-ID: <20121231180951.1974.90590.launchpad@chaenomeles.canonical.com> ** Changed in: mailman 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/1062893 Title: No ability to add prefix on subject line To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1062893/+subscriptions From 1062893 at bugs.launchpad.net Mon Dec 31 20:18:41 2012 From: 1062893 at bugs.launchpad.net (Terri) Date: Mon, 31 Dec 2012 19:18:41 -0000 Subject: [Bug 1062893] Re: No ability to add prefix on subject line References: <20121006153824.15101.97308.malonedeb@chaenomeles.canonical.com> Message-ID: <20121231191841.2225.71092.malone@chaenomeles.canonical.com> For my birthday, I got a bug I could fix easily! Thanks Barry. ;) Fixed in rev 112. ** Changed in: postorius Status: In Progress => 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/1062893 Title: No ability to add prefix on subject line To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1062893/+subscriptions