When setting TSL for SMTP, mozilla does not send any certificate.



MailNews Core
Networking: SMTP
14 years ago
9 years ago


(Reporter: Massimiliano Pala, Assigned: (not reading, please use seth@sspitzer.org instead))


Firefox Tracking Flags

(Not tracked)




14 years ago
User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040207 Firefox/0.8
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040207 Firefox/0.8

The problems appears when sending an email over TSL channel. The client correctly
performs all the steps: connects to the server, setup the channel, authenticates
(if required), and send the message. The issue is that there is no way to force
mozilla to send one of the installed certificates during the handshake, neither
does Mozilla chose the one configured for the email signing. This problem
prevents system administrators to force client authentication on SMTP to solve
spam-related issues.

Reproducible: Always
Steps to Reproduce:
1. Setup the SMTP server to use TSL
2. Send an e-mail using the configured server (SMTP)

Actual Results:  
No user certificate is presented by Mozilla during the TSL connection setup.

Expected Results:  
There should be an available option to set where the user can select the
certificate to be presented for client authentication during the TSL channel
setup with the SMTP server.

Comment 1

14 years ago
Isn't this also true for SMTP over SSL, POP3 over SSL and IMAP over SSL?
Do you have the address of a server requesting a client cert at your fingertips?
Product: MailNews → Core
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.
Last Resolved: 13 years ago
Resolution: --- → EXPIRED
Product: Core → MailNews Core
You need to log in before you can comment on or make changes to this bug.