If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

OCSP validation fails with -8073 if first mail is sent

RESOLVED INVALID

Status

MailNews Core
Networking: SMTP
RESOLVED INVALID
13 years ago
8 years ago

People

(Reporter: Wolfgang Knauf, Unassigned)

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) Gecko/20040616
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7) Gecko/20040616

I'm connecting to the mail provider GMX (www.gmx.de)

Sending the first mail of a mozilla sesion fails with the following message:
"Error trying to validate certificate from mail.gmx.net using OCSP - corrupted
or unknown response. Error Code: -8073"

My security preferences are quite strict: 
"Use OCSP to validate all certificates using this URL and signer" is active.
Response signer is:
"Verisign class 1 Primary OCSP Responder"
Service URL:
http://ocsp.verisign.com/ocsp/status

How can I find out whether mail.gmx.net sends a certificate while performing
SMTP or not? 

Maybe I'm misusing the OCSP validation feature, but this message does not give
me the feeling that it's my failure :-)

Reproducible: Always
Steps to Reproduce:

Comment 1

13 years ago
have a look at Bug 130885 OCSP validation failure, -8073, -5961,
maybe Bug 130885 comment 20 is explaining your issue.

http://bugzilla.mozilla.org/show_bug.cgi?id=130885#c20
http://bugzilla.mozilla.org/show_bug.cgi?id=130885#c41

related:
Bug 151271 Allow browsing sites after OCSP validation failure
Bug 123114 pacbell.com - OCSP error for PacBell online account manager
(Reporter)

Comment 2

13 years ago
I came across 130885 while doing some bugzilla research. Probably it's related
but I'm not knowing how to verify it.

Some more detail information about my mail account settings:
Outgoing server (SMTP): Server name is "mail.gmx.net". The option "use name and
passwort" is checked. "Use secure connection" is set to "TLS, if available".

I tried to set it to "TLS", and in this case the same happened as with "TLS if
available".
Setting it to "SSL" made the sending fail (no server response ?).
After setting it to "No" the sending worked.

My guess would be that GMX somehow rejects the TLS sending attempt, but Mozilla
thinks this is some certificate response and tries to evaluate it. Then he
realizes that TLS is impossible and sends the mail by plain SMTP.

Comment 3

13 years ago
If you want to see what is going on you can make a log, see
http://www.mozilla.org/quality/mailnews/mail-troubleshoot.html
They also recommend reading Bug 47524

Does sending work after the sending of the first mail failed?
Dumb question ;-), does sending work after you had a look at your inbox?
(Reporter)

Comment 4

13 years ago
Sending the mail fails only once, I can re-send it after the message without any
problems.
Doing POP before does not influence this behaviour.
Interesting is that after closing and reopening Mozilla sending still works. It
fails once again after shutting down and reopening the internet connection.

That's the log for a mail sent to myself (only up to the "sending failed"
message box):
16384[80826b0]: SMTP Connecting to: mail.gmx.net
16384[80826b0]: SMTP entering state: 0
16384[80826b0]: SMTP Response: 220 {mp010} GMX Mailservices ESMTP
16384[80826b0]: SMTP entering state: 15
16384[80826b0]: SMTP Send: EHLO [80.184.47.92]
16384[80826b0]: SMTP entering state: 0
16384[80826b0]: SMTP Response: 250-{mp010} GMX Mailservices
16384[80826b0]: SMTP entering state: 0
16384[80826b0]: SMTP Response: 250-8BITMIME
16384[80826b0]: SMTP entering state: 0
16384[80826b0]: SMTP Response: 250-ENHANCEDSTATUSCODES
16384[80826b0]: SMTP entering state: 0
16384[80826b0]: SMTP Response: 250-AUTH=LOGIN CRAM-MD5 PLAIN
16384[80826b0]: SMTP entering state: 0
16384[80826b0]: SMTP Response: 250-AUTH CRAM-MD5 LOGIN PLAIN
16384[80826b0]: SMTP entering state: 0
16384[80826b0]: SMTP Response: 250 STARTTLS
16384[80826b0]: SMTP entering state: 4
16384[80826b0]: SMTP entering state: 22
16384[80826b0]: SMTP Send: STARTTLS
16384[80826b0]: SMTP entering state: 0
16384[80826b0]: SMTP Response: 220 2.7.0 {mp010} Ready to start TLS
16384[80826b0]: SMTP entering state: 20
16384[80826b0]: SMTP entering state: 15
16384[80826b0]: SMTP Send: EHLO [80.184.47.92]
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/
(Reporter)

Comment 6

12 years ago
I cannot verify it against a current Mozilla Suite / Seamonkey because I
migrated to thunderbird and this one does not offer OCSP validation.

But something strange: with firefox 1.0.7, if I activate OCSP validation ("use
OCSP to validate all certificates.." with "Verisign class 1 Primary OCSP
responder" and service url "http://ocsp.verisign.com/ocsp/status" (default), I
receive this error message for even this bug site:
"Error trying to validate certificate from bugzilla.mozilla.org using OCSP -
unauthorized request."

With "use OCSP to validate only certificates that specify an OCSP service URL"
it works without error.
(Reporter)

Comment 7

12 years ago
I checked it against Mozilla 1.7.12 and it still happens.

One idea: is the OCSP validation done via HTTP ? My internet provider,
www.freenet.de, often redirects the first HTTP request to their own homepage. 
sorry for the spam.  making bugzilla reflect reality as I'm not working on these bugs.  filter on FOOBARCHEESE to remove these in bulk.
Assignee: sspitzer → nobody
(Assignee)

Updated

9 years ago
Product: Core → MailNews Core
QA Contact: networking.smtp
(Reporter)

Comment 9

8 years ago
Too old bug and I don't find this option in Thunderbird. So I'm closing it.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 8 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.