When migrating to new version of Exchange Servers you must move your internal SMTP relay endpoints. This can be a challeging tasks as application owners mostly ignore your requests for such changes.
You can use the information provided in the receive connector log files to identify remote clients (MTAs / MTUs) connecting to the legacy infrastructure. The assumption is that protocol logging is enabled. You can easily active protocol logging across all receive connector fo a single server using the following EMS PowerShell one-liner:
Get-ReceiveConnector -Server EX01 | Set-ReceiveConnector -ProtocolLoggingLevel Verbose
The scripts searches the log files for the connection's EHLO response which containes the remote name or remote IP-address of the system connecting to the receive connector.
You can either search
For more information read the readme.md file at Github.
You need to adjust the log file path to suit your IT infrastructure. A next releas will contain a more automatic solution.
# Search legacy Exchange servers SMTP receive log files for the last 4 days and save search results in a single CSV file
.\Get-RemoteSmtpServers.ps1 -Servers SRV01,SRV02 -LegacyExchange -AddDays -4 -ToCsv
Exchange email adress policies are used to generate addresses since the early days of Exchange. Email address policies are used to automatically generate addresses for various protocols (SMTP, FAX, CCMAIL, MSMAIL). These overall use of address policies is well documented, but there is still some odd behaviour of the policies when it comes to language specific character handling.
The following list describes the common parameters:
All language specific characters and other non RFC 821/822 compliant characters are either translated or removed.
User without any language specific characters
Given Name: John
Last Name : Doe
Alias : JohnDoe
Email address policy results
%firstname.lastname@example.org = John.Doe@mcsmemail.de
%email@example.com = JohnDoe@mcsmemail.de
%firstname.lastname@example.org = J_Doe@mcsmemail.de
User with German language specific characters
Given Name: Michael
Last Name : Müller
Alias : Michael Mueller
%email@example.com = Michael.Mueller@mcsmemail.de
%firstname.lastname@example.org = Michael-Mueller@mcsmemail.de
%email@example.com = MiMueller@mcsmemail.de
User with Scottish language specific characters
Given Name: Ian
Last Name : O'Connell
Alias : IanOConnell
%firstname.lastname@example.org = Ian.O'Connell@mcsmemail.de
%email@example.com = IanOConnell@mcsmemail.de
%firstname.lastname@example.org = IanO'Con@mcsmemail.de
As you might have noticed, the apostrophe is not handled as a special character but an RFC compliant character. The address policy is applied without any issues at all.
But a SMTP address containing an apostrophe leads to email transport errors and must be removed.
You can use the replacement parameter to strip all apostrophes from the surname by using the following email address policy.
%email@example.com = Ian.OConnell@mcsmemail.de
This example will only remove apostrophes from the surname (%s) as the replacement parameter is placed in front of the surname parameter.