Configuring preferences and options in Outlook.com
SMTP is available for Outlook.com / Microsoft 365 consumer mailboxes, including new accounts, but it can be disabled at the service side. The error message “SmtpClientAuthentication is disabled for the Mailbox” indicates that SMTP AUTH is currently disabled for that mailbox or tenant, not that the Microsoft 365 Basic subscription type blocks SMTP.
For Exchange Online/Outlook.com mailboxes, SMTP can be disabled either:
- At the tenant level
- Check the current setting:
Get-TransportConfig | Select SmtpClientAuthenticationDisabled-
False= SMTP AUTH is not disabled tenant-wide. -
True= SMTP AUTH is disabled for the whole tenant.
-
- To enable SMTP AUTH tenant-wide:
Set-TransportConfig -SmtpClientAuthenticationDisabled $False
- Check the current setting:
- At the mailbox level
- Check the mailbox setting:
Get-EXOCasMailbox <mailbox account> -Properties SmtpClientAuthenticationDisabled | Select SmtpClientAuthenticationDisabled- Blank = mailbox follows the tenant-level setting.
-
False= SMTP AUTH is enabled for this mailbox (overrides tenant setting). -
True= SMTP AUTH is disabled for this mailbox.
- To enable SMTP AUTH for a specific mailbox:
Set-CasMailbox <mailbox account> -SmtpClientAuthenticationDisabled $False
- Check the mailbox setting:
If SMTP AUTH is disabled at either level, OAuth-capable clients such as K-9 will fail to send mail via SMTP even though IMAP/POP with OAuth works.
If direct PowerShell access to the tenant is not available (for example, for a purely consumer Outlook.com account), this needs to be corrected by Microsoft on the service side; in that case, contact Outlook.com/Microsoft 365 consumer support and provide the exact error text so they can re-enable SMTP AUTH for the mailbox.
Note that Basic authentication is being deprecated across Outlook.com and Exchange Online. For POP/IMAP/SMTP, OAuth 2.0 is supported and should be used, as in the K-9 configuration.
References: