Scan Messages
| + |
+ Default: yes + +If this is set to yes, then email messages passing +through MailScanner will be processed and checked, and all +the other options in this file will be used to control what +checks are made on the message. If this is set to no, then +email messages will NOT be processed or checked *at all*, +and so any viruses or other problems will be ignored. + |
+
| + |
Maximum Attachments Per Message |
Quarantine Modified Body
| + |
+ Default: no + +Do you want to store copies of messages which have been +disarmed by having their HTML modified at all? This can also +be the filename of a ruleset. + |
+
| + |
Quarantine Whole Message |
Default: no
-# The Bayesian database rebuild and expiry may take a 2 -or 3 minutes # to complete. During this time you can either -wait, or simply # disable SpamAssassin checks until it has -completed. WaitDuringBayesRebuild = no
+The Bayesian database rebuild and expiry may take a 2 or +3 minutes to complete. During this time you can either wait, +or simply disable SpamAssassin checks until it has +completed.
+| + |
+ Use Custom Spam Scanner |
+
| + |
+ Default: no + +Use the Custom Spam Scanner. This is code you will have +to write yourself, a function called +"GenericSpamScanner" stored in the file +"MailScanner/lib/MailScanner/CustomFunctions/GenericSpamScanner.pm". +A sample function is given in the correct file in the +distribution. This sample function also includes code to +show you how to make it run an external program to produce a +spam score. This can also be the filename of a ruleset. The +function will be passed + |
+
| + |
+
+ • + |
++ |
+
+ $IP + |
++ | +
| + | + | + | + | +
+
+ − the numeric IP address of the system on the +remote end of the SMTP connections + |
+
| + |
+
+ • + |
++ |
+
+ $From + |
++ |
+
+ − the address of the envelope sender of the +message + |
++ | +
| + |
+
+ • + |
++ |
+
+ $To + |
++ | + | +
| + | + | + | + | +
+
+ − a perl reference to the envelope recipients of +the message + |
++ | +
| + |
+
+ • + |
++ |
+
+ $Message + |
++ | +
| + |
+ − a perl reference to the list of line of the +message |
+
| + |
+ Max Custom Spam Scanner Size |
+
| + |
+ Default: 20000 + +How much of the message should be passed tot he Custom +Spam Scanner. Most spam tools only need the first 20kbytes +of the message to determine if it is spam or not. Passing +more than is necessary only slows things down. This can also +be the filename of a ruleset. + |
+
| + |
+ Custom Spam Scanner Timeout |
+
| + |
+ Default: 20 + +How long should the custom spam scanner take to run? If +it takes more seconds than this, then it should be +considered to have crashed and should be killed. This stops +denial−of−service attacks. + |
+
| + |
+ Max Custom Spam Scanner Timeouts |
+
| + |
+ Default: 10 + +If the Custom Spam Scanner times out more times in a row +than this, then it will be marked as "unavailable" +until MailScanner next re−starts itself. + |
+
| + |
+ Custom Spam Scanner Timeout History |
+
| + |
+ Default: 20 + +The total number of Custom Spam Scanner attempts during +which "Max Custom Spam Scanner Timeouts" will +cause the Custom Spam Scanner to be marked as +"unavailable". See the previous comment for more +information. The default values of 10 and 20 mean that 10 +timeouts in any sequence of 20 attempts will trigger the +behaviour described above, until the next periodic restart +(see "Restart Every"). |