[Serverfilters-commit] server_side_filters config_example.php, 1.3, 1.4

[Paul L. <pdo...@us...>]

Update of /cvsroot/serverfilters/server_side_filters
In directory sfp-cvsdas-3.v30.ch3.sourceforge.com:/tmp/cvs-serv23119

Modified Files:
	config_example.php 
Log Message:
Add infomration about how to use Sieve spamtest and virustest extensions in predefined rules

Index: config_example.php
===================================================================
RCS file: /cvsroot/serverfilters/server_side_filters/config_example.php,v
retrieving revision 1.3
retrieving revision 1.4
diff -C2 -d -r1.3 -r1.4
*** config_example.php	10 Jan 2011 21:40:12 -0000	1.3
--- config_example.php	11 Jan 2011 01:36:42 -0000	1.4
***************
*** 327,336 ****
  //                           (beside normal header field names, the special
  //                           values "TO_OR_CC", "BODY", "ANY_HEADER", and
! //                           "ANYWHERE" are accepted)
  //    MATCHING_METHOD     -- How to "search" the header - this value MUST
  //                           be one of the following: "CONTAINS", "NOT_CONTAINS",
  //                           "BEGINS_WITH", "DOESNT_BEGIN_WITH", "ENDS_WITH",
  //                           "DOESNT_END_WITH", "IS_EXACTLY", "ISNT_EXACTLY",
! //                           "MATCHES_REGEX" or "DOESNT_MATCH_REGEX"
  //    MATCH_STRING        -- The value to search in the header for
  //    ACTION              -- What to do with matching messages - this value
--- 327,350 ----
  //                           (beside normal header field names, the special
  //                           values "TO_OR_CC", "BODY", "ANY_HEADER", and
! //                           "ANYWHERE" are accepted) (the Sieve backend
! //                           (Server Side Filters Sieve plugin) also supports
! //                           "VIRUSTEST", "NOT_VIRUSTEST", "SPAMTEST",
! //                           "NOT_SPAMTEST", "SPAMTEST_PERCENT",
! //                           "NOT_SPAMTEST_PERCENT" as long as your Sieve
! //                           server provides the spamtest, spamtestplus or
! //                           virustest extensions; any of these should be
! //                           used in conjunction with the Sieve-specific
! //                           values for MATCHING_METHOD as explained below)
  //    MATCHING_METHOD     -- How to "search" the header - this value MUST
  //                           be one of the following: "CONTAINS", "NOT_CONTAINS",
  //                           "BEGINS_WITH", "DOESNT_BEGIN_WITH", "ENDS_WITH",
  //                           "DOESNT_END_WITH", "IS_EXACTLY", "ISNT_EXACTLY",
! //                           "MATCHES_REGEX" or "DOESNT_MATCH_REGEX" (the Sieve
! //                           backend (Server Side Filters Sieve plugin) also
! //                           supports "GT" (greater than), "GE" (greater than or
! //                           equal to), "LT" (less than), "LE" (less than or equal
! //                           to), "EQ" (equal), or "NE" (not equal), which are to
! //                           be used with the "SPAMTEST" and "VIRUSTEST" values
! //                           for the "HEADER_FIELD" (see above))
  //    MATCH_STRING        -- The value to search in the header for
  //    ACTION              -- What to do with matching messages - this value
***************
*** 498,501 ****
--- 512,531 ----
  // );
  //
+ // Here is a "spam" rule that makes use of the special values
+ // for "HEADER_FIELD" and "MATCHING_METHOD" that the Sieve
+ // backend (Server Side Filters Sieve plugin) provides:
+ //
+ // $predefined_filter_rules = array(
+ //    'Spam Filter' => array(
+ //          'HEADER_FIELD'    => 'SPAMTEST',
+ //          'MATCHING_METHOD' => 'GT',
+ //          'MATCH_STRING'    => '3',
+ //          'CRITERIA_TEXT'   => 'If message is marked as <strong>spam</strong>%s%s%s,',
+ //          'ACTION_TEXT'     => 'then %s to',
+ //          'FOLDER_TEXT'     => '%sFolder',
+ //          'EMAIL_TEXT'      => '%sEmail',
+ //    ),
+ // );
+ //
  // WARNING: If you remove or change one of these rules after users have
  //          started using them, there is a chance of users losing those