From esr at thyrsus.com Mon Oct 3 17:08:33 2011 From: esr at thyrsus.com (Eric S. Raymond) Date: Mon, 03 Oct 2011 15:08:33 -0000 Subject: [Bug 865421] [NEW] Need list download function inverse to mass subscription References: <20111003150833.15281.77808.malonedeb@wampee.canonical.com> Message-ID: <20111003150833.15281.77808.malonedeb@wampee.canonical.com> Public bug reported: The forge site Berlios announced its impending death recently, requiring me to move the GPSD project elsewhere. The most difficult part of the job was extracting the Mailman state of my lists. At forge sites, usually only the web interface is available, so the export script is not a useful answer. Scraping the lists of names from the web display was painful. Please add to the admin screen of a list a button to download the list state as a file. It should be in the same format accepted for upload. For bonus points, enhance the format so per-user options are preserved. ** 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/865421 Title: Need list download function inverse to mass subscription To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/865421/+subscriptions From mark at msapiro.net Tue Oct 4 03:18:38 2011 From: mark at msapiro.net (Mark Sapiro) Date: Tue, 04 Oct 2011 01:18:38 -0000 Subject: [Bug 865825] [NEW] Undisplayed new_member_options bits are reset whenever the General Options page is submitted. References: <20111004011838.6182.47512.malonedeb@chaenomeles.canonical.com> Message-ID: <20111004011838.6182.47512.malonedeb@chaenomeles.canonical.com> Public bug reported: The code in Mailman/Gui/General.py for setting new_member_options doesn't take into account the fact that there might be option bits other than 'hide', 'ack', 'notmetoo' and 'nodupes' that are set, and it resets them even if the four displayed options are unchanged. This also affects bin/config_list which cannot set bits other than those 4 unless set via mlist.new_member_options =. ** Affects: mailman Importance: Medium Assignee: Mark Sapiro (msapiro) Status: Confirmed -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/865825 Title: Undisplayed new_member_options bits are reset whenever the General Options page is submitted. To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/865825/+subscriptions From mark at msapiro.net Tue Oct 4 04:21:32 2011 From: mark at msapiro.net (Mark Sapiro) Date: Tue, 04 Oct 2011 02:21:32 -0000 Subject: [Bug 865421] Re: Need list download function inverse to mass subscription References: <20111003150833.15281.77808.malonedeb@wampee.canonical.com> Message-ID: <20111004022132.12302.28635.malone@soybean.canonical.com> Have you seen the FAQ at ? That FAQ mentions the email 'who' command which can be used to obtain the names and addresses of members in a format suitable for mass subscribe. It also mentions the script at which already exists to do the screen scraping and which can retrieve most of the user options (everything in the admin Membership List page except language). ** 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/865421 Title: Need list download function inverse to mass subscription To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/865421/+subscriptions From 867459 at bugs.launchpad.net Tue Oct 4 14:58:52 2011 From: 867459 at bugs.launchpad.net (Florian Fuchs) Date: Tue, 04 Oct 2011 12:58:52 -0000 Subject: =?utf-8?q?=5BBug_867459=5D_=5BNEW=5D_REST_API=3A_Implement_a_simpl?= =?utf-8?q?e_way_to_check_user_credentials=C2=A0?= References: <20111004125852.25954.77334.malonedeb@chaenomeles.canonical.com> Message-ID: <20111004125852.25954.77334.malonedeb@chaenomeles.canonical.com> Public bug reported: Currently there is no way to check a user's credentials via the REST API. While there were discussions on implementing a middleware "hook" to implement complex authentication logic, there should also be a simple way to check if a given combination of a user's credentials (user name and password) matches the one stored in mailman's internal db. A good way to do this (as discussed on IRC a while ago) could be to implement a SQL stored procedure-like behavior in the REST API. Meaning: A client sends a uname/pwd-combination to a specific URL resource and receives a plain True or False (1 or 0?) if the combination matches. This way, no password string is sent out via the API. Things to discuss or consider: 1.) How is the password stored in MMs internal db? (plaintext or hashed? if hashed, which algorithm is used?) 2.) (How) should the pwd be encrypted when sent to the API (depends on 1.)? 3.) Should this API resource be limited to requests from localhost and/or via SSL? ** Affects: mailman Importance: Undecided Status: New ** 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/867459 Title: REST API: Implement a simple way to check user credentials To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/867459/+subscriptions From mark at msapiro.net Tue Oct 4 17:47:51 2011 From: mark at msapiro.net (Mark Sapiro) Date: Tue, 04 Oct 2011 15:47:51 -0000 Subject: [Bug 867611] [NEW] Patch to send password reminders per-list. References: <20111004154751.12017.58228.malonedeb@gac.canonical.com> Message-ID: <20111004154751.12017.58228.malonedeb@gac.canonical.com> Public bug reported: Password reminders are sent with a single reminder email for all lists in a domain for which a user is receiving reminders. Thus there is no list context for the reminder, and a list specific version of the cronpass.txt reminder template isn't consulted. This is an issue for some installations who want a list specific reminder. This patch modifies cron/mailpasswds to send reminders individually per list and will allow a list specific cronpass.txt template to work for the reminders. This will not become a standard feature as it is too annoying to people who are members of multiple lists in the installation. ** Affects: mailman Importance: Wishlist Assignee: Mark Sapiro (msapiro) Status: Triaged -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/867611 Title: Patch to send password reminders per-list. To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/867611/+subscriptions From mark at msapiro.net Tue Oct 4 17:47:51 2011 From: mark at msapiro.net (Mark Sapiro) Date: Tue, 04 Oct 2011 15:47:51 -0000 Subject: [Bug 867611] Re: Patch to send password reminders per-list. References: <20111004154751.12017.58228.malonedeb@gac.canonical.com> Message-ID: <20111004154752.12017.42903.malone@gac.canonical.com> ** Patch added: "Patch to enable per-list password reminders" https://bugs.launchpad.net/bugs/867611/+attachment/2508063/+files/mailpasswds.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/867611 Title: Patch to send password reminders per-list. To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/867611/+subscriptions From mark at msapiro.net Tue Oct 4 23:56:12 2011 From: mark at msapiro.net (Mark Sapiro) Date: Tue, 04 Oct 2011 21:56:12 -0000 Subject: [Bug 865825] Re: Undisplayed new_member_options bits are reset whenever the General Options page is submitted. References: <20111004011838.6182.47512.malonedeb@chaenomeles.canonical.com> Message-ID: <20111004215612.22413.8582.launchpad@wampee.canonical.com> ** 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/865825 Title: Undisplayed new_member_options bits are reset whenever the General Options page is submitted. To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/865825/+subscriptions From 867459 at bugs.launchpad.net Wed Oct 5 13:51:04 2011 From: 867459 at bugs.launchpad.net (Florian Fuchs) Date: Wed, 05 Oct 2011 11:51:04 -0000 Subject: =?utf-8?q?=5BBug_867459=5D_Re=3A_REST_API=3A_Implement_a_simple_wa?= =?utf-8?q?y_to_check_user_credentials=C2=A0?= References: <20111004125852.25954.77334.malonedeb@chaenomeles.canonical.com> Message-ID: <20111005115105.23431.66674.launchpad@wampee.canonical.com> ** Description changed: Currently there is no way to check a user's credentials via the REST API. While there were discussions on implementing a middleware "hook" to implement complex authentication logic, there should also be a simple way to check if a given combination of a user's credentials (user name and password) matches the one stored in mailman's internal db. A good way to do this (as discussed on IRC a while ago) could be to implement a SQL stored procedure-like behavior in the REST API. - Meaning: A client sends a uname/pwd-combination to a specific URL resource and receives a plain True or False (1 or 0?) if the combination matches. This way, no password string is sent out via the API. + Meaning: A client sends a uname/pwd-combination to a specific URL resource and receives a plain True or False (200/403 status codes?) if the combination matches. This way, no password string is sent out via the API. Things to discuss or consider: 1.) How is the password stored in MMs internal db? (plaintext or hashed? if hashed, which algorithm is used?) 2.) (How) should the pwd be encrypted when sent to the API (depends on 1.)? 3.) Should this API resource be limited to requests from localhost and/or via SSL? ** Changed in: mailman Milestone: None => 3.0.0b1 -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/867459 Title: REST API: Implement a simple way to check user credentials To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/867459/+subscriptions From 867459 at bugs.launchpad.net Thu Oct 6 17:25:18 2011 From: 867459 at bugs.launchpad.net (Barry Warsaw) Date: Thu, 06 Oct 2011 15:25:18 -0000 Subject: =?utf-8?q?=5BBug_867459=5D_Re=3A_REST_API=3A_Implement_a_simple_wa?= =?utf-8?q?y_to_check_user_credentials=C2=A0?= References: <20111004125852.25954.77334.malonedeb@chaenomeles.canonical.com> Message-ID: <20111006152519.28102.91026.launchpad@soybean.canonical.com> ** Changed in: mailman Status: New => Confirmed ** 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/867459 Title: REST API: Implement a simple way to check user credentials To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/867459/+subscriptions From steveth45 at gmail.com Thu Oct 6 18:20:28 2011 From: steveth45 at gmail.com (Stephen A. Goss) Date: Thu, 06 Oct 2011 16:20:28 -0000 Subject: [Bug 869317] [NEW] Mailman startup script missing --force option. References: <20111006162028.11515.35600.malonedeb@gac.canonical.com> Message-ID: <20111006162028.11515.35600.malonedeb@gac.canonical.com> Public bug reported: I rebooted the VM that mailman was running on, when I tried to start mailman up after the reboot, i got this output: $ mailman -C /etc/mailman.cfg start usage: mailman [-h] [-v] [-C CONFIG] {info,status,help,withlist,start,unshunt,create,stop,remove,lists,reopen,version,import21,inject,members,qfile,restart,aliases} ... mailman: error: A previous run of GNU Mailman did not exit cleanly. Try using --force. Running with the --force option didn't work: $ mailman --force -C /etc/mailman.cfg start usage: mailman [-h] [-v] [-C CONFIG] {info,status,help,withlist,start,unshunt,create,stop,remove,lists,reopen,version,import21,inject,members,qfile,restart,aliases} ... mailman: error: unrecognized arguments: --force ** Affects: mailman Importance: Undecided Status: New ** 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/869317 Title: Mailman startup script missing --force option. To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/869317/+subscriptions From steveth45 at gmail.com Thu Oct 6 19:15:09 2011 From: steveth45 at gmail.com (Stephen A. Goss) Date: Thu, 06 Oct 2011 17:15:09 -0000 Subject: [Bug 869347] [NEW] bin/test script fails unless zope.testrunner is pip installed References: <20111006171509.28591.25023.malonedeb@soybean.canonical.com> Message-ID: <20111006171509.28591.25023.malonedeb@soybean.canonical.com> Public bug reported: I am running Mailman 3 in a virtualenv with most of its package dependencies installed through pip. In this particular configuration, if I run `buildout`, the test script that is created cannot seem to load zope.testrunner properly: $ bin/test -vv Traceback (most recent call last): File "bin/test", line 35, in import zope.testrunner ImportError: No module named testrunner The workaround is to remove the eggs folder, pip install zope.testrunner, and then re-run buildout. ** Affects: mailman Importance: Undecided Status: New ** 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/869347 Title: bin/test script fails unless zope.testrunner is pip installed To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/869347/+subscriptions From steveth45 at gmail.com Thu Oct 6 19:10:26 2011 From: steveth45 at gmail.com (Stephen A. Goss) Date: Thu, 06 Oct 2011 17:10:26 -0000 Subject: [Bug 869342] [NEW] bootstrap.py fails if buildout already installed in Python environment References: <20111006171026.27641.73992.malonedeb@soybean.canonical.com> Message-ID: <20111006171026.27641.73992.malonedeb@soybean.canonical.com> Public bug reported: If zc.buildout is already installed (say it was pip installed) in Python environment, the bootstrap.py script fails without reasonable explanation: $ python bootstrap.py Traceback (most recent call last): File "bootstrap.py", line 255, in import zc.buildout.buildout ImportError: No module named zc.buildout.buildout This is confusing because you can see that zc.buildout.buildout is available. $ python Python 2.6.5 (r265:79063, Jun 25 2011, 08:36:25) [GCC 4.4.4 20100726 (Red Hat 4.4.4-13)] on linux2 Type "help", "copyright", "credits" or "license" for more information. >>> import zc.buildout.buildout >>> It turns out that if zc.buildout is already available, bootstrap.py does not need to be run, but that is less than obvious to someone who is not intimately familiar with buildout. ** Affects: mailman Importance: Undecided Status: New ** Tags: mailman3 ** 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/869342 Title: bootstrap.py fails if buildout already installed in Python environment To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/869342/+subscriptions From 871415 at bugs.launchpad.net Sun Oct 9 21:01:07 2011 From: 871415 at bugs.launchpad.net (Johnathan Ritzi) Date: Sun, 09 Oct 2011 19:01:07 -0000 Subject: [Bug 871415] [NEW] "Approved:" password not stripped when list in BCC References: <20111009190107.9514.10008.malonedeb@gac.canonical.com> Message-ID: <20111009190107.9514.10008.malonedeb@gac.canonical.com> *** This bug is a security vulnerability *** Private security bug reported: I'm using Mailman 2.1.13 to set up lists where no subscriber can mail the list without "Approved: " being on the first line. This works according to Mailman documentation when I send "To:" the list (the "Approved:" line is stripped out of the email before it is forwarded along to the list). However, if I leave the "To:" field blank and instead BCC the list, the email gets forwarded along _without_ the approval password being stripped (in other words, the password is broadcast to the entire list). ** Affects: mailman Importance: Undecided Status: New -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/871415 Title: "Approved:" password not stripped when list in BCC To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/871415/+subscriptions From 871416 at bugs.launchpad.net Sun Oct 9 21:02:18 2011 From: 871416 at bugs.launchpad.net (Marly G) Date: Sun, 09 Oct 2011 19:02:18 -0000 Subject: [Bug 871416] [NEW] Can't open downloads. References: <20111009190218.18656.64426.malonedeb@soybean.canonical.com> Message-ID: <20111009190218.18656.64426.malonedeb@soybean.canonical.com> Public bug reported: When I download and click to open the download, it always goes to Archive Manager and says: "An error occurred while loading the archive". And beneath that it would read: Archive: /home/administrator/Downloads/PageRageSetup(2).exe [/home/administrator/Downloads/PageRageSetup(2).exe] End-of-central-directory signature not found. Either this file is not a zipfile, or it constitutes one disk of a multi-part archive. In the latter case the central directory and zipfile comment will be found on the last disk(s) of this archive. zipinfo: cannot find zipfile directory in one of /home/administrator/Downloads/PageRageSetup(2).exe or /home/administrator/Downloads/PageRageSetup(2).exe.zip, and cannot find /home/administrator/Downloads/PageRageSetup(2).exe.ZIP, period. I can't download anything. ** 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/871416 Title: Can't open downloads. To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/871416/+subscriptions From mark at msapiro.net Sun Oct 9 22:32:13 2011 From: mark at msapiro.net (Mark Sapiro) Date: Sun, 09 Oct 2011 20:32:13 -0000 Subject: [Bug 871415] Re: "Approved:" password not stripped when list in BCC References: <20111009190107.9514.10008.malonedeb@gac.canonical.com> Message-ID: <20111009203213.7544.71757.malone@chaenomeles.canonical.com> I cannot duplicate this. Please attach a file to this report containing the complete, raw message as received from the list with the Approved: first line not removed. ** 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 the bug report. https://bugs.launchpad.net/bugs/871415 Title: "Approved:" password not stripped when list in BCC To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/871415/+subscriptions From mark at msapiro.net Sun Oct 9 22:55:12 2011 From: mark at msapiro.net (Mark Sapiro) Date: Sun, 09 Oct 2011 20:55:12 -0000 Subject: [Bug 871416] Re: Can't open downloads. References: <20111009190218.18656.64426.malonedeb@soybean.canonical.com> Message-ID: <20111009205512.8452.93181.malone@chaenomeles.canonical.com> Is this even a Mailman issue? What are you trying to download? From where? ** 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/871416 Title: Can't open downloads. To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/871416/+subscriptions From steveth45 at gmail.com Mon Oct 10 22:57:28 2011 From: steveth45 at gmail.com (Stephen A. Goss) Date: Mon, 10 Oct 2011 20:57:28 -0000 Subject: [Bug 869317] Re: Mailman startup script missing --force option. References: <20111006162028.11515.35600.malonedeb@gac.canonical.com> Message-ID: <20111010205728.19696.52123.malone@gac.canonical.com> OK, the option is not missing, I was using it wrong. However, it still doesn't do anything! $ mailman -C /etc/mailman.cfg start --force usage: mailman [-h] [-v] [-C CONFIG] {info,status,help,withlist,start,unshunt,create,stop,remove,lists,reopen,version,import21,inject,members,qfile,restart,aliases} ... mailman: error: A previous run of GNU Mailman did not exit cleanly. Try using --force. -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/869317 Title: Mailman startup script missing --force option. To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/869317/+subscriptions From steveth45 at gmail.com Mon Oct 10 23:14:44 2011 From: steveth45 at gmail.com (Stephen A. Goss) Date: Mon, 10 Oct 2011 21:14:44 -0000 Subject: [Bug 869317] Re: Mailman startup script missing --force option. References: <20111006162028.11515.35600.malonedeb@gac.canonical.com> Message-ID: <20111010211444.20316.38430.malone@gac.canonical.com> I found the acquire_lock method and it seems to honor the force option, so the attached patch has allowed me to get past this stale lock situation. ** Patch added: "869317.patch" https://bugs.launchpad.net/mailman/+bug/869317/+attachment/2535454/+files/869317.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/869317 Title: Mailman startup script missing --force option. To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/869317/+subscriptions From 869317 at bugs.launchpad.net Tue Oct 11 13:56:24 2011 From: 869317 at bugs.launchpad.net (Barry Warsaw) Date: Tue, 11 Oct 2011 11:56:24 -0000 Subject: [Bug 869317] Re: Mailman startup script missing --force option. References: <20111006162028.11515.35600.malonedeb@gac.canonical.com> Message-ID: <20111011115624.30460.28742.launchpad@soybean.canonical.com> ** Changed in: mailman Milestone: None => 3.0.0b1 ** Changed in: mailman Importance: Undecided => Medium ** Changed in: mailman Assignee: (unassigned) => Barry Warsaw (barry) ** 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/869317 Title: Mailman startup script missing --force option. To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/869317/+subscriptions From 871415 at bugs.launchpad.net Tue Oct 11 16:59:44 2011 From: 871415 at bugs.launchpad.net (Johnathan Ritzi) Date: Tue, 11 Oct 2011 14:59:44 -0000 Subject: [Bug 871415] Re: "Approved:" password not stripped when list in BCC References: <20111009190107.9514.10008.malonedeb@gac.canonical.com> Message-ID: <20111011145944.13355.88035.malone@wampee.canonical.com> After further review and testing, it has nothing to do with the To or Bcc fields. Instead, the issue has to do with sending the message using Gmail's web interface. Gmail by default sends messages in HTML format. In several cases, the "Approved:" line with password were being sent out to the mailing list. Looking at the raw message body shows that the "Approved:" line was successfully stripped out of the plain text version of the email at the top, but not the HTML part at the bottom (which is what the end-user's client displays). Maybe this is "correct" because Mailman can't be expected to reliably parse the approval line out of HTML. But it's definitely dangerous behavior, because the email goes through (rather than bouncing) but without the password being stripped, broadcasting the owner password to the entire list. Maybe if the message is sent in HTML format Mailman should try (and succeed/fail) only on the HTML portion of the message, not the plain- text version? -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/871415 Title: "Approved:" password not stripped when list in BCC To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/871415/+subscriptions From mark at msapiro.net Tue Oct 11 18:37:59 2011 From: mark at msapiro.net (Mark Sapiro) Date: Tue, 11 Oct 2011 16:37:59 -0000 Subject: [Bug 871415] Re: "Approved:" password not stripped when list in BCC References: <20111009190107.9514.10008.malonedeb@gac.canonical.com> Message-ID: <20111011163800.29699.58866.launchpad@soybean.canonical.com> *** This bug is a duplicate of bug 266220 *** https://bugs.launchpad.net/bugs/266220 ** This bug has been marked a duplicate of bug 266220 Approved: only removed from text/plain part -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/871415 Title: "Approved:" password not stripped when list in BCC To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/871415/+subscriptions From mark at msapiro.net Tue Oct 11 18:59:21 2011 From: mark at msapiro.net (Mark Sapiro) Date: Tue, 11 Oct 2011 16:59:21 -0000 Subject: [Bug 871415] Re: "Approved:" password not stripped when list in BCC References: <20111009190107.9514.10008.malonedeb@gac.canonical.com> Message-ID: <20111011165921.13234.47178.malone@wampee.canonical.com> *** This bug is a duplicate of bug 266220 *** https://bugs.launchpad.net/bugs/266220 This is a known issue. We remove the Approved: text from any part in which we can find it, but we can't deal with all pathological HTML renderings, so this is only best effort, not a guarantee. That is why we strongly recommend using a true header rather than the first body line, but you probably can't do that with the gmail web client either. Note that in Mailman 2.1.15, there will be a 'poster' password that is only for pre-approving posts, thus minimizing the consequences of leaking the password as you don't have to use the admin or moderator password. See . If you post an excerpt of the exact HTML from which removal failed (you can mung the password) to the original bug , I'll try to recognize that case. Note that the current code looks for a match of the "(X-)Approve(d): password" string it found in the plain text, but with any combination of spaces, \xA0 and   between the : and the password. It will not find a match if there is a newline inserted, but it does decode base64 and quoted-printable HTML parts before looking. -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/871415 Title: "Approved:" password not stripped when list in BCC To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/871415/+subscriptions From 266220 at bugs.launchpad.net Tue Oct 11 18:59:45 2011 From: 266220 at bugs.launchpad.net (Johnathan Ritzi) Date: Tue, 11 Oct 2011 16:59:45 -0000 Subject: [Bug 266220] Re: Approved: only removed from text/plain part References: <20080905192945.27052.44689.launchpad@forster.canonical.com> Message-ID: <20111011165945.12927.10196.malone@wampee.canonical.com> Bug 871415 was just marked as a duplicate of this. However, I'm running Mailman 2.1.13. Was the fix mentioned by Mark in 2007 not incorporated into the 2.1 branch? -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/266220 Title: Approved: only removed from text/plain part To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/266220/+subscriptions From 266220 at bugs.launchpad.net Tue Oct 11 19:01:58 2011 From: 266220 at bugs.launchpad.net (Johnathan Ritzi) Date: Tue, 11 Oct 2011 17:01:58 -0000 Subject: [Bug 266220] Re: Approved: only removed from text/plain part References: <20080905192945.27052.44689.launchpad@forster.canonical.com> Message-ID: <20111011170158.30116.17811.malone@soybean.canonical.com> Sorry, didn't read your comment in the other bug first. -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/266220 Title: Approved: only removed from text/plain part To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/266220/+subscriptions From 266220 at bugs.launchpad.net Tue Oct 11 19:05:29 2011 From: 266220 at bugs.launchpad.net (Johnathan Ritzi) Date: Tue, 11 Oct 2011 17:05:29 -0000 Subject: [Bug 266220] Re: Approved: only removed from text/plain part References: <20080905192945.27052.44689.launchpad@forster.canonical.com> Message-ID: <20111011170529.1459.8871.malone@gac.canonical.com> As requested in bug 871415, the Approved line in the HTML that was not removed was:
Appro= ved: passwo<= span class=3D"Apple-style-span" style=3D"background-color: rgb(255, 255, 25= 5);">rd
Pretty horrific HTML by Gmail, I know... -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/266220 Title: Approved: only removed from text/plain part To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/266220/+subscriptions From steveth45 at gmail.com Tue Oct 11 19:29:35 2011 From: steveth45 at gmail.com (Stephen A. Goss) Date: Tue, 11 Oct 2011 17:29:35 -0000 Subject: [Bug 872391] [NEW] KeyError: u'outgoing' in runner References: <20111011172935.1249.61590.malonedeb@gac.canonical.com> Message-ID: <20111011172935.1249.61590.malonedeb@gac.canonical.com> Public bug reported: Found this in my mailman.log. It may have happened around the time I was attempting to send a message through a mailing list and the SMTP receiver (fakemail.py in this case) died, so there were some failures to deliver. Oct 07 16:14:47 2011 (12057) Uncaught runner exception: u'outgoing' Oct 07 16:14:47 2011 (12057) Traceback (most recent call last): File "/home/phoenix/mailman_clone/src/mailman/core/runner.py", line 138, in _one_iteration self._process_one_file(msg, msgdata) File "/home/phoenix/mailman_clone/src/mailman/core/runner.py", line 220, in _process_one_file keepqueued = self._dispose(mlist, msg, msgdata) File "/home/phoenix/mailman_clone/src/mailman/runners/retry.py", line 40, in _dispose config.switchboards['outgoing'].enqueue(msg, msgdata) KeyError: u'outgoing' ** Affects: mailman Importance: Undecided Status: New ** 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/872391 Title: KeyError: u'outgoing' in runner To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/872391/+subscriptions From mark at msapiro.net Tue Oct 11 20:09:12 2011 From: mark at msapiro.net (Mark Sapiro) Date: Tue, 11 Oct 2011 18:09:12 -0000 Subject: [Bug 266220] Re: Approved: only removed from text/plain part References: <20080905192945.27052.44689.launchpad@forster.canonical.com> Message-ID: <20111011180912.1039.75327.malone@gac.canonical.com> I'm not going to try to handle that one. The current code looks in the HTML for a match to the pattern constructed by pattern = name + ':(\xA0|\s| )*' + re.escape(passwd) which seems to work in most cases. I'm not sure how the above was created, but at a minimum, the text was colored dark grey. If I just create a simple, 'rich formatting' message in gmail, I don't see that. Even with colored text, I see only things like Approved: password I suggest that your poster try creating the post using gmail's "plain text" composition if possible. This (at least in my tests) creates a simple text/plain message. If the poster feels it is necessary to include whatever fonts, colors, etc. that cause the 'Approved: password' line to be split up into those multiple segments, there's not much I can do. I could try to detect a case where I can find the Approved: password text if I strip out all the HTML tags, but not if I don't, and refuse to approve the post in that case, but I'm not sure how that should work. Probably, I should reject the post entirely with some reason like "Unable to remove 'Approved: password' text from HTML part". Holding the post doesn't seem right because it could be manually approved which would expose the password. -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/266220 Title: Approved: only removed from text/plain part To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/266220/+subscriptions From 266220 at bugs.launchpad.net Tue Oct 11 20:52:24 2011 From: 266220 at bugs.launchpad.net (Johnathan Ritzi) Date: Tue, 11 Oct 2011 18:52:24 -0000 Subject: [Bug 266220] Re: Approved: only removed from text/plain part References: <20080905192945.27052.44689.launchpad@forster.canonical.com> Message-ID: <20111011185224.14097.81471.malone@wampee.canonical.com> I believe all I did in that case was to copy and paste the "Approved" line from a previous email I sent, and it somehow got mutilated with HTML... I think rejection if you find the password in the stripped-out HTML part is a great idea. The dangerous part of this bug is that a failure in parsing can lead to an admin password being broadcast over email to hundreds of people. It seems like Mailman should either require the header or plain-text email and not even allow HTML emails, or ensure (via some liberal matching) that the password isn't going to get sent out if parsing fails. -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/266220 Title: Approved: only removed from text/plain part To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/266220/+subscriptions From 872538 at bugs.launchpad.net Tue Oct 11 23:19:12 2011 From: 872538 at bugs.launchpad.net (Michael Marvick) Date: Tue, 11 Oct 2011 21:19:12 -0000 Subject: [Bug 872538] [NEW] hyperlinks at end of email broken References: <20111011211912.24101.62075.malonedeb@chaenomeles.canonical.com> Message-ID: <20111011211912.24101.62075.malonedeb@chaenomeles.canonical.com> Public bug reported: I do not know exactly how to replicate this problem, as I am merely a subscriber on a mailman listserv. I received an email where there was a hyperlink to a webpage at the very end. Then, the default signature for the listserv was the next thing in the email. For some reason, the hyperlink had merged with the signature, causing the link to fail and the signature at the end to look awkward. I assume that the user forgot to include the end tag for the hyperlink at the end of the message, but I'm not entirely sure what happened. I would be happy to forward the email if necessary. ** 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/872538 Title: hyperlinks at end of email broken To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/872538/+subscriptions From mark at msapiro.net Wed Oct 12 00:17:00 2011 From: mark at msapiro.net (Mark Sapiro) Date: Tue, 11 Oct 2011 22:17:00 -0000 Subject: [Bug 872538] Re: hyperlinks at end of email broken References: <20111011211912.24101.62075.malonedeb@chaenomeles.canonical.com> Message-ID: <20111011221700.24520.15136.malone@chaenomeles.canonical.com> I don't know what happened either, but it appears that the list admin may have specified the list's msg_footer incorrectly. What I do know is this. Footers can't contain HTML tags because footers are always added either directly to the end of a text/plain message or in a separate text/plain message part. If URLs in footers are rendered as hyperlinks, it is the recipient's mail client that is doing this. When Mailman adds a footer at the end of a text/plain message, it always ensures there is at least one newline between the message body and the footer, so the possible explanations that I see are either a broken mail client is reading the message, or the footer was created with the URL not separated from the rest of the footer, or this is not standard GNU Mailman. I would have to see the raw message to say more. ** 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/872538 Title: hyperlinks at end of email broken To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/872538/+subscriptions From mark at msapiro.net Wed Oct 12 00:20:09 2011 From: mark at msapiro.net (Mark Sapiro) Date: Tue, 11 Oct 2011 22:20:09 -0000 Subject: [Bug 872538] Re: hyperlinks at end of email broken References: <20111011211912.24101.62075.malonedeb@chaenomeles.canonical.com> Message-ID: <20111011222009.1249.93393.malone@gac.canonical.com> You can either forward the mail to me (see my Launchpad profile) or save it to a file and attach that to this report. -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/872538 Title: hyperlinks at end of email broken To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/872538/+subscriptions From mark at msapiro.net Fri Oct 14 05:55:26 2011 From: mark at msapiro.net (Mark Sapiro) Date: Fri, 14 Oct 2011 03:55:26 -0000 Subject: [Bug 873821] [NEW] cron/checkdbs doesn't report unsubscribe requests References: <20111014035526.1785.70306.malonedeb@gac.canonical.com> Message-ID: <20111014035526.1785.70306.malonedeb@gac.canonical.com> Public bug reported: The daily "nn LISTNAME moderator requests" mail counts unsubscribe requests in the total, but doesn't list them. ** Affects: mailman Importance: Low Assignee: Mark Sapiro (msapiro) Status: Triaged -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/873821 Title: cron/checkdbs doesn't report unsubscribe requests To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/873821/+subscriptions From mark at msapiro.net Fri Oct 14 06:30:06 2011 From: mark at msapiro.net (Mark Sapiro) Date: Fri, 14 Oct 2011 04:30:06 -0000 Subject: [Bug 873821] Re: cron/checkdbs doesn't report unsubscribe requests References: <20111014035526.1785.70306.malonedeb@gac.canonical.com> Message-ID: <20111014043007.23802.24401.launchpad@chaenomeles.canonical.com> ** 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/873821 Title: cron/checkdbs doesn't report unsubscribe requests To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/873821/+subscriptions From mark at msapiro.net Fri Oct 14 06:33:50 2011 From: mark at msapiro.net (Mark Sapiro) Date: Fri, 14 Oct 2011 04:33:50 -0000 Subject: [Bug 266220] Re: Approved: only removed from text/plain part References: <20080905192945.27052.44689.launchpad@forster.canonical.com> Message-ID: <20111014043350.14308.48064.malone@wampee.canonical.com> The fix for this bug has been enhanced as discussed in comments #6 and #7. The enhanced fix is committed for release with Mailman 2.1.15. ** Changed in: mailman Status: Fix Released => Fix Committed ** Changed in: mailman Milestone: 2.1-beta => 2.1.15 ** 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/266220 Title: Approved: only removed from text/plain part To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/266220/+subscriptions From steveth45 at gmail.com Fri Oct 14 20:21:02 2011 From: steveth45 at gmail.com (Stephen A. Goss) Date: Fri, 14 Oct 2011 18:21:02 -0000 Subject: [Bug 869317] Re: Mailman startup script missing --force option. References: <20111006162028.11515.35600.malonedeb@gac.canonical.com> Message-ID: <20111014182102.30342.1048.malone@soybean.canonical.com> The patch I uploaded doesn't really fix the problem. With that patch, if there is a stale lock file, it raises an AttributeError, then if you run with --force, you get a different error, and then if you try again without the --force option it starts up normally :/ -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/869317 Title: Mailman startup script missing --force option. To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/869317/+subscriptions From barry at list.org Fri Oct 14 20:37:28 2011 From: barry at list.org (Barry Warsaw) Date: Fri, 14 Oct 2011 14:37:28 -0400 Subject: [Bug 869317] Re: Mailman startup script missing --force option. In-Reply-To: <20111014182102.30342.1048.malone@soybean.canonical.com> References: <20111006162028.11515.35600.malonedeb@gac.canonical.com> <20111014182102.30342.1048.malone@soybean.canonical.com> Message-ID: <20111014143728.1ab92430@limelight.wooz.org> On Oct 14, 2011, at 06:21 PM, Stephen A. Goss wrote: >The patch I uploaded doesn't really fix the problem. With that patch, >if there is a stale lock file, it raises an AttributeError, then if you >run with --force, you get a different error, and then if you try again >without the --force option it starts up normally :/ I think I have a fix in my local copy, but I'm currently hung up on one particularly nasty test failure. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 836 bytes Desc: not available URL: From 869317 at bugs.launchpad.net Fri Oct 14 20:37:28 2011 From: 869317 at bugs.launchpad.net (Barry Warsaw) Date: Fri, 14 Oct 2011 18:37:28 -0000 Subject: [Bug 869317] Re: Mailman startup script missing --force option. References: <20111006162028.11515.35600.malonedeb@gac.canonical.com> <20111014182102.30342.1048.malone@soybean.canonical.com> Message-ID: <20111014143728.1ab92430@limelight.wooz.org> On Oct 14, 2011, at 06:21 PM, Stephen A. Goss wrote: >The patch I uploaded doesn't really fix the problem. With that patch, >if there is a stale lock file, it raises an AttributeError, then if you >run with --force, you get a different error, and then if you try again >without the --force option it starts up normally :/ I think I have a fix in my local copy, but I'm currently hung up on one particularly nasty test failure. -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/869317 Title: Mailman startup script missing --force option. To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/869317/+subscriptions From vincent.fretin at gmail.com Sat Oct 15 12:24:01 2011 From: vincent.fretin at gmail.com (Vincent Fretin) Date: Sat, 15 Oct 2011 10:24:01 -0000 Subject: [Bug 874929] [NEW] Missing aliases in postfix_lmtp file when using more than one mailing-list References: <20111015102401.825.28137.malonedeb@gac.canonical.com> Message-ID: <20111015102401.825.28137.malonedeb@gac.canonical.com> Public bug reported: With mailman 3.0.0a8. When I create a first mailing-list, I get in var/data/postfix_lmtp cpoi at example.com lmtp:[127.0.0.1]:8024 cpoi-bounces at example.com lmtp:[127.0.0.1]:8024 cpoi-confirm at example.com lmtp:[127.0.0.1]:8024 cpoi-join at example.com lmtp:[127.0.0.1]:8024 cpoi-leave at example.com lmtp:[127.0.0.1]:8024 cpoi-owner at example.com lmtp:[127.0.0.1]:8024 cpoi-request at example.com lmtp:[127.0.0.1]:8024 cpoi-subscribe at example.com lmtp:[127.0.0.1]:8024 cpoi-unsubscribe at example.com lmtp:[127.0.0.1]:8024 Then if I create a second mailing-list, I get: cpoi at example.com lmtp:[127.0.0.1]:8024 test at example.com lmtp:[127.0.0.1]:8024 test-bounces at example.com lmtp:[127.0.0.1]:8024 test-confirm at example.com lmtp:[127.0.0.1]:8024 test-join at example.com lmtp:[127.0.0.1]:8024 test-leave at example.com lmtp:[127.0.0.1]:8024 test-owner at example.com lmtp:[127.0.0.1]:8024 test-request at example.com lmtp:[127.0.0.1]:8024 test-subscribe at example.com lmtp:[127.0.0.1]:8024 test-unsubscribe at example.com lmtp:[127.0.0.1]:8024 I lost all aliases of the first mailing-list. I attached a patch for the src/mailman/mta/postfix.py file. ** 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/874929 Title: Missing aliases in postfix_lmtp file when using more than one mailing- list To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/874929/+subscriptions From vincent.fretin at gmail.com Sat Oct 15 12:24:01 2011 From: vincent.fretin at gmail.com (Vincent Fretin) Date: Sat, 15 Oct 2011 10:24:01 -0000 Subject: [Bug 874929] Re: Missing aliases in postfix_lmtp file when using more than one mailing-list References: <20111015102401.825.28137.malonedeb@gac.canonical.com> Message-ID: <20111015102401.825.1406.malone@gac.canonical.com> ** Patch added: "Fixed of losing aliases for previous mailing-list" https://bugs.launchpad.net/bugs/874929/+attachment/2546793/+files/mta_postfix.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/874929 Title: Missing aliases in postfix_lmtp file when using more than one mailing- list To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/874929/+subscriptions From 874929 at bugs.launchpad.net Sat Oct 15 15:48:09 2011 From: 874929 at bugs.launchpad.net (Barry Warsaw) Date: Sat, 15 Oct 2011 13:48:09 -0000 Subject: [Bug 874929] Re: Missing aliases in postfix_lmtp file when using more than one mailing-list References: <20111015102401.825.28137.malonedeb@gac.canonical.com> Message-ID: <20111015134809.24727.82732.launchpad@chaenomeles.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/874929 Title: Missing aliases in postfix_lmtp file when using more than one mailing- list To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/874929/+subscriptions From 869317 at bugs.launchpad.net Sun Oct 16 21:49:27 2011 From: 869317 at bugs.launchpad.net (Barry Warsaw) Date: Sun, 16 Oct 2011 19:49:27 -0000 Subject: [Bug 869317] Re: Mailman startup script missing --force option. References: <20111006162028.11515.35600.malonedeb@gac.canonical.com> Message-ID: <20111016194928.30011.37072.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/869317 Title: Mailman startup script missing --force option. To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/869317/+subscriptions From 874929 at bugs.launchpad.net Sun Oct 16 22:16:02 2011 From: 874929 at bugs.launchpad.net (Barry Warsaw) Date: Sun, 16 Oct 2011 20:16:02 -0000 Subject: [Bug 874929] Re: Missing aliases in postfix_lmtp file when using more than one mailing-list References: <20111015102401.825.28137.malonedeb@gac.canonical.com> Message-ID: <20111016201602.929.21025.malone@gac.canonical.com> Thanks Vincent! Fixed in bzr. ** Changed in: mailman Milestone: None => 3.0.0b1 ** Changed in: mailman Assignee: (unassigned) => Barry Warsaw (barry) ** Changed in: mailman Importance: Undecided => Medium ** Changed in: mailman Status: New => In Progress ** 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/874929 Title: Missing aliases in postfix_lmtp file when using more than one mailing- list To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/874929/+subscriptions From 872391 at bugs.launchpad.net Sun Oct 16 22:18:58 2011 From: 872391 at bugs.launchpad.net (Barry Warsaw) Date: Sun, 16 Oct 2011 20:18:58 -0000 Subject: [Bug 872391] Re: KeyError: u'outgoing' in runner References: <20111011172935.1249.61590.malonedeb@gac.canonical.com> Message-ID: <20111016201858.23901.26452.malone@chaenomeles.canonical.com> Thanks for the report. I think for now I'll mark this Incomplete until we get more information or a reproducible test case. ** 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/872391 Title: KeyError: u'outgoing' in runner To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/872391/+subscriptions From 869347 at bugs.launchpad.net Sun Oct 16 22:31:56 2011 From: 869347 at bugs.launchpad.net (Barry Warsaw) Date: Sun, 16 Oct 2011 20:31:56 -0000 Subject: [Bug 869347] Re: bin/test script fails unless zope.testrunner is pip installed References: <20111006171509.28591.25023.malonedeb@soybean.canonical.com> Message-ID: <20111016203156.30221.24458.launchpad@soybean.canonical.com> ** Changed in: mailman Status: New => Incomplete ** Changed in: mailman Importance: Undecided => Low -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/869347 Title: bin/test script fails unless zope.testrunner is pip installed To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/869347/+subscriptions From 869347 at bugs.launchpad.net Sun Oct 16 22:39:09 2011 From: 869347 at bugs.launchpad.net (Barry Warsaw) Date: Sun, 16 Oct 2011 20:39:09 -0000 Subject: [Bug 869347] Re: bin/test script fails unless zope.testrunner is pip installed References: <20111006171509.28591.25023.malonedeb@soybean.canonical.com> Message-ID: <20111016203910.13355.28858.malone@wampee.canonical.com> Are you sure you started with a clean environment? In a bzr trunk checkout (try `bzr clean-tree --ignored`) I did the following: $ virtualenv /tmp/xx $ source /tmp/xx/bin/activate $ python setup.py install $ buildout $ bin/test Everything worked and all tests succeeded. The other thing is that I'm not even sure if buildout is supposed to be compatible with virtualenv. Assuming it is, I'm still thinking about getting rid of buildout support for the final release. The hang up right now is replacing zope.testrunner. -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/869347 Title: bin/test script fails unless zope.testrunner is pip installed To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/869347/+subscriptions From vincent.fretin at gmail.com Mon Oct 17 21:18:40 2011 From: vincent.fretin at gmail.com (Vincent Fretin) Date: Mon, 17 Oct 2011 19:18:40 -0000 Subject: [Bug 876774] [NEW] AttributeError: 'MailingList' object has no attribute 'bounce_processing' References: <20111017191840.17234.34787.malonedeb@soybean.canonical.com> Message-ID: <20111017191840.17234.34787.malonedeb@soybean.canonical.com> Public bug reported: With mailman 3.0.0a8 Oct 17 12:06:34 2011 (15436) Traceback (most recent call last): File "/home/zope/mailman/src/mailman/core/runner.py", line 138, in _one_iteration self._process_one_file(msg, msgdata) File "/home/zope/mailman/src/mailman/core/runner.py", line 220, in _process_one_file keepqueued = self._dispose(mlist, msg, msgdata) File "/home/zope/mailman/src/mailman/runners/bounce.py", line 46, in _dispose if not mlist.bounce_processing: AttributeError: 'MailingList' object has no attribute 'bounce_processing' It seems that bounce_processing is defined in src/mailman/styles/default.py The style are applied at mailing-list creation, but bounce_processing attribute is not persisted, the src/mailman/database/mailman.sql file doesn't define it. ** 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/876774 Title: AttributeError: 'MailingList' object has no attribute 'bounce_processing' To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/876774/+subscriptions From 876774 at bugs.launchpad.net Mon Oct 17 22:06:47 2011 From: 876774 at bugs.launchpad.net (Barry Warsaw) Date: Mon, 17 Oct 2011 20:06:47 -0000 Subject: [Bug 876774] Re: AttributeError: 'MailingList' object has no attribute 'bounce_processing' References: <20111017191840.17234.34787.malonedeb@soybean.canonical.com> Message-ID: <20111017200647.29279.87551.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/876774 Title: AttributeError: 'MailingList' object has no attribute 'bounce_processing' To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/876774/+subscriptions From 860159 at bugs.launchpad.net Sat Oct 22 22:18:11 2011 From: 860159 at bugs.launchpad.net (Barry Warsaw) Date: Sat, 22 Oct 2011 20:18:11 -0000 Subject: [Bug 860159] Re: Mailman 3.0 support for Postgres References: <20110927001849.9391.31768.malonedeb@gac.canonical.com> Message-ID: <20111022201812.21740.37974.launchpad@chaenomeles.canonical.com> ** 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/860159 Title: Mailman 3.0 support for Postgres To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/860159/+subscriptions From 860159 at bugs.launchpad.net Sat Oct 22 23:59:51 2011 From: 860159 at bugs.launchpad.net (Barry Warsaw) Date: Sat, 22 Oct 2011 21:59:51 -0000 Subject: [Bug 860159] Re: Mailman 3.0 support for Postgres References: <20110927001849.9391.31768.malonedeb@gac.canonical.com> Message-ID: <20111022215951.23677.62781.malone@gac.canonical.com> I'm going to accept the patch and merge it into trunk, with some refactoring to separate out the SQLite and PostgreSQL database. You will need to change the `class` key in the [database] section of your mailman.cfg to enable PostgreSQL. We still need documentation, and if possible tests against Postgres. -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/860159 Title: Mailman 3.0 support for Postgres To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/860159/+subscriptions From 860159 at bugs.launchpad.net Sun Oct 23 01:14:36 2011 From: 860159 at bugs.launchpad.net (Barry Warsaw) Date: Sat, 22 Oct 2011 23:14:36 -0000 Subject: [Bug 860159] Re: Mailman 3.0 support for Postgres References: <20110927001849.9391.31768.malonedeb@gac.canonical.com> Message-ID: <20111022231436.24492.52742.malone@gac.canonical.com> I've had to comment out a few more constraints to get the suite to run without failure. I do still get 7 test failures with the branch though. I'll push what I have and will continue to work on getting the test suite to pass. I won't merge the branch until I do. Then I'll file a separate bug on the constraint issues. ** Branch linked: lp:~barry/mailman/postgres-merge -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/860159 Title: Mailman 3.0 support for Postgres To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/860159/+subscriptions From 860159 at bugs.launchpad.net Sun Oct 23 02:08:17 2011 From: 860159 at bugs.launchpad.net (Barry Warsaw) Date: Sun, 23 Oct 2011 00:08:17 -0000 Subject: [Bug 860159] Re: Mailman 3.0 support for Postgres References: <20110927001849.9391.31768.malonedeb@gac.canonical.com> Message-ID: <20111023000818.2825.76269.malone@wampee.canonical.com> I'm down to three test failures in the above branch. There seems to be two actual bugs going on here: 1) Even though I fixed the SQL type for digest_size_threshold to REAL for Postgres (and FLOAT for SQLite, but it doesn't care), it still seems that when we store 10.5 into it in configuration.rst, 11.0 comes out. 2) It looks to me like Postgres doesn't reset the primary key id to 1 for deleted tables. Two of the failing tests print the Pended dictionary, which contains its id, i.e. its primary key. For SQLite, this always gets reset to 1 for subsequent tests (because we delete all tables between every test). For Postgres though, deleting the table does not seem to reset the primary key back to 1. This might be a case where the tests need to be fixed to not assume the id is already reset at the beginning of the test, unless there's a good way to guarantee this for Postgres. -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/860159 Title: Mailman 3.0 support for Postgres To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/860159/+subscriptions From 860159 at bugs.launchpad.net Mon Oct 24 03:46:31 2011 From: 860159 at bugs.launchpad.net (Barry Warsaw) Date: Mon, 24 Oct 2011 01:46:31 -0000 Subject: [Bug 860159] Re: Mailman 3.0 support for Postgres References: <20110927001849.9391.31768.malonedeb@gac.canonical.com> Message-ID: <20111024014632.22364.56121.malone@chaenomeles.canonical.com> Never mind. I've fixed these all and now have the full test suite working with PostgreSQL. I'll write up a little documentation and merge this to trunk. Thanks for the great work! -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/860159 Title: Mailman 3.0 support for Postgres To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/860159/+subscriptions From 860159 at bugs.launchpad.net Mon Oct 24 04:13:32 2011 From: 860159 at bugs.launchpad.net (Barry Warsaw) Date: Mon, 24 Oct 2011 02:13:32 -0000 Subject: [Bug 860159] Re: Mailman 3.0 support for Postgres References: <20110927001849.9391.31768.malonedeb@gac.canonical.com> Message-ID: <20111024021333.16633.95225.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/860159 Title: Mailman 3.0 support for Postgres To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/860159/+subscriptions From 880613 at bugs.launchpad.net Mon Oct 24 04:16:01 2011 From: 880613 at bugs.launchpad.net (Barry Warsaw) Date: Mon, 24 Oct 2011 02:16:01 -0000 Subject: [Bug 880613] [NEW] PostgreSQL constraints disabled References: <20111024021601.22590.71420.malonedeb@chaenomeles.canonical.com> Message-ID: <20111024021601.22590.71420.malonedeb@chaenomeles.canonical.com> Public bug reported: In src/mailman/database/sql/postgres.sql, several foreign key constraints have been commented out because otherwise the test suite, or other aspects do not work. This is probably because there are cases where Mailman violates these constraints, but SQLite3 (the default database) does not care. All disabled constraints are marked with XXX in the above file. Really, these should be fixed. ** Affects: mailman Importance: Medium Status: Confirmed ** 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/880613 Title: PostgreSQL constraints disabled To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/880613/+subscriptions From steveth45 at gmail.com Mon Oct 24 19:37:22 2011 From: steveth45 at gmail.com (Stephen A. Goss) Date: Mon, 24 Oct 2011 17:37:22 -0000 Subject: [Bug 880990] [NEW] Broken archiver: pipermail: TypeError: decoding Unicode is not supported References: <20111024173722.22015.38940.malonedeb@gac.canonical.com> Message-ID: <20111024173722.22015.38940.malonedeb@gac.canonical.com> Public bug reported: I enabled the pipermail archiver in the cfg and sent a single email through a list to see how well it works. Found this error in mailman.log: Oct 23 20:54:47 2011 (3824) Broken archiver: pipermail Traceback (most recent call last): File "/home/phoenix/mailman_clone/src/mailman/runners/archive.py", line 87, in _dispose archiver.archive_message(mlist, msg) File "/home/phoenix/mailman_clone/src/mailman/archiving/pipermail.py", line 123, in archive_message h.processUnixMailbox(path) File "/home/phoenix/mailman_clone/src/mailman/Archiver/pipermail.py", line 572, in processUnixMailbox self.add_article(a) File "/home/phoenix/mailman_clone/src/mailman/Archiver/pipermail.py", line 604, in add_article temp = self.format_article(article) File "/home/phoenix/mailman_clone/src/mailman/Archiver/HyperArch.py", line 1198, in format_article self.__processbody_URLquote(lines) File "/home/phoenix/mailman_clone/src/mailman/Archiver/HyperArch.py", line 1096, in __processbody_URLquote atmark = unicode(atmark, self.lang.charset, 'replace') TypeError: decoding Unicode is not supported ** Affects: mailman Importance: Undecided Status: New ** 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/880990 Title: Broken archiver: pipermail: TypeError: decoding Unicode is not supported To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/880990/+subscriptions From steveth45 at gmail.com Mon Oct 24 20:09:15 2011 From: steveth45 at gmail.com (Stephen A. Goss) Date: Mon, 24 Oct 2011 18:09:15 -0000 Subject: [Bug 872391] Re: KeyError: u'outgoing' in runner References: <20111011172935.1249.61590.malonedeb@gac.canonical.com> Message-ID: <20111024180915.2509.89266.malone@wampee.canonical.com> >From mailman.cfg: [runner.out] class: mailman.runners.outgoing.OutgoingRunner >From switchboard.py: @staticmethod def initialize(): """Initialize the global switchboards for input/output.""" for conf in config.runner_configs: name = conf.name.split('.')[-1] ... config.switchboards[name] = Switchboard(name, path) It looks like the name of the runner should be config.switchboards['out'], not ['outgoing'] -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/872391 Title: KeyError: u'outgoing' in runner To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/872391/+subscriptions From steveth45 at gmail.com Mon Oct 24 22:33:33 2011 From: steveth45 at gmail.com (Stephen A. Goss) Date: Mon, 24 Oct 2011 20:33:33 -0000 Subject: [Merge] lp:~postfuturist/mailman/retry-test into lp:mailman Message-ID: <20111024203322.8255.33299.launchpad@ackee.canonical.com> Stephen A. Goss has proposed merging lp:~postfuturist/mailman/retry-test into lp:mailman. Requested reviews: Mailman Coders (mailman-coders) Related bugs: Bug #872391 in GNU Mailman: "KeyError: u'outgoing' in runner" https://bugs.launchpad.net/mailman/+bug/872391 For more details, see: https://code.launchpad.net/~postfuturist/mailman/retry-test/+merge/80267 The RetryRunner has a simple but fatal bug. This branch includes a fix, plus a unit test that tests the basic function of the RetryRunner. -- https://code.launchpad.net/~postfuturist/mailman/retry-test/+merge/80267 Your team Mailman Coders is requested to review the proposed merge of lp:~postfuturist/mailman/retry-test into lp:mailman. -------------- next part -------------- A non-text attachment was scrubbed... Name: review-diff.txt Type: text/x-diff Size: 2757 bytes Desc: not available URL: From steveth45 at gmail.com Mon Oct 24 22:29:16 2011 From: steveth45 at gmail.com (Stephen A. Goss) Date: Mon, 24 Oct 2011 20:29:16 -0000 Subject: [Bug 872391] Re: KeyError: u'outgoing' in runner References: <20111011172935.1249.61590.malonedeb@gac.canonical.com> Message-ID: <20111024202917.23461.13266.launchpad@gac.canonical.com> ** Branch linked: lp:~postfuturist/mailman/retry-test -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/872391 Title: KeyError: u'outgoing' in runner To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/872391/+subscriptions From 872391 at bugs.launchpad.net Tue Oct 25 03:08:12 2011 From: 872391 at bugs.launchpad.net (Barry Warsaw) Date: Tue, 25 Oct 2011 01:08:12 -0000 Subject: [Bug 872391] Re: KeyError: u'outgoing' in runner References: <20111011172935.1249.61590.malonedeb@gac.canonical.com> Message-ID: <20111025010812.3522.73526.launchpad@chaenomeles.canonical.com> ** Changed in: mailman Status: Incomplete => Confirmed ** Changed in: mailman Milestone: None => 3.0.0b1 ** Changed in: mailman Assignee: (unassigned) => Barry Warsaw (barry) ** Changed in: mailman Importance: Undecided => Medium -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/872391 Title: KeyError: u'outgoing' in runner To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/872391/+subscriptions From noreply at launchpad.net Tue Oct 25 03:18:29 2011 From: noreply at launchpad.net (noreply at launchpad.net) Date: Tue, 25 Oct 2011 01:18:29 -0000 Subject: [Merge] lp:~postfuturist/mailman/retry-test into lp:mailman In-Reply-To: <20111024203322.8255.33299.launchpad@ackee.canonical.com> Message-ID: <20111025011823.18191.59256.launchpad@ackee.canonical.com> The proposal to merge lp:~postfuturist/mailman/retry-test into lp:mailman has been updated. Status: Needs review => Merged For more details, see: https://code.launchpad.net/~postfuturist/mailman/retry-test/+merge/80267 -- https://code.launchpad.net/~postfuturist/mailman/retry-test/+merge/80267 Your team Mailman Coders is requested to review the proposed merge of lp:~postfuturist/mailman/retry-test into lp:mailman. From 872391 at bugs.launchpad.net Tue Oct 25 03:16:37 2011 From: 872391 at bugs.launchpad.net (Barry Warsaw) Date: Tue, 25 Oct 2011 01:16:37 -0000 Subject: [Bug 872391] Re: KeyError: u'outgoing' in runner References: <20111011172935.1249.61590.malonedeb@gac.canonical.com> Message-ID: <20111025011638.3187.39535.launchpad@chaenomeles.canonical.com> ** 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/872391 Title: KeyError: u'outgoing' in runner To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/872391/+subscriptions From 876774 at bugs.launchpad.net Tue Oct 25 04:41:34 2011 From: 876774 at bugs.launchpad.net (Barry Warsaw) Date: Tue, 25 Oct 2011 02:41:34 -0000 Subject: [Bug 876774] Re: AttributeError: 'MailingList' object has no attribute 'bounce_processing' References: <20111017191840.17234.34787.malonedeb@soybean.canonical.com> Message-ID: <20111025024134.23461.15038.launchpad@gac.canonical.com> ** Changed in: mailman Milestone: None => 3.0.0b1 ** Changed in: mailman Assignee: (unassigned) => Barry Warsaw (barry) ** Changed in: mailman Importance: Undecided => Medium ** Changed in: mailman Status: New => 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/876774 Title: AttributeError: 'MailingList' object has no attribute 'bounce_processing' To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/876774/+subscriptions From vincent.fretin at gmail.com Tue Oct 25 10:55:38 2011 From: vincent.fretin at gmail.com (Vincent Fretin) Date: Tue, 25 Oct 2011 08:55:38 -0000 Subject: [Bug 881312] [NEW] Properly decode payload References: <20111025085538.27451.45372.malonedeb@soybean.canonical.com> Message-ID: <20111025085538.27451.45372.malonedeb@soybean.canonical.com> Public bug reported: With mailman 3.0.0a8 in src/mailman/runners/command.py, there is an issue with body = part.get_payload(decode=True) if you send a mail to test-unsubscribe at example.com, with accents in the mail, in the signature for example, you get a body string encoded in iso-8859-1. When you try to concatenate iso-8859-1 string with unicode, this the case when the mail body with "Unprocessed:" and "Ignored:" is generated, you get a UnicodeDecodeError ascii. The code should be modified to correctly decode the mail body like it is done in src/mailman/pipeline/decorate.py mcset = msg.get_content_charset() or 'us-ascii' unicode(msg.get_payload(decode=True), mcset) There are similar issues in src/mailman/rules/administrivia.py with the line: if line == '': where it give you a warning because it compare an iso to an empty unicode. and in src/mailman/rules/approved.py where it simply crashes: Oct 18 17:54:41 2011 (18207) Traceback (most recent call last): File "/home/zope/mailman/src/mailman/core/runner.py", line 138, in _one_iteration self._process_one_file(msg, msgdata) File "/home/zope/mailman/src/mailman/core/runner.py", line 220, in _process_one_file keepqueued = self._dispose(mlist, msg, msgdata) File "/home/zope/mailman/src/mailman/runners/incoming.py", line 65, in _dispose process(mlist, msg, msgdata, mlist.start_chain) File "/home/zope/mailman/src/mailman/core/chains.py", line 68, in process if link.rule.check(mlist, msg, msgdata): File "/home/zope/mailman/src/mailman/rules/approved.py", line 81, in check if ':' in line: UnicodeDecodeError: 'ascii' codec can't decode byte 0xe0 in position 14: invalid continuation byte Currently, mailman is unusable for another language than English, like French. ** 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/881312 Title: Properly decode payload To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/881312/+subscriptions From vincent.fretin at gmail.com Tue Oct 25 11:03:01 2011 From: vincent.fretin at gmail.com (Vincent Fretin) Date: Tue, 25 Oct 2011 09:03:01 -0000 Subject: [Bug 881316] [NEW] RuntimeError: maximum recursion depth exceeded while pickling an object References: <20111025090301.27890.71203.malonedeb@soybean.canonical.com> Message-ID: <20111025090301.27890.71203.malonedeb@soybean.canonical.com> Public bug reported: With mailman 3.0.0a8. I got the following traceback from a html mail with html signature+image from Outlook, Oct 14 09:21:31 2011 (17579) Traceback (most recent call last): File "/home/zope/mailman/src/mailman/core/runner.py", line 138, in _one_iteration self._process_one_file(msg, msgdata) File "/home/zope/mailman/src/mailman/core/runner.py", line 220, in _process_one_file keepqueued = self._dispose(mlist, msg, msgdata) File "/home/zope/mailman/src/mailman/runners/incoming.py", line 64, in _dispose process(mlist, msg, msgdata, mlist.start_chain) File "/home/zope/mailman/src/mailman/core/chains.py", line 90, in process link.function(mlist, msg, msgdata) File "/home/zope/mailman/src/mailman/chains/hold.py", line 245, in _process nmsg.send(mlist, **dict(tomoderators=True)) File "/home/zope/mailman/src/mailman/email/message.py", line 198, in send self._enqueue(mlist, **_kws) File "/home/zope/mailman/src/mailman/email/message.py", line 216, in _enqueue virginq.enqueue(self, **str_keywords) File "/home/zope/mailman/src/mailman/core/switchboard.py", line 133, in enqueue msgsave = cPickle.dumps(_msg, protocol) RuntimeError: maximum recursion depth exceeded while pickling an object It's really an obscure issue for me. I resolved it by adding sys.setrecursionlimit(10000) in src/mailman/core/switchboard.py before msgsave = cPickle.dumps(_msg, protocol) line 134 and doing bin/mailman unshunt fixed the issue. By default sys.getrecursionlimit() returns 1000. If you want to have a test email to reproduce, I can ask my customer to send an email to a test mailing-list. ** 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/881316 Title: RuntimeError: maximum recursion depth exceeded while pickling an object To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/881316/+subscriptions From vincent.fretin at gmail.com Tue Oct 25 11:09:49 2011 From: vincent.fretin at gmail.com (Vincent Fretin) Date: Tue, 25 Oct 2011 09:09:49 -0000 Subject: [Bug 881320] [NEW] Mailman 3 translations References: <20111025090949.27890.99511.malonedeb@soybean.canonical.com> Message-ID: <20111025090949.27890.99511.malonedeb@soybean.canonical.com> Public bug reported: In mailman 3.0.0a8, the locales directory contains actually mailman 2 translations. The unsubscribe mail is not translated into French because the msgids are different between mailman2 and mailman3. Do you have a script to generate a pot file and sync the po files? I had to generate myself the French mo file from the po. It's maybe a good idea to include mo files in the sdist, or generate mo files at mailman startup. ** 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/881320 Title: Mailman 3 translations To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/881320/+subscriptions From 881312 at bugs.launchpad.net Tue Oct 25 13:33:37 2011 From: 881312 at bugs.launchpad.net (Barry Warsaw) Date: Tue, 25 Oct 2011 11:33:37 -0000 Subject: [Bug 881312] Re: Properly decode payload References: <20111025085538.27451.45372.malonedeb@soybean.canonical.com> Message-ID: <20111025113338.19705.31674.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/881312 Title: Properly decode payload To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/881312/+subscriptions From 881320 at bugs.launchpad.net Tue Oct 25 13:32:58 2011 From: 881320 at bugs.launchpad.net (Barry Warsaw) Date: Tue, 25 Oct 2011 11:32:58 -0000 Subject: [Bug 881320] Re: Mailman 3 translations References: <20111025090949.27890.99511.malonedeb@soybean.canonical.com> Message-ID: <20111025113258.17261.77601.launchpad@gac.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/881320 Title: Mailman 3 translations To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/881320/+subscriptions From 881316 at bugs.launchpad.net Tue Oct 25 13:33:18 2011 From: 881316 at bugs.launchpad.net (Barry Warsaw) Date: Tue, 25 Oct 2011 11:33:18 -0000 Subject: [Bug 881316] Re: RuntimeError: maximum recursion depth exceeded while pickling an object References: <20111025090301.27890.71203.malonedeb@soybean.canonical.com> Message-ID: <20111025113318.19210.86457.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/881316 Title: RuntimeError: maximum recursion depth exceeded while pickling an object To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/881316/+subscriptions From steveth45 at gmail.com Tue Oct 25 23:56:05 2011 From: steveth45 at gmail.com (Stephen A. Goss) Date: Tue, 25 Oct 2011 21:56:05 -0000 Subject: [Bug 880990] Re: Broken archiver: pipermail: TypeError: decoding Unicode is not supported References: <20111024173722.22015.38940.malonedeb@gac.canonical.com> Message-ID: <20111025215606.19606.48134.malone@wampee.canonical.com> It tries to encode an already Unicode encoded string as Unicode, causing an error. This attachment is a quick work-around. ** Patch added: "880990.patch" https://bugs.launchpad.net/mailman/+bug/880990/+attachment/2572647/+files/880990.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/880990 Title: Broken archiver: pipermail: TypeError: decoding Unicode is not supported To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/880990/+subscriptions From steveth45 at gmail.com Wed Oct 26 00:10:52 2011 From: steveth45 at gmail.com (Stephen A. Goss) Date: Tue, 25 Oct 2011 22:10:52 -0000 Subject: [Bug 881699] [NEW] pipermail archiver renders the file location of HTML template, not the template itself References: <20111025221052.19606.11498.malonedeb@wampee.canonical.com> Message-ID: <20111025221052.19606.11498.malonedeb@wampee.canonical.com> Public bug reported: To reproduce, enable pipermail archiver and send an email to one of your mailing lists. In the archive folder for your mailing list there will be some generated HTML files and folders. Take a look at index.html, it will contain the absolute file path of the template it should have rendered, unless I'm confused about how the archives are supposed to work: /home/phoenix/mailman_clone/src/mailman/templates/en/archtocnombox.html One of the month archive folders might have an index.html that looks like this: /home/phoenix/mailman_clone/src/mailman/templates/en/archidxhead.html /home/phoenix/mailman_clone/src/mailman/templates/en/archidxentry.html /home/phoenix/mailman_clone/src/mailman/templates/en/archidxfoot.html ** Affects: mailman Importance: Undecided Status: New ** 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/881699 Title: pipermail archiver renders the file location of HTML template, not the template itself To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/881699/+subscriptions From steveth45 at gmail.com Wed Oct 26 00:46:37 2011 From: steveth45 at gmail.com (Stephen A. Goss) Date: Tue, 25 Oct 2011 22:46:37 -0000 Subject: [Bug 881699] Re: pipermail archiver renders the file location of HTML template, not the template itself References: <20111025221052.19606.11498.malonedeb@wampee.canonical.com> Message-ID: <20111025224637.16720.99222.malone@soybean.canonical.com> A simple fix: the template rendering code was misconstruing the return value of the find function from mailman/utilities/i18n.py . ** Patch added: "881699.patch" https://bugs.launchpad.net/mailman/+bug/881699/+attachment/2572699/+files/881699.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/881699 Title: pipermail archiver renders the file location of HTML template, not the template itself To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/881699/+subscriptions From noreply at launchpad.net Thu Oct 27 12:20:19 2011 From: noreply at launchpad.net (noreply at launchpad.net) Date: Thu, 27 Oct 2011 10:20:19 -0000 Subject: [Branch ~mailman-coders/mailman.client/trunk] Rev 17: - Fixes bug lp:882491 (breaking tests, caused by renaming of config sections in MM core) Message-ID: <20111027102019.798.32554.launchpad@ackee.canonical.com> ------------------------------------------------------------ revno: 17 fixes bugs: https://launchpad.net/bugs/882491 https://launchpad.net/bugs/882395 committer: Florian Fuchs branch nick: mailman.client timestamp: Thu 2011-10-27 12:17:10 +0200 message: - Fixes bug lp:882491 (breaking tests, caused by renaming of config sections in MM core) - Fixes bug lp:882395 (renaming of email_host attribute) modified: mailman/client/_client.py mailman/client/docs/using.txt mailman/client/tests/test_docs.py -- lp:mailman.client https://code.launchpad.net/~mailman-coders/mailman.client/trunk Your team Mailman Coders is subscribed to branch lp:mailman.client. To unsubscribe from this branch go to https://code.launchpad.net/~mailman-coders/mailman.client/trunk/+edit-subscription -------------- next part -------------- A non-text attachment was scrubbed... Name: revision-diff.txt Type: text/x-diff Size: 6020 bytes Desc: not available URL: From 799689 at bugs.launchpad.net Thu Oct 27 12:48:41 2011 From: 799689 at bugs.launchpad.net (Florian Fuchs) Date: Thu, 27 Oct 2011 10:48:41 -0000 Subject: [Bug 799689] Re: Add API call >>>delete_domain("example.net") References: <20110620112749.26476.62275.malonedeb@gac.canonical.com> Message-ID: <20111027104842.16666.80826.launchpad@wampee.canonical.com> ** Changed in: mailman.client 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/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 noreply at launchpad.net Thu Oct 27 13:00:17 2011 From: noreply at launchpad.net (noreply at launchpad.net) Date: Thu, 27 Oct 2011 11:00:17 -0000 Subject: [Branch ~mailman-coders/mailman.client/trunk] Rev 18: Added delete_domain('example.com') call to Client Message-ID: <20111027110017.10879.17296.launchpad@ackee.canonical.com> ------------------------------------------------------------ revno: 18 fixes bug: https://launchpad.net/bugs/799689 committer: Florian Fuchs branch nick: mailman.client timestamp: Thu 2011-10-27 12:57:00 +0200 message: Added delete_domain('example.com') call to Client modified: mailman/client/_client.py mailman/client/docs/using.txt -- lp:mailman.client https://code.launchpad.net/~mailman-coders/mailman.client/trunk Your team Mailman Coders is subscribed to branch lp:mailman.client. To unsubscribe from this branch go to https://code.launchpad.net/~mailman-coders/mailman.client/trunk/+edit-subscription -------------- next part -------------- A non-text attachment was scrubbed... Name: revision-diff.txt Type: text/x-diff Size: 1440 bytes Desc: not available URL: From 799689 at bugs.launchpad.net Thu Oct 27 12:57:42 2011 From: 799689 at bugs.launchpad.net (Florian Fuchs) Date: Thu, 27 Oct 2011 10:57:42 -0000 Subject: [Bug 799689] Re: Add API call >>>delete_domain("example.net") References: <20110620112749.26476.62275.malonedeb@gac.canonical.com> Message-ID: <20111027105742.19670.28808.launchpad@soybean.canonical.com> ** Changed in: mailman.client 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/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 799689 at bugs.launchpad.net Thu Oct 27 12:59:22 2011 From: 799689 at bugs.launchpad.net (Launchpad Bug Tracker) Date: Thu, 27 Oct 2011 10:59:22 -0000 Subject: [Bug 799689] Re: Add API call >>>delete_domain("example.net") References: <20110620112749.26476.62275.malonedeb@gac.canonical.com> Message-ID: <20111027105923.10833.53116.launchpad@ackee.canonical.com> ** Branch linked: 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 noreply at launchpad.net Thu Oct 27 18:34:12 2011 From: noreply at launchpad.net (noreply at launchpad.net) Date: Thu, 27 Oct 2011 16:34:12 -0000 Subject: [Branch ~mailman-coders/mailman.client/trunk] Rev 19: - Added `lists` property to _Domain class to retrive all lists for a specific domain Message-ID: <20111027163412.866.3723.launchpad@ackee.canonical.com> ------------------------------------------------------------ revno: 19 fixes bug: https://launchpad.net/bugs/802971 committer: Florian Fuchs branch nick: mailman.client timestamp: Thu 2011-10-27 18:18:28 +0200 message: - Added `lists` property to _Domain class to retrive all lists for a specific domain modified: mailman/client/_client.py mailman/client/docs/using.txt -- lp:mailman.client https://code.launchpad.net/~mailman-coders/mailman.client/trunk Your team Mailman Coders is subscribed to branch lp:mailman.client. To unsubscribe from this branch go to https://code.launchpad.net/~mailman-coders/mailman.client/trunk/+edit-subscription -------------- next part -------------- A non-text attachment was scrubbed... Name: revision-diff.txt Type: text/x-diff Size: 1420 bytes Desc: not available URL: From 802971 at bugs.launchpad.net Thu Oct 27 18:33:36 2011 From: 802971 at bugs.launchpad.net (Launchpad Bug Tracker) Date: Thu, 27 Oct 2011 16:33:36 -0000 Subject: [Bug 802971] Re: Mailman Client doesn't _DOMAIN doesn't offer a list of lists References: <20110628125543.26674.56509.malonedeb@chaenomeles.canonical.com> Message-ID: <20111027163336.828.384.launchpad@ackee.canonical.com> ** Branch linked: 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/802971 Title: Mailman Client doesn't _DOMAIN doesn't offer a list of lists To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/802971/+subscriptions From 802971 at bugs.launchpad.net Thu Oct 27 18:36:42 2011 From: 802971 at bugs.launchpad.net (Florian Fuchs) Date: Thu, 27 Oct 2011 16:36:42 -0000 Subject: [Bug 802971] Re: Mailman Client doesn't _DOMAIN doesn't offer a list of lists References: <20110628125543.26674.56509.malonedeb@chaenomeles.canonical.com> Message-ID: <20111027163642.19571.11578.malone@soybean.canonical.com> List for a specific domain can be retreived now via the domains `lists`property: >>> example = client.get_domain(web_host='http://example.com') >>> for mlist in example.lists: ... print mlist ** Changed in: mailman.client Status: New => 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/802971 Title: Mailman Client doesn't _DOMAIN doesn't offer a list of lists To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/802971/+subscriptions From 883158 at bugs.launchpad.net Fri Oct 28 17:52:42 2011 From: 883158 at bugs.launchpad.net (Barry Warsaw) Date: Fri, 28 Oct 2011 15:52:42 -0000 Subject: [Bug 883158] [NEW] Remove X-BeenThere headers References: <20111028155242.32482.86197.malonedeb@chaenomeles.canonical.com> Message-ID: <20111028155242.32482.86197.malonedeb@chaenomeles.canonical.com> Public bug reported: MM3 uses List-Post headers to detect mail loops now, so X-BeenThere can be removed entirely. It makes no sense to detect the MM2 legacy X-BeenThere header in MM3. Most examples currently are in the test suite, however the cook_header.py handler still sets it, and this should be removed. ** Affects: mailman Importance: Undecided Status: New ** 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/883158 Title: Remove X-BeenThere headers To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/883158/+subscriptions From 883158 at bugs.launchpad.net Fri Oct 28 18:10:08 2011 From: 883158 at bugs.launchpad.net (Barry Warsaw) Date: Fri, 28 Oct 2011 16:10:08 -0000 Subject: [Bug 883158] Re: Remove X-BeenThere headers References: <20111028155242.32482.86197.malonedeb@chaenomeles.canonical.com> Message-ID: <20111028161008.32169.50960.malone@chaenomeles.canonical.com> Also, fix gate_news.py to recognize List-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/883158 Title: Remove X-BeenThere headers To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/883158/+subscriptions From 883193 at bugs.launchpad.net Fri Oct 28 19:17:15 2011 From: 883193 at bugs.launchpad.net (Barry Warsaw) Date: Fri, 28 Oct 2011 17:17:15 -0000 Subject: [Bug 883193] [NEW] Remove the X- prefix from some headers References: <20111028171715.19571.45030.malonedeb@soybean.canonical.com> Message-ID: <20111028171715.19571.45030.malonedeb@soybean.canonical.com> Public bug reported: MM3 still uses a lot of X- headers, but some of the X- prefixes can be removed. In general, we can just claim the Mailman- prefix for Mailman specific headers. Candidates include: Mailman-Rule-Hits Mailman-Rule-Misses Mailman-Version Mailman-Approved-At Mailman-LMTP-MailFrom (i.e. X-MailFrom) Mailman-Copy (or remove this header) Mailman-Content-Filter (from X-Content-Filtered-By) Also, fix the outdated comments about add-dup-header in avoid_duplicates.py and verp.py. Probably also get rid of X-List-Administrivia (and possibly reduced_list_headers). These seem unnecessary now. ** Affects: mailman Importance: Undecided Status: New ** 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/883193 Title: Remove the X- prefix from some headers To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/883193/+subscriptions From 883193 at bugs.launchpad.net Fri Oct 28 19:29:47 2011 From: 883193 at bugs.launchpad.net (Barry Warsaw) Date: Fri, 28 Oct 2011 17:29:47 -0000 Subject: [Bug 883193] Re: Remove the X- prefix from some headers References: <20111028171715.19571.45030.malonedeb@soybean.canonical.com> Message-ID: <20111028172947.32379.51048.malone@chaenomeles.canonical.com> Also, from the mailman-developers thread, possibly: X-Mailman-Version -> List-Agent X-Mailman-Approved-At -> List-Approved-Date -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/883193 Title: Remove the X- prefix from some headers To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/883193/+subscriptions From noreply at launchpad.net Sun Oct 30 20:51:12 2011 From: noreply at launchpad.net (noreply at launchpad.net) Date: Sun, 30 Oct 2011 19:51:12 -0000 Subject: [Branch ~mailman-coders/mailman.client/trunk] Rev 20: - Added handling of MM3's user API resource. Message-ID: <20111030195112.27404.6811.launchpad@ackee.canonical.com> ------------------------------------------------------------ revno: 20 committer: Florian Fuchs branch nick: mailman.client timestamp: Sun 2011-10-30 20:48:24 +0100 message: - Added handling of MM3's user API resource. - Added user addresses lookup. modified: mailman/client/_client.py mailman/client/docs/using.txt -- lp:mailman.client https://code.launchpad.net/~mailman-coders/mailman.client/trunk Your team Mailman Coders is subscribed to branch lp:mailman.client. To unsubscribe from this branch go to https://code.launchpad.net/~mailman-coders/mailman.client/trunk/+edit-subscription -------------- next part -------------- A non-text attachment was scrubbed... Name: revision-diff.txt Type: text/x-diff Size: 5111 bytes Desc: not available URL: From noreply at launchpad.net Mon Oct 31 23:48:12 2011 From: noreply at launchpad.net (noreply at launchpad.net) Date: Mon, 31 Oct 2011 22:48:12 -0000 Subject: [Branch ~mailman-coders/mailman.client/trunk] Rev 21: - refactored retrieval of user addresses: user.addresses now returns an _Addresses object which i... Message-ID: <20111031224812.24782.38521.launchpad@ackee.canonical.com> ------------------------------------------------------------ revno: 21 committer: Florian Fuchs branch nick: mailman.client timestamp: Mon 2011-10-31 23:42:40 +0100 message: - refactored retrieval of user addresses: user.addresses now returns an _Addresses object which in turn yields _Address objects if iterated over. - added `preferences` property to Client class (global preferences) modified: mailman/client/_client.py mailman/client/docs/using.txt -- lp:mailman.client https://code.launchpad.net/~mailman-coders/mailman.client/trunk Your team Mailman Coders is subscribed to branch lp:mailman.client. To unsubscribe from this branch go to https://code.launchpad.net/~mailman-coders/mailman.client/trunk/+edit-subscription -------------- next part -------------- A non-text attachment was scrubbed... Name: revision-diff.txt Type: text/x-diff Size: 3884 bytes Desc: not available URL: