Sending of the Message Failed - connection ... office365 ... lost. Last Working Version 24.2.0?

RESOLVED WORKSFORME

Status

MailNews Core
Networking: SMTP
RESOLVED WORKSFORME
3 years ago
3 years ago

People

(Reporter: Mark Heitbrink, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [regression:TB3?])

(Reporter)

Description

3 years ago
User Agent: Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/42.0.2311.152 Safari/537.36

Steps to reproduce:

Send Mail to: smtp.office365.com:587 (STARTTLS)
There was an update in November 2014(?), since then I need to stay on 24.2.0, no newer version can send message from this account.
Reset/Delete Password and other hints from internet like create new profile tested, but without luck.


Actual results:

Error-Message:
Die Nachricht konnte nicht gesendet werden, weil die Verbindung mit dem SMTP-Server smtp.office365.com mitten in der Transaktion verloren wurde. Versuchen Sie es nochmals oder kontaktieren Sie Ihren Netzwerkadministrator. 


Expected results:

Send Mail without error ...

Comment 1

3 years ago
You can create a log of the communication with the server, see https://wiki.mozilla.org/MailNews:Logging. Use set NSPR_LOG_MODULES=smtp:5 .
Translation of error message:

"The message could not be sent because the connection to the SMTP server smtp.office365.com was lost in the middle of the transaction. Please try again or contact your network administrator."

This makes it sound like TB is not (completely) the issue. Apparently it had connection but then lost it. Sounds like either an internet or server problem.
Summary: Senden der Nachricht ist fehlgeschlagen - Last Working Version 24.2.0? → Sending of the Message Failed - Last Working Version 24.2.0?
(Reporter)

Comment 3

3 years ago
I started from scratch and can verify the problem right in that moment, when I add my S/MIME certificate. I do not need to sign the message, just adding my private key, will result in that error.

Tested on 38.0.1

It´s a selfsigned certificate, created with makecert.exe  


----- smtp.log with imported certificate, Email not signed  -----
0[f11140]: SMTP Connecting to: smtp.outlook.com
0[f11140]: SMTP entering state: 0
0[f11140]: SMTP Response: 220 AM3PR05CA038.outlook.office365.com Microsoft ESMTP MAIL Service ready at Wed, 24 Jun 2015 13:46:14 +0000
0[f11140]: SMTP entering state: 14
0[f11140]: SMTP Send: EHLO [192.168.10.20]

0[f11140]: SMTP entering state: 0
0[f11140]: SMTP Response: 250-AM3PR05CA038.outlook.office365.com Hello [93.223.10.22]
0[f11140]: SMTP entering state: 0
0[f11140]: SMTP Response: 250-SIZE 157286400
0[f11140]: SMTP entering state: 0
0[f11140]: SMTP Response: 250-PIPELINING
0[f11140]: SMTP entering state: 0
0[f11140]: SMTP Response: 250-DSN
0[f11140]: SMTP entering state: 0
0[f11140]: SMTP Response: 250-ENHANCEDSTATUSCODES
0[f11140]: SMTP entering state: 0
0[f11140]: SMTP Response: 250-STARTTLS
0[f11140]: SMTP entering state: 0
0[f11140]: SMTP Response: 250-8BITMIME
0[f11140]: SMTP entering state: 0
0[f11140]: SMTP Response: 250-BINARYMIME
0[f11140]: SMTP entering state: 0
0[f11140]: SMTP Response: 250 CHUNKING
0[f11140]: SMTP entering state: 4
0[f11140]: SMTP entering state: 21
0[f11140]: SMTP Send: STARTTLS

0[f11140]: SMTP entering state: 0
0[f11140]: SMTP Response: 220 2.0.0 SMTP server ready
0[f11140]: SMTP entering state: 19
0[f11140]: SMTP entering state: 14
0[f11140]: SMTP Send: EHLO [192.168.10.20]

----- smtp.log with imported certificate, Email not signed  -----

 ----- smtp.log removed SMIME Certificate -----
0[3611140]: SMTP Connecting to: smtp.outlook.com
0[3611140]: SMTP entering state: 0
0[3611140]: SMTP Response: 220 AM3PR06CA041.outlook.office365.com Microsoft ESMTP MAIL Service ready at Wed, 24 Jun 2015 13:48:00 +0000
0[3611140]: SMTP entering state: 14
0[3611140]: SMTP Send: EHLO [192.168.10.20]

0[3611140]: SMTP entering state: 0
0[3611140]: SMTP Response: 250-AM3PR06CA041.outlook.office365.com Hello [93.223.10.22]
0[3611140]: SMTP entering state: 0
0[3611140]: SMTP Response: 250-SIZE 157286400
0[3611140]: SMTP entering state: 0
0[3611140]: SMTP Response: 250-PIPELINING
0[3611140]: SMTP entering state: 0
0[3611140]: SMTP Response: 250-DSN
0[3611140]: SMTP entering state: 0
0[3611140]: SMTP Response: 250-ENHANCEDSTATUSCODES
0[3611140]: SMTP entering state: 0
0[3611140]: SMTP Response: 250-STARTTLS
0[3611140]: SMTP entering state: 0
0[3611140]: SMTP Response: 250-8BITMIME
0[3611140]: SMTP entering state: 0
0[3611140]: SMTP Response: 250-BINARYMIME
0[3611140]: SMTP entering state: 0
0[3611140]: SMTP Response: 250 CHUNKING
0[3611140]: SMTP entering state: 4
0[3611140]: SMTP entering state: 21
0[3611140]: SMTP Send: STARTTLS

0[3611140]: SMTP entering state: 0
0[3611140]: SMTP Response: 220 2.0.0 SMTP server ready
0[3611140]: SMTP entering state: 19
0[3611140]: SMTP entering state: 14
0[3611140]: SMTP Send: EHLO [192.168.10.20]

0[3611140]: SMTP entering state: 0
0[3611140]: SMTP Response: 250-AM3PR06CA041.outlook.office365.com Hello [93.223.10.22]
0[3611140]: SMTP entering state: 0
0[3611140]: SMTP Response: 250-SIZE 157286400
0[3611140]: SMTP entering state: 0
0[3611140]: SMTP Response: 250-PIPELINING
0[3611140]: SMTP entering state: 0
0[3611140]: SMTP Response: 250-DSN
0[3611140]: SMTP entering state: 0
0[3611140]: SMTP Response: 250-ENHANCEDSTATUSCODES
0[3611140]: SMTP entering state: 0
0[3611140]: SMTP Response: 250-AUTH LOGIN
0[3611140]: SMTP entering state: 0
0[3611140]: SMTP Response: 250-8BITMIME
0[3611140]: SMTP entering state: 0
0[3611140]: SMTP Response: 250-BINARYMIME
0[3611140]: SMTP entering state: 0
0[3611140]: SMTP Response: 250 CHUNKING
0[3611140]: SMTP entering state: 4
0[3611140]: SMTP entering state: 21
0[3611140]: SMTP auth: server caps 0x20114, pref 0x300, failed 0x0, avail caps 0x100
0[3611140]: (GSSAPI = 0x800, CRAM = 0x2000, NTLM = 0x4000, MSN =  0x8000, PLAIN = 0x200, LOGIN = 0x100, EXTERNAL = 0x400)
0[3611140]: trying auth method 0x100
0[3611140]: SMTP entering state: 15
0[3611140]: SMTP: MSN or LOGIN auth, step 0
0[3611140]: SMTP Send: AUTH LOGIN

0[3611140]: SMTP entering state: 0
0[3611140]: SMTP Response: 334 VXNlcm5hbWU6
0[3611140]: SMTP entering state: 13
0[3611140]: SMTP entering state: 16
0[3611140]: SMTP AuthLoginStep1() for mark@gruppenrichtlinien.de@,ŸîoœŸîo
0[3611140]: LOGIN auth
0[3611140]: Logging suppressed for this command (it probably contained authentication information)
0[3611140]: SMTP entering state: 0
0[3611140]: SMTP Response: 334 UGFzc3dvcmQ6
0[3611140]: SMTP entering state: 18
0[3611140]: SMTP Login response, code 334
0[3611140]: SMTP entering state: 17
0[3611140]: SMTP AuthLoginStep2
0[3611140]: PLAIN/LOGIN auth, step 2
0[3611140]: Logging suppressed for this command (it probably contained authentication information)
0[3611140]: SMTP entering state: 0
0[3611140]: SMTP Response: 235 2.7.0 Authentication successful target host DB3PR07MB058.eurprd07.prod.outlook.com
0[3611140]: SMTP entering state: 18
0[3611140]: SMTP Login response, code 235
0[3611140]: SMTP entering state: 3
0[3611140]: SMTP Send: MAIL FROM:<mark@gruppenrichtlinien.de> SIZE=407

0[3611140]: SMTP entering state: 0
0[3611140]: SMTP Response: 250 2.1.0 Sender OK
0[3611140]: SMTP entering state: 5
0[3611140]: SMTP Send: RCPT TO:<mark@gruppenrichtlinien.de>

0[3611140]: SMTP entering state: 0
0[3611140]: SMTP Response: 250 2.1.5 Recipient OK
0[3611140]: SMTP entering state: 6
0[3611140]: SMTP Send: DATA

0[3611140]: SMTP entering state: 0
0[3611140]: SMTP Response: 354 Start mail input; end with <CRLF>.<CRLF>
0[3611140]: SMTP entering state: 7
0[3611140]: SMTP entering state: 8
0[3611140]: SMTP Send: .

0[3611140]: SMTP entering state: 0
0[3611140]: SMTP Response: 250 2.6.0 <558AB513.5030402@gruppenrichtlinien.de> [InternalId=88579405518763, Hostname=DB3PR07MB058.eurprd07.prod.outlook.com] Queued mail for delivery
0[3611140]: SMTP entering state: 9
0[3611140]: SMTP Send: QUIT

0[3611140]: SMTP entering state: 0
0[3611140]: SMTP entering state: 0
0[3611140]: SMTP Response: 221 2.0.0 Service closing transmission channel
0[3611140]: SMTP entering state: 10
0[3611140]: SMTP entering state: 12
0[3611140]: SMTP connection error quitting 804b0002, ignoring 

 ----- smtp.log removed SMIME Certificate -----
(Reporter)

Comment 4

3 years ago
in addition: I can not add my selfsigned certificate (my public key) as a certificate authority to allow email usage from this "authority". I know it a certificate and a not a "real" authority, but it should work. I my Windows 7/8/8.1/10 I can add my pubic key a trusted root, trusted publisher etc, but not in Thunderbird 38.0.1 or any version newer than ESR 24.2
(Reporter)

Comment 5

3 years ago
I created the certificate like that:

Makecert -r -pe -n "CN=Mark Heitbrink,E=mark@gruppenrichtlinien.de,E=info@gruppenrichtlinien.de" -e 07/27/2070 -ss my -eku "1.3.6.1.5.5.7.3.3,1.3.6.1.5.5.7.3.4,1.3.6.1.5.5.7.3.2,1.3.6.1.4.1.311.10.3.4,1.3.6.1.4.1.311.10.3.3,2.16.840.1.113730.4.1" -l "http://www.gruppenrichtlinien.de/ueber-mich/public-key/" -a sha512 -len 8192

I will be added into the Microsoft personal certstore. Export it to .PFX and import in TB.
Directly after importing the Cert, without defining SMIME settings to a specific account, the SMTP send fails.

Updated

3 years ago
Component: Mail Window Front End → Networking: SMTP
Product: Thunderbird → MailNews Core
Summary: Sending of the Message Failed - Last Working Version 24.2.0? → Sending of the Message Failed - connection ... office365 ... lost. Last Working Version 24.2.0?

Comment 6

3 years ago
Can you try the betas between 24 and 31 to determine in which version the problem first appears?
https://ftp.mozilla.org/pub/mozilla.org/thunderbird/releases/
Flags: needinfo?(mark)
Whiteboard: [regression:TB3?]
(Reporter)

Comment 7

3 years ago
My test:

functional from 24.2 to 26.0b1
NOT functional  27.0b1 to 38.0b6 -> always the same error, timeout - lost in Transmission

In Version 38.1.0 it is funtional again!! :-)
functional aswell in 40.0b1
Flags: needinfo?(mark)

Comment 8

3 years ago
Thanks
Status: UNCONFIRMED → RESOLVED
Last Resolved: 3 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.