From maelvon.hawk at laposte.net Mon Feb 1 00:08:52 2010 From: maelvon.hawk at laposte.net (Maelvon) Date: Sun, 31 Jan 2010 23:08:52 -0000 Subject: [Bug 515305] [NEW] List password reset while pending messages, they are deleted! References: <20100131230852.19326.9252.malonedeb@soybean.canonical.com> Message-ID: <20100131230852.19326.9252.malonedeb@soybean.canonical.com> Public bug reported: I've reseted the admin password with : /usr/lib/mailman/bin/change_pw -l mylist -p mynewpassword While having a pending message. But after the reset, the message seems deleted, cannot find it anymore! So, is that a feature? Can I retrieve the lost message and reapproved it? Maelvon ** Affects: mailman Importance: Undecided Status: New -- List password reset while pending messages, they are deleted! https://bugs.launchpad.net/bugs/515305 You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. From mark at msapiro.net Mon Feb 1 01:37:11 2010 From: mark at msapiro.net (Mark Sapiro) Date: Mon, 01 Feb 2010 00:37:11 -0000 Subject: [Bug 515305] Re: List password reset while pending messages, they are deleted! References: <20100131230852.19326.9252.malonedeb@soybean.canonical.com> Message-ID: <20100201003711.4434.26160.malone@wampee.canonical.com> I am unable to duplicate this problem. I changed a list's password twice with bin/change_pw -l mylist -p mynewpassword while a message was waiting approval. and when I finally logged in to the admindb interface, the message was still there. Perhaps the original poster canceled the post before you got to it. If the message is no longer in the admindb interface, it might possibly still be in the data/heldmsg-mylist-nn.pck (or .txt) file, but that's really unlikely. If the file is there, there is a script at that can be used to reprocess it. ** Changed in: mailman Status: New => Invalid ** Changed in: mailman Assignee: (unassigned) => Mark Sapiro (msapiro) -- List password reset while pending messages, they are deleted! https://bugs.launchpad.net/bugs/515305 You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. From maelvon.hawk at laposte.net Mon Feb 1 03:19:51 2010 From: maelvon.hawk at laposte.net (Maelvon) Date: Mon, 01 Feb 2010 02:19:51 -0000 Subject: [Bug 515305] Re: List password reset while pending messages, they are deleted! References: <20100131230852.19326.9252.malonedeb@soybean.canonical.com> Message-ID: <20100201021951.19399.74135.malone@soybean.canonical.com> Strange! Cannot find any heldmsg-* ... Is there normal that the /var/lib/mailman/lists/mylist/pending.pck exists? And contains that : ---------- (dp1 S'version' p2 I2 sS'evictions' p3 (dp4 s. ---------- I don't think the user delete the message, they are not aware of all the different possibilities of mailman! :-) I've tested "hold_again" and "list_pending" scripts, without success. I'm stuck, only have the mail saying that a message is pending. Thanks for the reactivity. -- List password reset while pending messages, they are deleted! https://bugs.launchpad.net/bugs/515305 You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. From mark at msapiro.net Mon Feb 1 03:48:54 2010 From: mark at msapiro.net (Mark Sapiro) Date: Mon, 01 Feb 2010 02:48:54 -0000 Subject: [Bug 515305] Re: List password reset while pending messages, they are deleted! References: <20100131230852.19326.9252.malonedeb@soybean.canonical.com> Message-ID: <20100201024854.19494.18169.malone@soybean.canonical.com> Yes, that is a normal 'empty' pending.pck. And, I didn't expect there to be any heldmsg* files. The fact that the pending.pck is empty is further evidence that the confirmation cookie that was sent to the user along with the email that her post was held was actually used to cancel the post. I.e., the user sends a post which is held for some reason. If the list's respond_to_post_requests setting is Yes (the default), an email is sent to the poster which contains a link which can be followed to cancel the post. Replying to the email will also cancel the post. This requires no 'awareness' on the part of the user. Look in Mailman's vette log and you should find an entry for the holding of the post and another entry for it's cancellation indicating what was done and why. Also, I'm certain there's no way that bin/change_pw would cause a post to be discarded. -- List password reset while pending messages, they are deleted! https://bugs.launchpad.net/bugs/515305 You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. From maelvon.hawk at laposte.net Mon Feb 1 10:42:58 2010 From: maelvon.hawk at laposte.net (Maelvon) Date: Mon, 01 Feb 2010 09:42:58 -0000 Subject: [Bug 515305] Re: List password reset while pending messages, they are deleted! References: <20100131230852.19326.9252.malonedeb@soybean.canonical.com> Message-ID: <20100201094258.19399.75947.malone@soybean.canonical.com> Thanks again, I've find the mailman's vette log and it said that the sender has ignored the message thought website interface. -------- mylist: Discarded posting: [...] Reason: Sender discarded message via web. --------- So you're right it seems the sender discarded it as I'm trying to validate it, searching the password, recreating it... Suprise no more message! :-) Now, I understand. I'd should have take a look at logs before opening a ticket. Thanks a lot Mark, Maelvon -- List password reset while pending messages, they are deleted! https://bugs.launchpad.net/bugs/515305 You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. From barry at canonical.com Sun Feb 7 20:36:15 2010 From: barry at canonical.com (Barry Warsaw) Date: Sun, 07 Feb 2010 19:36:15 -0000 Subject: [Bug 518517] [NEW] Add the equivalent of postconf(1) References: <20100207193615.31330.60613.malonedeb@soybean.canonical.com> Message-ID: <20100207193615.31330.60613.malonedeb@soybean.canonical.com> Public bug reported: Postfix has a very handy command called postconf(1) which lets you dump all or one Postfix configuration variable. It would be very handy for Mailman 3 to have something similar. ** Affects: mailman Importance: Medium Assignee: Barry Warsaw (barry) Status: Triaged ** Affects: mailman/3.0 Importance: Medium Assignee: Barry Warsaw (barry) Status: Triaged ** Also affects: mailman/3.0 Importance: Medium Assignee: Barry Warsaw (barry) Status: Triaged -- Add the equivalent of postconf(1) https://bugs.launchpad.net/bugs/518517 You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. From richard.m.tew at gmail.com Wed Feb 10 07:14:15 2010 From: richard.m.tew at gmail.com (Richard Tew) Date: Wed, 10 Feb 2010 06:14:15 -0000 Subject: [Bug 266572] Re: Fix to fallback of thread by subject References: <20080905193742.32763.75146.launchpad@forster.canonical.com> Message-ID: <20100210061415.24819.25990.malone@palladium.canonical.com> Oops ** Changed in: mailman Status: Invalid => Confirmed ** Changed in: mailman Status: Confirmed => Invalid -- Fix to fallback of thread by subject https://bugs.launchpad.net/bugs/266572 You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. From richard.m.tew at gmail.com Wed Feb 10 07:22:12 2010 From: richard.m.tew at gmail.com (Richard Tew) Date: Wed, 10 Feb 2010 06:22:12 -0000 Subject: [Bug 519654] [NEW] mailman archiving sorting broken References: <20100210062212.15956.77196.malonedeb@soybean.canonical.com> Message-ID: <20100210062212.15956.77196.malonedeb@soybean.canonical.com> Public bug reported: This bug is for Mailman 2.1.x. Checking the mailman/2.1 branch shows that the problem still exists there. I am aware the focus is now on the 3.x branches. I am reporting this in case development is still being done on this branch. Pipermail has indexes by subject, author and date. It stores by a tuple typed key. When doing the default threading approach, HyperDatabase calls getOldestArticle with the subject. def getOldestArticle(self, archive, subject): self.__openIndices(archive) subject = subject.lower() try: key, tempid=self.subjectIndex.set_location(subject) self.subjectIndex.next() [subject2, date]= key.split('\0') if subject!=subject2: return None return tempid except KeyError: return None Note the key used in the index operation is a string. This will always fail, because it is not the specialised article specific tuple that was actually used as a key by pipermail. This bug was also reported here (but is attached to a milestone I cannot change): https://bugs.launchpad.net/mailman/+bug/266572 ** Affects: mailman Importance: Undecided Status: New -- mailman archiving sorting broken https://bugs.launchpad.net/bugs/519654 You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. From bryan-launchpad at lunch.org Thu Feb 11 09:02:58 2010 From: bryan-launchpad at lunch.org (butter71) Date: Thu, 11 Feb 2010 08:02:58 -0000 Subject: [Bug 520321] [NEW] postfix interacts badly with postfix-to-mailman.py when recipient_delimiter="-" References: <20100211080258.20554.64057.malonedeb@wampee.canonical.com> Message-ID: <20100211080258.20554.64057.malonedeb@wampee.canonical.com> Public bug reported: mailman 2.1.12 postfix 2.6.5 ubuntu 9.10/karmic setup according to the instructions in postfix-to-mailman.py. when postfix recipient_delimiter="-", the 'user' gets passed to postfix- to-mailman.py with the trailing -xxx removed. mail to "list-owner" or "list-subscribe", etc gets passed as "list". this breaks anything but mail to the list. i patched postfix master.cf to send the entire recipient address and postfix-to-mailman to manually extract the username. ** Affects: mailman Importance: Undecided Status: New -- postfix interacts badly with postfix-to-mailman.py when recipient_delimiter="-" https://bugs.launchpad.net/bugs/520321 You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. From bryan-launchpad at lunch.org Thu Feb 11 09:02:58 2010 From: bryan-launchpad at lunch.org (butter71) Date: Thu, 11 Feb 2010 08:02:58 -0000 Subject: [Bug 520321] Re: postfix interacts badly with postfix-to-mailman.py when recipient_delimiter="-" References: <20100211080258.20554.64057.malonedeb@wampee.canonical.com> Message-ID: <20100211080259.20554.49864.malone@wampee.canonical.com> ** Patch added: "mailman.patch.txt" http://launchpadlibrarian.net/39050311/mailman.patch.txt -- postfix interacts badly with postfix-to-mailman.py when recipient_delimiter="-" https://bugs.launchpad.net/bugs/520321 You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. From mark at msapiro.net Thu Feb 11 17:18:02 2010 From: mark at msapiro.net (Mark Sapiro) Date: Thu, 11 Feb 2010 16:18:02 -0000 Subject: [Bug 520321] Re: postfix interacts badly with postfix-to-mailman.py when recipient_delimiter="-" References: <20100211080258.20554.64057.malonedeb@wampee.canonical.com> Message-ID: <20100211161803.20554.73054.malone@wampee.canonical.com> postfix_to_mailman.py is neither distributed by nor supported by the GNU Mailman project. This bug/patch should be reported to Debian/Ubuntu since they are the ones that choose to distribute this with their Mailman package. Note that all of Mailman's default VERP like processing depends on Postfix's recipient_delimiter = +. If you set it to '-' you need to alter some formats and regexps in mm_cfg.py. See http://wiki.list.org/x/D4CE ** Changed in: mailman Importance: Undecided => Low ** Changed in: mailman Status: New => Invalid -- postfix interacts badly with postfix-to-mailman.py when recipient_delimiter="-" https://bugs.launchpad.net/bugs/520321 You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. From mark at msapiro.net Thu Feb 11 22:27:19 2010 From: mark at msapiro.net (Mark Sapiro) Date: Thu, 11 Feb 2010 21:27:19 -0000 Subject: [Bug 519654] Re: mailman archiving sorting broken References: <20100210062212.15956.77196.malonedeb@soybean.canonical.com> Message-ID: <20100211212721.20902.19768.launchpad@wampee.canonical.com> *** This bug is a duplicate of bug 266572 *** https://bugs.launchpad.net/bugs/266572 ** This bug has been marked a duplicate of bug 266572 Fix to fallback of thread by subject -- mailman archiving sorting broken https://bugs.launchpad.net/bugs/519654 You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. From mark at msapiro.net Thu Feb 11 22:26:26 2010 From: mark at msapiro.net (Mark Sapiro) Date: Thu, 11 Feb 2010 21:26:26 -0000 Subject: [Bug 266572] Re: Fix to fallback of thread by subject References: <20080905193742.32763.75146.launchpad@forster.canonical.com> Message-ID: <20100211212626.15555.47211.malone@soybean.canonical.com> This bug is still valid, but the patch is incomplete at best. Preliminary testing shows that with the patch, rebuilding the archive with bin/arch --wipe works generally as expected, but individual posts without In-Reply-To: headers are still not threaded by Subject if the list has a subject_prefix. This appears to be the case whether or not the prefix is included in the reply as sent. The posts are unthreaded in the archive until the archive is rebuilt with bin/arch --wipe. ** Changed in: mailman Status: Invalid => Triaged ** Changed in: mailman Milestone: mailman-2.0.x => 2.1-stable ** Changed in: mailman Assignee: (unassigned) => Mark Sapiro (msapiro) -- Fix to fallback of thread by subject https://bugs.launchpad.net/bugs/266572 You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. From mark at msapiro.net Thu Feb 11 22:33:29 2010 From: mark at msapiro.net (Mark Sapiro) Date: Thu, 11 Feb 2010 21:33:29 -0000 Subject: [Bug 519654] [NEW] mailman archiving sorting broken References: <20100210062212.15956.77196.malonedeb@soybean.canonical.com> Message-ID: *** This bug is a duplicate of bug 266572 *** https://bugs.launchpad.net/bugs/266572 Richard Tew wrote: > >This bug was also reported here (but is attached to a milestone I cannot change): >https://bugs.launchpad.net/mailman/+bug/266572 > I marked this as a duplicate of 266572. I also made some changes to 266572 and added a comment which you may not have seen because I did that before I marked this as a duplicate. In any case, I think the patch with 266572 is incomplete. If you have any ideas on how to fix it, let me know. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan -- mailman archiving sorting broken https://bugs.launchpad.net/bugs/519654 You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. From mark at msapiro.net Sun Feb 14 00:13:32 2010 From: mark at msapiro.net (Mark Sapiro) Date: Sat, 13 Feb 2010 23:13:32 -0000 Subject: [Bug 266572] Re: Fix to fallback of thread by subject References: <20080905193742.32763.75146.launchpad@forster.canonical.com> Message-ID: <20100213231332.15555.80118.malone@soybean.canonical.com> Fixed at rev 1220 on the 2.1 branch and rev 1093 on the 2.2 branch. The fix is probably still incomplete. I think there will still be issues when long subjects are folded and unfolded. A possible fix is to remove all white space from 'stripped' subjects or maybe replace all runs of whitespace with a single space. ** Changed in: mailman Status: Triaged => Fix Committed ** Branch linked: lp:mailman/2.1 ** Branch linked: lp:mailman/2.2 -- Fix to fallback of thread by subject https://bugs.launchpad.net/bugs/266572 You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. From cedric at gn.apc.org Tue Feb 16 20:35:28 2010 From: cedric at gn.apc.org (Cedders) Date: Tue, 16 Feb 2010 19:35:28 -0000 Subject: [Bug 266273] Re: Error while editiing general list information page References: <20080905193024.27052.82385.launchpad@forster.canonical.com> Message-ID: <20100216193528.15677.22220.malone@soybean.canonical.com> It looks like a few people (eg on Sourceforge) have reported that the suspicious HTML check is too suspicious since it was introduced in version 2.1.9; for instance rejecting innocent META tags. Also, it links to http://wiki.list.org/x/jYA9 for more information, but there is no information there about the reasons for rejection leading to frustration for the list owner. "The page you saved contains suspicious HTML that could potentially expose your users to cross-site scripting attacks. This change has therefore been rejected. If you still want to make these changes, you must have shell access to your Mailman server. See FAQ 4.48." Could either the list of "badwords" be moved to Defaults.py, or there be an option to say that we trust list owners to edit their own HTML? I've worked around by hacking /usr/lib/mailman/Mailman/Cgi/edithtml.py line 162. ** Changed in: mailman Status: New => Confirmed -- Error while editiing general list information page https://bugs.launchpad.net/bugs/266273 You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. From mark at msapiro.net Tue Feb 16 20:57:50 2010 From: mark at msapiro.net (Mark Sapiro) Date: Tue, 16 Feb 2010 19:57:50 -0000 Subject: [Bug 266273] Re: Error while editiing general list information page References: <20080905193024.27052.82385.launchpad@forster.canonical.com> Message-ID: <20100216195751.18571.25811.launchpad@wampee.canonical.com> ** Changed in: mailman Milestone: None => 2.1.12 -- Error while editiing general list information page https://bugs.launchpad.net/bugs/266273 You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. From mark at msapiro.net Tue Feb 16 21:23:40 2010 From: mark at msapiro.net (Mark Sapiro) Date: Tue, 16 Feb 2010 20:23:40 -0000 Subject: [Bug 266273] Re: Error while editiing general list information page References: <20080905193024.27052.82385.launchpad@forster.canonical.com> Message-ID: <20100216202340.19305.31159.malone@wampee.canonical.com> You have hijacked a totally different (invalid) bug report. This original 'bug' is the result of a lack of permission to create or write the lists/LISTNAME/en/listinfo.html file. The SF bug #2164798 which is relevant to your issue was created after the migration to Launchpad as noted in that bug. That bug was closed and was fixed in Mailman 2.1.12. The web interface will be entirely redone for MM 3 and this is unlikely to be an issue there. I did consider a "trusted list admin" option for the suspicious HTML check, but decided against it. Also note that the reference to FAQ 4.48 is not intended to explain the "suspicious html". It is intended to explain how to install the template without triggering the check. -- Error while editiing general list information page https://bugs.launchpad.net/bugs/266273 You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. From cedric at gn.apc.org Thu Feb 18 21:07:03 2010 From: cedric at gn.apc.org (Cedders) Date: Thu, 18 Feb 2010 20:07:03 -0000 Subject: [Bug 266273] Re: Error while editiing general list information page References: <20080905193024.27052.82385.launchpad@forster.canonical.com> Message-ID: <20100218200704.19194.2109.malone@wampee.canonical.com> Oops, sorry. I was trying too hard not to create a duplicate, and am surprised it isn't already on launchpad, having seen the Sourceforge report you mention. Should I resubmit as a new bug/request? I'm using 2.1.12 and still seeing the error - I gather the fix was to add a lookahead exclusion based on the current options template. Having seen quite a few recent injected HTML attacks on the lines of Gumblar, I wonder if it would be adequate to block on the basis only of meta refresh, iframe, script src= and certain JS keywords like unescape and str_replace; on the other hand, the badwords list is probably not that comprehensive: it doesn't exclude possible XSS routes like embed, object or the obscure table background=javascript:.... IMHO a "trusted list admin" option would cover most needs most easily - giving SSH access to an (untrusted?) user might create greater security problems. I shared the list administrator's misunderstanding of the FAQ reference because of context. -- Error while editiing general list information page https://bugs.launchpad.net/bugs/266273 You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. From mark at msapiro.net Sun Feb 21 05:00:42 2010 From: mark at msapiro.net (Mark Sapiro) Date: Sun, 21 Feb 2010 04:00:42 -0000 Subject: [Bug 266273] Re: Error while editiing general list information page References: <20080905193024.27052.82385.launchpad@forster.canonical.com> Message-ID: <20100221040042.18637.44856.malone@soybean.canonical.com> If by "still seeing the error" you mean that the default options.html template generates the "suspicious html" message in the GUI editor, then I don't understand why, because that was fixed in 2.1.12 as you gather, by adding a negative lookahead to except that specific tag. If you mean just that the test is too strict because it thinks various innocent tags are suspicious, then yes, you are correct. It does that. And, it should be a whitelist rather than a blacklist which would make it even stricter. It is not intended to be a 100% perfect XSS detector or even close. It is intended to require that anything remotely suspicious be installed by an admin with shell access. This doesn't mean that list admins should be given shell access to do this. That would defeat the whole purpose of the test. It means that only a site admin has authority to bypass the test. As I said, the web interface will be redone completely for MM 3. It is not clear that this will have any relevance there, but if you wish to submit an RFE for the "trusted list admin" option that would allow list admins to alter the web interface for their list in any way they wish, please do, However, nothing is likely to change on the 2.1 branch. -- Error while editiing general list information page https://bugs.launchpad.net/bugs/266273 You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. From mark at msapiro.net Tue Feb 23 01:58:14 2010 From: mark at msapiro.net (Mark Sapiro) Date: Tue, 23 Feb 2010 00:58:14 -0000 Subject: [Bug 526143] [NEW] List-Post header should be retained in MIME digest messages References: <20100223005814.14825.18826.malonedeb@soybean.canonical.com> Message-ID: <20100223005814.14825.18826.malonedeb@soybean.canonical.com> Public bug reported: The List-Post header should be retained by default in messages in the MIME format digest to facilitate 'reply list' with MUAs that have that feature. ** Affects: mailman Importance: Undecided Status: New -- List-Post header should be retained in MIME digest messages https://bugs.launchpad.net/bugs/526143 You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. From mark at msapiro.net Tue Feb 23 02:27:02 2010 From: mark at msapiro.net (Mark Sapiro) Date: Tue, 23 Feb 2010 01:27:02 -0000 Subject: [Bug 526143] Re: List-Post header should be retained in MIME digest messages References: <20100223005814.14825.18826.malonedeb@soybean.canonical.com> Message-ID: <20100223012702.7700.13817.malone@palladium.canonical.com> Fix committed on 2.1 branch at rev 1224. ** Changed in: mailman Importance: Undecided => Low ** Changed in: mailman Status: New => Fix Committed ** Changed in: mailman Milestone: None => 2.1.14 ** Changed in: mailman Assignee: (unassigned) => Mark Sapiro (msapiro) ** Branch linked: lp:mailman/2.1 -- List-Post header should be retained in MIME digest messages https://bugs.launchpad.net/bugs/526143 You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. From barry at canonical.com Tue Feb 23 03:42:50 2010 From: barry at canonical.com (Barry Warsaw) Date: Tue, 23 Feb 2010 02:42:50 -0000 Subject: [Bug 526143] Re: List-Post header should be retained in MIME digest messages References: <20100223005814.14825.18826.malonedeb@soybean.canonical.com> Message-ID: <20100223024251.6315.33564.launchpad@gandwana.canonical.com> ** Also affects: mailman/2.1 Importance: Undecided Status: New ** Also affects: mailman/3.0 Importance: Low Assignee: Mark Sapiro (msapiro) Status: Fix Committed ** Changed in: mailman/2.1 Status: New => Fix Committed ** Changed in: mailman/2.1 Milestone: None => 2.1.14 ** Changed in: mailman/2.1 Importance: Undecided => Low ** Changed in: mailman/2.1 Assignee: (unassigned) => Mark Sapiro (msapiro) ** Changed in: mailman/3.0 Status: Fix Committed => Triaged ** Changed in: mailman/3.0 Assignee: Mark Sapiro (msapiro) => Barry Warsaw (barry) ** Changed in: mailman/3.0 Milestone: 2.1.14 => 3.0.0a6 -- List-Post header should be retained in MIME digest messages https://bugs.launchpad.net/bugs/526143 You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. From mark at msapiro.net Sat Feb 27 18:25:04 2010 From: mark at msapiro.net (Mark Sapiro) Date: Sat, 27 Feb 2010 17:25:04 -0000 Subject: [Bug 529100] [NEW] Initial 'emptyarchive' page can have wrong host name in listinfo page link References: <20100227172504.20479.13774.malonedeb@wampee.canonical.com> Message-ID: <20100227172504.20479.13774.malonedeb@wampee.canonical.com> Public bug reported: Because of the processing sequence in bin/newlist and Mailman/Cgi/create.py The initial archive index page for a new list is built with a link to the listinfo page with host name DEFAULT_URL_HOST instead of the host name supplied to newlist with -u or the host name of the create web page. ** Affects: mailman Importance: Undecided Status: New -- Initial 'emptyarchive' page can have wrong host name in listinfo page link https://bugs.launchpad.net/bugs/529100 You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. From mark at msapiro.net Sat Feb 27 20:04:59 2010 From: mark at msapiro.net (Mark Sapiro) Date: Sat, 27 Feb 2010 19:04:59 -0000 Subject: [Bug 529100] Re: Initial 'emptyarchive' page can have wrong host name in listinfo page link References: <20100227172504.20479.13774.malonedeb@wampee.canonical.com> Message-ID: <20100227190500.7152.94328.malone@palladium.canonical.com> Fixed on the 2.1 branch at rev 1225. ** Changed in: mailman Status: New => Fix Committed ** Changed in: mailman Importance: Undecided => Low ** Changed in: mailman Milestone: None => 2.1.14 ** Changed in: mailman Assignee: (unassigned) => Mark Sapiro (msapiro) ** Branch linked: lp:mailman/2.1 -- Initial 'emptyarchive' page can have wrong host name in listinfo page link https://bugs.launchpad.net/bugs/529100 You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. From markspangler at earthlink.net Sun Feb 28 18:23:06 2010 From: markspangler at earthlink.net (Maypo) Date: Sun, 28 Feb 2010 17:23:06 -0000 Subject: [Bug 529550] [NEW] Held Messages Won't Accept Action - Underscore in Email References: <20100228172306.21397.19345.malonedeb@soybean.canonical.com> Message-ID: <20100228172306.21397.19345.malonedeb@soybean.canonical.com> Public bug reported: It seems when mailman encounters an email address with an underscore embedded in the user name that is sent from a non-member, the held message gets stuck and won't accept accept, defer, reject or delete ie xxx_xxx at domain.com. Tested this by setting up test list, using default setup only changing administrative email and adding one member to accept the forwarded email. When sending from non-member with xxx_xxx at domain.com, moderation web page will accept radio button for action, but no action is taken. The moderation web page for moderation is re-displayed with no action taken. At that point if mailman get other requests from non-members even if thay are other email addresses, mailman will append these to the held messages file and they will all stack up with no way to delete them. I now have 3 held messages in one of my lists. One underscore sandwiched between 2 'normal' email addresses. I have tried: Setting held days with no help Looking at each individually and trying to delete Add user to the mebership list (the moderate screen will then show the moderated user as a member) All with no change. The radio button is activated, submit is hit and mailman takes no action and re-displays the moderator screen. Bluehost has this loaded as a basic service and I cannot get to the files to manually delete the held messages. At this point, the only work around is to delete the entire list and start from default (painful for a big list). Thanks, ** Affects: mailman Importance: Undecided Status: New -- Held Messages Won't Accept Action - Underscore in Email https://bugs.launchpad.net/bugs/529550 You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. From markspangler at earthlink.net Sun Feb 28 18:34:55 2010 From: markspangler at earthlink.net (Maypo) Date: Sun, 28 Feb 2010 17:34:55 -0000 Subject: [Bug 529550] Re: Held Messages Won't Accept Action - Underscore in Email References: <20100228172306.21397.19345.malonedeb@soybean.canonical.com> Message-ID: <20100228173455.20181.36857.malone@wampee.canonical.com> version 2.1.12.cp3 -- Held Messages Won't Accept Action - Underscore in Email https://bugs.launchpad.net/bugs/529550 You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. From mark at msapiro.net Sun Feb 28 18:55:02 2010 From: mark at msapiro.net (Mark Sapiro) Date: Sun, 28 Feb 2010 17:55:02 -0000 Subject: [Bug 529550] Re: Held Messages Won't Accept Action - Underscore in Email References: <20100228172306.21397.19345.malonedeb@soybean.canonical.com> Message-ID: <20100228175503.10909.34162.malone@gandwana.canonical.com> I cannot duplicate this in standard GNU Mailman. This is almost certainly a cPanel bug. I suggest reporting this to bluehost and asking them to remove the held messages and report this to cPanel. See the cPanel FAQ at . ** Changed in: mailman Status: New => Invalid -- Held Messages Won't Accept Action - Underscore in Email https://bugs.launchpad.net/bugs/529550 You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman.