bugzilla.mozilla.org will be intermittently unavailable on Saturday, March 24th, from 16:00 until 20:00 UTC.

UI do not call message verification if a really long S/MIME signed message in IMAP folder is viewed in a separate window



MailNews: Message Display
15 years ago
8 years ago


(Reporter: Vladimír Solnický, Unassigned)


Windows XP

Firefox Tracking Flags

(Not tracked)




15 years ago
Steps to reproduce:

1. Set MailNews to use IMAP to access INBOX (incoming mailbox)
2. Create a message
3. Attach a long attachment (to invoke the code for IMAP delayed download when
reading such an invoming message from IMAP folder). For me, 392196 bytes were
4. Set digitally sign this message and do NOT encrypt this message (both S/MIME
5. Send a message
6. Press Get New Mesages
7. Click Once on a message row. You will see a mesage in the lower part of a
window and message wil have pen icon crossed by a question mark with it.
8. If you click on the question mark, mozilla ask you to download the rest of
message (attachments) to verify signatures. Say OK.
9. Pen icon is diplayed and clicking on it say, that signature is good.
10. Now dobleclik the message to have it opened in a separate window.
11. You will see question mark -- click on it.
12. Mozilla asks you to download attachments in order to verify signature. Clik OK.
13. Nothing happens, question mark is still there and clicking on it returns you
to the item 12 (the same problem is with Message Security Info in a separate
message window).

Expected behavior: 

The same what happen in item 9.

I tested it in Windows XP but it may be platform independent. 

If I move the message to a local folder, the problem disappears (it looks like a
forgotten call to an IMAP delayed download).

This bug prevents users with habit of opening messages in a separate windows
from verifying long signed messages.
Product: Browser → Seamonkey


13 years ago
Assignee: sspitzer → mail


12 years ago
Blocks: 332771
Assignee: mail → nobody
QA Contact: esther → message-display

Comment 1

9 years ago
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614

Comment 2

8 years ago
This bug report is registered in the SeaMonkey product, but still has no comment since the inception of the SeaMonkey project 5 years ago.

Because of this, we're resolving the bug as EXPIRED.

If you still can reproduce the bug on SeaMonkey 2 or otherwise think it's still valid, please REOPEN it and if it is a platform or toolkit issue, move it to the according component.

Query tag for this change: EXPIRED-20100420
Last Resolved: 8 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.