1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
|
--- ../MailScanner-install-4.48.4.orig/docs/man/MailScanner.conf.5 Wed Dec 7 18:33:04 2005
+++ docs/man/MailScanner.conf.5 Wed Dec 7 18:33:54 2005
@@ -1,4 +1,4 @@
-.TH "MailScanner.conf" "5" "4.42.9" "Julian Field" "Mail"
+.TH "MailScanner.conf" "5" "4.48.4" "Julian Field" "Mail"
.SH "NAME"
.LP
MailScanner.conf \- Main configuration for MailScanner
@@ -326,6 +326,23 @@
.br
If more messages are found in the queue than this, then switch to an "accelerated" mode of processing messages. This will cause it to stop scanning messages in strict date order, but in the order it finds them in the queue. If your queue is bigger than this size a lot of the time, then some messages could be greatly delayed. So treat this option as "in emergency only".
+
+.TP
+\fBScan Messages\fR
+Default: yes
+.br
+
+.br
+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.
+
+.TP
+\fBReject Messages\fR
+Default: no
+.br
+
+.br
+You may not want to receive mail from certain addresses and/or to certain addresses. If so, you can do this with your email transport (sendmail, Postfix, etc) but that will just send a one\-line message which is not helpful to the user sending the message. If this is set to yes, then the message set by the "Rejection Report" will be sent instead, and the incoming message will be deleted. If you want to store a copy of the original incoming message then use the "Archive Mail" setting to archive a copy of it. The purpose of this option is to set it to be a ruleset, so that you can reject messages from a few offending addresses where you need to send a polite reply instead of just a brief 1\-line rejection message.
+
.TP
\fBMaximum Attachments Per Message\fR
Default: 200
@@ -853,6 +870,15 @@
There is no point quarantining most viruses these days, so if you set this to "no" then no infections listed in your "Silent Viruses" setting will be quarantined, even if you have chosen to quarantine infections in general. This is currently set to "yes" so the behaviour is the same as it was in in previous versions. This can also be the filename of a ruleset.
.TP
+\fBQuarantine Modified Body\fR
+Default: no
+.br
+
+.br
+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.
+
+
+.TP
\fBQuarantine Whole Message\fR
Default: no
.br
@@ -885,6 +911,16 @@
.br
Set where to find all the strings used so they can be translated into your local language. This can also be the filename of a ruleset so you can produce different languages for different messages.
+
+.TP
+\fBRejection Report\fR
+Default: %reports\-dir%/rejection.report.txt
+.br
+
+.br
+Set where to find the message text sent to users who triggered the ruleset you are using with the "Reject Message" option.
+
+
.TP
\fBDeleted Bad Filename Message Report\fR
Default: %reports\-dir%/deleted.filename.message.txt
@@ -1701,12 +1737,64 @@
.br
.br
-# 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.
+
+
+
+.SH "Custom Spam Scanner Plugin"
+.TP
+\fBUse Custom Spam Scanner\fR
+Default: no
+.br
+
+.br
+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
+.br
+.RS 7
+.IP \(bu 4
+$IP \- the numeric IP address of the system on the remote end of the SMTP connections
+.IP \(bu 4
+$From \- the address of the envelope sender of the message
+.IP \(bu 4
+$To \- a perl reference to the envelope recipients of the message
+.IP \(bu 4
+$Message \- a perl reference to the list of line of the message
+.RE
+.br
+
+
+.TP
+\fBMax Custom Spam Scanner Size\fR
+Default: 20000
+.br
+.br
+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.
+.TP
+\fBCustom Spam Scanner Timeout\fR
+Default: 20
+.br
+
+.br
+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.
+
+
+.TP
+\fBMax Custom Spam Scanner Timeouts\fR
+Default: 10
+.br
+
+.br
+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.
+
+.TP
+\fBCustom Spam Scanner Timeout History\fR
+Default: 20
+.br
+
+.br
+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").
.SH "What to do with spam"
.TP
\fBSpam Actions\fR
|
