Closed
Bug 30777
Opened 25 years ago
Closed 25 years ago
overly alarming message when viewing signed mail
Categories
(MailNews Core :: MIME, defect, P3)
MailNews Core
MIME
Tracking
(Not tracked)
People
(Reporter: jgmyers, Assigned: rhp)
Details
When mozilla displays a message that is signed using S/MIME, it displays in a double-bordered box the message "This message is possibly SIGNED. Mozilla Mail does not support signed mail." This message is overly alarming. It seems to indicate that there is something wrong, yet fails to give the user any hint as to what the user should do. The correct thing for the user to do in this situation is ignore the fact that the message was signed. Mozilla is, however, able to do that for the user without the user's help. Mozilla should completely ignore signatures that it does not support, treating it as if there were no signature to begin with.
Assignee | ||
Comment 1•25 years ago
|
||
Well, I can live with changing a message, but I don't think we should remove the box alltogether. In 4.x we display a problem icon that says we can't validate the signature. Perhaps just a signature or something like that would be better. I don't think we should remove the message all together. - rhp
Comment 2•25 years ago
|
||
When/if we get secure mail in mozilla, we should integrate this failure with the sign/encrypt UI which has yet to be designed. For the moment, I think think what we have is fine. Strictly, it's more necessary for encrypted messages where we can't show any body text.
Assignee | ||
Comment 3•25 years ago
|
||
Uhhh...so what should I do with this bug? - rhp
Comment 4•25 years ago
|
||
My vote would be to sit on it until Seamonkey UI freeze or until we get secure mail, whichever comes first. I'd want to wordsmith the error message before we ship, but I know you have bigger fish to fry right now.
Reporter | ||
Comment 5•25 years ago
|
||
Why don't you think the message should be removed? What purpose does the message serve?
Reporter | ||
Comment 6•25 years ago
|
||
This bug is about signatures, not encrypted messages. An unrecognized encrypted message needs to be indicated because there is content that the user cannot read. An unrecognized signature has no useful information content.
Assignee | ||
Updated•25 years ago
|
Status: NEW → ASSIGNED
Target Milestone: M17
Assignee | ||
Updated•25 years ago
|
Target Milestone: M17 → M19
Assignee | ||
Comment 7•25 years ago
|
||
*** This bug has been marked as a duplicate of 34570 ***
Status: ASSIGNED → RESOLVED
Closed: 25 years ago
Resolution: --- → DUPLICATE
Updated•20 years ago
|
Product: MailNews → Core
Updated•16 years ago
|
Product: Core → MailNews Core
You need to log in
before you can comment on or make changes to this bug.
Description
•