thunderbird refuses to 'accept certificate permanantly' when sending through a TLS mail server

RESOLVED EXPIRED

Status

Thunderbird
Message Compose Window
RESOLVED EXPIRED
13 years ago
13 years ago

People

(Reporter: Trent Lloyd, Assigned: Scott MacGregor)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

13 years ago
User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.6) Gecko/20050405 Epiphany/1.6.2 (Ubuntu) (Ubuntu package 1.0.2)
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.6) Gecko/20050405 Epiphany/1.6.2 (Ubuntu) (Ubuntu package 1.0.2)

If you are attempting to send through a TLS smtp server with a self-signed
certificate, it loops asking whether you would like to accept permanantly, for
this session or reject the certificate.

If you select the option to accept permanantly, it just throws the dialog back
at you, the other two options work as expected.

Reproducible: Always

Steps to Reproduce:
1. Setup an outgoing TLS mail server with a self-signed certificate.
2. Compose an email
3. Hit send
4. Select 'accept this certificate permanantly'

Actual Results:  
The dialog asking that question comes back up, over and over again.

Expected Results:  
It accepts the certificate and never asks about it again.

Workaround: simply accept the certificate temporarily for each session, it gets
annoying after a while though.

Comment 1

13 years ago
Duplicate of/related to bug 221552?
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
Last Resolved: 13 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.