177688 - POP/SSL: Untrusted certificate dialog speaks about websites instead of mailservers

Status: RESOLVED DUPLICATE of bug 378004

(SeaMonkey :: MailNews: Message Display, defect)

Description

[Daniel Küstner]

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; de-AT; rv:1.2b) Gecko/20021016
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; de-AT; rv:1.2b) Gecko/20021016

If the pop servers certificate is not trusted (i.e. its Certificate Authority is
unknown), you get a window with the title "Website Certified by an Unknown
Authority" and in the body of the message: "Please notify the webmaster ...",
"Are you willing ... Web site ...". This is somewhat irritating if you
configured mozilla to start with mailnews & browser window _and_ the account in
question to receive mails on startup, because you wonder why there is a website
which presents a certificate.

Reproducible: Always

Steps to Reproduce:
1. Create a pop3/ssl account with a provider whos Certificate are not authorized
(I confess, this is not trivial. At the moment securepop.t-online.de has such
certificates. But the accounts there are not free. Maybe someone who has a
T-Online account could try to reproduce)

2. select this account

3. CTRL-T (or what you prefer to receive mails).

Actual Results:  
see above.

Expected Results:  
Speak about mail server instead of website.

Comment 1

[Todd Cohn]

Yup, this is true.  I have a similar setup on my personal email server, and it
does talk about "website".

Comment 2

[JoSH Lehan]

This also bothers me.

My "ISP" (a homebrew setup) uses a self-signed certificate for checking mail via
secure IMAP.  The security is perfectly good, but since the certificate wasn't
signed by a known authority, it triggers the warning.  This is irritating
because the warning happens every time mail is checked.

There should be a way to say "Yes, I trust this certificate, do not warn me
about it anymore".  Perhaps this should be managed by the Certificate Manager,
like other certificates from websites.  Mozilla should remember the user's
choice and add the certificate to a "known good" list, and not trigger the
warning again unless the certificate changes from its remembered state.

Comment 3

[Daniel Küstner]

Krellan: This is not what this bug is about. This bug is only about the typo.
Please file another bug for your request.

Comment 4

[Robert Kaiser]

MASS-CHANGE:
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 5

[Robert Kaiser]

MASS-CHANGE:
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 6

[Robert Kaiser]

MASS-CHANGE:
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 7

[Robert Kaiser]

MASS-CHANGE:
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

Comment 8

[Philip Chee]

Strings come from PSM (See Bug 378004) Duplicating this to the TB bug since it's more likely to be fixed there (or PSM).