Closed Bug 175598 Opened 22 years ago Closed 19 years ago

certificate view does not show recipients name

Categories

(SeaMonkey :: MailNews: Message Display, defect)

x86
Windows XP
defect
Not set
trivial

Tracking

(Not tracked)

RESOLVED EXPIRED

People

(Reporter: tobias-mailings, Unassigned)

References

(Blocks 1 open bug)

Details

Attachments

(2 files)

Hello, in our company we are using Microsoft Exchange and sign emails with Verisign digitalIDs - Verisign does create the IDs automatically based upon the configuration of the mailbox. When I send a signed email to my private Mozilla account and view the details, I see "Recipients" as "signed by" and not my real name. I'll add screenshots and my public cert. Tobias
Attached file my public key (deleted) —
if you open this public key using the Windows Certificate Manager you'll see the correct data for "signed by".
QA Contact: olgam → esther
Blocks: 195937
Tobias, is this bug still a problem for you? I just looked at a sample mail that was signed by a Thawte Personal certificate and the name displayed as expected in all the locations indicated in your screenshot. (Path to these dialogs is now: View | Message Security Info)
no, it still looks the same. I assume what is special on our signatures is that it is based on our Exchange email system. In Exchange55, the mail boxes are not configured in a organizational unit but in some sort of common name cn structure. Mozilla ends up displaying only one of the cn's in my certificate, but not multiple or the correct one.
Product: Browser → Seamonkey
Assignee: sspitzer → mail
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/
This bug has been automatically resolved after a period of inactivity (see above comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: