Closed Bug 1954633 Opened 1 month ago Closed 1 month ago

Failed authentication when connecting to Godaddy/outlook365 outgoing smtp server

Categories

(Thunderbird :: Untriaged, defect)

Thunderbird 128
defect

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: djholeman1, Unassigned)

Details

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:136.0) Gecko/20100101 Firefox/136.0

Steps to reproduce:

Attempted to send an email via an outlook365 smtp account that was properly configured both dynamically by tbird and manually as a troubleshooting measure. To be clear, the domain name for the account is branded, not vanilla outlook.com. I verified the outgoing server settings with godaddy.com and they matched the autoconfig settings which I replaced manually anyway. Deleting and readding the account does not fix the problem. Incoming mail works properly. I have three email accounts that are affected with the same problem.

Actual results:

Mail sending times out with a message that the username and password are not accepted. Popup prompts with enter new password link that then fails to popup a new password dialogue.

Expected results:

Handshake with the smtp server should have occurred silently and the email should have been accepted by the server.

Are you using the primary server side identity for sending (other identities will not work, IIRC)

Yes, though happy to provide the credentials via email on request. FWIW I changed the Thunderbird version to 136 and the problem still persists. Seems like maybe godaddy are blanket killing incoming Thunderbird mediated traffic. When I set up these accounts a couple months ago the automatic settings worked until they stopped working a few weeks ago.

Sure you can send me credentials for testing. Please mention the bug number in the subject.

(In reply to Don Holeman from comment #2)

Yes, though happy to provide the credentials via email on request. FWIW I changed the Thunderbird version to 136 and the problem still persists. Seems like maybe godaddy are blanket killing incoming Thunderbird mediated traffic. When I set up these accounts a couple months ago the automatic settings worked until they stopped working a few weeks ago.

You mention 'automatic' settings worked , but Thunderbird has no knowledge of what you have got set up as a 'primary' account in the Microsoft Account, so the SMTP for each account using office365 server would need to be set up manually. Which makes me wonder if you really do have settings set up correctly?
All accounts/email addresses in a Microsoft Account are considered 'alias' accounts. All accounts in a Microsoft Account ar supposed to use the same password as the 'Microsoft Account' password. In Microsoft account accessed via a browser, one of the 'alias' accounts will be set up as 'primary'.
In Thunderbird, all mail accounts who use the office365/outlook server (any email address considered as an alias) must all use the same smtp outgoing server which has the same username as whatever account is set up as primary in the Microsoft Account and is using same password as Microsoft Account. So no matter what the mail account email address, if it uses the the office365 server, all of those acounts only use the one account/email address for sending.

Also - as smtp is failing for everything - It's worth checking the error console to see if there is a 'disabled for the Tenant' error mesasge.

In Thunderbird
Tools > Developer Tools > Error Console
do you see a line like the following:
mailnews.smtp: Command failed: 535 Authentication unsuccessful, SmtpClientAuthentication is disabled for the Tenant. Visit https://aka.ms/smtp_auth_disabled for more information. [BL1PR13CA0131.namprd13.prod.outlook.com 2024-09-25T16:17:00.055Z 08DCDC7DB9525546]; currentAction=_actionAUTH_XOAUTH2 SmtpClient.sys.mjs:602:19

It means you do not have SMTP enabled.
The link mentioned in error console : https://aka.ms/smtp_auth_disabled
That link goes to this location - I specifically include the info on 'enable smtp':
https://learn.microsoft.com/en-us/exchange/clients-and-mobile-in-exchange-online/authenticated-client-smtp-submission#enable-smtp-auth-for-specific-mailboxes

Flags: needinfo?(djholeman1)

Thank you for clarifying what is meant by the primary account. This is the main problem then. As well, SMTP was not enabled at the admin interface and the instructions you linked to provided helped in that regard as well. Godaddy has a provision for enabling it in their email admin but its buried a bit. They have crippled the microsoft365 admin interface for their branded offerings but at least left this available.

Please close this bug - which turned out to not be a bug. Hopefully this discussion will help others in this situation.

Status: UNCONFIRMED → RESOLVED
Closed: 1 month ago
Flags: needinfo?(djholeman1)
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.