From mark at msapiro.net Mon Feb 7 03:09:52 2011 From: mark at msapiro.net (Mark Sapiro) Date: Mon, 07 Feb 2011 02:09:52 -0000 Subject: [Bug 266051] Re: respond_to_post_requests is not configurable but should be References: <20080905192824.27052.98426.launchpad@forster.canonical.com> Message-ID: <20110207020953.9052.17433.launchpad@wampee.canonical.com> ** Changed in: mailman Status: Confirmed => In Progress ** Changed in: mailman Milestone: 2.1-stable => 2.1.15 -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/266051 Title: respond_to_post_requests is not configurable but should be From mark at msapiro.net Mon Feb 7 03:07:52 2011 From: mark at msapiro.net (Mark Sapiro) Date: Mon, 07 Feb 2011 02:07:52 -0000 Subject: [Bug 410236] Re: mailman responds to mail with no valid command References: <20090807111657.11653.85580.malonedeb@gandwana.canonical.com> Message-ID: <20110207020753.13835.88597.malone@wampee.canonical.com> I am implementing this differently from the patch. It will be a site option, not a list setting. The implementation is not a complete solution to the problem as it doesn't address mail to the -join, -leave, -subscribe or -unsubscribe addresses as mail to these doesn't contain commands. It does check that mail to -confirm does contain a token (To: matches VERP_CONFIRM_REGEXP), but not whether the token is valid. I am also implementing another option to not include any 'spam' payload in the response to email commands which will help in some cases, but there is still a problem with From: containing a spamtrap address. ** Changed in: mailman Importance: Undecided => High ** Changed in: mailman Status: Confirmed => In Progress ** Changed in: mailman Milestone: None => 2.1.15 -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/410236 Title: mailman responds to mail with no valid command From mark at msapiro.net Mon Feb 7 08:46:44 2011 From: mark at msapiro.net (Mark Sapiro) Date: Mon, 07 Feb 2011 07:46:44 -0000 Subject: [Bug 714424] [NEW] Held message user notification should be from -owner, not -bounces References: <20110207074644.27343.87673.malonedeb@soybean.canonical.com> Message-ID: <20110207074644.27343.87673.malonedeb@soybean.canonical.com> Public bug reported: If respond_to_post_requests is Yes the notice to the poster of a held post is From: the listname-bounces address. It should be from the listname-owner address. ** Affects: mailman Importance: Medium 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/714424 Title: Held message user notification should be from -owner, not -bounces From mark at msapiro.net Mon Feb 7 20:38:43 2011 From: mark at msapiro.net (Mark Sapiro) Date: Mon, 07 Feb 2011 19:38:43 -0000 Subject: [Bug 265835] Re: held message notice options References: <20080905192620.27052.80993.launchpad@forster.canonical.com> Message-ID: <20110207193844.11575.77887.launchpad@soybean.canonical.com> ** Changed in: mailman Status: New => In Progress ** Changed in: mailman Milestone: 2.1-stable => 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/265835 Title: held message notice options From mark at msapiro.net Mon Feb 7 20:53:30 2011 From: mark at msapiro.net (Mark Sapiro) Date: Mon, 07 Feb 2011 19:53:30 -0000 Subject: [Bug 705715] Re: @listname entries in *_these_nonmembers are case sensitive. References: <20110121025646.5547.15531.malonedeb@soybean.canonical.com> Message-ID: <20110207195331.16476.72063.launchpad@palladium.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/705715 Title: @listname entries in *_these_nonmembers are case sensitive. From mark at msapiro.net Mon Feb 7 20:54:34 2011 From: mark at msapiro.net (Mark Sapiro) Date: Mon, 07 Feb 2011 19:54:34 -0000 Subject: [Bug 702516] Re: RFC 2047 encoded From: header is not correctly parsed. References: <20110113181434.18877.20098.malonedeb@wampee.canonical.com> Message-ID: <20110207195437.20485.31018.launchpad@gandwana.canonical.com> ** Changed in: mailman/3.0 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/702516 Title: RFC 2047 encoded From: header is not correctly parsed. From mark at msapiro.net Mon Feb 7 20:50:54 2011 From: mark at msapiro.net (Mark Sapiro) Date: Mon, 07 Feb 2011 19:50:54 -0000 Subject: [Bug 266224] Re: Bug if bounced message canceled after being discarded References: <20080905192947.27052.69721.launchpad@forster.canonical.com> Message-ID: <20110207195055.11575.75671.launchpad@soybean.canonical.com> ** Changed in: mailman Importance: Medium => Low ** Changed in: mailman Status: New => In Progress ** Changed in: mailman Milestone: 2.1-stable => 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/266224 Title: Bug if bounced message canceled after being discarded From mark at msapiro.net Mon Feb 7 21:48:45 2011 From: mark at msapiro.net (Mark Sapiro) Date: Mon, 07 Feb 2011 20:48:45 -0000 Subject: [Bug 410236] Re: mailman responds to mail with no valid command References: <20090807111657.11653.85580.malonedeb@gandwana.canonical.com> Message-ID: <20110207204846.6935.34418.launchpad@wampee.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/410236 Title: mailman responds to mail with no valid command From mark at msapiro.net Mon Feb 7 21:49:29 2011 From: mark at msapiro.net (Mark Sapiro) Date: Mon, 07 Feb 2011 20:49:29 -0000 Subject: [Bug 266224] Re: Bug if bounced message canceled after being discarded References: <20080905192947.27052.69721.launchpad@forster.canonical.com> Message-ID: <20110207204931.11693.45799.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/266224 Title: Bug if bounced message canceled after being discarded From mark at msapiro.net Mon Feb 7 21:48:25 2011 From: mark at msapiro.net (Mark Sapiro) Date: Mon, 07 Feb 2011 20:48:25 -0000 Subject: [Bug 265835] Re: held message notice options References: <20080905192620.27052.80993.launchpad@forster.canonical.com> Message-ID: <20110207204828.20419.49678.launchpad@gandwana.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/265835 Title: held message notice options From mark at msapiro.net Mon Feb 7 21:49:03 2011 From: mark at msapiro.net (Mark Sapiro) Date: Mon, 07 Feb 2011 20:49:03 -0000 Subject: [Bug 266051] Re: respond_to_post_requests is not configurable but should be References: <20080905192824.27052.98426.launchpad@forster.canonical.com> Message-ID: <20110207204904.6862.82833.launchpad@wampee.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/266051 Title: respond_to_post_requests is not configurable but should be From 715166 at bugs.launchpad.net Tue Feb 8 14:54:01 2011 From: 715166 at bugs.launchpad.net (Florian Fuchs) Date: Tue, 08 Feb 2011 13:54:01 -0000 Subject: [Bug 715166] [NEW] REST-API: HTTPError - unexpected parameters References: <20110208135402.6862.29729.malonedeb@wampee.canonical.com> Message-ID: <20110208135402.6862.29729.malonedeb@wampee.canonical.com> Public bug reported: Sending list settings to the REST server (PATCH /lists/[fqdn_listname]/config) raised the following HTTPError: HTTPError: HTTP Error 400: Unexpected parameters: bounces_address, created_at, digest_last_sent_at, fqdn_listname, host_name, http_etag, join_address, last_post_at, leave_address, list_id, list_name, next_digest_number, no_reply_address, owner_address, post_id, posting_address, request_address, scheme, volume, web_host The HTTPError is thrown because these paramaters are not listed in ATTRIBUTES (src/mailman/rest/configuration.py:159). However all of these parameters were received via GET /lists/[fqdn_listsname]/config. Are the parameters simply missing in the ATTRIBUTES dict or is there any other reason they're not accepted? ** Affects: mailman Importance: Undecided Status: New ** Tags: mailman3 rest -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/715166 Title: REST-API: HTTPError - unexpected parameters From 715166 at bugs.launchpad.net Tue Feb 8 16:14:21 2011 From: 715166 at bugs.launchpad.net (Barry Warsaw) Date: Tue, 08 Feb 2011 15:14:21 -0000 Subject: [Bug 715166] Re: REST-API: HTTPError - unexpected parameters References: <20110208135402.6862.29729.malonedeb@wampee.canonical.com> Message-ID: <20110208151421.6935.42857.malone@wampee.canonical.com> Are you sure you have an up-to-date configuration.py file? All those parameters are named in ATTRIBUTES except http_etag, which is an artifact of the GET. If you remove http_etag from the PATCH call, does it work for you? If that's the only offender then there might be a bug in the error message, since it should only complain about http_etag in the 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/715166 Title: REST-API: HTTPError - unexpected parameters From 716561 at bugs.launchpad.net Thu Feb 10 18:55:42 2011 From: 716561 at bugs.launchpad.net (Andrew Erickson) Date: Thu, 10 Feb 2011 17:55:42 -0000 Subject: [Bug 716561] [NEW] waiting" email contains a link that uses the vHosts name instead of the systems host name References: <20110210175542.6797.43110.malonedeb@wampee.canonical.com> Message-ID: <20110210175542.6797.43110.malonedeb@wampee.canonical.com> Public bug reported: Using Mailman version 2.1.14 on a cPanel host. The "MgtTeam moderator request(s) waiting" email contains a link that uses the vHosts name instead of the systems host name which ends up being a broken link because the website is hosted on another server. (cPanel host= host1.example.com while the virtual host account name is virtualdomain.com, where virtualdomain.com does not point host1.example.com. The link presented in the email would be http://virtualdomain.com/mailman/admindb/mgtteam_virtualdomain.com where it should be http://host1.example.com/mailman/admindb/mgtteam_virtualdomain.com. ** 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/716561 Title: waiting" email contains a link that uses the vHosts name instead of the systems host name From mark at msapiro.net Thu Feb 10 21:28:39 2011 From: mark at msapiro.net (Mark Sapiro) Date: Thu, 10 Feb 2011 20:28:39 -0000 Subject: [Bug 716561] Re: waiting" email contains a link that uses the vHosts name instead of the systems host name References: <20110210175542.6797.43110.malonedeb@wampee.canonical.com> Message-ID: <20110210202839.16423.26217.malone@palladium.canonical.com> This is a cPanel issue, not a Mailman bug. If you have sufficient access to the server, you can create lists with Mailman's /usr/local/cpanel/3rdparty/mailman/bin/newlist instead of cPanel's list creation process and you can specify the the name of the hosts for web and email access separately. You probably still need to specify the list name as LIST_virtualdomain.com so that the cPanel Exim router properly routes mail sent to the LIST at virtualdomain.com list. For the existing list, if you have sufficient access, you could "fix" this by using Mailman's /usr/local/cpanel/3rdparty/mailman/bin/withlist tool to set the host you want in the list's hidden web_page_url attribute. Also, see the FAQ at . ** Changed in: mailman Importance: Undecided => Low ** Changed in: mailman Status: New => Won't Fix -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/716561 Title: waiting" email contains a link that uses the vHosts name instead of the systems host name From 716561 at bugs.launchpad.net Fri Feb 11 17:43:11 2011 From: 716561 at bugs.launchpad.net (Andrew Erickson) Date: Fri, 11 Feb 2011 16:43:11 -0000 Subject: [Bug 716561] Re: waiting" email contains a link that uses the vHosts name instead of the systems host name References: <20110210175542.6797.43110.malonedeb@wampee.canonical.com> Message-ID: <20110211164311.2881.90321.malone@wampee.canonical.com> I am working with cPanel to change this without adding an inconsistent "Monkey Patch" in the backend of cPanel. Thanks for the advise and the FAQ link. --ACE ** Changed in: mailman Assignee: (unassigned) => Andrew Erickson (aerickson-voonami) ** Changed in: mailman Assignee: Andrew Erickson (aerickson-voonami) => (unassigned) -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/716561 Title: waiting" email contains a link that uses the vHosts name instead of the systems host name From mark at msapiro.net Sun Feb 13 02:30:56 2011 From: mark at msapiro.net (Mark Sapiro) Date: Sun, 13 Feb 2011 01:30:56 -0000 Subject: [Bug 558106] Re: A MemberAdaptor for LDAP-based membership References: <20100408090607.1687.22727.launchpad@loganberry.canonical.com> Message-ID: <20110213013056.26718.14482.malone@soybean.canonical.com> This version includes a contribution by Seth Bromberger to support LDAP groups. It also fixes a problem with version 0.6 that would throw an exception if variables having to do with real name options were not set in mm_cfg.py. They are now given reasonable defaults if not set. ** Attachment added: "LDAP_Memberships.py, version 0.62" https://bugs.launchpad.net/mailman/+bug/558106/+attachment/1846317/+files/LDAP_Memberships.py -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/558106 Title: A MemberAdaptor for LDAP-based membership From mark at msapiro.net Fri Feb 18 00:22:14 2011 From: mark at msapiro.net (Mark Sapiro) Date: Thu, 17 Feb 2011 23:22:14 -0000 Subject: [Bug 721015] [NEW] Typo in cron/gate_news usage() definition. References: <20110217232215.7066.16571.malonedeb@wampee.canonical.com> Message-ID: <20110217232215.7066.16571.malonedeb@wampee.canonical.com> Public bug reported: The usage function defined in cron/gate_news defines its first argument as 'status' but then refers to it as 'code'. ** Affects: mailman Importance: Low Assignee: Mark Sapiro (msapiro) Status: 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/721015 Title: Typo in cron/gate_news usage() definition. From 721169 at bugs.launchpad.net Fri Feb 18 11:12:39 2011 From: 721169 at bugs.launchpad.net (Matt Clauson) Date: Fri, 18 Feb 2011 10:12:39 -0000 Subject: [Bug 721169] [NEW] Messages with empty subject lines not linked from index pages in archives References: <20110218101239.6679.62147.malonedeb@palladium.canonical.com> Message-ID: <20110218101239.6679.62147.malonedeb@palladium.canonical.com> Public bug reported: In Mailman 2.1.14, if a message is submitted to the list with an empty Subject: header, the message is processed for archiving, but is not linked from the Date-, Subject, etc. indexes. ** 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/721169 Title: Messages with empty subject lines not linked from index pages in archives From mark at msapiro.net Fri Feb 18 18:32:58 2011 From: mark at msapiro.net (Mark Sapiro) Date: Fri, 18 Feb 2011 17:32:58 -0000 Subject: [Bug 721169] Re: Messages with empty subject lines not linked from index pages in archives References: <20110218101239.6679.62147.malonedeb@palladium.canonical.com> Message-ID: <20110218173259.12758.94624.malone@potassium.ubuntu.com> I can't duplicate this. If I post a message with no Subject: header or with an empty Subject: or one consisting only of spaces, and the list has no subject_prefix, the message is archived and indexed with subject "No subject". If the list has a non-empty subject_prefix, the message is given a subject consisting of the prefix followed by "(no subject)" and archived and indexed with that subject. If you can reproduce this, please tell me how. ** Changed in: mailman Status: New => Incomplete ** Changed in: mailman Assignee: (unassigned) => Mark Sapiro (msapiro) -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/721169 Title: Messages with empty subject lines not linked from index pages in archives From 266325 at bugs.launchpad.net Fri Feb 18 20:59:35 2011 From: 266325 at bugs.launchpad.net (gaurav_pawaskar) Date: Fri, 18 Feb 2011 19:59:35 -0000 Subject: [Bug 266325] Re: Typos in the Mailman 2.1.8a PO file References: <20080905193058.27052.74038.launchpad@forster.canonical.com> Message-ID: <20110218195936.30180.93299.launchpad@wampee.canonical.com> ** Changed in: mailman Assignee: (unassigned) => gaurav_pawaskar (gaurav-pawaskar) -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/266325 Title: Typos in the Mailman 2.1.8a PO file From 266325 at bugs.launchpad.net Fri Feb 18 22:19:50 2011 From: 266325 at bugs.launchpad.net (gaurav_pawaskar) Date: Fri, 18 Feb 2011 21:19:50 -0000 Subject: [Bug 266325] Re: Typos in the Mailman 2.1.8a PO file References: <20080905193058.27052.74038.launchpad@forster.canonical.com> Message-ID: <20110218211950.28272.67598.launchpad@soybean.canonical.com> ** Changed in: mailman Assignee: gaurav_pawaskar (gaurav-pawaskar) => (unassigned) -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/266325 Title: Typos in the Mailman 2.1.8a PO file From curtis.hovey at canonical.com Thu Feb 24 14:53:44 2011 From: curtis.hovey at canonical.com (Curtis Hovey) Date: Thu, 24 Feb 2011 13:53:44 -0000 Subject: [Bug 724318] [NEW] mailman rejects encoded from addresses References: <20110224135344.6810.2259.malonedeb@wampee.canonical.com> Message-ID: <20110224135344.6810.2259.malonedeb@wampee.canonical.com> Public bug reported: A user subscribed to a launchpad list reported his email were not being received. This issue may be a duplicate of bug 702516, but the patch I read does not appear to be working with the encoding issue. This is what user Lp user ~ralf-claussnitzer provided: We managed to figure out why LP is rejecting my mail. Shortcut: my name contains special characters. LP is not able to identify my email address form the mail header. Here is a detailed explanation: In failure cases my name "Ralf Clau?nitzer" is encoded in the From field like this: (given it's sent using ISO) From: =?iso-8859-1?Q?Clau=DFnitzer=2C_Ralf?= (given it's sent using UTF-8) From: =?utf-8?B?Q2xhdcOfbml0emVyLCBSYWxm?= If the special character "?" is removed from the mail servers dictionary, the From-Field looks more like expected and LP delivers that mail: (using UTF-8 but without special character) From: "Claussnitzer, Ralf" Sending messages with HTML body is not a problem for LP. As LP decides whether to moderate or block a message based on the From field, it looks like LP is not able to identify the address from those screwed up headers. However, RFC5335 on Internationalized Email Headers states on Page 5 (http://tools.ietf.org/html/rfc5335#page-5) that "The bodies of header fields are allowed to contain UTF-8 characters, but the header field names themselves must contain only ASCII characters." If so, I don?t understand where the encoding shown above comes from. But I expect LP to handle those messages correctly if a valid email address is in the From field somewhere. ** Affects: mailman Importance: Undecided Status: New ** Tags: launchpad -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/724318 Title: mailman rejects encoded from addresses From mark at msapiro.net Thu Feb 24 18:53:49 2011 From: mark at msapiro.net (Mark Sapiro) Date: Thu, 24 Feb 2011 17:53:49 -0000 Subject: [Bug 724318] Re: mailman rejects encoded from addresses References: <20110224135344.6810.2259.malonedeb@wampee.canonical.com> Message-ID: <20110224175349.27460.21617.malone@potassium.ubuntu.com> The remark about RFC5335 is not relevant. The example From: headers in the report are RFC 2047 encoded, and are valid as the encoded headers contain only us-ascii characters. In any case, the report talks about LP rejecting mail. Is this mail to a Mailman list? If so, what happens to the mail. Is there an actual rejection notice? If so, what does it say? What's in Mailman's various logs, in particular 'vette' and 'error', relating to these messages? What are the lists settings for Privacy options... -> Sender filters? Is this user in accept_these_nonmembers? What is generic_nonmember_action? This very well could be bug 702516 as the actual decoded From: header is From: Clau?nitzer, Ralf which does contain an unquoted comma which is the issue of bug 702516. If this is the issue, the reason it works if the "?" is replaced with "s" is the real name then contains no non-ascii, so the users MUA simply quotes it rather than RFC 2047 encoding it. -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/724318 Title: mailman rejects encoded from addresses From curtis.hovey at canonical.com Thu Feb 24 20:52:33 2011 From: curtis.hovey at canonical.com (Curtis Hovey) Date: Thu, 24 Feb 2011 19:52:33 -0000 Subject: [Bug 724318] Re: mailman rejects encoded from addresses References: <20110224135344.6810.2259.malonedeb@wampee.canonical.com> Message-ID: <20110224195233.19184.78573.malone@palladium.canonical.com> This user was unaware that sending emails to a launchpad list does go directly the Launchpad's mailman. The mail was not forwarded to the subscribers. It was not archived. It was not moderated because of Launchpad's own handler. Launchpad discards any message that does not come from a Launchpad user. http://bazaar.launchpad.net/~launchpad-pqm/launchpad/devel/view/head:/lib/lp/services/mailman/monkeypatches/lphandler.py The crucial issue is that msg.get_sender() is not returning the email address (ralf.claussnitzer at slub-dresden.de). WIthout an exact match, Lp will tell mailman to discard the message. Thank you for a second reading of the encoded name. I neglected to see that the name order was reversed. I agree that this is a dupe of bug 702516. -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/724318 Title: mailman rejects encoded from addresses From mark at msapiro.net Thu Feb 24 21:47:35 2011 From: mark at msapiro.net (Mark Sapiro) Date: Thu, 24 Feb 2011 20:47:35 -0000 Subject: [Bug 724318] Re: mailman rejects encoded from addresses References: <20110224135344.6810.2259.malonedeb@wampee.canonical.com> Message-ID: <20110224204737.27279.11435.launchpad@potassium.ubuntu.com> *** This bug is a duplicate of bug 702516 *** https://bugs.launchpad.net/bugs/702516 ** This bug has been marked a duplicate of bug 702516 RFC 2047 encoded From: header is not correctly parsed. * You can subscribe to bug 702516 by following this link: https://bugs.launchpad.net/mailman/+bug/702516/+subscribe -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/724318 Title: mailman rejects encoded from addresses From mark at msapiro.net Thu Feb 24 21:54:28 2011 From: mark at msapiro.net (Mark Sapiro) Date: Thu, 24 Feb 2011 20:54:28 -0000 Subject: [Bug 724318] Re: mailman rejects encoded from addresses References: <20110224135344.6810.2259.malonedeb@wampee.canonical.com> Message-ID: <20110224205428.28342.97306.malone@gandwana.canonical.com> *** This bug is a duplicate of bug 702516 *** https://bugs.launchpad.net/bugs/702516 See bug 702516 for fix. ** Changed in: mailman Importance: Undecided => Medium ** Changed in: mailman Status: New => Fix Committed ** Changed in: mailman Milestone: None => 2.1.15 ** Changed in: mailman Assignee: (unassigned) => Mark Sapiro (msapiro) -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/724318 Title: mailman rejects encoded from addresses From 715166 at bugs.launchpad.net Fri Feb 25 21:03:42 2011 From: 715166 at bugs.launchpad.net (Barry Warsaw) Date: Fri, 25 Feb 2011 20:03:42 -0000 Subject: [Bug 715166] Re: REST-API: HTTPError - unexpected parameters References: <20110208135402.6862.29729.malonedeb@wampee.canonical.com> Message-ID: <20110225200342.25753.82569.malone@soybean.canonical.com> Can you post some Python to reproduce the problem? ** 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/715166 Title: REST-API: HTTPError - unexpected parameters From 667252 at bugs.launchpad.net Fri Feb 25 21:06:05 2011 From: 667252 at bugs.launchpad.net (Barry Warsaw) Date: Fri, 25 Feb 2011 20:06:05 -0000 Subject: [Bug 667252] Re: Mailman 3 Branch, install fails with --prefix specified References: <20101027122355.7038.41189.malonedeb@gandwana.canonical.com> Message-ID: <20110225200605.25753.74488.malone@soybean.canonical.com> I'm not sure a straight 'python setup.py install' works since MM3 is based on buildout. Does this work or fail for you: $ /software/bin/python-2.6.3 bootstrap.py $ bin/buildout ? ** Changed in: mailman Status: Triaged => Incomplete -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/667252 Title: Mailman 3 Branch, install fails with --prefix specified From kink at squirrelmail.org Sat Feb 26 12:05:34 2011 From: kink at squirrelmail.org (Thijs Kinkhorst) Date: Sat, 26 Feb 2011 11:05:34 -0000 Subject: [Bug 725498] [NEW] expose message-id to templates References: <20110226110534.9071.23909.malonedeb@potassium.ubuntu.com> Message-ID: <20110226110534.9071.23909.malonedeb@potassium.ubuntu.com> Public bug reported: As reported by Adrian von Bidder to Debian: Please consider this trivial patch, which exposees message-ids to the templates used for the email archive. See it in action on lists.debian.ch. (I don't think my modification to the templates should be in, but having te message-id exposed would mean I won't have to remember to patch mailman on every update...) (AFAICT mailman adds a Message-Id when an incoming email doesn't have one, so this should never be a problem.) ** Affects: mailman Importance: Undecided Status: New ** Affects: mailman (Debian) Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/725498 Title: expose message-id to templates From kink at squirrelmail.org Sat Feb 26 12:05:34 2011 From: kink at squirrelmail.org (Thijs Kinkhorst) Date: Sat, 26 Feb 2011 11:05:34 -0000 Subject: [Bug 725498] Re: expose message-id to templates References: <20110226110534.9071.23909.malonedeb@potassium.ubuntu.com> Message-ID: <20110226110535.9071.81660.malone@potassium.ubuntu.com> ** Patch added: "hyperarch.patch" https://bugs.launchpad.net/bugs/725498/+attachment/1872574/+files/hyperarch.patch ** Bug watch added: Debian Bug tracker #614340 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=614340 ** Also affects: mailman (Debian) via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=614340 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/725498 Title: expose message-id to templates From 725498 at bugs.launchpad.net Sat Feb 26 12:34:18 2011 From: 725498 at bugs.launchpad.net (Bug Watch Updater) Date: Sat, 26 Feb 2011 11:34:18 -0000 Subject: [Bug 725498] Re: expose message-id to templates References: <20110226110534.9071.23909.malonedeb@potassium.ubuntu.com> Message-ID: <20110226113419.26055.21614.launchpad@loganberry.canonical.com> ** Changed in: mailman (Debian) Status: Unknown => 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/725498 Title: expose message-id to templates From 715166 at bugs.launchpad.net Mon Feb 28 18:15:27 2011 From: 715166 at bugs.launchpad.net (Florian Fuchs) Date: Mon, 28 Feb 2011 17:15:27 -0000 Subject: [Bug 715166] Re: REST-API: HTTPError - unexpected parameters References: <20110208135402.6862.29729.malonedeb@wampee.canonical.com> Message-ID: <20110228171527.25879.20521.malone@soybean.canonical.com> What's the most decent way to take back a bug report? :-/ Trying to reproduce it again I found out the reason for the bug was just me messing up a test case. Sorry... ** Changed in: mailman Status: Incomplete => Invalid -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/715166 Title: REST-API: HTTPError - unexpected parameters