A routing policy determines if a message should be sent and notifies the sender and/or administrators of the disposition of the message. A routing policy has two delivery options for the original message: Send Per Policy or Do Not Send. The routing Recipients function allows the administrator to return messages to the sender and send copies to a defined administrative mailbox.
When a message matches a routing policy with Send per Policy specified, then it is sent to the intended recipients. ZixGateway also sends a copy of the message or a notification to each of the specified routing recipients. ZixGateway applies the pattern and action of Routing first. Then it executes Content, Branding, and/or Encryption actions for each of the policies matched by the message.
When a message matches a routing policy with Do Not Send specified, then it is not sent. If routing recipients have been defined for the policy, ZixGateway can send a copy of the message and/or a notification message to each of the routing recipients. Some examples of routing recipients are administrators, auditors, and the original sender. The routing recipient can not be the sender’s intended recipients.
There are three options for the Send Format of a routing message: return the original, do not return the original, and send original as an attachment. An explanation of why the message was or was not sent is inserted into the body of the routing message. Administrators can accept the default bounce message or create a custom message. The intended recipients are unaware of the existence of the original message.
You might use a Do Not Send policy when:
Routing polices for Send Per Policy can be used for administrative monitoring or auditing. For example, administrators may want to know about: