SMTPS certificate incorrectly presumed invalid/corrupted when sending e-mail only when previous send was cancelled; but working otherwise.

RESOLVED INCOMPLETE

Status

MailNews Core
Networking: SMTP
RESOLVED INCOMPLETE
12 years ago
9 years ago

People

(Reporter: John, Unassigned)

Tracking

Trunk
x86
Windows XP

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: closeme 2008-11-13)

(Reporter)

Description

12 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.0.1) Gecko/20060111 Firefox/1.5.0.1
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.0.1) Gecko/20060111 Firefox/1.5.0.1

* Using SMTPS for sending e-mail
* Normally works, however if I cancel any SMTPS send-in-progress, then attempt to send any e-mail following this, Thunderbird reports the following error:

>>Could not establish an encrypted connection because certificate presented by [smtp-host-name] is invalid or corrupted. Error code: -8182.

Reproducible: Always

Steps to Reproduce:
1. Set up outgoing e-mail to use a SMTPS server.
2. Compose an e-mail.
3. Send the composed e-mail, BUT HIT cancel BEFORE it completes.
4. Try to send any other e-mail, and the error occurs.

Actual Results:  
Received error dialoge:

Could not establish an encrypted connection because certificate presented by [smtp-host-name] is invalid or corrupted. Error code: -8182.

Expected Results:  
The e-mail should have been sent without error.

Workaround: 

1. save composed e-mail as a draft.
2. restart Thunderbird.
3. retrieve e-mail from draft folder.
4. SMTPS send completes without error.

Updated

11 years ago
Component: General → Networking: SMTP
Product: Thunderbird → Core
Version: unspecified → Trunk
Assignee: mscott → nobody
QA Contact: general
Reporter, does the issue still occur with the latest supported Thunderbird 2.0.0.x / Shredder trunk nightlies?

(1.5.0.x is now end-of-life and the latest supported Thunderbird 2.0.0.x is 2.0.0.17)
Whiteboard: closeme 2008-11-13
RESO INCO due to lack of response to last question. If you feel this change was made in error, please respond to this bug with your reasons why.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 9 years ago
Resolution: --- → INCOMPLETE
(Assignee)

Updated

9 years ago
Product: Core → MailNews Core
You need to log in before you can comment on or make changes to this bug.