Mail does not arrive at destination - also impossible to mail to myself
I noticed yesterday that when I tried to send a mail to myself that it did not arrive in the Inbox of either Thunderbird or that of the Inbox of the webmail of my ISP which is Proximus in Belgium. The mail is correctly copied to the sent folder where it can be viewed without a problem. There are no visible error messages displayed.
I use two identities and it is my identity, which is the default one, that has the problems. My wife’s identity-address can still mail to itself without problems. I have contacted a few regular recipients and they mention that the last mail from my address was around 10 days ago. Mails destined for them have been sent since then but have not reached their destination …
I have tried the Troubleshoot mode and clearing the cache without success in sending a mail to the same default identity-sending address.
I use Bitdefender Total security and the firewall allows access to thunderbird.exe regularly. Details of the Thunderbird release, the SMTP server and add-ons are shown in the screen prints attached.
Other suggestions ?
Thanks in advance Peter
All Replies (15)
It looks like you have two smtp servers, yet just one incoming server. Am I misreading that? If there are two accounts, there should be four accounts, two input and two output. Please show screenprint for your incoming and smtp servers and also those for your wife. I think that may resolve the issue.
Hello David,
Thanks for your reply.
Attached are the screen prints.
Both identities use the same SMTP server - relay.proximus.be -> this is the only value defined as you'll see from image 0 - SMTP server values.
The user name is the same for both identities and that in the IMAP server values.
I'm going to take a look at setting up a detailed logging, which I saw recommended elsewhere when experiencing such mail transmission problems :
https://bugzilla.mozilla.org/show_bug.cgi?id=1726106#c1
Peter
If both smtp servers have the same name, how do you specify which to use for each account? It appears that, although there are two smtp servers defined, only one is used? And maybe I'm just confusing myself.
You begin to confuse me now ... 8-))
You talk about accounts ... I talk about identities .... and I have only 1 account ...
take a look here : https://kb.mozillazine.org/Multiple_identities_per_e-mail_account
Problems only became apparent last weekend - last week on 18 Feb I was upgraded automatically to the latest version of Thunderbird ... maybe something went amiss during the upgrade... who knows ...
Puzzling. Does Proximus allow aliases? If you have just one account, then the identity needs to be legitimate to an outside source. That is, if i send an email to xyz@proximus.be, then that 'xyz' identity must have been predefined at the proximus host so it knows where to send the message. Otherwise, the address does not exist and no mail is delivered.
Yes Proximus does allow aliases - my wife's address is defined elsewhere in "My Proximus"
Proximus have asked me to remove my account/email address and then reconfigure the smtp server ...
this means a lot of work --> backup, transfer to local folders and lots of other trickery ... I told them that I wasn't too keen to do it ... unless you know a good alternative with less hard work required
which version of Thunderbird are you on ?
have to go now ... talk again in morning
I think change the name of one of the SMTP accounts. Then check which is being used for which identity.
The next step is try sending from a completely different domain. I have no idea about this proximus, but most providers requires the user credentials used in the SMTP to match the sending account, or one authorized on their server. Further generally there is a trend to not delivering or not sending mail that is from the receiving account (something about spam is generally given as the reason). Google for example hide mail you submit from the delivery account, they assume if you sent it you have already read it. So it only appears in the all mail folder.
Hello Matt - thanks for replying
Not sure what you mean by smtp account ... server ?? Or sending from another domain ...
yes, user credentials match sending account - my case
Proximus doesn't "hide" any mail that should be delivered
Th. crashed just before moving up to version 108.2.0 - not sure if any incidence on this issue here ...
I am no guru for aliases, but my understanding is that they are not always legitimate for smtp servers. You may need to verify with email host that alias can be used for smtp server. If it cannot, then you just need one smtp server, not two.
David - it has been working fine with these settings since 2017.
It's only the last 7-10 days that there is an issue and mails don't reach their destination.
Below a couple of logs from Thunderbird :
To VVVV mailnews.smtp: Sending message <328a14dd-272f-c607-4529-58dd6661f0f0@skynet.be> SmtpService.jsm:85:18 mailnews.smtp: Connecting to smtp://relay.proximus.be:587 SmtpClient.jsm:119:17 mailnews.smtp: Connected SmtpClient.jsm:387:17 mailnews.smtp: S: 220-smtp.skynet.be ESMTP
220 Belgacom relay service - authentication required!
SmtpClient.jsm:413:17 mailnews.smtp: C: EHLO [192.168.1.44] SmtpClient.jsm:590:19 mailnews.smtp: S: 250-smtp.skynet.be
250-8BITMIME
250-SIZE 26214400
250 STARTTLS
SmtpClient.jsm:413:17 mailnews.smtp: C: STARTTLS SmtpClient.jsm:590:19 mailnews.smtp: S: 220 Go ahead with TLS
SmtpClient.jsm:413:17 mailnews.smtp: C: EHLO [192.168.1.44] SmtpClient.jsm:590:19 mailnews.smtp: S: 250-smtp.skynet.be
250-8BITMIME
250-SIZE 26214400
250-AUTH PLAIN LOGIN
250 AUTH=PLAIN LOGIN
SmtpClient.jsm:413:17 mailnews.smtp: Possible auth methods: PLAIN,LOGIN SmtpClient.jsm:876:17 mailnews.smtp: Current auth method: PLAIN SmtpClient.jsm:628:17 mailnews.smtp: Authentication via AUTH PLAIN SmtpClient.jsm:643:21 mailnews.smtp: C: Logging suppressed (it probably contained auth information) SmtpClient.jsm:586:19 mailnews.smtp: S: 235 #2.0.0 OK Authenticated
SmtpClient.jsm:413:17 mailnews.smtp: Authentication successful. SmtpClient.jsm:1101:17 mailnews.smtp: C: MAIL FROM:<aaa.bbb@skynet.be> BODY=8BITMIME SIZE=974 SmtpClient.jsm:590:19 mailnews.smtp: S: 250 sender <aaa.bbb@skynet.be> ok
SmtpClient.jsm:413:17 mailnews.smtp: MAIL FROM successful, proceeding with 1 recipients SmtpClient.jsm:1135:17 mailnews.smtp: Adding recipient... SmtpClient.jsm:1140:17 mailnews.smtp: C: RCPT TO:<ddd.eee@yahoo.com> SmtpClient.jsm:590:19 mailnews.smtp: S: 250 recipient <ddd.eee@yahoo.com> ok
SmtpClient.jsm:413:17 mailnews.smtp: RCPT TO done, proceeding with payload SmtpClient.jsm:1200:19 mailnews.smtp: C: DATA SmtpClient.jsm:590:19 mailnews.smtp: S: 354 go ahead
SmtpClient.jsm:413:17 mailnews.smtp: Sending 974 bytes of payload SmtpClient.jsm:560:17 mailnews.smtp: S: 250 ok: Message 24110932 accepted
SmtpClient.jsm:413:17 mailnews.smtp: Message sent successfully. SmtpClient.jsm:1259:21 mailnews.smtp: C: QUIT SmtpClient.jsm:590:19 mailnews.smtp: Socket closed. SmtpClient.jsm:498:17 mailnews.smtp: S: 221 smtp.skynet.be
SmtpClient.jsm:413:17 mailnews.smtp: Closing connection... SmtpClient.jsm:153:17
To OOOO
mailnews.smtp: Sending message <6109789a-ae4d-ccb6-17ae-6199bc96a1a2@skynet.be> SmtpService.jsm:85:18
mailnews.smtp: Connecting to smtp://relay.proximus.be:587 SmtpClient.jsm:119:17
mailnews.smtp: Connected SmtpClient.jsm:387:17
mailnews.smtp: S: 220-smtp.skynet.be ESMTP
220 Belgacom relay service - authentication required!
SmtpClient.jsm:413:17 mailnews.smtp: C: EHLO [192.168.1.44] SmtpClient.jsm:590:19 mailnews.smtp: S: 250-smtp.skynet.be
250-8BITMIME
250-SIZE 26214400
250 STARTTLS
SmtpClient.jsm:413:17 mailnews.smtp: C: STARTTLS SmtpClient.jsm:590:19 mailnews.smtp: S: 220 Go ahead with TLS
SmtpClient.jsm:413:17 mailnews.smtp: C: EHLO [192.168.1.44] SmtpClient.jsm:590:19 mailnews.smtp: S: 250-smtp.skynet.be
250-8BITMIME
250-SIZE 26214400
250-AUTH PLAIN LOGIN
250 AUTH=PLAIN LOGIN
SmtpClient.jsm:413:17 mailnews.smtp: Possible auth methods: PLAIN,LOGIN SmtpClient.jsm:876:17 mailnews.smtp: Current auth method: PLAIN SmtpClient.jsm:628:17 mailnews.smtp: Authentication via AUTH PLAIN SmtpClient.jsm:643:21 mailnews.smtp: C: Logging suppressed (it probably contained auth information) SmtpClient.jsm:586:19 mailnews.smtp: S: 235 #2.0.0 OK Authenticated
SmtpClient.jsm:413:17 mailnews.smtp: Authentication successful. SmtpClient.jsm:1101:17 mailnews.smtp: C: MAIL FROM:<aaa.bbb@skynet.be> BODY=8BITMIME SIZE=1066 SmtpClient.jsm:590:19 mailnews.smtp: S: 250 sender <aaa.bbb@skynet.be> ok
SmtpClient.jsm:413:17 mailnews.smtp: MAIL FROM successful, proceeding with 1 recipients SmtpClient.jsm:1135:17 mailnews.smtp: Adding recipient... SmtpClient.jsm:1140:17 mailnews.smtp: C: RCPT TO:<ooooo@xxxxxx.be> SmtpClient.jsm:590:19 mailnews.smtp: S: 250 recipient <ooooo@xxxxxx.be> ok
SmtpClient.jsm:413:17 mailnews.smtp: RCPT TO done, proceeding with payload SmtpClient.jsm:1200:19 mailnews.smtp: C: DATA SmtpClient.jsm:590:19 mailnews.smtp: S: 354 go ahead
SmtpClient.jsm:413:17 mailnews.smtp: Sending 1066 bytes of payload SmtpClient.jsm:560:17 mailnews.smtp: S: 250 ok: Message 24111035 accepted
SmtpClient.jsm:413:17 mailnews.smtp: Message sent successfully. SmtpClient.jsm:1259:21 mailnews.smtp: C: QUIT SmtpClient.jsm:590:19 mailnews.smtp: S: 221 smtp.skynet.be
SmtpClient.jsm:413:17 mailnews.smtp: Closing connection...
OK, I can't argue that. Have you tried sending to someone else, such as your wife? Have you tried with Bitdefender off? I'm almost at a full loss in this.
I have some detailed logs of the IMAP communications - how can I find someone on the development side to take a look at them.
Thanks for any help Peter
If you place them on a cloud drive and send me the link, I will have a look at them.