[Tracker-discuss] [issue147] Current email headers corrupt mail reader display

[Dennis Allison]

Dennis Allison added the comment:

Paul, I was the source of the original problem.  I suspect that the module
that constructs the email message sent out to all of use that track bug   
reports does not construct the  From header in the proper form.                    

The mail reader that is failing is Pine.  It's an ascii reader, old and 
stable.

When I export some example headers I get: 

From: =?utf-8?q?=0A=09=09=09=09=09Hirokazu_Yamamoto=0A=09=09=09=09?=
        <report at bugs.python.org>
and

From: =?utf-8?q?=0A=09=09=09=09=09Mark_Dickinson=0A=09=09=09=09?=
        <report at bugs.python.org>

The header is supposed to be limited to 72 characters and folded if it is
long (RFC2882).  These headers looks to be too long and/or incorrectly 
folded.  I do not know how well Pine deals with the utf-8 but I suspect 
that the safe limit is the byte length of the header and not the 
character count.  

The problem seems to be the =0A element which will be decoded into a
newline character.  The =09 element is a tab which is likely to mess up 
formatting as well.

On Wed, 19 Sep 2007, Paul Dubois wrote:

> 
> Paul Dubois added the comment:
> 
> I examined his user record and do not see any extra spaces.
> 
> On 9/19/07, Guido van Rossum <metatracker at psf.upfronthosting.co.za> wrote:
> >
> >
> > Guido van Rossum added the comment:
> >
> > I pasted the headers from the example that Dennis mailed me into issue
> > 158.
> >
> > I also noted this in the new-bugs digest email. It seems to be a problem
> > only
> > with Jim Jewett:
> >
> > """
> > Message: 3
> > Date: Tue, 18 Sep 2007 20:22:53 -0000
> > From:                                   Jim
> > Jewett                                      <report at bugs.python.org>
> > Subject: [New-bugs-announce] [issue1177] urllib* 20x responses not OK?
> > To: new-bugs-announce at python.org
> > Message-ID:
> >         <1190146973.85.0.192058090901.issue1177 at psf.upfronthosting.co.za>
> > Content-Type: text/plain; charset=utf-8
> >
> >
> > New submission from
> >                                         Jim Jewett
> >                                 :
> >
> > Under the http protocol, any 2xx response is OK.
> > """
> >
> > Note the extra whitespace around Jim Jewett.  Perhaps something wacky is
> > going
> > on with Jim Jewett's user entry?  Other entries in the same digest don't
> > have this.
> >
> > Even if the RFC doesn't strictly disallow this behavior, I think we should
> > fix
> > it if we can.
> >
> > _______________________________________________________
> > Meta Tracker <metatracker at psf.upfronthosting.co.za>
> > <http://psf.upfronthosting.co.za/roundup/meta/issue147>
> > _______________________________________________________
> > _______________________________________________
> > Tracker-discuss mailing list
> > Tracker-discuss at python.org
> > http://mail.python.org/mailman/listinfo/tracker-discuss
> >
> 
> _______________________________________________________
> Meta Tracker <metatracker at psf.upfronthosting.co.za>
> <http://psf.upfronthosting.co.za/roundup/meta/issue147>
> _______________________________________________________

--

_______________________________________________________
Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue147>
_______________________________________________________