Additional notes

Support for multiple recipients

Customers leveraging Microsoft 365 alongside JEMHC may have an interest in utilizing Project Mappings. This feature enables JEMHC to efficiently direct emails to various projects via a centralized mailbox. The available options include:

Sub addresses

See https://learn.microsoft.com/en-us/exchange/recipients-in-exchange-online/plus-addressing-in-exchange-online for more information. Apparently this still only works with mailboxes, not for DL/group addresses.

Account aliases

Microsoft 365 business subscription users can set up aliases and send email using that alias. Seehttps://learn.microsoft.com/en-us/microsoft-365/admin/email/add-another-email-alias-for-a-user?view=o365-worldwide for more information. This feature was previously IDs 59437 and 64123 on the Microsoft 365 Roadmap | Microsoft 365.

Email Aliases in Microsoft 365 take 24 hours to become valid, prior to this they will be rejected (shown below).

Microsoft 365 Doesn't always retain the inbound Alias address

Microsoft 365 doesn't yet support the ‘Delivered-To’ header for Alias addresses (even when the mail is routed correctly, JEMHC has no way to determine what that Alias is, reliably).

Anecdotal comments from a customer using Microsoft 365:

… Exchange Online is writing the To: header differently based on if the message is sent internally or externally. Messages sent from inside our Exchange organization always get the primary SMTP address, while messages sent from external senders write the actual address.

Retaining in the incoming address in outbound mail

You may also want to retain the incoming address for use in all outbound notifications. The support for Aliases, as covered in the prior section is not not guaranteed, in such cases, all you get is the common primary mailbox address. We encourage

Microsoft 365 customers to engage with MS support on this topic.

JEMHC can store inbound address in a Custom Field default

  1. Storing the $catchemail (see end of : Setting a custom field value )

  2. Using the custom field during sending:Changing the from: address used (statically or from a Custom Field)