[ mailman-Bugs-1605144 ] mailman corrupts RFC2047-encoded headers

SourceForge.net noreply at sourceforge.net
Wed Nov 29 12:53:26 CET 2006

Bugs item #1605144, was opened at 2006-11-29 10:28
Message generated for change (Comment added) made by dwmw2
You can respond by visiting: 

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,

The input was RFC2047-compliant. The output isn't.


>Comment By: David Woodhouse (dwmw2)
Date: 2006-11-29 11:53

Logged In: YES 
Originator: YES

Hm, good point; thanks. I've fixed the script which generates mail for
each commit to the Linux kernel git tree, and it should no longer generate
encoded-words longer than 75 characters.

I still see this input...


and this output...

Subject: =?UTF-8?Q?[MTD]_NAND:_CAF=C3=89_NAND_driver_cleanup,
        _fix_ECC_on_reading?= =?UTF-8?Q?_empty_flash?=

The comma is allowed, and doesn't have to be '=2C', does it? See §4.2 (3)
and §5 (1).


Comment By: Harald Hoyer (Red Hat) (saturn_de)
Date: 2006-11-29 10:44

Logged In: YES 
Originator: NO


   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: 

More information about the Mailman-coders mailing list