Cisco Cisco Email Security Appliance C190 Guida Utente

Pagina di 570
6-351
Cisco IronPort AsyncOS 7.3 for Email Advanced Configuration Guide
OL-23081-01
Chapter 6      Using Message Filters to Enforce Email Policies
The filter performs matches loosely. It is not case-sensitive. If the optional 
sieve-char parameter is supplied, the last portion of an address that follows the 
specified character will be ignored for the purposes of comparison. For example, 
if the 
+
 character is included as a parameter, the filter ignores the portion of the 
address 
joe+folder@example.com
 that follows the 
+
 character. If the address was 
joe+smith+folder@example.com
, only the 
+folder
 portion is ignored. If the 
SMTP authenticated user ID string is a simple username and not a fully-qualified 
e-mail address, only the username portion of the target will be examined to 
determine a match. The domain must be verified in a separate rule.
Also, you can use the $SMTPAuthID variable to insert the STMP authenticated 
user ID into headers.
The following table shows examples of comparisons between the SMTP 
authenticated ID and email addresses and whether they would match using the 
smtp-auth-id-matches 
filter rule:
*Any
Matches messages that were 
created during an authenticated 
SMTP session regardless of 
identity. 
*None
Matches messages that were not 
created during an authenticated 
SMTP session. This is useful 
when authentication is optional 
(preferred).
Target
Description
SMTP Auth ID
Sieve Char
Comparison Address
Matches?
someuser
otheruser@example.com
No
someuser
someuser@example.com
Yes
someuser
someuser@another.com
Yes
SomeUser
someuser@example.com
Yes
someuser
someuser+folder@example.com
No
someuser
+
someuser+folder@example.com
Yes
someuser@example.com
someuser@forged.com
No