Fw: [Mailman-Users] Re: Example of bad line break in subject header

2003-02-25 Thread Sumeet Pannu 
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)
&g

[Mailman-Users] Re: Example of bad line break in subject header

2003-02-24 Thread Sumeet Pannu 
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

>  >List-Unsubscribe:
,
>  >   
>  >List-Archive: 
>  >List-Post: 
>  >List-Help: 
>  >List-Subscribe: ,
>  >   
>  >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.ma

[Mailman-Users] further 2.0.x to 2.1.1 issues

2003-02-23 Thread Sumeet Pannu 
looking at this change it kinda breaks the subject line into parts.
smart wrapping or something which breaks people's procmail rules.
Note the self imposed indentation.
do you think it's possible to have the same behaviour as in mailman 2.0?
In 2.0 Subject lines are displayed as they show up. Alternatively does anyone
have info on migrating from 2.1 to 2.0? 
thanks
sumeet.
example:
> Subject: [build-notify]
>  This an example of broken subject headers.
>  It will break my procmail.
--
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: Example of bad line break in subject header wasRe:[Mailman-Users]Upgrade from 2.0.x to 2.1.1-- incorrect padding error.

2003-02-23 Thread Sumeet Pannu 
Wow! Thanks for the really quick turnaround. I appreciate all the help. Also
can someone point out the edicate here. I notice many people top posting so
i do too. Is that OK? And should I direct my emails to the sender and list?
Thanks again. Unfortunately I only got 6
lines down:
18:37:[EMAIL PROTECTED] python -S ~mailman/cron/senddigests
Traceback (most recent call last):
  File "/var/mailman/cron/senddigests", line 94, in ?
main()
  File "/var/mailman/cron/senddigests", line 86, in main
mlist.send_digest_now()
  File "/list/Mailman/Digester.py", line 60, in send_digest_now
ToDigest.send_digests(self, mboxfp)
  File "/list/Mailman/Handlers/ToDigest.py", line 123, in send_digests
send_i18n_digests(mlist, mboxfp)
  File "/list/Mailman/Handlers/ToDigest.py", line 295, in send_i18n_digests
msg = scrubber(mlist, msg)
  File "/list/Mailman/Handlers/Scrubber.py", line 326, in process
msg.set_payload(sep.join(text), charset)
TypeError: sequence item 2: expected string, NoneType found

- Original Message -
From: "Tokio Kikuchi" <[EMAIL PROTECTED]>
To: "Mitchell Marks" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Sunday, February 23, 2003 5:48 PM
Subject: Re: Example of bad line break in subject header was
Re:[Mailman-Users]Upgrade from 2.0.x to 2.1.1-- incorrect padding error.


> Hi,
>
> I've uploaded a new patch. Please try.
>
http://sourceforge.net/tracker/?func=detail&aid=687338&group_id=25568&atid=3
84680
>
http://sourceforge.net/tracker/download.php?group_id=25568&atid=384680&file_
id=43260&aid=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=detail&aid=601117&group_id=103&atid=300
103
>
http://sourceforge.net/tracker/download.php?group_id=103&atid=300103&file_id
=42418&aid=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
>
>
> --
> 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