A mail with this subject line was sent to a mailman list: Subject: =?UTF-8?Q?[MTD]=20NAND:=20CAF=C3=89=20NAND=20driver=20cleanup,=20fix=20ECC=20on=20reading=20empty=20flash?= Mailman sent it out again like this: Subject: =?UTF-8?Q?[MTD]=20NAND:=20CAF=C3=89=20NAND=20driver=20cleanup, =20fix=20ECC=20on=20reading=20empty=20flash?= The first was RFC2047-compliant; the second wasn't. Mailman broke it. I originally filed an Evolution bug (bug 217631) but upon closer inspection of RFC2047 (and verifying that it's happening in transit through mailman) I think it's actually mailman that's at fault.
Upstream bug filed: http://sourceforge.net/tracker/index.php?func=detail&aid=1605144&group_id=103&atid=100103
Thanks :) I was about to do the same... added my comment there..
Fixing the length of the encoded-word doesn't help (in this case) -- it seems to be the comma which triggers the line-wrap.
I really don't know what to do with this one... The SF bug has no resolution either and the discussion died. Closing with CANTFIX.