Mailman 3 January 2005 - Mailman-coders

[ mailman-Bugs-1108814 ] convert_html_to_plaintext strips text from hotmail
by SourceForge.net Jan. 28, 2005

Jan. 28, 2005

Bugs item #1108814, was opened at 2005-01-25 03:04 Message generated for change (Comment added) made by shub You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1108814&group_… Category: configuring/installing Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Kalvos (kalvos) Assigned to: Nobody/Anonymous (nobody) Summary: convert_html_to_plaintext strips text from hotmail Initial Comment: Mailman version 2.1.5 installed on FreeBSD at pair Networks. I use the web configuration of mailman. It is set up with convert_html_to_plaintext enabled. Recent email via Hotmail has been coming in with no body, even though the original email has text. The text is present, and although ugly, the code looks average for HTML mail. The actual original email content (without headers) is pasted below. No text is passed through Mailman. You can see this archive at http://five.pairlist.net/pipermail/coco/ and the result in this message: http://five.pairlist.net/pipermail/coco/2005-January/012347.html Any advice is appreciated if this is not a bug. <html><div style='background-color:'><DIV class=RTE> <P>OK, this is the hotmail test.<BR>_Glen<BR><BR></P></DIV>> <DIV></DIV>> <DIV></DIV>>OK, the next message from me will come from hotmail, as a test. <DIV></DIV>>-Glen <DIV></DIV>> > > <DIV></DIV>> > Well, the thing to do is, now that we've got a clue, go back to the <DIV></DIV>> > original email agent and make a couple of test posts, & we'll see <DIV></DIV>>who <DIV></DIV>> > gets what now that we know to look for it. <DIV></DIV>> <DIV></DIV>> > >> <DIV></DIV>> > >> > -- John. <DIV></DIV>> > > <DIV></DIV>> > >Brought to you by the 6809, the 6803 and their cousins! <DIV></DIV>> > >Yahoo! Groups Links <DIV></DIV>> > > <DIV></DIV>> > > <DIV></DIV>> > > <DIV></DIV>> > <DIV></DIV>> > -- <DIV></DIV>> > Cheers, Gene <DIV></DIV>> > "There are four boxes to be used in defense of liberty: <DIV></DIV>> >  soap, ballot, jury, and ammo. Please use in that order." <DIV></DIV>> > -Ed Howdershelt (Author) <DIV></DIV>> > 99.32% setiathome rank, not too shabby for a WV hillbilly <DIV></DIV>> > Yahoo.com attorneys please note, additions to this message <DIV></DIV>> > by Gene Heskett are: <DIV></DIV>> > Copyright 2005 by Maurice Eugene Heskett, all rights reserved. <DIV></DIV>> <DIV></DIV>> <DIV></DIV>> <DIV></DIV>> <DIV></DIV>> <DIV></DIV>>Brought to you by the 6809, the 6803 and their cousins! <DIV></DIV>>Yahoo! Groups Links <DIV></DIV>> <DIV></DIV>><*> To visit your group on the web, go to: <DIV></DIV>>     http://groups.yahoo.com/group/ColorComputer/ <DIV></DIV>> <DIV></DIV>><*> To unsubscribe from this group, send an email to: <DIV></DIV>>     ColorComputer-unsubscribe(a)yahoogroups.com <DIV></DIV>> <DIV></DIV>><*> Your use of Yahoo! Groups is subject to: <DIV></DIV>>     http://docs.yahoo.com/info/terms/ <DIV></DIV>> <DIV></DIV>> <DIV></DIV>> <DIV></DIV>> <DIV></DIV></div></html> ---------------------------------------------------------------------- Comment By: Brad Knowles (shub) Date: 2005-01-28 15:03 Message: Logged In: YES user_id=18417 Pasting the content of the message body is not useful. There is MIME structure outside of the message body that is not included, and it is this MIME structure information that we need in order to find out what has happened. This is why I said that we needed to be able to look at the *COMPLETE* message contents, both before and after processing by Mailman. You can't just cut-n-paste the message body. ---------------------------------------------------------------------- Comment By: Kalvos (kalvos) Date: 2005-01-28 13:40 Message: Logged In: YES user_id=1204060 Hello, Thanks for the response. In my original post, there was a link the defectively received message, and it is just like the one you found. The other message was as sent through Yahoo and received by Yahoo list members -- the content is pasted above. According to the author, it is what he sent. Pasted above is exactly what would have been received by Mailman. The Yahoo Groups list is a member of our list (with dupes turned off) so both groups can share posts. Dennis ---------------------------------------------------------------------- Comment By: Brad Knowles (shub) Date: 2005-01-28 10:25 Message: Logged In: YES user_id=18417 It was hard to find examples of what you were talking about. Can I assume that you mean messages like <http://five.pairlist.net/pipermail/ coco/2005-January/012348.html>? In this case, what we need to do is to see the original, unedited, version of the message as it was submitted to Mailman, so that we can try to figure out what went wrong and why it was stripped to be "blank" but then submitted to the system. This may require that someone subscribe to Hotmail and send some test messages, both directly to another account as well as to the mailing list, so that we can see both the edited and the unedited versions of the message. Another problem is that this issue may be specific to the configurations of particular people using Hotmail, and it may be difficult to find out what options they have set/changed which result in this kind of behaviour. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1108814&group_…

1 0

[ mailman-Bugs-1108814 ] convert_html_to_plaintext strips text from hotmail
by SourceForge.net Jan. 28, 2005

Jan. 28, 2005

Bugs item #1108814, was opened at 2005-01-24 22:04 Message generated for change (Comment added) made by kalvos You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1108814&group_… Category: configuring/installing Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Kalvos (kalvos) Assigned to: Nobody/Anonymous (nobody) Summary: convert_html_to_plaintext strips text from hotmail Initial Comment: Mailman version 2.1.5 installed on FreeBSD at pair Networks. I use the web configuration of mailman. It is set up with convert_html_to_plaintext enabled. Recent email via Hotmail has been coming in with no body, even though the original email has text. The text is present, and although ugly, the code looks average for HTML mail. The actual original email content (without headers) is pasted below. No text is passed through Mailman. You can see this archive at http://five.pairlist.net/pipermail/coco/ and the result in this message: http://five.pairlist.net/pipermail/coco/2005-January/012347.html Any advice is appreciated if this is not a bug. <html><div style='background-color:'><DIV class=RTE> <P>OK, this is the hotmail test.<BR>_Glen<BR><BR></P></DIV>> <DIV></DIV>> <DIV></DIV>>OK, the next message from me will come from hotmail, as a test. <DIV></DIV>>-Glen <DIV></DIV>> > > <DIV></DIV>> > Well, the thing to do is, now that we've got a clue, go back to the <DIV></DIV>> > original email agent and make a couple of test posts, & we'll see <DIV></DIV>>who <DIV></DIV>> > gets what now that we know to look for it. <DIV></DIV>> <DIV></DIV>> > >> <DIV></DIV>> > >> > -- John. <DIV></DIV>> > > <DIV></DIV>> > >Brought to you by the 6809, the 6803 and their cousins! <DIV></DIV>> > >Yahoo! Groups Links <DIV></DIV>> > > <DIV></DIV>> > > <DIV></DIV>> > > <DIV></DIV>> > <DIV></DIV>> > -- <DIV></DIV>> > Cheers, Gene <DIV></DIV>> > "There are four boxes to be used in defense of liberty: <DIV></DIV>> >  soap, ballot, jury, and ammo. Please use in that order." <DIV></DIV>> > -Ed Howdershelt (Author) <DIV></DIV>> > 99.32% setiathome rank, not too shabby for a WV hillbilly <DIV></DIV>> > Yahoo.com attorneys please note, additions to this message <DIV></DIV>> > by Gene Heskett are: <DIV></DIV>> > Copyright 2005 by Maurice Eugene Heskett, all rights reserved. <DIV></DIV>> <DIV></DIV>> <DIV></DIV>> <DIV></DIV>> <DIV></DIV>> <DIV></DIV>>Brought to you by the 6809, the 6803 and their cousins! <DIV></DIV>>Yahoo! Groups Links <DIV></DIV>> <DIV></DIV>><*> To visit your group on the web, go to: <DIV></DIV>>     http://groups.yahoo.com/group/ColorComputer/ <DIV></DIV>> <DIV></DIV>><*> To unsubscribe from this group, send an email to: <DIV></DIV>>     ColorComputer-unsubscribe(a)yahoogroups.com <DIV></DIV>> <DIV></DIV>><*> Your use of Yahoo! Groups is subject to: <DIV></DIV>>     http://docs.yahoo.com/info/terms/ <DIV></DIV>> <DIV></DIV>> <DIV></DIV>> <DIV></DIV>> <DIV></DIV></div></html> ---------------------------------------------------------------------- >Comment By: Kalvos (kalvos) Date: 2005-01-28 08:40 Message: Logged In: YES user_id=1204060 Hello, Thanks for the response. In my original post, there was a link the defectively received message, and it is just like the one you found. The other message was as sent through Yahoo and received by Yahoo list members -- the content is pasted above. According to the author, it is what he sent. Pasted above is exactly what would have been received by Mailman. The Yahoo Groups list is a member of our list (with dupes turned off) so both groups can share posts. Dennis ---------------------------------------------------------------------- Comment By: Brad Knowles (shub) Date: 2005-01-28 05:25 Message: Logged In: YES user_id=18417 It was hard to find examples of what you were talking about. Can I assume that you mean messages like <http://five.pairlist.net/pipermail/ coco/2005-January/012348.html>? In this case, what we need to do is to see the original, unedited, version of the message as it was submitted to Mailman, so that we can try to figure out what went wrong and why it was stripped to be "blank" but then submitted to the system. This may require that someone subscribe to Hotmail and send some test messages, both directly to another account as well as to the mailing list, so that we can see both the edited and the unedited versions of the message. Another problem is that this issue may be specific to the configurations of particular people using Hotmail, and it may be difficult to find out what options they have set/changed which result in this kind of behaviour. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1108814&group_…

1 0

[ mailman-Feature Requests-1109139 ] a common custom explanation for all rejection messages
by SourceForge.net Jan. 28, 2005

Jan. 28, 2005

Feature Requests item #1109139, was opened at 2005-01-25 15:12 Message generated for change (Comment added) made by shub You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1109139&group_… Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Sam Steingold (sds) Assigned to: Nobody/Anonymous (nobody) Summary: a common custom explanation for all rejection messages Initial Comment: it would be very nice if there were a customization parameter where I could put some common text for all rejections messages. right now, I have to manually insert "For more information on the mailing list policy, please see <http://clisp.cons.org/faq.html#rejected>." ---------------------------------------------------------------------- Comment By: Brad Knowles (shub) Date: 2005-01-28 10:32 Message: Logged In: YES user_id=18417 I've got one attempt to address this issue at <http://sourceforge.net/ tracker/index.php? func=detail&aid=1107169&group_id=103&atid=300103>. However, please note that text entered via the admin web interface will get HTML-escaped when it is saved, so you can't use angle brackets around URLs and expect that to work. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1109139&group_…

1 0

[ mailman-Feature Requests-1109135 ] more informative rejection message
by SourceForge.net Jan. 28, 2005

Jan. 28, 2005

Feature Requests item #1109135, was opened at 2005-01-25 15:09 Message generated for change (Comment added) made by shub You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1109135&group_… Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Sam Steingold (sds) Assigned to: Nobody/Anonymous (nobody) Summary: more informative rejection message Initial Comment: Mailman/Handlers/Hold.py: class SuspiciousHeaders: it would be nice if the rejection message contained the name of the Suspicious Header. (it is much easier for the moderator to remove that if she wants to than to match the actual headers to the "privacy rules"). ---------------------------------------------------------------------- Comment By: Brad Knowles (shub) Date: 2005-01-28 10:30 Message: Logged In: YES user_id=18417 IIRC, you can't name the suspicious header, otherwise you'll get caught by the same rule. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1109135&group_…

1 0

[ mailman-Bugs-1111321 ] cron failures are sent to mailman list
by SourceForge.net Jan. 28, 2005

Jan. 28, 2005

Bugs item #1111321, was opened at 2005-01-28 09:47 Message generated for change (Comment added) made by shub You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1111321&group_… Category: command line scripts Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Wim Heirman (wheirman) Assigned to: Nobody/Anonymous (nobody) Summary: cron failures are sent to mailman list Initial Comment: When a cronjob fails (e.g. nightly_gzip has a permission problem), the output is sent to mailman@localhost. However, mailman is by default a mailing list (at least it was on my older Debian system, I copied the /var/mailman/lists from there to a new Fedora Core 3 installation). Since root is not on the mailman list, I get "message awaits moderator approval" messages. Shouldn't the error go straight to root? For instance, with a MAILTO=root directive in /etc/cron.d/mailman ? ---------------------------------------------------------------------- Comment By: Brad Knowles (shub) Date: 2005-01-28 10:28 Message: Logged In: YES user_id=18417 This sounds like an OS/distribution-specific issue. I get no such problems with Mailman on FreeBSD (for ntp.isc.org), nor with Mailman on Debian (for python.org). Feel free to try out your suggested change, and if it works, then recommend that to the people at Redhat for inclusion in future versions of their RPM. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1111321&group_…

1 0

[ mailman-Bugs-1108814 ] convert_html_to_plaintext strips text from hotmail
by SourceForge.net Jan. 28, 2005

Jan. 28, 2005

Bugs item #1108814, was opened at 2005-01-25 03:04 Message generated for change (Comment added) made by shub You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1108814&group_… Category: configuring/installing Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Kalvos (kalvos) Assigned to: Nobody/Anonymous (nobody) Summary: convert_html_to_plaintext strips text from hotmail Initial Comment: Mailman version 2.1.5 installed on FreeBSD at pair Networks. I use the web configuration of mailman. It is set up with convert_html_to_plaintext enabled. Recent email via Hotmail has been coming in with no body, even though the original email has text. The text is present, and although ugly, the code looks average for HTML mail. The actual original email content (without headers) is pasted below. No text is passed through Mailman. You can see this archive at http://five.pairlist.net/pipermail/coco/ and the result in this message: http://five.pairlist.net/pipermail/coco/2005-January/012347.html Any advice is appreciated if this is not a bug. <html><div style='background-color:'><DIV class=RTE> <P>OK, this is the hotmail test.<BR>_Glen<BR><BR></P></DIV>> <DIV></DIV>> <DIV></DIV>>OK, the next message from me will come from hotmail, as a test. <DIV></DIV>>-Glen <DIV></DIV>> > > <DIV></DIV>> > Well, the thing to do is, now that we've got a clue, go back to the <DIV></DIV>> > original email agent and make a couple of test posts, & we'll see <DIV></DIV>>who <DIV></DIV>> > gets what now that we know to look for it. <DIV></DIV>> <DIV></DIV>> > >> <DIV></DIV>> > >> > -- John. <DIV></DIV>> > > <DIV></DIV>> > >Brought to you by the 6809, the 6803 and their cousins! <DIV></DIV>> > >Yahoo! Groups Links <DIV></DIV>> > > <DIV></DIV>> > > <DIV></DIV>> > > <DIV></DIV>> > <DIV></DIV>> > -- <DIV></DIV>> > Cheers, Gene <DIV></DIV>> > "There are four boxes to be used in defense of liberty: <DIV></DIV>> >  soap, ballot, jury, and ammo. Please use in that order." <DIV></DIV>> > -Ed Howdershelt (Author) <DIV></DIV>> > 99.32% setiathome rank, not too shabby for a WV hillbilly <DIV></DIV>> > Yahoo.com attorneys please note, additions to this message <DIV></DIV>> > by Gene Heskett are: <DIV></DIV>> > Copyright 2005 by Maurice Eugene Heskett, all rights reserved. <DIV></DIV>> <DIV></DIV>> <DIV></DIV>> <DIV></DIV>> <DIV></DIV>> <DIV></DIV>>Brought to you by the 6809, the 6803 and their cousins! <DIV></DIV>>Yahoo! Groups Links <DIV></DIV>> <DIV></DIV>><*> To visit your group on the web, go to: <DIV></DIV>>     http://groups.yahoo.com/group/ColorComputer/ <DIV></DIV>> <DIV></DIV>><*> To unsubscribe from this group, send an email to: <DIV></DIV>>     ColorComputer-unsubscribe(a)yahoogroups.com <DIV></DIV>> <DIV></DIV>><*> Your use of Yahoo! Groups is subject to: <DIV></DIV>>     http://docs.yahoo.com/info/terms/ <DIV></DIV>> <DIV></DIV>> <DIV></DIV>> <DIV></DIV>> <DIV></DIV></div></html> ---------------------------------------------------------------------- Comment By: Brad Knowles (shub) Date: 2005-01-28 10:25 Message: Logged In: YES user_id=18417 It was hard to find examples of what you were talking about. Can I assume that you mean messages like <http://five.pairlist.net/pipermail/ coco/2005-January/012348.html>? In this case, what we need to do is to see the original, unedited, version of the message as it was submitted to Mailman, so that we can try to figure out what went wrong and why it was stripped to be "blank" but then submitted to the system. This may require that someone subscribe to Hotmail and send some test messages, both directly to another account as well as to the mailing list, so that we can see both the edited and the unedited versions of the message. Another problem is that this issue may be specific to the configurations of particular people using Hotmail, and it may be difficult to find out what options they have set/changed which result in this kind of behaviour. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1108814&group_…

1 0

[ mailman-Bugs-1111321 ] cron failures are sent to mailman list
by SourceForge.net Jan. 28, 2005

Jan. 28, 2005

Bugs item #1111321, was opened at 2005-01-28 10:47 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1111321&group_… Category: command line scripts Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Wim Heirman (wheirman) Assigned to: Nobody/Anonymous (nobody) Summary: cron failures are sent to mailman list Initial Comment: When a cronjob fails (e.g. nightly_gzip has a permission problem), the output is sent to mailman@localhost. However, mailman is by default a mailing list (at least it was on my older Debian system, I copied the /var/mailman/lists from there to a new Fedora Core 3 installation). Since root is not on the mailman list, I get "message awaits moderator approval" messages. Shouldn't the error go straight to root? For instance, with a MAILTO=root directive in /etc/cron.d/mailman ? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1111321&group_…

1 0

[ mailman-Bugs-1109325 ] Bug with upgrading to Mailman 2.1.4 in SuSE 9.1
by SourceForge.net Jan. 25, 2005

Jan. 25, 2005

Bugs item #1109325, was opened at 2005-01-25 13:44 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1109325&group_… Category: Web/CGI Group: 2.0.x Status: Open Resolution: None Priority: 5 Submitted By: Tim Smith (jallen13) Assigned to: Nobody/Anonymous (nobody) Summary: Bug with upgrading to Mailman 2.1.4 in SuSE 9.1 Initial Comment: [NOTE: This is a "I did it!" story.. the fix is at the bottom of this post :) ) Just wanted to make a report here about some problems I had upgrading Mailman from 2.1.3 to 2.1.4 using Yast Online Update (YOU) in Suse 9.1 AMD64. It broke my web-based GUI, and spit this error into my apache error logs: [Tue Jan 25 12:43:57 2005] [error] [client IPADDR] @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ [Tue Jan 25 12:43:57 2005] [error] [client IPADDR] [----- Mailman Version: 2.1.4 -----] [Tue Jan 25 12:43:57 2005] [error] [client IPADDR [----- Traceback ------] [Tue Jan 25 12:43:57 2005] [error] [client IPADDR] Traceback (most recent call last): [Tue Jan 25 12:43:57 2005] [error] [client IPADDR] File "/usr/lib/mailman/scripts/driver", line 241, in ? [Tue Jan 25 12:43:57 2005] [error] [client IPADDR] run_main() [Tue Jan 25 12:43:57 2005] [error] [client IPADDR] File "/usr/lib/mailman/scripts/driver", line 69, in run_main [Tue Jan 25 12:43:57 2005] [error] [client IPADDR] import xml.sax.saxutils [Tue Jan 25 12:43:57 2005] [error] [client IPADDR] ImportError: No module named xml.sax.saxutils [Tue Jan 25 12:43:57 2005] [error] [client IPADDR] [Mailman: low level unrecoverable exception] And the output of the Web browser going to the mailman location gives this error: Bug in Mailman version 2.1.4 We're sorry, we hit a bug! If you would like to help us identify the problem, please email a copy of this page to the webmaster for this site with a description of what happened. Thanks! Traceback: Content-type: text/html We're sorry, we hit a bug! Mailman experienced a very low level failure and could not even generate a useful traceback for you. Please report this to the Mailman administrator at this site. --------------------------------------------------------------------- So, I googled around, and found that this error is very common in 2.1.4 version. Just google for "Mailman Low level failure" and you'll get a lot of web pages like the one I just pasted, all for 2.1.4. I got some help from Don Burns from mailman-users list, he told me all I need to do is install python-xml. (Thanks Don!!) So, I used the trusty YAST and searched for python-xml and installed it. Wham-Bam, it works. I guess 2.1.4 version expects python-xml as a depends, whereas the earlier versions didn't care about that. I wanted to document this so maybe it''ll come up quicker for some poor sucker like myself googling around for this answer :) Cheers, Tim Smith ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1109325&group_…

1 0

[ mailman-Feature Requests-1109139 ] a common custom explanation for all rejection messages
by SourceForge.net Jan. 25, 2005

Jan. 25, 2005

Feature Requests item #1109139, was opened at 2005-01-25 10:12 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1109139&group_… Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Sam Steingold (sds) Assigned to: Nobody/Anonymous (nobody) Summary: a common custom explanation for all rejection messages Initial Comment: it would be very nice if there were a customization parameter where I could put some common text for all rejections messages. right now, I have to manually insert "For more information on the mailing list policy, please see <http://clisp.cons.org/faq.html#rejected>." ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1109139&group_…

1 0

[ mailman-Feature Requests-1109135 ] more informative rejection message
by SourceForge.net Jan. 25, 2005

Jan. 25, 2005

Feature Requests item #1109135, was opened at 2005-01-25 10:09 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1109135&group_… Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Sam Steingold (sds) Assigned to: Nobody/Anonymous (nobody) Summary: more informative rejection message Initial Comment: Mailman/Handlers/Hold.py: class SuspiciousHeaders: it would be nice if the rejection message contained the name of the Suspicious Header. (it is much easier for the moderator to remove that if she wants to than to match the actual headers to the "privacy rules"). ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1109135&group_…

1 0