SpamAssassin spamfilterN config file

When using SpamAssassin, a    MTA option might be set as  msconfig&#x3e; set mta.spamfilter1_config_file IMTA_TABLE:spamassassin.dat With SpamAssassin (supported as of MS 6.1), the file that this option names may contain the following options:



 DEBUG (0 or 1 up through MS 6.2; in MS 6.3, value is an integer   and currently values of 0, 1, or 2 have meaning), default 0. 

 MESSAGE_BUFFER_SIZE (integer), default 100000. New in  MS 6.2. Specifies the maximum message size; larger messages will be truncated. 

 HOST (hostname or IP address). A value must be specified for this   option (its presence is required). 

 PORT (integer), default 783. 

 USE_CHECK (integer), default 1. If set to 1, use the spamd CHECK command rather than SYMBOLS  command 

 (New in 8.0) CONNECT_TIMEOUT (integer), defaults to the TIMEOUT  option&#x27;s value if TIMEOUT is greater than 0; if TIMEOUT is 0, then   CONNECT_TIMEOUT defaults to 120. Attempting to set CONNECT_TIMEOUT to a  non-positive value will result in a value of 60 being used. This option   specifies the time, in seconds, that the MTA will wait to connect to   SpamAssassin. 

 (New in 6.2p5 and 6.3.) TIMEOUT (integer), default 3600   (seconds). This option controls how long the MTA will wait for a   response from SpamAssassin. (Prior to MS 6.3 the timeout was hard-coded   as 3600 seconds.) Note that the timeout for an initial connection to    SpamAssassin is not controlled by this option, but rather is a setting    for the TCP stack; this option instead controls the timeout for the MTA    in getting back responses after the initial connection is established. 

 SOCKS_HOST </li>

 SOCKS_PORT (integer), default 1080. </li>

 SOCKS_USERNAME </li>

 SOCKS_PASSWORD </li>

 MODE default 0. (Values 0, 1, 2, and (new in MS 6.2p1) 3 are    supported.) </li>

 FIELD default "Spam-Test". </li>

 VERDICT </li>

 USE_CHECK (0 or 1), default 1. </li>

 USERNAME </li>

 (New in MS 6.3p1.) USERNAME_MAPPING. This option is used to   specify the name of a  mapping table to probe with address information    as the plugin receives recipient addresses from the MTA, to potentially override the USERNAME option&#x27;s value. The probe   format is: </li>

</ul> current-username&#x7c;current-recipient-address&#x7c;current-optin-string <ul>

 Both the   and the preceeding vertical bar are omitted if no optin value was specified. If the mapping sets the   flag, then the output string is taken to be the  updated username (overriding the USERNAME SpamAssassin option value) to pass  to spamd. </li>

</ul>

For instance, with SpamAssassin configured as spam/virus filter package number 2, and SpamAssassin option file settings that include MODE=2 FIELD= and a setting that does an " " action, such as msconfig&#x3e; set spamfilter2_string_action &#x27;data:,addheader "Spam-test: $U";&#x27; msconfig# show spamfilter2_string_action role.mta.spamfilter2_string_action = data:,addheader "Spam-test: $U"; or in legacy configuration: SPAMFILTER2_STRING_ACTION1=data:,addheader "Spam-test: $U" could result in the addition of header lines such as: Spam-test: False ; 0.1 / 4.5 ; FORGED_RCVD_HELO Spam-test: True ; 12.9 / 4.5 ; RCVD_HELO_IP_MISMATCH,RCVD_IN_BL_SPAMCOP_NET, RCVD_IN_XBL,RCVD_NUMERIC_HELO,URIBL_OB_SURBL,URIBL_SC_SURBL,URIBL_WS_SURBL

See also:
 * Mapping tables
 * spamfilter1_string_action MTA Option
 * spamfilter1_config_file MTA Option