Hexamail Nexus Administration Guide - Route - Action

Action

Action

   Recipients

Send to
Specify a default routing address to send all email that matches the route (but not necessarily any sub-rules) to this new address. Leave this setting blank to retain the original recipient(s) on the email if no rules are matched. This address can be used to change the address using specific tokens: Use <rcptlocalpart> in the email address to have any local part of the matched original route recipient email address inserted into the new recipient email address. For example if the original recipient was someuser@somedomain.com and you want to route to someuser@newdomain.com you can specify <rcptlocalpart>@newdomain.com as the route destination address Use <rcptdomain> in the email address to have any domain part of the matched original route recipient email address inserted into the new recipient email address. For example if the original recipient was someuser@somedomain.com and you want to route to alert_somedomain.com@myserver.com you can specify alert_<rcptdomain>@myserver.com as the route destination address Use <phonenumber> in the email address to have any phone number from the matched original route recipient email address inserted into the new recipient email address. For example if the original recipient was 123456789fax@somedomain.com and you want to route to fax123456789@faxdomain.com you can specify fax<phonenumber>@faxdomain.com as the route destination address Use <number> in the email address to have any number from the matched original route recipient email address inserted into the new recipient email address. For example if the original recipient was user1234@somedomain.com and you want to route to newuser1234@newdomain.com you can specify newuser<number>@newdomain.com as the route destination address
Example interface
BCC new recipients
New recipients can be added as hidden recipients, equivalent to BCC when sending an email from a mail client. Any removed recipients will still be removed from the To: field unless you have checked the Retain original To information checkbox.
Example interface
On/Off
Retain To field
The original MIME To: field will be retained, so that the email looks unmodified, but new recipients may be added as per the rules configured. New recipients are added as BCC recipients and none are removed from the To header field
Example interface
On/Off
Copy to original recipient(s)
Also deliver to the original recipient(s) of the email
Example interface
On/Off
Return
Return to sender
Example interface
On/Off
Force From
From address to use for email
Example interface
Force Reply-To
Address to use for rply-to
Example interface
Change Message-ID
Change the email MIME Message-Id
Example interface
On/Off

   Server

Force Server Switch
Force any email that matches the route to be sent through the specific server
Example interface
On/Off
Email Server
You can force email that match a route to be sent via a particular server. The server specified here will override any 'internal mail server' or 'smart host' configured in the SMTP Relay module, and email matching the route will ALWAYS be delivered to the specified host and port.
Example interface