On Sun, Sep 04, 2005 at 05:06:54PM +0100, Philip Rowlands wrote: > On Sun, 4 Sep 2005, Paul Koster wrote: > > >Hans Verkuil wrote: > > > What's this garbage at the end? I don't see it in the ticket mailed > >directly > >> to me! > > > >My user agent also shows this weird stuff, though a lot less (only the > >last line of the signature). > > Heh. The trailing crud (which I see in Pine) is the sourceforge list > sig, being messed up by the base64 encoding of the utf8 mail. > > >My guess would be something with the character encoding (utf-8). Is > >there any reason not to use plain-ascii? > > Yes please! The current ticket-mailer routine places =?utf-8?q? junk in > the Subject header, and writes the body in base64, which makes mail > spool files hard to search.
Which part in the subject is utf-8? > Can someone fix? The question is what exactly is broken, the mail that trac sent, or sourceforge's appending of the sig? I've put myself to the direct cc of trac, so I'll get the next notification mail w/o sourceforge's sig and with to compare. -- Axel.Thimm at ATrpms.net
pgpD6uCcLUUZY.pgp
Description: PGP signature
