Avatar for Username

Przeszukaj pomoc

Unikaj oszustw związanych z pomocą.Nigdy nie będziemy prosić Cię o dzwonienie na numer telefonu, wysyłanie SMS-ów ani o udostępnianie danych osobowych. Zgłoś podejrzaną aktywność, korzystając z opcji „Zgłoś nadużycie”.

Więcej informacji

Wątek został zarchiwizowany. Jeśli potrzebujesz pomocy, zadaj nowe pytanie.

Unable to send any email on any of the three Accounts working proir to problem.

  • 1 odpowiedź
  • 1 osoba ma ten problem
  • 1 wyświetlenie
  • Ostatnia odpowiedź od Matt

wildpossum
wildpossum
more options

Running Thunderbird release 52.1.1 (64 bit) on GNU/Linux Kernel 4.4.0-78-generic #99-Ubuntu SMP x86_64. Previous Thunderbird releases did not create any send problems, and my SMTP's have been very stable for the last 24 months. There are no crash-reports generated, and I have followed the tips given else where in the support section to try to resolve my problem.

Usually, once a email is composed - you depress "send", auto spelling takes place and once OK, that particular email is sent. Unfortunately there is no "holding folder" so as to ascertain when the message actually is dispatched. i.e.: email travels from "composing" folder to a waiting "dispatch" folder then finally to the "sent" folder of completion.

I had noticed two strange slow takes happening several months before my problem (may be related or not - unsure). Firstly, saving a small email to "Sent" box or "Drafts" became really slow (order of tens of seconds). Lastly, Thunderbird Activity Manager does not show any activity at all once the "Send" button is depressed - Moreover there is some type of disk activity each time "Send" is depressed - I can hear it.

I agree that the problem appears to be SMTP related. I have tested email sending after turning off firewall, VPN and email options like encryption without any luck. I totally deinstalled Thunderbird from my system (especially the /home/user/.thunderbird tree). Installed the latest copy via apt-get. As expected the fault does not reappear - checked all the SMTP servers and passwords etc. all OK.

Any further ideas ?

Running Thunderbird release 52.1.1 (64 bit) on GNU/Linux Kernel 4.4.0-78-generic #99-Ubuntu SMP x86_64. Previous Thunderbird releases did not create any send problems, and my SMTP's have been very stable for the last 24 months. There are no crash-reports generated, and I have followed the tips given else where in the support section to try to resolve my problem. Usually, once a email is composed - you depress "send", auto spelling takes place and once OK, that particular email is sent. Unfortunately there is no "holding folder" so as to ascertain when the message actually is dispatched. i.e.: email travels from "composing" folder to a waiting "dispatch" folder then finally to the "sent" folder of completion. I had noticed two strange slow takes happening several months before my problem (may be related or not - unsure). Firstly, saving a small email to "Sent" box or "Drafts" became really slow (order of tens of seconds). Lastly, Thunderbird Activity Manager does not show any activity at all once the "Send" button is depressed - Moreover there is some type of disk activity each time "Send" is depressed - I can hear it. I agree that the problem appears to be SMTP related. I have tested email sending after turning off firewall, VPN and email options like encryption without any luck. I totally deinstalled Thunderbird from my system (especially the /home/user/.thunderbird tree). Installed the latest copy via apt-get. As expected the fault does not reappear - checked all the SMTP servers and passwords etc. all OK. Any further ideas ?

Wszystkie odpowiedzi (1)

Matt
Matt
  • Moderator
  • Top 10 Contributor
more options

You can force the use of an outbox by sending the mail later. (Ctrl+shift Enter)

Or go into offline mode.

My guess is an SSL or TLS issue with the authentication, but I would expect that to pop something into the error console.

open the througleshooting information from the Help menu and look at the account settings in both profiles (old troublesome and new) and see if one uses SSL and the other TLS or STARTTLS.