Bug 217667 - Mailman inserts whitespace into RFC2047-encoded headers.
Summary: Mailman inserts whitespace into RFC2047-encoded headers.
Status: CLOSED CANTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: mailman   
(Show other bugs)
Version: 6
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Tomas Smetana
QA Contact:
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2006-11-29 09:55 UTC by David Woodhouse
Modified: 2007-11-30 22:11 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2007-08-06 09:18:33 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description David Woodhouse 2006-11-29 09:55:21 UTC 
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.
Comment 2 Harald Hoyer 2006-11-29 10:45:11 UTC 
Thanks :) I was about to do the same... added my comment there..
Comment 3 David Woodhouse 2006-11-29 11:55:00 UTC 
Fixing the length of the encoded-word doesn't help (in this case) -- it seems to
be the comma which triggers the line-wrap.
Comment 4 Tomas Smetana 2007-08-06 09:18:33 UTC 
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.
Note You need to log in before you can comment on or make changes to this bug.