Milter spamfilterN config file

When using Milter, a    MTA option might be set as  msconfig&#x3e; set mta.spamfilter4_config_file IMTA_TABLE:milter.dat With milter (supported as of MS 6.3), the file that a    MTA option names may contain the following options:



 (integer). (New in 8.0) This option provides  a separate timeout for the initial milter connection separate from the timeout   waiting for milter responses. If this option is not set, it  defaults to the value set for the   option. A non-positive setting for,    whether explicitly set or   inherited from  , will result in using a      value of. 

 (integer; default is 1). (New in 8.0.1) The milter interface  expresses header modification actions in terms of offsets, e.g., "delete the   third occurrence of the Authentication-results: header field" or "replace the   value of the first occurrence of the DKIM-Signature: field with ...". For the  most part these actions have obvious analogues in Sieve using the index extension. However, when multiple milters acting in parallel modify the same header field it&#x27;s possible  for the changes to overlap and produce anomalous results. This can be ameliorated by  converting offsets into references to the header field&#x27;s value, something the   Sieve editheader extension also supports. The  option   controls whether or not milter header modification actions are translated from   offsets into value references. A non-zero value (the default) enables this  translation; a zero value disables it. 

 (integer; default is 0). Non-zero values enable   increasingly higher levels of debug output: a value of 1 enables basic   debugging; a value of 2 enables, for instance, hex dumps of the milter     responses; a value of 3 is also meaningful, enabling output of the octets    of the milter responseand as of the 8.0 release, additional other debug output such as debugging of use of the    mapping table. 

 (integer; default is 0). (New in MS 8.0.1) Normally  messages are transferred to the milter server as they are presented to the   MTA. Setting  to a non-zero value   defers the transfer until after the preceding spamfilter plugin has completed   its actions, at which point the message header and body are transferred to   the milter server from the MTA&#x27;s internal storage areas. Normally this  option is used in conjunction with setting the     option on a previous milter spamfilter plugin, which results in the modifications   made by the previous milter being visible to the current milter. 

 (hostname or IP address). Specify a host running a Milter server. A value must be specified for this option; (its presence is required). 

 (0 or 1; default is 0). (New in 8.0.2, and for  new in a patch to MS 7.0.5) When set to 0 (the default), message body material is not sent as part of the milter BODYEOB (body end of body) command. Setting this option to 1 allows message body material to be sent with the BODYEOB command, which while legal per the milter specifications and more efficient, may cause trouble with milters such as Proofpoint&#x27;s milter. 

 (0 or 1; default is 0). (New in 8.0.1.3.) Setting this option to 1 disables SSL/TLS certificate checking. This option is only meaningful if the  option is set to 1. 

 (integer, default 0). (New in MS 8.0.1) By default  the milter interface converts milter header modification actions to    Sieve actions. Setting this option to a non-zero value will cause the plugin  to modify the MTA&#x27;s internal copy of the message header directly; no Sieve   actions will be generated. IMPORTANT NOTE: This option should ONLY be used  with plugins enabled on the basis of the    source channel; use with   plugins enabled via    destination channels    will cause inconsistent results. Additionally, the 8.0.1 release of this   capability implements different semantics for multiple deletes with    different indices than would be obtained otherwise. These semantics   have been brought in line with normal milter operation as of MS 8.0.2.2. </li>

 (integer; default is 1) (New in 8.0) Specifies the smallest index value that can be passed to SMFI_INSHEADER by the milter server and cause the resulting header field to be inserted at the top of the header block rather than the bottom. </li>

 (0 or 1; default is 0). (New in 7.0.5.33) Setting this option to 1 enables availability of Oracle&#x27;s  milter extension SMFIF_SPECRCPT  for per-recipient modification actions. </li>

 (0 or 1; default is 1) (New in Messaging  Server 7.0.5)   Preserve line breaks (line folding) in header lines during processing. </li>

 (integer). Specify the port on which the Milter server is listening. A value must be specified for this option; (its presence is required). </li>

 (string; default is " "). (New in 8.0.1.) This option specifies the Sieve action to use when a milter  quarantine message modifier  (SMFIF_QUARANTINE) is engaged. For example:  Milter quarantine actions always have an associated "reason" string. A  can be used to substitute this string into the Sieve action. For example:  A literal dollar sign in the Sieve action string must be doubled, e.g.,. The default action that is performed if   is not set is " ". </li>

 (integer). (New in 8.0.2.3) This option&#x27;s value is used instead of the  value when a message is undergoing reprocessing. This allows a longer timeout to be used in the case where there&#x27;s no protocol session and thus no need for quick completion. If this option is not set, it defaults to the value set for the  option. A non-positive setting for,  whether explicitly set or inherited from  , will result in using a    value of. </li>

 (integer). (New in 8.0.2.3) This option&#x27;s value is used instead of the  value when a message is undergoing reprocessing. This allows a longer timeout to be used in the case where there&#x27;s no protocol session and thus no need for quick completion. If this option is not set, it defaults to the value set for the  option. A non-positive setting for,  whether explicitly set or inherited from  , will result in using a    value of. </li>

 (integer; default is 0). Setting     enables    milter debugging conditionally: only if channel debugging enabled. (Such channel debugging might be enabled via       on the channel, or via the   flag in a     and    recipient      mapping table.) </li>

 (integer; default is 3600). Attempting to set a  non-positive value will result in a value of   being used. </li>

 (integer; default is 180). (New in 8.0) Time in session that a session is allowed to remain idle  and still be a candidate for reuse. </li>

 (integer; default is 3600). (New in 8.0)  Maximum time, in seconds, that a single session can be used. </li>

 (integer; default is 100). (New in 8.0) Number of transactions allowed in a single session. </li>

 (0 or 1; default 0). (New in 8.0.1.3.) Setting this option to 1 causes the NODELAY flag to be set at the TCP level on all milter connections. Note that the behavior of the milter protocol is highly dependent on what options are negotiated: One milter may require many round trips per message while another may only need one. As such, it isn&#x27;t clear that there&#x27;s an optimal setting for the NODELAY flag. </li>

 (0 or 1; default is 0). (New in Messaging Server 7.0 update 2.) If   this option is set to 1, then the   Sieve    " " action will be used instead of    " " if the milter calls for the message to    be discarded. The default value of 0 causes   " " to be used. </li>

 (0 or 1; default is 0). (New in 8.0) Setting this option to 1 enables use of the QUIT_NC milter command  so that sessions can be reused. This should only be set when the version of libmilter is recent enough to support the feature (Sendmail 8.14 or later). </li>

 (0 or 1; default is 0). (New in 8.0.1.3.) Setting this option to 1 enables use of SSL/TLS on the milter connection. Note that libmilter.so does not provide support for SSL/TLS so a proxy/tunnel server such as stunnel must be placed in front of most milters before this option can be used. </li>

</ul>

As of 8.0, support for milter connections via Socks has been removed, so the,  ,   , and   milter options are no longer supported.

Some complex modifications of the milter spam filter plugin&#x27;s behavior may be achieved using the  mapping table.

Note that when using a Milter, the only relevant     options are      (which has a proper default value) and     ; the      and      MTA options used with other sorts of spam/virus filter packages are not relevant with a Milter. And it is essential with Milter to also explicitly set the    MTA option (to its   special-for-Milters value of  ) as the default value for     is not appropriate for Milter use.

See also:
 * slave_debug Option
 * FROM_ACCESS mapping table
 * Recipient access mapping tables
 * Sieve editheader extension
 * Sieve discard and jettison actions
 * MILTER_ACTIONS mapping table
 * MILTER_MACROS mapping table
 * Milter implementation
 * Milter single recipient extension
 * Milter errors
 * spamfilter1_config_file MTA Option