Can't send email with Thunderbird after change to IMAP
I have my email with Godaddy, and after changing from pop to imap I can no longer send emails. I get a message saying the login to the account has failed. I have checked the password stored in Thunderbird and it is correct and also re-entering it does not work. I called Godaddy help and they confirmed my IMAP settings in Thunderbird are correct, (actually Thunderbird populated everything correctly when the change to IMAP was made). Godaddy help were no help, and did not seem at all interested in helping. I have attached images of the error messages and IMAP settings.
I am using Windows 10 and Thunderbird version 78.13.0
All Replies (12)
Hello there We have read your message. We try to help you.
Is this issue still there?
https://support.mozilla.org/en-US/kb/difference-between-imap-and-pop3
https://support.mozilla.org/en-US/kb/switch-pop-imap-account#w_delete-your-pop-account
Greetings Firefox volunteer.
Edeziri
yes, I can't send email, I get the error message: Login to server smtp.office365.com with username x@x.com failed
Edeziri
Hello there again.Moz.8
Yes the Smtp.office365.com is your server inlog name and your users name is xox@com. oké the message says it for itself some Smtp settings are not filled in correctly. Lets see if I can help you to fill out this input fields to have a working email program again.
Where to start with this issue is at the Smtp configuration.
Edeziri
In Thunderbird the settings are:
Server name: smtp.office365.com Port: 587 Authentication method: Normal password Connection security: STARTTLS
In Godaddy: IMAP setting Server name: outlook.office365.com Port: 993 Encryption method: TLS
SMTP setting Server name: smtp.office365.com Port: 587 Encryption method: STARTTLS
Hello there again.
I’ve have being search some documents for you.
Some issues are discribed in this one. Explanations about blocking the mail after updates. It also could have some info about the change of the pop method to imap in the documents I have sended you. Did you delete the complete pop account after switching?
Your Smtp settings looks fine. I will check them out if they are right this way.
Greetings Firefo volunteer.
Edeziri
Yes, I deleted the old pop account. The correct SMPT server is set. thanks
Hello there again.
Can you change your port number to 465? Look what happens? Both port numbers are usable for outgoing mail. Port 587 is the most coming port for traffic in 2021. Port 465 is alo a good choice to do the same.
Greetings Firefox volunteer.
Edeziri
Port 465 doesn't work either. If I change the server name it just hangs.
Hello there again.
I’ve got some documents about cannot sending email.can you read this form and contact me back after reading this?
ok, thanks
Hello there again Moz 8.
Some methods to check and solve your issue with no connection to the server can be solved by trying to following.
The next steps I will send them to you direct.
As following:
There I a way that your connection could contain spam but that’s not so serious.
Edeziri
Hello there again moz8.
Oké here we go try to follow me.
Try to put out your firewall and security setting for a while because it can block certain connections.look if it s gone and can use it now. We try to solve this Smtp server error for connection for outgoing mail ,sending mails.
Deleting the Smtp password will help sometimes to. Try the steps below.
Delete SMTP Password
An email sending problem can be solved by deleting and reconfiguring Thunderbird email account. :
Update Thunderbird email client to the latest edition Once it is done, try to send mail for checking the issue still persists or not If it is then, choose Tools >> click on Options From the Options wizard, choose on Security >> click on Password Now, delete SMTP password and configure account again. After that, try to send mail again and this can help to resolve Thunderbird email not sending problem. Once the mail is send then, you can reset your SMTP password if you want to be secured.
It says update to the latest version to solve some of this issue. It might perhaps already solve the whole issue.
Greetings Firefox volunteer
Edeziri