In case you are not following the EHLO blog, you might have missed an announcement made recently regarding some changes coming to SMTP authenticated submission in Exchange Online. In a nutshell:
- Sent email will now be stored in the Sent Items folder of the mailbox.
- Only three concurrent connections to our service per mailbox will be allowed. Additional connections will be rejected with the error: 4.3.2 STOREDRV.ClientSubmit; sender thread limit exceeded.
In addition to the changes mentioned above, another set of changes has been rolled out to the service, allowing us to control the SMTP authenticated submission protocol on the organizational or per-mailbox level. Here’s how to do this.
The organization-wide settings are controlled via the Set-TransportConfig cmdlet. To disable SMTP authenticated submission on the company level, use:
Set-TransportConfig -SmtpClientAuthenticationDisabled $true
To enable SMTP authenticated submission on the company level, use
Set-TransportConfig -SmtpClientAuthenticationDisabled $false
As the default value for this setting is $false, as in SMTP authenticated submission enabled, you don’t need to make any changes unless you want to disable it. To check the currently set value, use:
Get-TransportConfig | ft SmtpClientAuthenticationDisabled
To control SMTP authenticated submission on the per-mailbox level, use the Get-CASMailbox cmdlet. For example, to disable SMTP authenticated submission on a specific mailbox:
Set-CASMailbox mailboxname -SmtpClientAuthenticationDisabled $true
To enable SMTP authenticated submission , use:
Set-CASMailbox mailboxname -SmtpClientAuthenticationDisabled $false
To check the status of SMTP authenticated submission for particular user, use:
Get-CASMailbox mailboxname | ft SmtpClientAuthenticationDisabled