Closed Bug 207947 Opened 21 years ago Closed 21 years ago

recieving SMTP response code 454 freezes Mozilla at 100% CPU load

Categories

(MailNews Core :: Networking: SMTP, defect)

x86
Linux
defect
Not set
critical

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 98399

People

(Reporter: kurtjaeke, Assigned: sspitzer)

Details

User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1) Build Identifier: Mozilla 1.3.1 official release I used "ethereal" to locate this problem. The connection trace looks like that: (there should be a HELO from Mozilla here, but I started capturing too late) Response (from server): 220 my.mail.server EHLO Command (from MailNews): EHLO my.host Response (from server): 250 my.mail.server 250 STARTTLS 250 PIPELINING 250 8BITMIME Message body (from MailNews): STARTTLS\r\n Response (from server): 454 TLS missing certificate: error:0200100D:system library:fopen:Permission denied (#4.3.0) And that's it. Nothing happens, the "Sending Mail" window remains on top, the progress bar stops. Reproducible: Always Steps to Reproduce: 1. Open Mail&News Account Settings, go to "Outgoing Server (SMTP)" 2. Check "Use secure connection" [x] "sometimes" or [x] "always" 3. Try sending an email Actual Results: Mozilla (the entire app, including open browser windows) freezes at 100% CPU load Expected Results: 1. Print an error message. 2. Ask to send the mail without SMTP STARTTLS.
> User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1) Yes, I am overriding my Browser's UA and falsifiying statistics.
*** This bug has been marked as a duplicate of 98399 ***
Status: UNCONFIRMED → RESOLVED
Closed: 21 years ago
Resolution: --- → DUPLICATE
The code submitted to fix 98399 looks like it'll fix this bug too. It needs to be reviewed and super-reviewed tho.
Has that code made it into 1.4rc3 already? I pulled the CVS tree, it looks different at all the interesting places, but it does not fix this one.
Product: MailNews → Core
Product: Core → MailNews Core
You need to log in before you can comment on or make changes to this bug.