Thunderbird 91.1.0 not sending, no error msg, email in sent folder
Emails sent and were received until upgraded from previous to latest TB 78 version (on 9-13) from 78.13 to 78.14 I think(?). Nothing was changed before upgrade. Email went to sent folder but not received and no error msg when sent. ISP Comcast, windows 10 pro. Smtp settings seem ok and could send before update. Receiving email worked. No issues sending from Comcast email on phone or Comcast web based email portal.
Then manually updated from latest 78 per above to 91.1.0 in hopes would fix issue. No change running TB in troubleshoot mode, disabling windows firewall or disabling windows built-in virus/threat protection.
UPDATE: Have 2 Comcast email addresses (i.e 2 accounts setup). Issue still occurs and don't receive anything when sending from "primary" account. If send from "secondary" account, emails are received? So what could be causing issue all of the sudden on one account and not other? The outgoing SMTP server settings are identical for the accounts in TB except for the "user name" (ie address) fields).
Would appreciate some help...
Modified by Jsm59
All Replies (5)
https://www.thunderbird.net/en-US/thunderbird/88.0beta/releasenotes/ the config editor can be used to revert sending to the old code that was replaced in V88. Does that change anything? It is not a permanent solution as the old code will be removed. But it is offered as a diagnostic.
Before doing that however try logging what is happening. I got these instructions here.
- open Config Editor, set mailnews.smtp.loglevel to All
- open DevTools (crel+Shift+J), go to the Console tab, clear any existing logs by clicking the trash can icon
- send a mail
- copy the logs from DevTools to a web file sharing service like oneDrive and post a link to that here. (I am certain the size of the log will make this forum choke.)
Probably a good idea to turn off the mailnews.smtp.loglevel afterward back to it's original Warn.
Matt... Thx for all help. Strange but email started sending. Probably not related/coincidence, but when I set up logging my Gmail acct received Comcast email from TB. I will keep eye on and post logs if issue seen in future. -- jerry
Has been working since 9/28 and now not sending again. Attached is the log after "mailnews.smtp.loglevel=All". It doesn't seem to be the large size as seen in some samples(?) (V91.2.1 now):
log ---------------------------------
mailnews.smtp: Sending message <92a9d301-641f-7d2e-b854-c41a464fe25e@comcast.net> SmtpService.jsm:84:18 mailnews.smtp: Connected SmtpClient.jsm:385:17 mailnews.smtp: S: 220 resomta-ch2-13v.sys.comcast.net resomta-ch2-13v.sys.comcast.net ESMTP server ready
SmtpClient.jsm:411:17 mailnews.smtp: C: EHLO [IPV6:2601:248:580:2b20:dced:7a72:f0e2:e909] SmtpClient.jsm:577:19 mailnews.smtp: S: 250-resomta-ch2-13v.sys.comcast.net hello [2601:248:580:2b20:dced:7a72:f0e2:e909], pleased to meet you
250-HELP
250-AUTH LOGIN PLAIN XOAUTH2
250-SIZE 36700160
250-ENHANCEDSTATUSCODES
250-8BITMIME
250 OK
SmtpClient.jsm:411:17 mailnews.smtp: Possible auth methods: PLAIN,LOGIN SmtpClient.jsm:897:17 mailnews.smtp: Maximum allowed message size: 36700160 SmtpClient.jsm:903:19 mailnews.smtp: Current auth method: PLAIN SmtpClient.jsm:615:17 mailnews.smtp: Authentication via AUTH PLAIN SmtpClient.jsm:630:21 mailnews.smtp: C: Logging suppressed (it probably contained auth information) SmtpClient.jsm:573:19 mailnews.smtp: S: 235 2.7.0 ... authentication succeeded
SmtpClient.jsm:411:17 mailnews.smtp: Authentication successful. SmtpClient.jsm:1087:17 mailnews.smtp: C: MAIL FROM:<jsm59@comcast.net> BODY=8BITMIME SIZE=939 SmtpClient.jsm:577:19 mailnews.smtp: S: 250 2.1.0 <jsm59@comcast.net> sender ok
SmtpClient.jsm:411:17 mailnews.smtp: MAIL FROM successful, proceeding with 1 recipients SmtpClient.jsm:1121:17 mailnews.smtp: Adding recipient... SmtpClient.jsm:1126:17 mailnews.smtp: C: RCPT TO:<jsm59jsm@gmail.com> SmtpClient.jsm:577:19 mailnews.smtp: S: 250 2.1.5 <jsm59jsm@gmail.com> recipient ok
SmtpClient.jsm:411:17 mailnews.smtp: RCPT TO done, proceeding with payload SmtpClient.jsm:1186:19 mailnews.smtp: C: DATA SmtpClient.jsm:577:19 mailnews.smtp: S: 354 OK
SmtpClient.jsm:411:17 mailnews.smtp: Sending 939 bytes of payload SmtpClient.jsm:547:17 mailnews.smtp: S: 250 2.0.0 eFk5mbS4hbtymeFk6mnHBW mail accepted for delivery
SmtpClient.jsm:411:17 mailnews.smtp: Message sent successfully. SmtpClient.jsm:1245:21 mailnews.smtp: Closing connection... SmtpClient.jsm:151:17 mailnews.smtp: Idling while waiting for new connections... SmtpClient.jsm:1255:19 mailnews.smtp: Socket closed. SmtpClient.jsm:485:17
end log ------------------------
Modified by Jsm59
All of the sudden, stopped working again. Log below with " mailnews.smtp.loglevel to All". Log doesn't seem big like some samples? Send from my comcast acct to a gmail acct. (TB 91.2.1)
begin log ----------
mailnews.smtp: Sending message <327b21b7-1223-4b79-495a-d1c361f9e352@comcast.net> SmtpService.jsm:84:18 mailnews.smtp: Connected SmtpClient.jsm:385:17 mailnews.smtp: S: 220 resomta-ch2-01v.sys.comcast.net resomta-ch2-01v.sys.comcast.net ESMTP server ready
SmtpClient.jsm:411:17 mailnews.smtp: C: EHLO [IPV6:2601:248:580:2b20:dced:7a72:f0e2:e909] SmtpClient.jsm:577:19 mailnews.smtp: S: 250-resomta-ch2-01v.sys.comcast.net hello [2601:248:580:2b20:dced:7a72:f0e2:e909], pleased to meet you
250-HELP
250-AUTH LOGIN PLAIN XOAUTH2
250-SIZE 36700160
250-ENHANCEDSTATUSCODES
250-8BITMIME
250 OK
SmtpClient.jsm:411:17 mailnews.smtp: Possible auth methods: PLAIN,LOGIN SmtpClient.jsm:897:17 mailnews.smtp: Maximum allowed message size: 36700160 SmtpClient.jsm:903:19 mailnews.smtp: Current auth method: PLAIN SmtpClient.jsm:615:17 mailnews.smtp: Authentication via AUTH PLAIN SmtpClient.jsm:630:21 mailnews.smtp: C: Logging suppressed (it probably contained auth information) SmtpClient.jsm:573:19 mailnews.smtp: S: 235 2.7.0 ... authentication succeeded
SmtpClient.jsm:411:17 mailnews.smtp: Authentication successful. SmtpClient.jsm:1087:17 mailnews.smtp: C: MAIL FROM:<jsm59@comcast.net> BODY=8BITMIME SIZE=1003 SmtpClient.jsm:577:19 mailnews.smtp: S: 250 2.1.0 <jsm59@comcast.net> sender ok
SmtpClient.jsm:411:17 mailnews.smtp: MAIL FROM successful, proceeding with 1 recipients SmtpClient.jsm:1121:17 mailnews.smtp: Adding recipient... SmtpClient.jsm:1126:17 mailnews.smtp: C: RCPT TO:<jsm59jsm@gmail.com> SmtpClient.jsm:577:19 mailnews.smtp: S: 250 2.1.5 <jsm59jsm@gmail.com> recipient ok
SmtpClient.jsm:411:17 mailnews.smtp: RCPT TO done, proceeding with payload SmtpClient.jsm:1186:19 mailnews.smtp: C: DATA SmtpClient.jsm:577:19 mailnews.smtp: S: 354 OK
SmtpClient.jsm:411:17 mailnews.smtp: Sending 1003 bytes of payload SmtpClient.jsm:547:17 mailnews.smtp: S: 250 2.0.0 eG0ymPKN2njRfeG0ymgpkn mail accepted for delivery
SmtpClient.jsm:411:17 mailnews.smtp: Message sent successfully. SmtpClient.jsm:1245:21 mailnews.smtp: Closing connection... SmtpClient.jsm:151:17 mailnews.smtp: Idling while waiting for new connections... SmtpClient.jsm:1255:19 mailnews.smtp: Socket closed. SmtpClient.jsm:485:17 --- end log -----------------
That last log says it is working
mailnews.smtp: S: 250 2.0.0 eG0ymPKN2njRfeG0ymgpkn mail accepted for delivery
Those X.x.x numbers a server return codes. so the comcast server says it has accepted the mail for delivery, not Thunderbird.
Time to ask the folks at comcast to explain where your mail is going. But you might want to reverse the send, just to be sure sending from gmail to comcast works. I am thinking it will.