Fw: [Mailman-Users] Re: Example of bad line break in subject header
I think the lack of response probably has everyone stumped on this bug (feature?). If it is a feature than there should certainly be a turn off botton. When subjects are too long, they get indented, which breaks procmail rules. I propose the following workarounds: 1. Migrate back to 2.0.13. Can anyone give me insight into the posibility of doing this and if it's even possible, ie, will the messages, archives remain there? 2. Does anyone have any idea how to force sendmail to pipe ALL mailman messages to procmail and set up a rule to remove the tabs before sending the message to the users, but after it has already mangled the subject line? thanks, sumeet. - Original Message - From: Sumeet Pannu [EMAIL PROTECTED] To: [EMAIL PROTECTED]; Mitchell Marks [EMAIL PROTECTED] Sent: Monday, February 24, 2003 12:52 AM Subject: [Mailman-Users] Re: Example of bad line break in subject header This is clearly what I meant to say in my last post. Doug Brandon also has this issue and no one was able to address it for him. I have the same issue as Mr. Marks. Would someone please point me to the correct Headers.py patch referred to below, perhaps my mileage will be better than Mr. Marks'. Alternatively a migration back to 2.0.13 would be acceptable if anyone has done this. Thanks, sumeet. - Original Message - From: Mitchell Marks [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Sunday, February 23, 2003 3:48 PM Subject: Example of bad line break in subject header was Re: [Mailman-Users] Upgrade from 2.0.x to 2.1.1-- incorrect padding error. I'm enclosing below the full headers from Sumeet P's recent message, as they reached me. This shows the formatting problem discussed last week, mentioned on the Mailman-Users list by Sarah from NOW and seconded by me, and also turned over a little on the Developers list. The discussion on Developers included requests for an example that would reproduce the problem. I don't know if this one will show the same behavior if re-tried on another installation, but here we can at least see it happening someplace we can observe in common. (In case this gets mangled on the way back through, the Subject header as I've received it and pasted below is: first line [Mailman-Users] then second line a Tab and the rest Upgrade from 2.0.x to 2.1.1-- incorrect padding error. ) I've installed the recommended Headers.py patch (and checked that it is /this/ headers.py that is being used), and I thought briefly that the problem was solved for my installation -- but it isn't. I'll quote a subject string that I've seen problems with, but note that whether it's reproducible seems to depend on what list it's going through. Here's the example: [CUIP Activity] NSPTECH 2097 Alex Wilson Wednesday 2003-01-15 OS install/Printer Install. It breaks after the list tag [CUIP Activity], and so do test messages with longish subjects that go through that list. But if I send a message with that same header through a Test list (or any of several others), it doesn't break funny. I'm trying to figure out the differences between the lists, but haven't managed to make the error happen in the Test list by fiddling with Language Options and Personalization. I'm close to ready to just suppress all wrapping in Subjects if that would cure this oddity. Would that be a disaster waiting to happen? How hard would it be (I don't know much about the Mailman python code)? Thanks, Mitch Marks P.S. The point was made in the Developers discussion that Eudora's handling of the newlines in the summary windows may not accord to the relevant standard. Would someone who can speak to this fairly authoritatively feel like sending a report/suggestion in Qualcomm's direction? This is indeed only bothering Eudora users here. (Including me...) The headers for the example passing through Mailman-Users: At 03:23 PM 2/23/03, Sumeet wrote: X-Originating-IP: [65.113.40.130] From: Sumeet [EMAIL PROTECTED] To: [EMAIL PROTECTED] Date: Sun, 23 Feb 2003 13:23:58 -0800 X-Mailer: Microsoft Outlook Express 5.50.4522.1200 X-OriginalArrivalTime: 23 Feb 2003 21:23:59.0699 (UTC) FILETIME=[E14D2A30:01C2DB81] X-Spam-Status: No, hits=1.4 required=5.0 tests=BODY_PYTHON_ZOPE,FORGED_HOTMAIL_RCVD,FROM_BIGISP,LARGE_HEX,SPAM_PHRAS E_00_01,USER_AGENT_OE X-Spam-Level: * Subject: [Mailman-Users] Upgrade from 2.0.x to 2.1.1-- incorrect padding error. X-BeenThere: [EMAIL PROTECTED] X-Mailman-Version: 2.1.1 List-Id: Mailman mailing list management users mailman-users.python.org List-Unsubscribe: http://mail.python.org/mailman/listinfo/mailman-users, mailto:[EMAIL PROTECTED] List-Archive: http://mail.python.org/pipermail/mailman-users List-Post: mailto:[EMAIL PROTECTED] List-Help: mailto:[EMAIL PROTECTED] List-Subscribe: http://mail.python.org/mailman
Re: [Mailman-Users] Re: Example of bad line break in subject header
On Monday, February 24, 2003, at 06:52 AM, Mitchell Marks wrote: Thank you for these patches. They didn't yet solve the problem. However, I think I can clarify the circumstances under which it occurs. It seems to be not the list settings (for Language or Personalization) which matter, but the message's original type. Specifically, I'm seeing the problem when the message is text/html when it arrives. (MM is sending it back out as multipart/mixed). These messages do not generally have any hi-bit or encoded characters in their Subjects. We're seeing that problem here as well, though I've confirmed it has happened with text/plain as the content type [as sent out by MM]. I upgraded MM from 2.0.13 to 2.1.1 on the 16th of Feb, just before NOW reported the problem to MM-users. Unfortunately most of our users use Eudora [5.1.1 or 5.2 under win2k]. Some have HTML mail enabled, others don't. I usually use Pine [though sometimes OS X mail], and haven't seen the problem viewing mail from either of those MUAs. So far, the problem has affected all of our 30+ lists, as some folks seem to have the habit of making really long subjects. I've already hand-entered all of the users' real names into the list rosters, so I would hate to move back to 2.0.13 as that feature was not available. I have a development box that I can put MM on and test out if anyone has other patches that might be worth trying. Any advice would be most welcome. Thanks, /vjl/ -- Vince LaMonica UC Irvine, School of Social Ecology W3 Developer * 116 Social Ecology I, Irvine, CA 92697 [EMAIL PROTECTED] http://www.seweb.uci.edu/techsupport This is like losing a game by forfeit when your team was ahead with the bases loaded and your best batter on deck. - Rep. John Conyers, on the DOJ agreeing to settle with Microsoft -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Re: Example of bad line break in subject header
The biggest problem isn't really your particular email client, it's procmail. I agree with you that it is not confined to any particular sort of message plain text etc, all have subject wrapping turned on. I'm trying to get around it by using some procmail magic, but the block format is really hard to grep for. The fact that no one has been able to tackle this makes me think it's a pretty big issue somewhere. - Original Message - From: Vince LaMonica [EMAIL PROTECTED] To: Mitchell Marks [EMAIL PROTECTED] Cc: Tokio Kikuchi [EMAIL PROTECTED]; [EMAIL PROTECTED] Sent: Tuesday, February 25, 2003 2:20 PM Subject: Re: [Mailman-Users] Re: Example of bad line break in subject header On Monday, February 24, 2003, at 06:52 AM, Mitchell Marks wrote: Thank you for these patches. They didn't yet solve the problem. However, I think I can clarify the circumstances under which it occurs. It seems to be not the list settings (for Language or Personalization) which matter, but the message's original type. Specifically, I'm seeing the problem when the message is text/html when it arrives. (MM is sending it back out as multipart/mixed). These messages do not generally have any hi-bit or encoded characters in their Subjects. We're seeing that problem here as well, though I've confirmed it has happened with text/plain as the content type [as sent out by MM]. I upgraded MM from 2.0.13 to 2.1.1 on the 16th of Feb, just before NOW reported the problem to MM-users. Unfortunately most of our users use Eudora [5.1.1 or 5.2 under win2k]. Some have HTML mail enabled, others don't. I usually use Pine [though sometimes OS X mail], and haven't seen the problem viewing mail from either of those MUAs. So far, the problem has affected all of our 30+ lists, as some folks seem to have the habit of making really long subjects. I've already hand-entered all of the users' real names into the list rosters, so I would hate to move back to 2.0.13 as that feature was not available. I have a development box that I can put MM on and test out if anyone has other patches that might be worth trying. Any advice would be most welcome. Thanks, /vjl/ -- Vince LaMonica UC Irvine, School of Social Ecology W3 Developer * 116 Social Ecology I, Irvine, CA 92697 [EMAIL PROTECTED] http://www.seweb.uci.edu/techsupport This is like losing a game by forfeit when your team was ahead with the bases loaded and your best batter on deck. - Rep. John Conyers, on the DOJ agreeing to settle with Microsoft -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/sumeetp%40hotmail.com -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
[Mailman-Users] Re: Example of bad line break in subject header
This is clearly what I meant to say in my last post. Doug Brandon also has this issue and no one was able to address it for him. I have the same issue as Mr. Marks. Would someone please point me to the correct Headers.py patch referred to below, perhaps my mileage will be better than Mr. Marks'. Alternatively a migration back to 2.0.13 would be acceptable if anyone has done this. Thanks, sumeet. - Original Message - From: Mitchell Marks [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Sunday, February 23, 2003 3:48 PM Subject: Example of bad line break in subject header was Re: [Mailman-Users] Upgrade from 2.0.x to 2.1.1-- incorrect padding error. I'm enclosing below the full headers from Sumeet P's recent message, as they reached me. This shows the formatting problem discussed last week, mentioned on the Mailman-Users list by Sarah from NOW and seconded by me, and also turned over a little on the Developers list. The discussion on Developers included requests for an example that would reproduce the problem. I don't know if this one will show the same behavior if re-tried on another installation, but here we can at least see it happening someplace we can observe in common. (In case this gets mangled on the way back through, the Subject header as I've received it and pasted below is: first line [Mailman-Users] then second line a Tab and the rest Upgrade from 2.0.x to 2.1.1-- incorrect padding error. ) I've installed the recommended Headers.py patch (and checked that it is /this/ headers.py that is being used), and I thought briefly that the problem was solved for my installation -- but it isn't. I'll quote a subject string that I've seen problems with, but note that whether it's reproducible seems to depend on what list it's going through. Here's the example: [CUIP Activity] NSPTECH 2097 Alex Wilson Wednesday 2003-01-15 OS install/Printer Install. It breaks after the list tag [CUIP Activity], and so do test messages with longish subjects that go through that list. But if I send a message with that same header through a Test list (or any of several others), it doesn't break funny. I'm trying to figure out the differences between the lists, but haven't managed to make the error happen in the Test list by fiddling with Language Options and Personalization. I'm close to ready to just suppress all wrapping in Subjects if that would cure this oddity. Would that be a disaster waiting to happen? How hard would it be (I don't know much about the Mailman python code)? Thanks, Mitch Marks P.S. The point was made in the Developers discussion that Eudora's handling of the newlines in the summary windows may not accord to the relevant standard. Would someone who can speak to this fairly authoritatively feel like sending a report/suggestion in Qualcomm's direction? This is indeed only bothering Eudora users here. (Including me...) The headers for the example passing through Mailman-Users: At 03:23 PM 2/23/03, Sumeet wrote: X-Originating-IP: [65.113.40.130] From: Sumeet [EMAIL PROTECTED] To: [EMAIL PROTECTED] Date: Sun, 23 Feb 2003 13:23:58 -0800 X-Mailer: Microsoft Outlook Express 5.50.4522.1200 X-OriginalArrivalTime: 23 Feb 2003 21:23:59.0699 (UTC) FILETIME=[E14D2A30:01C2DB81] X-Spam-Status: No, hits=1.4 required=5.0 tests=BODY_PYTHON_ZOPE,FORGED_HOTMAIL_RCVD,FROM_BIGISP,LARGE_HEX,SPAM_PHRAS E_00_01,USER_AGENT_OE X-Spam-Level: * Subject: [Mailman-Users] Upgrade from 2.0.x to 2.1.1-- incorrect padding error. X-BeenThere: [EMAIL PROTECTED] X-Mailman-Version: 2.1.1 List-Id: Mailman mailing list management users mailman-users.python.org List-Unsubscribe: http://mail.python.org/mailman/listinfo/mailman-users, mailto:[EMAIL PROTECTED] List-Archive: http://mail.python.org/pipermail/mailman-users List-Post: mailto:[EMAIL PROTECTED] List-Help: mailto:[EMAIL PROTECTED] List-Subscribe: http://mail.python.org/mailman/listinfo/mailman-users, mailto:[EMAIL PROTECTED] Sender: [EMAIL PROTECTED] -- Mitchell Marks CUIP Tech Coordinatorhttp://cuip.uchicago.edu CUIP: Chicago Public Schools / Univ. of Chicago Internet Project 5640 S Ellis Ave AAC-045, Univ of Chgo, Chgo IL 60637 Telephone: Ofc 773-702-6041 Fax 702-8212 Home (v.m. only, ok any time) 241-7166 Email: Primary address: [EMAIL PROTECTED] Alternate UofC addresses (use especially to report problems with cuip.uchicago.edu): [EMAIL PROTECTED] and [EMAIL PROTECTED] Off-campus (ISP) address: [EMAIL PROTECTED] -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options
[Mailman-Users] Re: Example of bad line break in subject header
Thank you for these patches. They didn't yet solve the problem. However, I think I can clarify the circumstances under which it occurs. It seems to be not the list settings (for Language or Personalization) which matter, but the message's original type. Specifically, I'm seeing the problem when the message is text/html when it arrives. (MM is sending it back out as multipart/mixed). These messages do not generally have any hi-bit or encoded characters in their Subjects. Thanks, -- Mitch At 07:48 PM 2/23/03, Tokio Kikuchi wrote: Hi, I've uploaded a new patch. Please try. http://sourceforge.net/tracker/?func=detailaid=687338group_id=25568atid=384680 http://sourceforge.net/tracker/download.php?group_id=25568atid=384680file_id=43260aid=687338 I also recommend to use my version of CookHeaders.py. Looks like it's complicated by more stable than CVS. http://sourceforge.net/tracker/?func=detailaid=601117group_id=103atid=300103 http://sourceforge.net/tracker/download.php?group_id=103atid=300103file_id=42418aid=601117 Tokio Mitchell Marks wrote: I'm enclosing below the full headers from Sumeet P's recent message, as they reached me. This shows the formatting problem discussed last week, mentioned on the Mailman-Users list by Sarah from NOW and seconded by me, and also turned over a little on the Developers list. snip -- Mitchell Marks CUIP Tech Coordinatorhttp://cuip.uchicago.edu CUIP: Chicago Public Schools / Univ. of Chicago Internet Project 5640 S Ellis Ave AAC-045, Univ of Chgo, Chgo IL 60637 Telephone: Ofc 773-702-6041 Fax 702-8212 Home (v.m. only, ok any time) 241-7166 Email: Primary address: [EMAIL PROTECTED] Alternate UofC addresses (use especially to report problems with cuip.uchicago.edu): [EMAIL PROTECTED] and [EMAIL PROTECTED] Off-campus (ISP) address: [EMAIL PROTECTED] -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
