Event banner
Event details
It often seems that features implemented in M365 eventually show up in the on-premises version. Will this behavior end up sneaking in to Ex2019 or Ex2025? If so, PLEASE don't sneak it in. Admins, architects, and implementers need to know up front if on-premises versions of Exchange will receive this same feature.
Like I said, we don't just throttle or block right away. We notify you through Message Center posts. Then, we give you 30 days of reporting only in EAC.
In the event of throttling or blocking, e admin and/or end user will be notified of the reason their email was rejected, e.g.:
450 4.7.230 Connecting Exchange server version is out-of-date; connection to Exchange Online throttled for 5 mins/hr. For more information see https://aka.ms/BlockUnsafeExchange.
550 5.7.230 Connecting Exchange server version is out-of-date; connection to Exchange Online blocked for 10 mins/hr. For more information see https://aka.ms/BlockUnsafeExchange.
I get that not everyone has money to move, but that does not give them the right to put their recipients at risk by running a persistently vulnerable Exchange Server.
This behavior is a system built into Exchange Online. The transport enforcement system will not be put into Exchange Server, but it will be used for all versions of Exchange Server, including Exchange Server 2016, Exchange Server 2019, and the next version of Exchange Server that ships in 2025.
That said, we are looking into ways we can leverage things like the Outlook infobar and the Exchange admin center in the next version of Exchange Server to notify an admin/user that their Exchange Server is out of date. For the record, we don't "sneak things" into our product. Our customers require transparency, and we are very open about the code changes we make in Exchange.