Bug 66318 - message/rfc822 attachment MUST NOT use a Content-Transfer-Encoding
Summary: message/rfc822 attachment MUST NOT use a Content-Transfer-Encoding
Status: RESOLVED DUPLICATE of bug 108939
Alias: None
Product: kmail
Classification: Unmaintained
Component: mime (show other bugs)
Version: unspecified
Platform: Debian testing Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-10-21 10:10 UTC by Adrian von Bidder
Modified: 2007-09-14 12:17 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Adrian von Bidder 2003-10-21 10:10:21 UTC 
Version:            (using KDE KDE 3.1.4)
Installed from:    Debian testing/unstable Packages
OS:          Linux

Hi,

This is relevant because it makes mail bounce with some extremely pedantic mail systems, including ABUSE@NIC.IT.

When I forward a mail as attachment, kmail adds a Content-Transfer-Encoding header to the MIME header for the message/rfc822 message part, which, as far as I understand the rfc, MUST NOT be done. It is supposed that the attached message has to be properly encoded.

cheers
-- vbi
Comment 1 Adrian von Bidder 2004-05-11 08:35:29 UTC 
Verified, as requested. Problem is still there as of KDE 3.2.2.
Comment 2 Andreas Gungl 2005-06-12 21:20:06 UTC 
Still valid for KMail 1.8.1 (KDE 3.4.1).
Comment 3 Carsten Pfeiffer 2005-11-01 19:01:01 UTC 
Merging this with #108939

*** This bug has been marked as a duplicate of 108939 ***