Address Alterations policies can be used to modify email addresses as inbound or outbound messages are processed for delivery. This can be configured for addresses based on the:
- Sender or recipient email address
- Header or envelope information
There are many reasons why you may require either inbound or outbound addresses to be rewritten. For example:
- A company merger where all emails going to acquired company now need to be rewritten to the new company domain.
- Your organization has a requirement to modify address information based on mail flow. For example, all inbound emails destined for "email@example.com" needs to be delivered to "firstname.lastname@example.org".
- When any sender from a Support Desk group sends an outbound email, the origination address appears to be sent from the "email@example.com" address.
- When searching the archive, you must search for the address specified in the "New Address" field of the Address Alteration Definition. The search is unable to find the "Old Address".
- As a cloud service, Mimecast cannot affect internal emails routed in the organization's infrastructure.
- Address alteration policies should only be used if the address alterations are required to be applied to certain routes of traffic.
- If the address alteration is specifically for the recipient address, the email address is rewritten with the message delivered to the new address only.
What You'll Need
- An Administrator Console logon with access to the Administration | Gateway | Policies menu item.
- A previously configured Address Alterations Policy Definition.
Creating a Policy
To create a policy, follow the instructions in the Creating / Changing a Policy article, but using the following options:
|Policy Narrative||Provide a description for the Policy to allow you to easily identify it in the future.|
|Select Address Alteration Set|
Use the Lookup button to select the required Address Alteration definition for the policy.