IronPort - advanced configuration guide

Chapter 6 Using Message Filters to Enforce Email Policies
Examples
OL-25137-01
For example, Alice signs a message with her two certificates. Bob signs the message with his single
certificate. All certificates are issued by a single corporate authority. After the message passes the
S/MIME scan, the extracted data contain three items:
[
]
{
},
{
},
{
}
'issuer': 'CN=Auth,O=Example\, Inc.',
'signer': ['alice@example.com', 'al@private.example.com']
'issuer': 'CN=Auth,O=Example\, Inc.',
'signer': ['alice@example.com', 'al@private.example.com']
'issuer': 'CN=Auth,O=Example\, Inc.',
'signer': ['bob@example.com', 'bob@private.example.com']
The $CertificateSigners variable expands to:
"alice@example.com, al@private.example.com, bob@example.com, bob@private.example.com"
The following example inserts a new header if the certificate issuer is from the US:
Issuer: if signed-certificate("issuer") == "(?i)C=US" {
}
insert-header("X-Test", "US issuer");
The following example notifies an administrator if the signer is not from example.com:
NotOurSigners: if signed-certificate("signer") AND
signed-certificate("signer") != "example\\.com$" {
Cisco IronPort AsyncOS 7.6 for Email Advanced Configuration Guide
6-41