Case In Point
My last post on this topic I said that I would provide some examples in order to help you more completely understand how Sentrion’s policy engine can add value within an organization’s SMTP application relaying infrastructure. Here’s my first example:
One of Sendmail’s large financial customers had the following requirement: certain internal applications can not directly route email messages to any of their traders. Apparently, information generated by the internal applications could create a conflict of interest and was therefore disallowed by corporate policy.
Sendmail’s recommendation to address the requirement was to integrate several Sentrion MP Appliances in front of the internal application servers. Next, Sendmail configured an Sentrion policy to perform a lookup into the organization’s in-house LDAP directory in real time to see if the message recipient was a trader. If the recipient check determined that the message was destined for a trader, the following actions (all carried out by the Sentrion policy engine) occurred:
- The message was discarded.
- An alert email message was sent to the person responsible for managing the internal application.
- Another alert was sent to the trader’s manager. The address of the trader’s manager was captured during the initial LDAP lookup.
- A custom log message was placed in Sendmail’s syslog file.
- A policy counter was incremented. Policy counters can be utilized to quickly produce reports detailing how many times a specific MM policy was triggered.
In my next post I will provide some further examples – and I promise not to wait so long to make that post!