Version: (using KDE KDE 3.5.0) Installed from: SuSE RPMs OS: Linux KMail currently doesn't set the content-description header for signed and encrypted mails. This is especially annoying because some anti virus programs (e.g. avast) detect mails with such unnamed attachments as "suspicious". I attached a trivial patch to fix this. In fact, support for that was already prepared in the code but commented out. Hmm.
Created attachment 13838 [details] patch to fix content-description
Created attachment 13894 [details] patch to fix content-description I forget something: "Content-Disposition: attachment\n" has to be removed from the pgp/mime version identification. It's simply not required according to RFC 2015 and makes the mail suspicious for certain anti virus software.
On Tuesday 13 December 2005 13:39, Stefan Scheler wrote: > patch to fix content-description Thanks for the patch, I'll have a look later today. Cheers, Till
I talked to our MIME guru and got the following intel: "The internal structure of a multipart/signed or /encrypted is nothing a user should see (yes, KMail shows it). As such, C-Desc headers on these parts (which are only for humans), are useless. C-Desc header should only be added at user discretion, never automatically. I guess such wording appears in the corresponding rfc, too." That translates to: you should fix the broken avast, adding c-desc headers is not the right answer to the problem. Do you happen to know how other MUAs (Evo, Thunderbird) deal with this? If they indeed add c-desc headers we might have to reconsider.
> C-Desc header should only be added at user discretion, never automatically. Why that? I don't see how a description like "digital signature" for a pgp signature would hurt anyone? The corresponding RFC doesn't say anything about whether this should be added automatically or not. And in fact most headers are added automatically, so I don't see the point here. > Do you happen to know how other MUAs (Evo, Thunderbird) deal with this? Well Thunderbird adds these headers, mutt doesn't.
I think the RFC was probably referring to attachments made by the user. There's no reason to ask the user for description for automatically-generated MIME parts.
Thank you for taking the time to file a bug report. KMail2 was released in 2011, and the entire code base went through significant changes. We are currently in the process of porting to Qt5 and KF5. It is unlikely that these bugs are still valid in KMail2. We welcome you to try out KMail 2 with the KDE 4.14 release and give your feedback.