236466 - KMail 1.6 S/MIME encrypted message not recognized

Status: RESOLVED WORKSFORME

(Thunderbird :: Mail Window Front End, defect)

Description

[Matej Cepl]

User-Agent:       Mozilla/5.0 (compatible; Konqueror/3.2; Linux; X11) (KHTML, like Gecko)
Build Identifier: Mozilla Thunderbird 0.5 (Debian/woody binary package from backports.org)

Hi, 
 
I am regular user of KMail (currently 1.6 from KDE 3.2) and when sending 
emails from there to myself (with installed Aegypten modules; http://
www.gnupg.org/aegypten/) encrypted as S/MIME, the message is not recognized as 
encrypted by Thunderbird (I have still Enigma extension for 0.4, but it should 
be irrelevant, isn't it?) and its content is not displayed, although 
apparently some cryptography stuff is going on because Thunderbird asks me for 
the Master Security Password (or how is it called). 
 
All certificates etc. should be correctly installed in Thunderbird, because I 
am able to send encrypted message to myself from there and they are 
recognized, decrypted and read by KMail. 
 
I first thought that it is problem with Aegypten modules, but its developers 
claimed that the message is all right, and it was also recognized and 
decrypted by mutt (through OpenSSL smime program), so the buck may after all 
stop in your side of the playground. 
 
I will attach to this bug the example of message which was not recognized by 
Thunderbird as encrypted and screenshots of whatever I was able to find out 
about the problem. I am not regular Mozilla/whatever user, so if I missed 
something obvious, please do not hesitate to contact me. 
 
Thanks, 
 
Matej 

Reproducible: Always
Steps to Reproduce:
1. Send S/MIME ecnrypted and signed message from KMail to myself 
2. Open the message in Mozilla Thunderbird 0.5 
3. Fill in Master Security Password 
Actual Results:  
Body of the message is not displayed. 

Expected Results:  
Well, I suppose it's obvious -- to show me the message and certify that it was 
correctly signed and encrypted.

Comment 1

[Matej Cepl]

Attachment: Message exported from Thunderbird

I guess, that content won't be readable to you, but at least headers may give
some information. See next screenshots for the content.

Comment 2

[Matej Cepl]

Attachment: Standard view of the message

Well, just to show that I can see nothing.

Comment 3

[Matej Cepl]

Attachment: Headers of the message as shown by Thunderbird

Unfortunately, my 800x600 display does not allow me to show more.

Comment 4

[Matej Cepl]

Attachment: Screenshot of KMail with the message unencrypted.

Here you can finally see, what I was actually sending :-)

Comment 5

[Matej Cepl]

Attachment: Screenshot of Thunderbird security info dialog

This is what Thunderbird thinks about the message security status. I do not
agree :-).

Comment 6

[Matej Cepl]

Attachment: Screenshot of mutt with the message opened

The reason why I think it is not altogether KMail's problem: mutt does not seem
to have any problems with the message.

Comment 7

[Nelson Bolyard (seldom reads bugmail)]

Since mozilla manages to correctly decode SMIME encrypted messages from 
most other SMIME clients, we have to ask: what'd different about this message?

Comparing it to S/MIME encrypted message sent by mozilla itself, I see 3 
apparent differences:

1. Content type is application/pkcs7-mime
   mozilla uses application/x-pkcs7-mime

2. Content type includes  smime-type=enveloped-data
   mozilla doesn't.

3. no Content-description header,
   mozilla uses 
      Content-description: S/MIME Encrypted Message

I'd guess the relevant difference is the first one.  Try editing the 
message, and change the content type to include the "x-", and see if 
that changes it.  

Comment 8

[Matej Cepl]

According to seemingly long time ago resolved bug 119418 and discussion on
Usenet (http://groups.google.com/groups?th=71fa5540127c8a59), Mozilla (not sure
about TB though) should be able to handle both application/pkcs7-mime and
application/x-pkcs7-mime.

Comment 9

[Nelson Bolyard (seldom reads bugmail)]

Let's talk about "should" after we know exactly what the problem is.
To find that out, I'm suggesting that you play with that email until it works.
I suggest you do this:
1. make a new mozilla email folder.  Call it "test" (say).
2. save the message in it
3. exit mozilla
4. edit the test folder with your favorite editor (vi or emacs :-)
   change one of the above headers, to look more like mozilla's emails.
   save the edited test folder.
5. restart mozilla
6. go look at the mail message in the test folder.  See if that fixed it.
7. If not, go back to step 3 and repeat, changing another header line.
8. repeat until you've gotten it to work, or until you've tried everything.
9. report back here on the results.

Comment 10

[Nelson Bolyard (seldom reads bugmail)]

This problem is apparently peculiar to Thunderbird.  It is NOT confirmed
in mozilla's mail client.  Leaving unconfirmed.

I stored the message (first attachment above) into a test folder, and 
looked at it with moz 1.3.1 and moz 1.7 RC3, and BOTH of them clearly 
identified it as an encrypted email that couldn't be decrypted because
I don't have the key.

Here's a question: if you go to the thunderbird window shown in your 
second attachment above, and click the little [+] symbol in front of the 
subject in the message preview pane, so that that header panel expands,
does it THEN show you that it was encrypted?

Comment 11

[Pedro Pessoa]

I confirmed this bug in Mozilla Mail 1.7.2. 
This is what I did: 
Received an encrypted email from KMail. 
Confirmed the behavior described by Matej. I could not see the message and 
Mozilla Mail informs that it is not encrypted. However, if I don't supply my master 
password for the "Software Security Device", Mozilla does indicate that it is 
encrypted and cannot decrypt it. 
 
Using Mozilla I sent another encrypted message to my self. 
I can view the contents of this one. 
I edited the folder as sugested by Nelson and replaced the body, not the headers, 
of the message I could not decrypt by the body of the message I could decrypt. 
After restarting Mozilla I could decrypt the original message sent by KMail and read 
the encrypted body I had just pasted. 
 
It seems that this is not a problem of the message header. 

Comment 12

[Gervase Markham [:gerv]]

This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/

Comment 13

[Matej Cepl]

This exact problem is really resolved, but other interoperability issues 
remain. I will eventually open new bugs about them. 

Comment 14

[Nelson Bolyard (seldom reads bugmail)]

Since no code in mozilla was changed to resolve this bug, 
I'm going to change the resolution from "fixed" (which implies that 
the code was changed to fix it) to "works for me" (which implies
that the problem was resolved without any code change).
So, I'm reopening it now, and will resolve it momentarily.

Comment 15

[Nelson Bolyard (seldom reads bugmail)]

Resolved/WorksForMe