[ mailman-Bugs-1605144 ] mailman corrupts RFC2047-encoded headers
SourceForge.net
noreply at sourceforge.net
Wed Nov 29 11:44:25 CET 2006
Bugs item #1605144, was opened at 2006-11-29 11:28
Message generated for change (Comment added) made by saturn_de
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1605144&group_id=103
Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: mail delivery
Group: 2.1 (stable)
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: David Woodhouse (dwmw2)
Assigned to: Nobody/Anonymous (nobody)
Summary: mailman corrupts RFC2047-encoded headers
Initial Comment:
Given an input like this:
Subject: =?UTF-8?Q?[MTD]=20NAND:=20CAF=C3=89=20NAND=20driver=20cleanup,=20fix=20ECC=20on=20reading=20empty=20flash?=
Mailman appears to emit mail like this:
Subject: =?UTF-8?Q?[MTD]=20NAND:=20CAF=C3=89=20NAND=20driver=20cleanup,
=20fix=20ECC=20on=20reading=20empty=20flash?=
The input was RFC2047-compliant. The output isn't.
----------------------------------------------------------------------
Comment By: Harald Hoyer (Red Hat) (saturn_de)
Date: 2006-11-29 11:44
Message:
Logged In: YES
user_id=5540
Originator: NO
http://www.ietf.org/rfc/rfc2047.txt
An 'encoded-word' may not be more than 75 characters long, including
'charset', 'encoding', 'encoded-text', and delimiters. If it is
desirable to encode more text than will fit in an 'encoded-word' of
75 characters, multiple 'encoded-word's (separated by CRLF SPACE) may
be used.
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1605144&group_id=103
More information about the Mailman-coders
mailing list