Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Unable to send emails via Outlook365 SMTP oAUTH2 settings

  • 8 replies
  • 1 has this problem
  • 1 view
  • Last reply by Matt

more options

Hello,

I am having issues with all my microsoft accounts and thunderbird on windows 10. (all my accounts use 2FA)

Currently using a @gmail.com, @live.com, @live.com.au and @unisa.edu.au These accounts all use office 365 for email exchange, except for the gmail one.

I am able to recieve emails via IMAP with no issues on all accounts. However recently all but my gmail smtp stopped working and Im now unable to send any email. error reported is a timeout to the server. I have checked the SMTP and IMAP settings in the exhange itself and confirm they are the same.

Im at a loss and unable to solve this,

Any assistance would be greatly appreciated

Hello, I am having issues with all my microsoft accounts and thunderbird on windows 10. (all my accounts use 2FA) Currently using a @gmail.com, @live.com, @live.com.au and @unisa.edu.au These accounts all use office 365 for email exchange, except for the gmail one. I am able to recieve emails via IMAP with no issues on all accounts. However recently all but my gmail smtp stopped working and Im now unable to send any email. error reported is a timeout to the server. I have checked the SMTP and IMAP settings in the exhange itself and confirm they are the same. Im at a loss and unable to solve this, Any assistance would be greatly appreciated
Attached screenshots

Chosen solution

There have been changes in oauth in Thunderbird and Microsoft's implementation of acceptable authentication methods in recent times.

I suggest you create a new profile in Thunderbird and set up one of your accounts there and try and send using that. If it works then the Thunderbird authentication changes are the issue and "can" be fixed by a lot of fiddling in the config editor but if at all possible just add all your accounts to the new profile as the things to be deleted are rather simple and at the same time complex to determine. A bit like some of the windows register changes that can be manually implemented.

Read this answer in context 👍 1

All Replies (8)

more options

Using thunderbird 115.2.0(64bit)

more options

State the antivirus, VPN (if used), especially if it is not Windows Security, e.g. Avast, AVG etc.

more options

Antivirus is mcafee; no vpn enabled. Its a very simple setup

Modified by seifer69er

more options

McAfee might be (probably is) the cause. Try disabling any option in McAfee that scans the TB profile folder or scans secure connections. The best way to test its effect is to run Windows in safe mode, then see if sending works.

more options

sfhowes said

McAfee might be (probably is) the cause. Try disabling any option in McAfee that scans the TB profile folder or scans secure connections. The best way to test its effect is to run Windows in safe mode, then see if sending works.

Thankyou for the suggestion, I have uninstalled Mcafee and restarted in safe mode with networking. There is no change in behaviour :(. sending via smtp still timesout

more options

Chosen Solution

There have been changes in oauth in Thunderbird and Microsoft's implementation of acceptable authentication methods in recent times.

I suggest you create a new profile in Thunderbird and set up one of your accounts there and try and send using that. If it works then the Thunderbird authentication changes are the issue and "can" be fixed by a lot of fiddling in the config editor but if at all possible just add all your accounts to the new profile as the things to be deleted are rather simple and at the same time complex to determine. A bit like some of the windows register changes that can be manually implemented.

more options

Matt said

There have been changes in oauth in Thunderbird and Microsoft's implementation of acceptable authentication methods in recent times. I suggest you create a new profile in Thunderbird and set up one of your accounts there and try and send using that. If it works then the Thunderbird authentication changes are the issue and "can" be fixed by a lot of fiddling in the config editor but if at all possible just add all your accounts to the new profile as the things to be deleted are rather simple and at the same time complex to determine. A bit like some of the windows register changes that can be manually implemented.

Very painful process, but it worked. Uninstalled Thunderbird, Deleted all thunderbird folders in appdata/local and appdata/roaming. reinstalled thunderbird, then added each account with the same settings again. They are all working except the uni one, but that may be a uni problem now :). Thankyou for your help

more options

seifer69er said

Matt said

There have been changes in oauth in Thunderbird and Microsoft's implementation of acceptable authentication methods in recent times. I suggest you create a new profile in Thunderbird and set up one of your accounts there and try and send using that. If it works then the Thunderbird authentication changes are the issue and "can" be fixed by a lot of fiddling in the config editor but if at all possible just add all your accounts to the new profile as the things to be deleted are rather simple and at the same time complex to determine. A bit like some of the windows register changes that can be manually implemented.

Very painful process, but it worked. Uninstalled Thunderbird, Deleted all thunderbird folders in appdata/local and appdata/roaming. reinstalled thunderbird, then added each account with the same settings again. They are all working except the uni one, but that may be a uni problem now :). Thankyou for your help

It got there, but creating is new profile to use is much simpler. You just go to the about:profiles in the troubleshooting information on the help menu and create one. No uninstalling removing or any of it.