Avatar for Username

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

This thread was archived. Please ask a new question if you need help.

Login to server smtp.office365.com with username failed

  • 1 reply
  • 0 have this problem
  • 4 views
  • Last reply by sfhowes

manoj dubey
manoj dubey
more options

All the settings for both incoming and outgoing servers are correct. I can receive emails but cannot send any from Tbird. I keep getting an error message that says "Login to server smtp.office365.com with username failed". Additionally, the SEND folder is not visible in my email folders. I have confirmed that the outgoing server information in the account settings is correct, please see the screen shots.

Server Name - smtp.office365.com Port-587 Connection Security- STARTTLS Authentication method - OAUTH2 Username: my full email ID

Please can you help how can I resolve this error, thanks.

All the settings for both incoming and outgoing servers are correct. I can receive emails but cannot send any from Tbird. I keep getting an error message that says "Login to server smtp.office365.com with username failed". Additionally, the SEND folder is not visible in my email folders. I have confirmed that the outgoing server information in the account settings is correct, please see the screen shots. Server Name - smtp.office365.com Port-587 Connection Security- STARTTLS Authentication method - OAUTH2 Username: my full email ID Please can you help how can I resolve this error, thanks.
Attached screenshots

All Replies (1)

sfhowes
sfhowes
  • Top 10 Contributor
more options

You shouldn't see the 2nd picture with the password prompt if the authentication is OAuth2, but there might be an obsolete password in Saved Passwords. Remove all entries for the account in Settings/Privacy & Security, Saved Passwords, restart TB, enter the account password in the OAuth window to allow access. Check that the incoming authentication is also OAuth2.