From hramrach at gmail.com Thu Jan 2 18:42:23 2014 From: hramrach at gmail.com (Michal Suchanek) Date: Thu, 02 Jan 2014 17:42:23 -0000 Subject: [Bug 265627] Re: Text and link colors in web interface References: <20080905192343.27052.31474.launchpad@forster.canonical.com> Message-ID: <20140102174223.26798.35033.malone@soybean.canonical.com> this page has still broken styles: https://mail.python.org/mailman/listinfo/mailman-users -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/265627 Title: Text and link colors in web interface To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/265627/+subscriptions From fumiyas-u-launchpad at sfo.jp Wed Jan 8 08:40:10 2014 From: fumiyas-u-launchpad at sfo.jp (SATOH Fumiyasu) Date: Wed, 08 Jan 2014 07:40:10 -0000 Subject: [Bug 1267003] [NEW] POSTFIX_STYLE_VIRTUAL_DOMAINS must be case-insensitively References: <20140108074010.10707.19511.malonedeb@wampee.canonical.com> Message-ID: <20140108074010.10707.19511.malonedeb@wampee.canonical.com> Public bug reported: If mlist.host_name is in POSTFIX_STYLE_VIRTUAL_DOMAINS but has different case chars, mlist is not listed in virtual-mailman file. Patch attached. ** Affects: mailman Importance: Undecided Status: New ** Patch added: "Patch for Mailman 2.1.17+" https://bugs.launchpad.net/bugs/1267003/+attachment/3943041/+files/0001-Treat-POSTFIX_STYLE_VIRTUAL_DOMAINS-case-insensitive.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/1267003 Title: POSTFIX_STYLE_VIRTUAL_DOMAINS must be case-insensitively To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1267003/+subscriptions From 1267003 at bugs.launchpad.net Thu Jan 9 19:46:17 2014 From: 1267003 at bugs.launchpad.net (Launchpad Bug Tracker) Date: Thu, 09 Jan 2014 18:46:17 -0000 Subject: [Bug 1267003] Re: POSTFIX_STYLE_VIRTUAL_DOMAINS must be case-insensitively References: <20140108074010.10707.19511.malonedeb@wampee.canonical.com> Message-ID: <20140109184618.4536.15592.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/1267003 Title: POSTFIX_STYLE_VIRTUAL_DOMAINS must be case-insensitively To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1267003/+subscriptions From mark at msapiro.net Thu Jan 9 19:47:10 2014 From: mark at msapiro.net (Mark Sapiro) Date: Thu, 09 Jan 2014 18:47:10 -0000 Subject: [Bug 1267003] Re: POSTFIX_STYLE_VIRTUAL_DOMAINS must be case-insensitively References: <20140108074010.10707.19511.malonedeb@wampee.canonical.com> Message-ID: <20140109184711.10472.61433.malone@gac.canonical.com> Thanks for the report and patch. ** Changed in: mailman Importance: Undecided => Low ** Changed in: mailman Status: New => Fix Committed ** Changed in: mailman Milestone: None => 2.1.18 ** 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/1267003 Title: POSTFIX_STYLE_VIRTUAL_DOMAINS must be case-insensitively To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1267003/+subscriptions From flo.fuchs at gmail.com Mon Jan 13 23:14:26 2014 From: flo.fuchs at gmail.com (Florian Fuchs) Date: Mon, 13 Jan 2014 22:14:26 -0000 Subject: [Merge] lp:~flo-fuchs/postorius/postorius_persona into lp:postorius Message-ID: <20140113221425.10784.37672.launchpad@ackee.canonical.com> Florian Fuchs has proposed merging lp:~flo-fuchs/postorius/postorius_persona into lp:postorius. Requested reviews: Terri (terriko) For more details, see: https://code.launchpad.net/~flo-fuchs/postorius/postorius_persona/+merge/201514 Hi, this change is mostly a switch from the django_social_auth library to django_browserid. It also includes some additions to the Persona audience verification process: Usually, django_browserid uses the SITE_URL setting to check if the domain of the site matches the one provided with the Persona assertion (to prevent audience spoofing). In most cases, SITE_URL might probably only contain one domain. There are however possible scenarios running Postorius/Mailman under multiple domains (say, an Apache catch-all configuration). In those cases, adding new domains to the SITE_URL setting is a redundant task, because those domains also have to be added to the Mailman DB via Postorius (or REST). This change includes a ``get_audience`` function which includes domains from the Mailman DB when verifying the audience in the Persona assertion. The function is disabled by default, but can be activated in settings.py. The code is tested (although I haven't run coverage...). But it sure won't hurt having someone else having a look at it. Thanks! Florian -- https://code.launchpad.net/~flo-fuchs/postorius/postorius_persona/+merge/201514 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: 27742 bytes Desc: not available URL: From joshua.brandt at cpanel.net Thu Jan 16 22:56:53 2014 From: joshua.brandt at cpanel.net (Joshua Brandt) Date: Thu, 16 Jan 2014 21:56:53 -0000 Subject: [Bug 1269959] [NEW] check_perms does not change UID References: <20140116215653.722.294.malonedeb@gac.canonical.com> Message-ID: <20140116215653.722.294.malonedeb@gac.canonical.com> *** This bug is a security vulnerability *** Private security bug reported: When running check_perms, the script fixes the GID for everything, however it does not fix the UID, which could allow users to still have access to those files. Granted, it is a remote possibility, however I feel it is significant enough to be fixed. I have included a patch in this report that will fix it as well (as I cannot get Bazaar to play nice with me). If you have any questions please feel free to ask them, I can be contacted here, or at joshua.brandt at cpanel.net as well. Cheers, Joshua Brandt cPanel Quality Assurance Analyst ** Affects: mailman Importance: Undecided Status: New ** Patch added: "This is a patch that will fix the script, since I can't seem to get Bazaar to play nice and get a good branch for me" https://bugs.launchpad.net/bugs/1269959/+attachment/3950418/+files/check_perms.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/1269959 Title: check_perms does not change UID To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1269959/+subscriptions From mark at msapiro.net Thu Jan 16 23:11:45 2014 From: mark at msapiro.net (Mark Sapiro) Date: Thu, 16 Jan 2014 22:11:45 -0000 Subject: [Bug 1269959] Re: check_perms does not change UID References: <20140116215653.722.294.malonedeb@gac.canonical.com> Message-ID: <20140116221145.496.1494.launchpad@gac.canonical.com> ** Information type changed from Private Security to Public Security -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1269959 Title: check_perms does not change UID To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1269959/+subscriptions From mark at msapiro.net Thu Jan 16 23:23:41 2014 From: mark at msapiro.net (Mark Sapiro) Date: Thu, 16 Jan 2014 22:23:41 -0000 Subject: [Bug 1269959] Re: check_perms does not change UID References: <20140116215653.722.294.malonedeb@gac.canonical.com> Message-ID: <20140116222341.784.54057.malone@gac.canonical.com> I don't see this as a bug. check_perms is doing what it's designed to do which is to report and optionally fix group and mode of files and directories that might cause operational problems for Mailman. Normally, the owner of all Mailman's files and directories with a very few exceptions will be the user who installed Mailman (normally root) and I don't see this as an issue. If you are really concerned, you can always do chown -R ** Changed in: mailman Status: New => Opinion ** 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/1269959 Title: check_perms does not change UID To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1269959/+subscriptions From 1270895 at bugs.launchpad.net Mon Jan 20 18:30:05 2014 From: 1270895 at bugs.launchpad.net (Cyril B.) Date: Mon, 20 Jan 2014 17:30:05 -0000 Subject: [Bug 1270895] [NEW] UnicodeDecodeError on mail processing References: <20140120173005.30660.67380.malonedeb@soybean.canonical.com> Message-ID: <20140120173005.30660.67380.malonedeb@soybean.canonical.com> Public bug reported: This is on the latest trunk (7232), with Python 2.7.5, when sending a message with an accent (e.g. '?'): Jan 20 18:19:04 2014 (1377272) ACCEPT: <52DD5A75.100 at excellency.fr> Jan 20 18:19:05 2014 (1377274) Uncaught runner exception: 'ascii' codec can't decode byte 0xe9 in position 5: ordinal not in range(128) Jan 20 18:19:05 2014 (1377274) Traceback (most recent call last): File "/home/cbay/mailman/python/lib/python2.7/site-packages/mailman/core/runner.py", line 169, in _one_iteration self._process_one_file(msg, msgdata) File "/home/cbay/mailman/python/lib/python2.7/site-packages/mailman/core/runner.py", line 252, in _process_one_file keepqueued = self._dispose(mlist, msg, msgdata) File "/home/cbay/mailman/python/lib/python2.7/site-packages/mailman/runners/pipeline.py", line 36, in _dispose process(mlist, msg, msgdata, pipeline) File "/home/cbay/mailman/python/lib/python2.7/site-packages/mailman/core/pipelines.py", line 66, in process handler.process(mlist, msg, msgdata) File "/home/cbay/mailman/python/lib/python2.7/site-packages/mailman/handlers/to_digest.py", line 58, in process mbox.add(msg) File "/home/cbay/mailman/python/lib/python2.7/mailbox.py", line 587, in add self._toc[self._next_key] = self._append_message(message) File "/home/cbay/mailman/python/lib/python2.7/mailbox.py", line 743, in _append_message offsets = self._install_message(message) File "/home/cbay/mailman/python/lib/python2.7/mailbox.py", line 805, in _install_message self._dump_message(message, self._file, self._mangle_from_) File "/home/cbay/mailman/python/lib/python2.7/mailbox.py", line 212, in _dump_message buffer.seek(0) File "/home/cbay/mailman/python/lib/python2.7/StringIO.py", line 106, in seek self.buf += ''.join(self.buflist) UnicodeDecodeError: 'ascii' codec can't decode byte 0xe9 in position 5: ordinal not in range(128) Jan 20 18:19:05 2014 (1377274) SHUNTING: 1390238345.418067+c3cd5177d093930a97531fcfccd6d1e08ae57b4e ** Affects: mailman Importance: Undecided Status: New ** Tags: 3.0 mailman -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1270895 Title: UnicodeDecodeError on mail processing To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1270895/+subscriptions From andreas.abel at ifi.lmu.de Mon Jan 20 20:56:40 2014 From: andreas.abel at ifi.lmu.de (Andreas Abel) Date: Mon, 20 Jan 2014 19:56:40 -0000 Subject: [Bug 1270933] [NEW] Feature request: secondary email-addresses References: <20140120195640.30943.30091.malonedeb@soybean.canonical.com> Message-ID: <20140120195640.30943.30091.malonedeb@soybean.canonical.com> Public bug reported: Mailman(aged) lists refuse posts by a user that sends the message from a different address than the one he is using to receive messages from this list. Request: allow users to add secondary addresses to their subscription that identify the user when posting. ** 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/1270933 Title: Feature request: secondary email-addresses To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1270933/+subscriptions From mark at msapiro.net Mon Jan 20 21:12:38 2014 From: mark at msapiro.net (Mark Sapiro) Date: Mon, 20 Jan 2014 20:12:38 -0000 Subject: [Bug 1270933] Re: Feature request: secondary email-addresses References: <20140120195640.30943.30091.malonedeb@soybean.canonical.com> Message-ID: <20140120201239.19307.90891.malone@chaenomeles.canonical.com> This is already implemented in Mailman 3. For Mailman 2.1.x the user can subscribe multiple addresses to the list and set any or all of them to "no mail". There are no plans to do anything more than this in Mailman 2.1. ** 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/1270933 Title: Feature request: secondary email-addresses To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1270933/+subscriptions From andreas.abel at ifi.lmu.de Wed Jan 22 14:27:36 2014 From: andreas.abel at ifi.lmu.de (Andreas Abel) Date: Wed, 22 Jan 2014 13:27:36 -0000 Subject: [Bug 1270933] Re: Feature request: secondary email-addresses References: <20140120195640.30943.30091.malonedeb@soybean.canonical.com> Message-ID: <20140122132736.25472.92208.malone@soybean.canonical.com> Thanks for suggesting this workaround! (Did not think of it...) -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1270933 Title: Feature request: secondary email-addresses To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1270933/+subscriptions From 1271897 at bugs.launchpad.net Thu Jan 23 12:28:07 2014 From: 1271897 at bugs.launchpad.net (Gernot Salzer) Date: Thu, 23 Jan 2014 11:28:07 -0000 Subject: [Bug 1271897] [NEW] mailman 2.1.14: action for held message cannot be submitted References: <20140123112807.30536.10084.malonedeb@soybean.canonical.com> Message-ID: <20140123112807.30536.10084.malonedeb@soybean.canonical.com> Public bug reported: A mail to a mailman mailing list is being held back ('Post by non-member to a members-only list'), but I as the administrator can neither accept nor reject nor discard it. As soon as I press "Submit All Data" the page refreshes with the same held mail and "Defer" preselected. I think that this worked for other mails for this version in the past, but it may well be that that there was an unnoticed update inbetween. The mail address DOES NOT contain an underscore as hypothesized as possible cause in bug report #529550 Here is the mail header as mailman shows it (x replaces letters, 9 replaces digits): Return-Path: X-Original-To: xxxxxxx9999 at xxxxx.xx Delivered-To: xxxxxxx9999 at xxxxx.xx Received: from xxxxxx.xxx.xxxxxx.xx.xx (xxxxxx.xxx.xxxxxx.xx.xx [999.99.999.99]) ?by xxxx.xxxxx.xxxxxx.xx.xx (Postfix) with ESMTP id F3D679DBB ?for ; Wed, 22 Jan 2014 22:58:01 +0100 (CET) Received: from xxxxxx.xx.xx (xxxxxx.xx.xx [999.99.999.99]) ?by xxxxxx.xxx.xxxxxx.xx.xx (8.14.5/8.14.5) with ESMTP id s0MLvtYm008750 ?(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=OK) ?for ; Wed, 22 Jan 2014 22:57:58 +0100 X-Connecting-Host: xxxxxx.xx.xx [999.99.999.99] X-Connecting-Addr: 999.99.999.99 X-Sent-To: X-Sent-From: x.xxx.xxxxxxxxx at xx.xx Received: from PEXHB011A.vu.local (999.99.999.99) by xxxxxx.xx.xx ?(999.99.999.99) with Microsoft SMTP Server (TLS) id 14.3.158.1; Wed, 22 Jan ?2014 22:57:54 +0100 Received: from PEXMB001A.vu.local ([999.999.9.999]) by PEXHB011A.vu.local ?([999.99.999.99]) with mapi id 14.03.0158.001; Wed, 22 Jan 2014 22:57:54 ?+0100 From: "Xxxxxxxxx, X. xxx" To: "" CC: "Xxxxxxxxx, X. xxx" Subject: Re: [XX XXX/XXXX 9999] XXXXXXX-9999: xxxxxxx xxxxxxx xxxxxxxxxx ?xxxxxx Thread-Topic: [XX XXX/XXXX 9999] XXXXXXX-9999: xxxxxxx xxxxxxx xxxxxxxxxx ?xxxxxx Thread-Index: AQHPFCybjeiURju1cUmY9WDxORuFLpqRQOEA Date: Wed, 22 Jan 2014 21:57:53 +0000 Message-ID: References: <52BBE32F.2020907 at xxxxx.xx> <52BD9EAF.3010006 at xxxxx.xxx.xx> ?<52BDF971.20007 at xx.xxxxxxxxxx.xxx-xxxxxxxxx.xx> ? ?<52D3F24C.5060204 at xxxxx.xx> <20140114130809.GA3845 at xxxxxxx> ?<3d12646c28427128240b086ed43cb59b.squirrel at xxxxxx.xxx.xx.xx.xx> ?<14c4c123f50c2fe06bd9ff738aeab014.squirrel at xxxxxx.xxx.xx.xx.xx> ?<52D661C5.20607 at mimuw.edu.pl> <52D66D50.9020006 at xxx.xx.xx.xx> ?<52D94E82.3050903 at cri.mines-paristech.fr> <52DA440B.1070000 at xxxxxx.xx> In-Reply-To: <52DA440B.1070000 at xxxxxx.xx> Accept-Language: en-GB, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [999.99.999.9] Content-Type: text/plain; charset="iso-8859-1" Content-ID: Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Greylist: Sender succeeded STARTTLS authentication, not delayed by milter-greylist-4.2.7 (xxxxxx.xxx.xxxxxx.xx.xx [999.99.999.99]); Wed, 22 Jan 2014 22:57:58 +0100 (CET) X-Spam-Status: LOW ; -26 X-Spam-Level: - X-Spam-TU-Processing-Host: xxxxxx.xxx.xxxxxx.xx.xx X-Virus-Scanned: by amavisd-new on xxx.xxx.xxxxxx.xx.xx ** Affects: mailman Importance: Undecided Status: New ** Description changed: A mail to a mailman mailing list is being held back ('Post by non-member to a members-only list'), but I as the administrator can neither accept nor reject nor discard it. As soon as I press "Submit All Data" the page refreshes with the same held mail and "Defer" preselected. I think that this worked for other mails for this version in the past, but it may - well be that that there was an unnoticed update in between. + well be that that there was an unnoticed update inbetween. The mail address DOES NOT contain an underscore as hypothesized as possible cause in bug report #529550 Here is the mail header as mailman shows it (x replaces letters, 9 replaces digits): Return-Path: X-Original-To: xxxxxxx9999 at xxxxx.xx Delivered-To: xxxxxxx9999 at xxxxx.xx Received: from xxxxxx.xxx.xxxxxx.xx.xx (xxxxxx.xxx.xxxxxx.xx.xx [999.99.999.99]) - by xxxx.xxxxx.xxxxxx.xx.xx (Postfix) with ESMTP id F3D679DBB - for ; Wed, 22 Jan 2014 22:58:01 +0100 (CET) + ?by xxxx.xxxxx.xxxxxx.xx.xx (Postfix) with ESMTP id F3D679DBB + ?for ; Wed, 22 Jan 2014 22:58:01 +0100 (CET) Received: from xxxxxx.xx.xx (xxxxxx.xx.xx [999.99.999.99]) - by xxxxxx.xxx.xxxxxx.xx.xx (8.14.5/8.14.5) with ESMTP id s0MLvtYm008750 - (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=OK) - for ; Wed, 22 Jan 2014 22:57:58 +0100 + ?by xxxxxx.xxx.xxxxxx.xx.xx (8.14.5/8.14.5) with ESMTP id s0MLvtYm008750 + ?(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=OK) + ?for ; Wed, 22 Jan 2014 22:57:58 +0100 X-Connecting-Host: xxxxxx.xx.xx [999.99.999.99] X-Connecting-Addr: 999.99.999.99 X-Sent-To: X-Sent-From: x.xxx.xxxxxxxxx at xx.xx Received: from PEXHB011A.vu.local (999.99.999.99) by xxxxxx.xx.xx - (999.99.999.99) with Microsoft SMTP Server (TLS) id 14.3.158.1; Wed, 22 Jan - 2014 22:57:54 +0100 + ?(999.99.999.99) with Microsoft SMTP Server (TLS) id 14.3.158.1; Wed, 22 Jan + ?2014 22:57:54 +0100 Received: from PEXMB001A.vu.local ([999.999.9.999]) by PEXHB011A.vu.local - ([999.99.999.99]) with mapi id 14.03.0158.001; Wed, 22 Jan 2014 22:57:54 - +0100 + ?([999.99.999.99]) with mapi id 14.03.0158.001; Wed, 22 Jan 2014 22:57:54 + ?+0100 From: "Xxxxxxxxx, X. xxx" To: "" CC: "Xxxxxxxxx, X. xxx" Subject: Re: [XX XXX/XXXX 9999] XXXXXXX-9999: xxxxxxx xxxxxxx xxxxxxxxxx - xxxxxx + ?xxxxxx Thread-Topic: [XX XXX/XXXX 9999] XXXXXXX-9999: xxxxxxx xxxxxxx xxxxxxxxxx - xxxxxx + ?xxxxxx Thread-Index: AQHPFCybjeiURju1cUmY9WDxORuFLpqRQOEA Date: Wed, 22 Jan 2014 21:57:53 +0000 Message-ID: References: <52BBE32F.2020907 at xxxxx.xx> <52BD9EAF.3010006 at xxxxx.xxx.xx> - <52BDF971.20007 at xx.xxxxxxxxxx.xxx-xxxxxxxxx.xx> - - <52D3F24C.5060204 at xxxxx.xx> <20140114130809.GA3845 at xxxxxxx> - <3d12646c28427128240b086ed43cb59b.squirrel at xxxxxx.xxx.xx.xx.xx> - <14c4c123f50c2fe06bd9ff738aeab014.squirrel at xxxxxx.xxx.xx.xx.xx> - <52D661C5.20607 at mimuw.edu.pl> <52D66D50.9020006 at xxx.xx.xx.xx> - <52D94E82.3050903 at cri.mines-paristech.fr> <52DA440B.1070000 at xxxxxx.xx> + ?<52BDF971.20007 at xx.xxxxxxxxxx.xxx-xxxxxxxxx.xx> + ? + ?<52D3F24C.5060204 at xxxxx.xx> <20140114130809.GA3845 at xxxxxxx> + ?<3d12646c28427128240b086ed43cb59b.squirrel at xxxxxx.xxx.xx.xx.xx> + ?<14c4c123f50c2fe06bd9ff738aeab014.squirrel at xxxxxx.xxx.xx.xx.xx> + ?<52D661C5.20607 at mimuw.edu.pl> <52D66D50.9020006 at xxx.xx.xx.xx> + ?<52D94E82.3050903 at cri.mines-paristech.fr> <52DA440B.1070000 at xxxxxx.xx> In-Reply-To: <52DA440B.1070000 at xxxxxx.xx> Accept-Language: en-GB, en-US Content-Language: en-US - X-MS-Has-Attach: - X-MS-TNEF-Correlator: + X-MS-Has-Attach: + X-MS-TNEF-Correlator: x-originating-ip: [999.99.999.9] Content-Type: text/plain; charset="iso-8859-1" Content-ID: Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Greylist: Sender succeeded STARTTLS authentication, not delayed by milter-greylist-4.2.7 (xxxxxx.xxx.xxxxxx.xx.xx [999.99.999.99]); Wed, 22 Jan 2014 22:57:58 +0100 (CET) X-Spam-Status: LOW ; -26 X-Spam-Level: - X-Spam-TU-Processing-Host: xxxxxx.xxx.xxxxxx.xx.xx X-Virus-Scanned: by amavisd-new on xxx.xxx.xxxxxx.xx.xx -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1271897 Title: mailman 2.1.14: action for held message cannot be submitted To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1271897/+subscriptions From mark at msapiro.net Thu Jan 23 15:35:16 2014 From: mark at msapiro.net (Mark Sapiro) Date: Thu, 23 Jan 2014 14:35:16 -0000 Subject: [Bug 1271897] Re: mailman 2.1.14: action for held message cannot be submitted References: <20140123112807.30536.10084.malonedeb@soybean.canonical.com> Message-ID: <20140123143517.30706.95564.malone@soybean.canonical.com> I do not think this is a Mailman bug. I think that somehow your web server is losing the post data from the form submission. Possibly there is a redirect in the server from http to https or similar. See the FAQ at . ** Changed in: mailman Status: New => Incomplete ** 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/1271897 Title: mailman 2.1.14: action for held message cannot be submitted To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1271897/+subscriptions From 558234 at bugs.launchpad.net Tue Jan 28 12:14:32 2014 From: 558234 at bugs.launchpad.net (jaromil) Date: Tue, 28 Jan 2014 11:14:32 -0000 Subject: [Bug 558234] Re: Addition of canonical list name References: <20100408090819.1687.70867.launchpad@loganberry.canonical.com> Message-ID: <20140128111432.29625.38475.malone@gac.canonical.com> This patch is very important, since it lets people link from the mailman listinfo page the html screens of other archivers as MHonarc or Lurker. For one, I urge you to include it: its totally sane, very simple and won't affect any running instance. -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/558234 Title: Addition of canonical list name To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/558234/+subscriptions From mark at msapiro.net Wed Jan 29 00:16:02 2014 From: mark at msapiro.net (Mark Sapiro) Date: Tue, 28 Jan 2014 23:16:02 -0000 Subject: [Bug 558234] Re: Addition of canonical list name References: <20100408090819.1687.70867.launchpad@loganberry.canonical.com> Message-ID: <20140128231602.12434.31953.malone@chaenomeles.canonical.com> Why do you need this? You already have the admitedly confusingly named tag which is replaced by the list's _internal_name which is the lower case of the list's real_name. The name is confusing, but it refers to the user portion(local part) of the list's email posting address which is the origin of the name. ** Changed in: mailman Importance: Undecided => Wishlist ** Changed in: mailman Status: New => Incomplete ** 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/558234 Title: Addition of canonical list name To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/558234/+subscriptions