Gnome/Balsa mailman may break signatures?

[Albrecht Dreß <albrecht dress arcor de>]

Hi,

when receiving the message re. "[bug+patch] libmutt charset conversion  
flaw" I sent to this list yesterday, balsa complained about a broken  
signature. Investigating this in more depth (cross-checking with the  
message in the sentbox), the header line of the attachment which is longer  
than 72 chars

Content-Disposition: attachment; filename="balsa-2.0-libmutt...

is converted into two lines

Content-Disposition: attachment;\r\n
\tfilename="balsa-2.0-libmutt...

(replace <space> by <cr><lf><tab>) which of course triggers the invalid  
signature error.

Sending the same message to myself through my ISP, I could verify that  
it's neither my nor their MTA (both postfix) which modifies the header.

I am not sure if there is a "hard" upper limit for the line length in rfc  
821/822/2821/2822 (which would mean that it is a balsa/libmutt bug), or if  
it's just a recommendation, which would mean that it is a mailman bug, as  
gateways (if you regard mailman as some kind of gateway) are supposed to  
leave messages untouched. Anyone there with deeper insight into this?

Tia, cheers,

	Albrecht.



--
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Albrecht Dreß  -  Johanna-Kirchner-Straße 13  -  D-53123 Bonn (Germany)
     Phone (+49) 228 6199571  -  mailto:albrecht dress arcor de
_________________________________________________________________________

Attachment: pgpnwkeOnPvAh.pgp
Description: PGP signature