I'm having an e-mail issues after using Thunderbird for 10 years.
About 2 weeks ago, I started getting error messages on certain e-mails, whether I'm sending or replying.
It says: "An error occurred while sending mail. The mail server sent an incorrect greeting. Service not available".
I am on Suddenlink, and they dont know anything about Thunderbird. Here's the funny part: I can take the SAME e-mail that gets an error message and wont go through.... but make it go through without any problems if I use FORWARD. Every Forward will go though but not the original e-mail. How do you account for that? It HAS to do with the recent Thunderbird update! Please help because I'm getting real tired of forwarding my original e-mails.
Wybrane rozwiązanie
It might be a problem at Suddenlink's end, if it works with forwards but not direct sending:
https://support.mozilla.org/en-US/questions/1330295
Przeczytaj tę odpowiedź w całym kontekście 👍 0Wszystkie odpowiedzi (3)
Wybrane rozwiązanie
It might be a problem at Suddenlink's end, if it works with forwards but not direct sending:
I've been on the Net since 1996, but this is a new one on me. What could Thunderbird possibility be doing different than any other e-mail program where Suddenlink doesnt like it? Why do other e-mail programs work with Suddenlink but not Thunderbird? What changed? This just happened a couple of weeks ago after getting a Thunderbird update, and I still cant help but think that had something to do with it.
The main thing is, what is Suddenlink requiring that Thunderbird is not providing? Is there any way for Thunderbird to fix whatever it is that Suddenlink requires? AND, why do the Forwards work perfectly and sending doesnt? Can anyone answer that?
Thanks!
When problems arise after an update, with no other obvious changes, it's often due to a 3rd-party security/antivirus/firewall app that suddenly (no pun intended) becomes incompatible with TB, although it might still work with other mail apps or resume working with TB after the 3rd-party app is updated.
Running Windows in safe mode might point to some startup app as the source. But I don't know why forwards would be treated differently from normal sending.