MapiMessage.Recipients.Add(...) - EX address validation too strict

My user’s data contains an EX address similar to:

/o=Contoso/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=Doe, John J.ab6

I want to add a message recipient with that address.

MapiMessage mapiMessage = new();
mapiMessage.Recipients.Add("/o=Contoso/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=Doe, John J.ab6", "EX", "John Doe", MapiRecipientType.MAPI_TO);

When I try to do that I get an ArgumentException with message, “The exchange address is not in a recognized format.”.

I think MapiRecipientCollection .Add(...) does not like the comma.

Since legacyExchangeDn can be created in Exchange with a comma, I think the address validation for address type “EX” in MapiRecipientCollection should allow it.

[PS] C:\windows\system32>New-Mailbox `
>>     -Name "Doe, John J." `
>>     -UserPrincipalName "john.j.doe@blah.blah" `
>>     -Alias "john.j.doe" `
>>     -Password (ConvertTo-SecureString "P@ssword!" -AsPlainText -Force)

[PS] C:\windows\system32>Get-Mailbox john.j.doe | Select LegacyExchangeDn | fl

Hello @weswt,

We will verify this behavior on our side and check whether the current validation is overly restrictive.

We’ll get back to you once we have an update.
Thank you for bringing this to our attention.