Closed Bug 286970 Opened 20 years ago Closed 20 years ago

domain name mismatch reported "using TLS if available"

Categories

(SeaMonkey :: Security, enhancement)

x86
Windows 98
enhancement
Not set
normal

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 255025

People

(Reporter: allltaken, Assigned: dveditz)

Details

User-Agent: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.8b2) Gecko/20050320 Build Identifier: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.8b2) Gecko/20050320 My ISP previously had one domain name and now has another, and the certificates are handled by a server upstream from my local ISP. When I access POP mail using the "Use TLS if available" security setting, the security certificate doesn't match the name of my POP server and a warning box is presented. I would like the enhancement of being able to set a preference or mail server setting to indicate that the certificate is OK for my mail server, so I don't have to enter it manually every time. I set the mail preference to "Use TLS if available" some months ago, perhaps more than a year ago, and just today noticed that the setting is changed to "Never". When I reset it, the certificate warnings began. Reproducible: Always Steps to Reproduce: 1. Set mail account security setting to "Use TLS if available". 2. Click button to get new messages 3. Actual Results: See "Security Error: Domain Name Mismatch" warning & dialog box. Expected Results: Store a setting that the certificate is OK for that mail server name, and refer to it on fetching the certificate instead of presenting the warning box. I've also had consistent crashes today trying to access the Certificate Manager with this particular build, for which Talkback reports were filed.
I should have added that my ISP kept the old mail-server name available to those who didn't want to change their addresses, and I opted to keep using the original name.
*** This bug has been marked as a duplicate of 255025 ***
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.