Who is doing S/MIME enveloping in KMail - gnupg2 or KMail?

[Nicholas Sushkin]

Hi, Aaron,

KMail 2.1.1 KDE 4.6.5 gpgsm (GnuPG) 2.0.17 libgcrypt 1.4.6 libksba 1.2.0

I send a signed unencrypted email. iPad and Outlook-web recipients cannot see 
the body of my email, only seeing the smime.p7m attachment. I am getting angry 
responses implying to stop using SMIME. I am looking at the email source and 
comparing to SMIME signed emails other people send from Outlook, Thunderbird, 
and Apple Mail that can be read on iPad and Outlook-web. I am also looking at 
the SMIME RFC http://tools.ietf.org/html/rfc3851#section-3.4

It seems that KMail is using saying Content-Type: multipart/signed and is 
using "SignedData format" option of sending out a signed email. It seems that 
that's against the RFC. The way I understand RFC is that if you do "SignedData 
format", you need to specify MIME Type "aplication/pcks7-mime".

So, I am wondering whether KMail can create signed only messages using the 
multipart/signed correctly, so that clients that do not support SMIME can 
properly display them.

I found a related bug filed in KMail 
https://bugs.kde.org/show_bug.cgi?id=280245 and commented on it, but I am not 
sure if the problem may be with gpgsm instead.

Aaron Toponce <aaron.toponce at gmail.com> wrote:
> On Wed, Dec 21, 2011 at 10:48:35AM -0500, Nicholas Sushkin wrote:
> > Hi, I think there is a bug in the way KMail is doing S/Mime envelop for
> > signed but not encrypted messages. I'd like to follow through, but I am
> > not sure if it's gnupg or KMail, which is the proper forum. Does anyone
> > (Werner) know by any chance?
> 
> Can you explain more? I'm assuming you're using GnuPG 2.0, seeing as though
> 1.4.* does not support S/MIME. Or are you confusing S/MIME with PGP/MIME?
> What errors are you seeing? What are you trying to do? Et cetera.
> 
> Thanks,
-- 
Nick
-------------- next part --------------
An HTML attachment was scrubbed...
URL: </pipermail/attachments/20111221/f34c0c93/attachment.htm>