S/MIME signature in messages with a binary attachment on IMAP server not verified: question mark in security info icon without any further explanation.



14 years ago
11 years ago


(Reporter: michael, Assigned: mscott)


Firefox Tracking Flags

(Not tracked)


(Whiteboard: closeme 2008-08-28)



14 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.5) Gecko/20041107 Firefox/0.10.1 StumbleUpon/1.998
Build Identifier: Thunderbird version 0.9+ (20041128)

This problem concerns messages that have been signed using S/MIME and that
contain a binary attachment (e.g. PDF or Excel spreadsheets), when reading them
through an IMAP server. This problem will *not* concern messages with inline
attachments that Thunderbird shows directly in the message text window, such as
JPEG or plain text, or when binary attachment + S/MIME signed messages are
downloaded via POP3.

What happens is that a message affected by the problem will show a pencil icon
with a question mark in the security status information. I guess this is because
the S/MIME signature cannot be verified because of the attachment still lying on
the IMAP server.

However, it is to my knowledge not possible to obtain information on the reason
why the question mark is shown next to the pencil icon. When clicking on the
pencil icon, simply nothing happens. The usual S/MIME security Info dialog does
not show up in this case. Nor is there any other indication of the problem's nature.

Reproducible: Always
Steps to Reproduce:
1. Attach a binary file to a message
2. Digitally sign using S/MIME
3. Send to an IMAP account
4. Read the message on your IMAP account using Thunderbird
Actual Results:  
Note the question mark next to the pencil icon and that no information about the
problem can be obtained. When clicking

Expected Results:  
Clicking on the pencil icon should give a description of the problem, preferably
offering to take the steps necessary to actually verify the digital signature.

Using the latest nightly 0.9 build with default theme: Thunderbird version 0.9+

Comment 1

14 years ago
I have the same problem too. This is essentially Bug#:199626 but even worse as
the message won't even verify in the preview pane. If you move the message to a
local folder, the problem goes away. 

As far as I can recall, the bug had been there since the first version (v0.2?)
of thunderbird I used.

Comment 2

14 years ago
This looks like a duplicate of bug 219290 which is older and has more comments.
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 4

14 years ago
I have the same problem, using Thunderbird 1.0.7 on Linux (Fedora Core 4).
Please don't auto-resolve it ;)

QA Contact: front-end
Reporter, does the issue still occur with the latest supported 2.0.0.x / Shredder trunk nightlies?

(1.5.0.x is now end-of-life and the latest supported Thunderbird version 2 is
Whiteboard: closeme 2008-08-28
RESO INCO per lack of response to the last question. If you feel this change was made in error, please respond to this bug with your reasons why.
Last Resolved: 11 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.