Return Home
Overview
<attach>
<body>
<body>
<clientip>
<comment>
<configuration>
<copy>
<delay>
<dnslookup>
<domainquery>
<email>
<expression>
<expressions>
<file>
<filter>
<filters>
<header>
<header>
<helo>
<http>
<imap>
<index>
<inputpath>
<ipquery>
<log>
<mailfrom>
<maxbuffer>
<maxlines>
<message>
<modifysource>
<multiplerecipients>
<option>
<parser>
<path>
<quickresult>
<rcptto>
<result>
<results>
<return>
<rule>
<rules>
<scope>
<select>
<smtpextendedstatuscode>
<smtpstatuscode>
<target_filter>
<target_index>
<test>
<title>
Boolean type
Macros
Regular Expressions
Node: index
<index name="index_name">
[target1]
[target2]
.
.
.
[targetN]
</index>
Attributes:
name
name used in target nodes to identify selection on this index; does not need to be present on the root index node
Notes
The index identifies the filter applicable to a specific email based on a hierarchical series of tests that can include the recipient domain, recipient mailbox and SMTP client IP address. It is processed sequentially until a match returning the filter type required for email processing is found.
If no matching filter is found, the email is not processed.
Avoid situations where no filter is found for processing an email. You should define a default filter that properly contains a result return codes for the SMTP mail server to pass the email. Refer to the sample configuration files and the filter "pass_everything" for an example.
If the content filter is running when the XML file containing the index is changed, the index and all associated filters will be reloaded when the next email is processed. This operation can safely occur asynchronously with any email processing in progress.