ports/96742: [MAINTAINER] mail/MailScanner: update to 4.53.7
Jan-Peter Koopmann
j.koopmann at seceidos.de
Thu May 4 00:10:27 UTC 2006
>Number: 96742
>Category: ports
>Synopsis: [MAINTAINER] mail/MailScanner: update to 4.53.7
>Confidential: no
>Severity: serious
>Priority: high
>Responsible: freebsd-ports-bugs
>State: open
>Quarter:
>Keywords:
>Date-Required:
>Class: maintainer-update
>Submitter-Id: current-users
>Arrival-Date: Thu May 04 00:10:21 GMT 2006
>Closed-Date:
>Last-Modified:
>Originator: Jan-Peter Koopmann
>Release: FreeBSD 4.9-STABLE i386
>Organization:
>Environment:
System: FreeBSD services.intern.seceidos.de 4.9-STABLE FreeBSD 4.9-STABLE #0: Mon Jan 5 10:56:46 CET
>Description:
- Update to 4.53.7
3/5/2006 New in Version 4.53.7-1
================================
* New Features and Improvements *
- Attachment extraction now checks for available disk space and a DoS attack
using messages with high expansion ratios will fail even quicker than it
did before.
- Added new setting "SpamAssassin Local State Dir" to support the sa-update
tool provided with MailScanner these days, to provide a way of auto-
updating the core SpamAssassin rulesets. The default value is set to what
you need for Linux (/var/lib).
- Added new cron job to run sa-update every night. The location of the
sa-update program is read from /etc/sysconfig/MailScanner.
- Added support for new header -H file format in Exim 4.61.
- Added 2 new configuration options "Gunzip Command" and "Gunzip Timeout" to
enable unpacking of gzip-ed files for filename and filetype checking.
Even if this is disabled, gzip-ed files will still be virus scanned.
- Added support for numerical entries in phishing.safe.sites.conf file.
- Added support for optional multipliers in numbers in MailScanner.conf.
So you can now write "50M" instead of "50000000". The multipliers supported
are "k", "m" and "g" to denote 1 thousand, 1 million and 1 billion (10^9)
in upper or lower case.
You must *not* put any spaces between the number and the multiplier character.
- Added a new configuration option "Ignored Web Bug Filenames". This allows
you to whitelist a bunch of filenames that can appear in the URLs of
potential web bugs. So if you decide that all potential web bugs with
"spacer" or "pixel.gif" in the filename are just padding for page layout,
then you can make it ignore them by adding them to this list. A sample
list is provided in MailScanner.conf.
This is disabled by default, as spammers may start to use this as a means
of circumventing the Web Bug trap.
- When Web Bugs are disarmed, the URL used to replace the original web bug
can now be set using the new configuration option "Web Bug Replacement".
If this is not specified, then the old value of "MailScannerWebBug" is used.
The default value supplied in the MailScanner.conf file is the address of
an untracked 1x1 pixel transparent gif (51 bytes) hosted on the MailScanner
web site. This will not be tracked other than to supply an overall count of
the number of hits this image gets, for overall statistical purposes.
- Added Razor2 to the list of plugins automatically enabled by the ClamAV+SA
easy-to-install package, due to the recent change in licence. Now if DCC
could go the same way...
- Updated Catalan translations.
* Fixes *
- Fixed bug in DoS attack handler. Thanks for Jorge for this.
- Commented out setting of "SpamAssassin Local State Dir" in MailScanner.conf.
Added file(s):
- files/patch-bin-cron-update_phishing_sites.cron
- files/patch-bin-cron-update_virus_scanners.cron
- files/patch-docs-man-MailScanner.8
- files/patch-docs-man-MailScanner.8.html
- files/patch-docs-man-MailScanner.conf.5
- files/patch-docs-man-MailScanner.conf.5.html
- files/patch-lib-clamav-wrapper
Removed file(s):
- files/patch-bin:cron:update_phishing_sites.cron
- files/patch-bin:cron:update_virus_scanners.cron
- files/patch-docs:man:MailScanner.8
- files/patch-docs:man:MailScanner.8.html
- files/patch-docs:man:MailScanner.conf.5
- files/patch-docs:man:MailScanner.conf.5.html
- files/patch-lib-MailScanner-Exim.pm
- files/patch-lib:clamav-wrapper
Generated with FreeBSD Port Tools 0.63
>How-To-Repeat:
>Fix:
--- MailScanner-4.53.7.patch begins here ---
Index: Makefile
===================================================================
RCS file: /home/ncvs/ports/mail/mailscanner/Makefile,v
retrieving revision 1.48
diff -u -r1.48 Makefile
--- Makefile 27 Apr 2006 17:30:45 -0000 1.48
+++ Makefile 3 May 2006 19:49:54 -0000
@@ -6,8 +6,7 @@
#
PORTNAME= MailScanner
-PORTVERSION= 4.52.2
-PORTREVISION= 1
+PORTVERSION= 4.53.7
CATEGORIES= mail
MASTER_SITES= http://www.sng.ecs.soton.ac.uk/mailscanner/files/4/tar/
DISTNAME= ${PORTNAME}-install-${PORTVERSION}-${PATCHLEVEL}
Index: distinfo
===================================================================
RCS file: /home/ncvs/ports/mail/mailscanner/distinfo,v
retrieving revision 1.34
diff -u -r1.34 distinfo
--- distinfo 13 Apr 2006 16:42:24 -0000 1.34
+++ distinfo 3 May 2006 19:49:54 -0000
@@ -1,2 +1,2 @@
-MD5 (MailScanner-install-4.52.2-1.tar.gz) = d559a96f1f5b51322293d1a9b5a37f1c
-SIZE (MailScanner-install-4.52.2-1.tar.gz) = 6554423
+MD5 (MailScanner-install-4.53.7-1.tar.gz) = e3d995cc3e1af611af71985bbef0f81e
+SIZE (MailScanner-install-4.53.7-1.tar.gz) = 8798424
Index: pkg-plist
===================================================================
RCS file: /home/ncvs/ports/mail/mailscanner/pkg-plist,v
retrieving revision 1.29
diff -u -r1.29 pkg-plist
--- pkg-plist 13 Apr 2006 16:42:24 -0000 1.29
+++ pkg-plist 3 May 2006 19:49:54 -0000
@@ -155,7 +155,6 @@
%%DATADIR%%/reports/cz/deleted.filename.message.txt.sample
%%DATADIR%%/reports/cz/deleted.virus.message.txt.sample
%%DATADIR%%/reports/cz/disinfected.report.txt.sample
-%%DATADIR%%/reports/cz/filename.rules.txt.sample
%%DATADIR%%/reports/cz/inline.sig.html.sample
%%DATADIR%%/reports/cz/inline.sig.txt.sample
%%DATADIR%%/reports/cz/inline.spam.warning.txt.sample
@@ -466,6 +465,8 @@
%%DATADIR%%/reports/sk/stored.content.message.txt.sample
%%DATADIR%%/reports/sk/stored.filename.message.txt.sample
%%DATADIR%%/reports/sk/stored.virus.message.txt.sample
+%%PORTDOCS%%%%DOCSDIR%%/ellen2.old.jpg
+%%PORTDOCS%%%%DOCSDIR%%/ellenweblogo.png
%%PORTDOCS%%%%DOCSDIR%%/Book.Dec04-Aug05.pdf
%%PORTDOCS%%%%DOCSDIR%%/COPYING
%%PORTDOCS%%%%DOCSDIR%%/ChangeLog
@@ -498,7 +499,6 @@
%%PORTDOCS%%%%DOCSDIR%%/images/thumb_JulianField5.jpg
%%PORTDOCS%%%%DOCSDIR%%/index.html
%%PORTDOCS%%%%DOCSDIR%%/index.new.html
-%%PORTDOCS%%%%DOCSDIR%%/index.old.html
%%PORTDOCS%%%%DOCSDIR%%/install/ClamAVModule.shtml
%%PORTDOCS%%%%DOCSDIR%%/install/OS-virus-scan-web.htm
%%PORTDOCS%%%%DOCSDIR%%/install/README.trend
@@ -513,6 +513,9 @@
%%PORTDOCS%%%%DOCSDIR%%/install/linux.shtml
%%PORTDOCS%%%%DOCSDIR%%/install/mailscanner.shtml
%%PORTDOCS%%%%DOCSDIR%%/install/mcafee.shtml
+%%PORTDOCS%%%%DOCSDIR%%/install/mcp/Message.pm.patch.3.1.1
+%%PORTDOCS%%%%DOCSDIR%%/install/mcp/Conf.pm.patch.3.1.1
+%%PORTDOCS%%%%DOCSDIR%%/install/mcp/PerMsgStatus.pm.patch.3.1.1
%%PORTDOCS%%%%DOCSDIR%%/install/mcp/Conf.pm.patch.2.55
%%PORTDOCS%%%%DOCSDIR%%/install/mcp/Conf.pm.patch.2.60
%%PORTDOCS%%%%DOCSDIR%%/install/mcp/Conf.pm.patch.2.61
Index: files/CHANGES.port
===================================================================
RCS file: /home/ncvs/ports/mail/mailscanner/files/CHANGES.port,v
retrieving revision 1.4
diff -u -r1.4 CHANGES.port
--- files/CHANGES.port 27 Apr 2006 17:30:45 -0000 1.4
+++ files/CHANGES.port 3 May 2006 19:49:54 -0000
@@ -1,3 +1,8 @@
+Version 4.53.7
+=================
+- Upgrade to MailScanner 4.53
+- changed some patch-names
+
Version 4.52.2_1
=================
- fixed bug in mta.sh script
Index: files/patch-bin-cron-update_phishing_sites.cron
===================================================================
RCS file: files/patch-bin-cron-update_phishing_sites.cron
diff -N files/patch-bin-cron-update_phishing_sites.cron
--- /dev/null 1 Jan 1970 00:00:00 -0000
+++ files/patch-bin-cron-update_phishing_sites.cron 3 May 2006 19:49:54 -0000
@@ -0,0 +1,38 @@
+--- ../MailScanner-install-4.50.15.orig/bin/cron/update_phishing_sites.cron Wed Feb 15 20:02:33 2006
++++ bin/cron/update_phishing_sites.cron Wed Feb 15 20:14:45 2006
+@@ -1,20 +1,24 @@
+ #!/bin/bash
+
+-# Insert a random delay up to this value, to spread virus updates round
+-# the clock. 1800 seconds = 30 minutes.
+-# Set this to 0 to disable it.
+-UPDATEMAXDELAY=3600
+-if [ -f /etc/sysconfig/MailScanner ] ; then
+- . /etc/sysconfig/MailScanner
+-fi
+-export UPDATEMAXDELAY
++# Add the following line to /etc/rc.conf to configure a maximum delay in
++# order to spread virus updates round the clock. 1800 seconds = 30 minutes.
++# Set this to 0 to disable it
++
++. %%RC_SUBR%%
++
++name="mailscanner"
++rcvar=`set_rcvar`
++
++load_rc_config $name
++
++: ${mailscanner_updatemaxdelay="600"}
+
+ [ -x /opt/MailScanner/bin/update_phishing_sites ] || exit 0
+-if [ "x$UPDATEMAXDELAY" = "x0" ]; then
++if [ "x${mailscanner_updatemaxdelay}" = "x0" ]; then
+ :
+ else
+- logger -p mail.info -t update.phishing.sites Delaying cron job up to $UPDATEMAXDELAY seconds
+- perl -e "sleep int(rand($UPDATEMAXDELAY));"
++ logger -p mail.info -t update.phishing.sites Delaying cron job up to ${mailscanner_updatemaxdelay} seconds
++ perl -e "sleep int(rand(${mailscanner_updatemaxdelay}));"
+ fi
+ exec /opt/MailScanner/bin/update_phishing_sites > /dev/null 2>&1
+ exit 0
Index: files/patch-bin-cron-update_virus_scanners.cron
===================================================================
RCS file: files/patch-bin-cron-update_virus_scanners.cron
diff -N files/patch-bin-cron-update_virus_scanners.cron
--- /dev/null 1 Jan 1970 00:00:00 -0000
+++ files/patch-bin-cron-update_virus_scanners.cron 3 May 2006 19:49:54 -0000
@@ -0,0 +1,38 @@
+--- ../MailScanner-install-4.50.15.orig/bin/cron/update_virus_scanners.cron Wed Feb 15 20:02:33 2006
++++ bin/cron/update_virus_scanners.cron Wed Feb 15 20:11:17 2006
+@@ -1,20 +1,24 @@
+ #!/bin/bash
+
+-# Insert a random delay up to this value, to spread virus updates round
+-# the clock. 1800 seconds = 30 minutes.
+-# Set this to 0 to disable it.
+-UPDATEMAXDELAY=600
+-if [ -f /etc/sysconfig/MailScanner ] ; then
+- . /etc/sysconfig/MailScanner
+-fi
+-export UPDATEMAXDELAY
++# Add the following line to /etc/rc.conf to configure a maximum delay in
++# order to spread virus updates round the clock. 1800 seconds = 30 minutes.
++# Set this to 0 to disable it
++
++. %%RC_SUBR%%
++
++name="mailscanner"
++rcvar=`set_rcvar`
++
++load_rc_config $name
++
++: ${mailscanner_updatemaxdelay="600"}
+
+ [ -x /opt/MailScanner/bin/update_virus_scanners ] || exit 0
+-if [ "x$UPDATEMAXDELAY" = "x0" ]; then
++if [ "x${mailscanner_updatemaxdelay}" = "x0" ]; then
+ :
+ else
+- logger -p mail.info -t update.virus.scanners Delaying cron job up to $UPDATEMAXDELAY seconds
+- perl -e "sleep int(rand($UPDATEMAXDELAY));"
++ logger -p mail.info -t update.virus.scanners Delaying cron job up to ${mailscanner_updatemaxdelay} seconds
++ perl -e "sleep int(rand(${mailscanner_updatemaxdelay}));"
+ fi
+ exec /opt/MailScanner/bin/update_virus_scanners
+ exit 0
Index: files/patch-bin:cron:update_phishing_sites.cron
===================================================================
RCS file: files/patch-bin:cron:update_phishing_sites.cron
diff -N files/patch-bin:cron:update_phishing_sites.cron
--- files/patch-bin:cron:update_phishing_sites.cron 27 Apr 2006 17:30:45 -0000 1.2
+++ /dev/null 1 Jan 1970 00:00:00 -0000
@@ -1,38 +0,0 @@
---- ../MailScanner-install-4.50.15.orig/bin/cron/update_phishing_sites.cron Wed Feb 15 20:02:33 2006
-+++ bin/cron/update_phishing_sites.cron Wed Feb 15 20:14:45 2006
-@@ -1,20 +1,24 @@
- #!/bin/bash
-
--# Insert a random delay up to this value, to spread virus updates round
--# the clock. 1800 seconds = 30 minutes.
--# Set this to 0 to disable it.
--UPDATEMAXDELAY=3600
--if [ -f /etc/sysconfig/MailScanner ] ; then
-- . /etc/sysconfig/MailScanner
--fi
--export UPDATEMAXDELAY
-+# Add the following line to /etc/rc.conf to configure a maximum delay in
-+# order to spread virus updates round the clock. 1800 seconds = 30 minutes.
-+# Set this to 0 to disable it
-+
-+. %%RC_SUBR%%
-+
-+name="mailscanner"
-+rcvar=`set_rcvar`
-+
-+load_rc_config $name
-+
-+: ${mailscanner_updatemaxdelay="600"}
-
- [ -x /opt/MailScanner/bin/update_phishing_sites ] || exit 0
--if [ "x$UPDATEMAXDELAY" = "x0" ]; then
-+if [ "x${mailscanner_updatemaxdelay}" = "x0" ]; then
- :
- else
-- logger -p mail.info -t update.phishing.sites Delaying cron job up to $UPDATEMAXDELAY seconds
-- perl -e "sleep int(rand($UPDATEMAXDELAY));"
-+ logger -p mail.info -t update.phishing.sites Delaying cron job up to ${mailscanner_updatemaxdelay} seconds
-+ perl -e "sleep int(rand(${mailscanner_updatemaxdelay}));"
- fi
- exec /opt/MailScanner/bin/update_phishing_sites > /dev/null 2>&1
- exit 0
Index: files/patch-bin:cron:update_virus_scanners.cron
===================================================================
RCS file: files/patch-bin:cron:update_virus_scanners.cron
diff -N files/patch-bin:cron:update_virus_scanners.cron
--- files/patch-bin:cron:update_virus_scanners.cron 27 Apr 2006 17:30:45 -0000 1.2
+++ /dev/null 1 Jan 1970 00:00:00 -0000
@@ -1,38 +0,0 @@
---- ../MailScanner-install-4.50.15.orig/bin/cron/update_virus_scanners.cron Wed Feb 15 20:02:33 2006
-+++ bin/cron/update_virus_scanners.cron Wed Feb 15 20:11:17 2006
-@@ -1,20 +1,24 @@
- #!/bin/bash
-
--# Insert a random delay up to this value, to spread virus updates round
--# the clock. 1800 seconds = 30 minutes.
--# Set this to 0 to disable it.
--UPDATEMAXDELAY=600
--if [ -f /etc/sysconfig/MailScanner ] ; then
-- . /etc/sysconfig/MailScanner
--fi
--export UPDATEMAXDELAY
-+# Add the following line to /etc/rc.conf to configure a maximum delay in
-+# order to spread virus updates round the clock. 1800 seconds = 30 minutes.
-+# Set this to 0 to disable it
-+
-+. %%RC_SUBR%%
-+
-+name="mailscanner"
-+rcvar=`set_rcvar`
-+
-+load_rc_config $name
-+
-+: ${mailscanner_updatemaxdelay="600"}
-
- [ -x /opt/MailScanner/bin/update_virus_scanners ] || exit 0
--if [ "x$UPDATEMAXDELAY" = "x0" ]; then
-+if [ "x${mailscanner_updatemaxdelay}" = "x0" ]; then
- :
- else
-- logger -p mail.info -t update.virus.scanners Delaying cron job up to $UPDATEMAXDELAY seconds
-- perl -e "sleep int(rand($UPDATEMAXDELAY));"
-+ logger -p mail.info -t update.virus.scanners Delaying cron job up to ${mailscanner_updatemaxdelay} seconds
-+ perl -e "sleep int(rand(${mailscanner_updatemaxdelay}));"
- fi
- exec /opt/MailScanner/bin/update_virus_scanners
- exit 0
Index: files/patch-docs-man-MailScanner.8
===================================================================
RCS file: files/patch-docs-man-MailScanner.8
diff -N files/patch-docs-man-MailScanner.8
--- /dev/null 1 Jan 1970 00:00:00 -0000
+++ files/patch-docs-man-MailScanner.8 3 May 2006 19:49:54 -0000
@@ -0,0 +1,37 @@
+--- ../MailScanner-install-4.53.7.orig/docs/man/MailScanner.8 Wed May 3 21:16:27 2006
++++ docs/man/MailScanner.8 Wed May 3 21:33:13 2006
+@@ -1,10 +1,10 @@
+-.TH "MailScanner" "8" "4.49.7" "Julian Field" "Mail"
++.TH "MailScanner" "8" "4.52.2" "Julian Field" "Mail"
+ .SH "NAME"
+ .LP
+ MailScanner \- Virus/Spam Scanner for Sendmail, Exim and Postfix
+ .SH "SYNOPSIS"
+ .LP
+-\fBMailScanner\fR [\fI\-v\fR] [\fIconfigfile\fR]
++\fBMailScanner\fR [\fI\-v\fR] [\fI\-\-lint\fR] [\fI\-\-debug\fR] [\fI\-\-debug\-sa\fR] [\fI\-\-help\fR] [\fIconfigfile\fR]
+
+ .SH "DESCRIPTION"
+ .LP
+@@ -29,6 +29,21 @@
+ \fB\-v\fR
+ Prints version information for Mailscanner and all used perl\-modules.
+
++.TP
++\fB\-\-lint\fR
++Checks config file, print what virus scanners you have chosen to use and check SpamAssassin configuration as well.
++
++.TP
++\fB\-\-debug\fR
++Starts MailScanner in debug mode. See MailScanner.conf "Debug=yes".
++
++.TP
++\fB\-\-debug\-sa\fR
++Starts MailScanner in debug spamassassin mode. See MailScanner.conf "Debug SpamAssassin=yes".
++
++.TP
++\fB\-\-lint\fR
++Test MailScanner config and SpamAssassin config.
+ .SH "MTA SETUP"
+ .LP
+ It is important that your MTA only queues incoming mail and does not deliver it automatically. You need two mail queues (incoming and outgoing). Moreover you should setup two instances of your MTA. One that accepts incoming mail and puts it to an incoming queue and one that sends out mail that resides in the outgoing queue.
Index: files/patch-docs-man-MailScanner.8.html
===================================================================
RCS file: files/patch-docs-man-MailScanner.8.html
diff -N files/patch-docs-man-MailScanner.8.html
--- /dev/null 1 Jan 1970 00:00:00 -0000
+++ files/patch-docs-man-MailScanner.8.html 3 May 2006 19:49:54 -0000
@@ -0,0 +1,104 @@
+--- ../MailScanner-install-4.53.7.orig/docs/man/MailScanner.8.html Wed May 3 21:16:27 2006
++++ docs/man/MailScanner.8.html Wed May 3 21:33:15 2006
+@@ -1,5 +1,5 @@
+ <!-- Creator : groff version 1.19 -->
+-<!-- CreationDate: Wed Jan 4 13:45:56 2006 -->
++<!-- CreationDate: Wed May 3 21:32:34 2006 -->
+ <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
+ "http://www.w3.org/TR/html4/loose.dtd">
+ <html>
+@@ -40,7 +40,9 @@
+ <td width="11%"></td>
+ <td width="89%">
+ <p><b>MailScanner</b> [<i>−v</i>]
+-[<i>configfile</i>]</p>
++[<i>−−lint</i>] [<i>−−debug</i>]
++[<i>−−debug−sa</i>]
++[<i>−−help</i>] [<i>configfile</i>]</p>
+ </td>
+ </table>
+ <a name="DESCRIPTION"></a>
+@@ -78,15 +80,81 @@
+ cols="4" cellspacing="0" cellpadding="0">
+ <tr valign="top" align="left">
+ <td width="11%"></td>
+-<td width="3%">
++<td width="9%">
+
+ <p><b>−v</b></p>
+ </td>
+-<td width="8%"></td>
++<td width="2%"></td>
+ <td width="78%">
+
+ <p>Prints version information for Mailscanner and all used
+ perl−modules.</p>
++</td>
++<tr valign="top" align="left">
++<td width="11%"></td>
++<td width="9%">
++
++<p><b>−−lint</b></p>
++</td>
++<td width="2%"></td>
++<td width="78%">
++
++<p>Checks config file, print what virus scanners you have
++chosen to use and check SpamAssassin configuration as
++well.</p>
++</td>
++</table>
++<!-- INDENTATION -->
++<table width="100%" border=0 rules="none" frame="void"
++ cols="2" cellspacing="0" cellpadding="0">
++<tr valign="top" align="left">
++<td width="11%"></td>
++<td width="89%">
++<p><b>−−debug</b></p></td>
++</table>
++<!-- INDENTATION -->
++<table width="100%" border=0 rules="none" frame="void"
++ cols="2" cellspacing="0" cellpadding="0">
++<tr valign="top" align="left">
++<td width="22%"></td>
++<td width="78%">
++<p>Starts MailScanner in debug mode. See MailScanner.conf
++"Debug=yes".</p>
++</td>
++</table>
++<!-- INDENTATION -->
++<table width="100%" border=0 rules="none" frame="void"
++ cols="2" cellspacing="0" cellpadding="0">
++<tr valign="top" align="left">
++<td width="11%"></td>
++<td width="89%">
++<p><b>−−debug−sa</b></p></td>
++</table>
++<!-- INDENTATION -->
++<table width="100%" border=0 rules="none" frame="void"
++ cols="2" cellspacing="0" cellpadding="0">
++<tr valign="top" align="left">
++<td width="22%"></td>
++<td width="78%">
++<p>Starts MailScanner in debug spamassassin mode. See
++MailScanner.conf "Debug SpamAssassin=yes".</p>
++</td>
++</table>
++<!-- TABS -->
++<table width="100%" border=0 rules="none" frame="void"
++ cols="5" cellspacing="0" cellpadding="0">
++<tr valign="top" align="left">
++<td width="11%"></td>
++<td width="9%">
++
++<p><b>−−lint</b></p>
++</td>
++<td width="2%"></td>
++<td width="73%">
++
++<p>Test MailScanner config and SpamAssassin config.</p>
++</td>
++<td width="5%">
+ </td>
+ </table>
+ <a name="MTA SETUP"></a>
Index: files/patch-docs-man-MailScanner.conf.5
===================================================================
RCS file: files/patch-docs-man-MailScanner.conf.5
diff -N files/patch-docs-man-MailScanner.conf.5
--- /dev/null 1 Jan 1970 00:00:00 -0000
+++ files/patch-docs-man-MailScanner.conf.5 3 May 2006 19:49:54 -0000
@@ -0,0 +1,223 @@
+--- ../MailScanner-install-4.53.7.orig/docs/man/MailScanner.conf.5 Wed May 3 21:16:27 2006
++++ docs/man/MailScanner.conf.5 Wed May 3 21:33:05 2006
+@@ -1,4 +1,4 @@
+-.TH "MailScanner.conf" "5" "4.50.1" "Julian Field" "Mail"
++.TH "MailScanner.conf" "5" "4.53.7" "Julian Field" "Mail"
+ .SH "NAME"
+ .LP
+ MailScanner.conf \- Main configuration for MailScanner
+@@ -24,6 +24,10 @@
+ .br
+
+ .br
++The following optional multipliers are supported: You can write "50M" instead of "50000000". The multipliers supported are "k", "m" and "g" to denote 1 thousand, 1 million and 1 billion (10^9) in upper or lower case. You must *not* put any spaces between the number and the multiplier character.
++.br
++
++.br
+ Many of the options can also be the filename of a ruleset, which can be used to control features depending on the addresses of the message, and/or the IP address where the message came from. You will find some examples of rulesets and an explanation of them in the "rules" directories within the MailScanner installation and in the section "RULESETS" later in this manpage.
+
+ .LP
+@@ -364,6 +368,22 @@
+ Should we use a TNEF decoder (external or Perl module)? This should be "yes" unless the scanner you are using (Sophos, McAfee) has the facility built\-in. However, if you set it to "no", then the filenames within the TNEF attachment will not be checked against the filename rules.
+
+ .TP
++\fBUse TNEF Contents\fR
++Default: replace
++.br
++When the TNEF (winmail.dat) attachments are expanded, should the attachments contained in there be added to the list of attachments in the message? If you set this to "add" or "replace" then recipients of messages sent in "Outlook Rich Text Format" (TNEF) will be able to read the attachments if they are not using Microsoft Outlook.
++.br
++.RS 7
++.IP \(bu 4
++no: Leave winmail.dat TNEF attachments alone.
++.IP \(bu 4
++add: Add the contents of winmail.dat as extra attachments, but also still include the winmail.dat file itself. This will result in TNEF messages being doubled in size.
++.IP \(bu 4
++replace: Replace the winmail.dat TNEF attachment with the files it contains, and delete the original winmail.dat file itself. This means the message stays the same size, but is usable by non\-Outlook recipients.
++.RE
++
++
++.TP
+ \fBDeliver Unparsable TNEF\fR
+ Default: no
+ .br
+@@ -405,6 +425,22 @@
+ .br
+ The maximum length of time the "file" command is allowed to run for one batch of messages (in seconds).
+
++.TP
++\fBGunzip Command\fR
++Default: /usr/bin/gunzip
++.br
++
++.br
++Where the "gunzip" command is installed. This is used for expanding .gz files. To disable gzipped file checking, set this value to blank and the timeout to 0.
++
++.TP
++\fBGunzip Timeout\fR
++Default: 50
++.br
++
++.br
++The maximum length of time the "gunzip" command is allowed to run to expand 1 attachment file (in seconds).
++
+
+ .TP
+ \fBUnrar Command\fR
+@@ -423,6 +459,12 @@
+ The maximum length of time the "unrar" command is allowed to run for 1 RAR archive (in seconds)
+
+ .TP
++\fBFind UU\-Encoded Files\fR
++Default: no
++.br
++A few viruses store their infected data in UU\-encoded files, to try to catch out virus scanners. This rarely succeeds at all. Setting this option to yes means that you can apply filename and filetype checks to the contents of UU\-encoded files. This may occasionally be useful, in which case you should set to yes. This can also be the filename of a ruleset.
++
++.TP
+ \fBBlock Encrypted Messages\fR
+ Default: no
+ .br
+@@ -521,7 +563,7 @@
+ .SH "Virus scanning and vulnerability testing"
+ .TP
+ \fBVirus Scanning\fR
+-Default: yes
++Default: auto
+ .br
+
+ .br
+@@ -529,7 +571,7 @@
+ .br
+ NOTE: Switching this to no completely disables all virus\-scanning functionality. If you just want to switch of actual virus scanning, then set "Virus Scanners = none" instead.
+ .br
+-If you want to be able to switch scanning on/off for different users or different domains, set this to the filename of a ruleset.
++If you want to be able to switch scanning on/off for different users or different domains, set this to the filename of a ruleset. If you set this to auto then it searches for and uses every available installed virus scanner.
+
+ .TP
+ \fBVirus Scanners\fR
+@@ -686,6 +728,23 @@
+ .br
+ While detecting "Phishing" attacks, do you also want to point out links to numeric IP addresses. Genuine links to totally numeric IP addresses are very rare, so this option is set to "yes" by default. If a numeric IP address is found in a link, the same phishing warning message is used as in the Find Phishing Fraud option above. This value cannot be the name of a ruleset, only a simple yes or no.
+
++.TP
++\fBUse Stricter Phishing Net\fR
++Default: yes
++.br
++
++.br
++If this is set to yes, then most of the URL in a link must match the destination address it claims to take you to. This is the default as it is a much stronger test and is very hard to maliciously avoid. If this is set to no, then just the company name and country (and any names between the two, dependent on the specific country) must match. This is not as strict as it will not protect you against internal malicious sites based within the company being abused. For example, it would not find www.nasty.company\-name.co.uk pretending to be www.nice.company\-name.co.uk. But it will still detect most phishing attacks of the type www.nasty.co.jp versus www.nice.co.jp. Depending on the country code it knows how many levels of domain need to be checked. This can also be the filename of a ruleset.
++
++
++.TP
++\fBHighlight Phishing Fraud\fR
++Default: yes
++.br
++
++.br
++If a phishing fraud is detected, do you want to highlight the tag with a message stating that the link may be to a fraudulent web site. This can also be the filename of a ruleeset.
++
+
+ .TP
+ \fBPhishing Safe Sites File\fR
+@@ -695,6 +754,15 @@
+ .br
+ There are some companies, such as banks, that insist on sending out email messages with links in them that are caught by the "Find Phishing Fraud" test described above. This is the name of a file which contains a list of link destinations which should be ignored in the test. This may, for example, contain the known websites of some banks. See the file itself for more information. This can only be the name of the file containing the list, it *cannot* be the filename of a ruleset.
+
++.TP
++\fBCountry Sub\-Domains List\fR
++Default: %etc\-dir%/country.domains.conf
++.br
++
++.br
++.TP
++This file lists all the countries that use 2nd\-level and 3rd\-level domain names to classify distinct types of website within their country. This cannot be the name of a ruleset, it is just a simple setting.
++
+
+ .TP
+ \fBAllow IFrame Tags\fR
+@@ -773,6 +841,22 @@
+ .RE
+
+ .TP
++\fBIgnored Web Bug Filenames\fR
++Default:
++.br
++
++.br
++This is a list of filenames (or parts of filenames) that may appear in the filename of a web bug URL. They are only checked in the filename, not any directories or hostnames in the URL of the possible web bug. If it appears, then the web bug is assumed to be a harmless "spacer" for page layout purposes and not a real web bug at all. It should be a space\- and/or comma\-separated list of filename parts. Note: Use this with care, as spammers may use this to circumvent the web bug trap. It is disabled by default because of this problem. This can also be the filename of a ruleset.
++
++.TP
++\fBWeb Bug Replacement\fR
++Default: http://www.sng.ecs.soton.ac.uk/mailscanner/images/1x1spacer.gif
++.br
++
++.br
++When a web bug is found, what image do you want to replace it with? By replacing it with a real image, the page layout still works properly, so the formatting and layout of the message is correct. The following is a harmless untracked 1x1 pixel transparent image. If this is not specified, the the old value of "MailScannerWebBug" is used, which of course is not an image and may well upset layout of the email. This can also be the filename of a ruleset.
++
++.TP
+ \fBAllow Object Codebase Tags\fR
+ Default: no
+ .br
+@@ -1682,7 +1766,7 @@
+ .SH "SpamAssassin"
+ .TP
+ \fBUse SpamAssassin\fR
+-Default: no
++Default: yes
+ .br
+
+ .br
+@@ -2076,6 +2160,15 @@
+ .RE
+
+ .TP
++\fBSpamAssassin Local State Dir\fR
++Default:
++.br
++
++.br
++The rules created by the "sa\-update" tool are searched for here. This directory contains the spamassassin/3.001001/updates_spamassassin_org directory structure beneath it. Only un\-comment this setting once you have proved that the sa\-update cron job has run successfully and has created a directory structure under the spamassassin directory within this one and has put some *.cf files in there. Otherwise it will ignore all your current rules!
++
++
++.TP
+ \fBSpamAssassin Default Rules Dir\fR
+ Default:
+ .br
+@@ -2113,6 +2206,22 @@
+ .RE
+
+ .TP
++\fBSpamAssassin Cache Timings\fR
++Default: 1800,300,10800,172800,600
++.br
++Do not change this unless you absolutely have to, these numbers have been carefully calculated. They affect the length of time that different types of message are stored in the SpamAssassin cache which can be configured earlier in this file (look for "Cache"). The numbers are all set in seconds. They are:
++.br
++1. Non\-Spam cache lifetime = 30 minutes
++.br
++2. Spam (low scoring) cache lifetime = 5 minutes
++.br
++3. High\-Scoring spam cache lifetime = 3 hours
++.br
++4. Viruses cache lifetime = 2 days
++.br
++5. How often to check the cache for expired messages = 10 minutes
++
++.TP
+ \fBDebug\fR
+ Default: no
+ .br
+@@ -2167,6 +2276,15 @@
+
+ .br
+ The value of the option is actually never used, but it is evaluated at the end of processing a batch of messages. It is designed to be used in conjunction with a Custom Function. The Custom Function should then be written to have a "side effect" of doing something useful such as logging lots of information about the batch of messages to a file or an SQL database.
++
++
++.TP
++\fBAlways Looked Up Last After Batch\fR
++Default: no
++.br
++
++.br
++This option is intended for people who want to log per\-batch information. This is evaluated after the "Always Looked Up Last" configuration option for each message in the batch. This is looked up once for the entire batch. Its value is completely ignored, it is purely there to have side effects. If you want to use it, read CustomConfig.pm.
+
+ .TP
+ \fBDeliver in Background\fR
Index: files/patch-docs-man-MailScanner.conf.5.html
===================================================================
RCS file: files/patch-docs-man-MailScanner.conf.5.html
diff -N files/patch-docs-man-MailScanner.conf.5.html
--- /dev/null 1 Jan 1970 00:00:00 -0000
+++ files/patch-docs-man-MailScanner.conf.5.html 3 May 2006 19:49:54 -0000
@@ -0,0 +1,594 @@
+--- ../MailScanner-install-4.53.7.orig/docs/man/MailScanner.conf.5.html Wed May 3 21:16:27 2006
++++ docs/man/MailScanner.conf.5.html Wed May 3 21:33:08 2006
+@@ -1,5 +1,5 @@
+ <!-- Creator : groff version 1.19 -->
+-<!-- CreationDate: Wed Jan 4 14:36:14 2006 -->
++<!-- CreationDate: Wed May 3 21:32:34 2006 -->
+ <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
+ "http://www.w3.org/TR/html4/loose.dtd">
+ <html>
+@@ -113,6 +113,13 @@
+ <!-- INDENTATION -->
+ <p>option = value</p>
+ <!-- INDENTATION -->
++<p>The following optional multipliers are supported: You can
++write "50M" instead of "50000000". The
++multipliers supported are "k", "m" and
++"g" to denote 1 thousand, 1 million and 1 billion
++(10^9) in upper or lower case. You must *not* put any spaces
++between the number and the multiplier character.</p>
++<!-- INDENTATION -->
+ <p>Many of the options can also be the filename of a
+ ruleset, which can be used to control features depending on
+ the addresses of the message, and/or the IP address where
+@@ -1064,6 +1071,73 @@
+ <tr valign="top" align="left">
+ <td width="11%"></td>
+ <td width="89%">
++<p><b>Use TNEF Contents</b></p></td>
++</table>
++<!-- INDENTATION -->
++<table width="100%" border=0 rules="none" frame="void"
++ cols="2" cellspacing="0" cellpadding="0">
++<tr valign="top" align="left">
++<td width="22%"></td>
++<td width="78%">
++<p>Default: replace<br>
++When the TNEF (winmail.dat) attachments are expanded, should
++the attachments contained in there be added to the list of
++attachments in the message? If you set this to
++"add" or "replace" then recipients of
++messages sent in "Outlook Rich Text Format" (TNEF)
++will be able to read the attachments if they are not using
++Microsoft Outlook.</p>
++</td>
++</table>
++<!-- TABS -->
++<table width="100%" border=0 rules="none" frame="void"
++ cols="4" cellspacing="0" cellpadding="0">
++<tr valign="top" align="left">
++<td width="22%"></td>
++<td width="1%">
++
++<p>•</p>
++</td>
++<td width="5%"></td>
++<td width="72%">
++
++<p>no: Leave winmail.dat TNEF attachments alone.</p>
++</td>
++<tr valign="top" align="left">
++<td width="22%"></td>
++<td width="1%">
++
++<p>•</p>
++</td>
++<td width="5%"></td>
++<td width="72%">
++
++<p>add: Add the contents of winmail.dat as extra
++attachments, but also still include the winmail.dat file
++itself. This will result in TNEF messages being doubled in
++size.</p>
++</td>
++<tr valign="top" align="left">
++<td width="22%"></td>
++<td width="1%">
++
++<p>•</p>
++</td>
++<td width="5%"></td>
++<td width="72%">
++
++<p>replace: Replace the winmail.dat TNEF attachment with
++the files it contains, and delete the original winmail.dat
++file itself. This means the message stays the same size, but
++is usable by non−Outlook recipients.</p>
++</td>
++</table>
++<!-- INDENTATION -->
++<table width="100%" border=0 rules="none" frame="void"
++ cols="2" cellspacing="0" cellpadding="0">
++<tr valign="top" align="left">
++<td width="11%"></td>
++<td width="89%">
+ <p><b>Deliver Unparsable TNEF</b></p></td>
+ </table>
+ <!-- INDENTATION -->
+@@ -1072,8 +1146,14 @@
+ <tr valign="top" align="left">
+ <td width="22%"></td>
+ <td width="78%">
+-<p>Default: no</p>
++<p>Default: no</p></td>
++</table>
+ <!-- INDENTATION -->
++<table width="100%" border=0 rules="none" frame="void"
++ cols="2" cellspacing="0" cellpadding="0">
++<tr valign="top" align="left">
++<td width="28%"></td>
++<td width="72%">
+ <p>Rich Text format attachments produced by some versions of
+ Microsoft Outlook cannot be completely decoded at present.
+ Setting this option to yes allows compatibility with the
+@@ -1177,6 +1257,48 @@
+ <tr valign="top" align="left">
+ <td width="11%"></td>
+ <td width="89%">
++<p><b>Gunzip Command</b></p></td>
++</table>
++<!-- INDENTATION -->
++<table width="100%" border=0 rules="none" frame="void"
++ cols="2" cellspacing="0" cellpadding="0">
++<tr valign="top" align="left">
++<td width="22%"></td>
++<td width="78%">
++<p>Default: /usr/bin/gunzip</p>
++<!-- INDENTATION -->
++<p>Where the "gunzip" command is installed. This
++is used for expanding .gz files. To disable gzipped file
++checking, set this value to blank and the timeout to 0.</p>
++</td>
++</table>
++<!-- INDENTATION -->
++<table width="100%" border=0 rules="none" frame="void"
++ cols="2" cellspacing="0" cellpadding="0">
++<tr valign="top" align="left">
++<td width="11%"></td>
++<td width="89%">
++<p><b>Gunzip Timeout</b></p></td>
++</table>
++<!-- INDENTATION -->
++<table width="100%" border=0 rules="none" frame="void"
++ cols="2" cellspacing="0" cellpadding="0">
++<tr valign="top" align="left">
++<td width="22%"></td>
++<td width="78%">
++<p>Default: 50</p>
++<!-- INDENTATION -->
++<p>The maximum length of time the "gunzip" command
++is allowed to run to expand 1 attachment file (in
++seconds).</p>
++</td>
++</table>
++<!-- INDENTATION -->
++<table width="100%" border=0 rules="none" frame="void"
++ cols="2" cellspacing="0" cellpadding="0">
++<tr valign="top" align="left">
++<td width="11%"></td>
++<td width="89%">
+ <p><b>Unrar Command</b></p></td>
+ </table>
+ <!-- INDENTATION -->
+@@ -1225,6 +1347,30 @@
+ <tr valign="top" align="left">
+ <td width="11%"></td>
+ <td width="89%">
++<p><b>Find UU−Encoded Files</b></p></td>
++</table>
++<!-- INDENTATION -->
++<table width="100%" border=0 rules="none" frame="void"
++ cols="2" cellspacing="0" cellpadding="0">
++<tr valign="top" align="left">
++<td width="22%"></td>
++<td width="78%">
++<p>Default: no<br>
++A few viruses store their infected data in UU−encoded
++files, to try to catch out virus scanners. This rarely
++succeeds at all. Setting this option to yes means that you
++can apply filename and filetype checks to the contents of
++UU−encoded files. This may occasionally be useful, in
++which case you should set to yes. This can also be the
++filename of a ruleset.</p>
++</td>
++</table>
++<!-- INDENTATION -->
++<table width="100%" border=0 rules="none" frame="void"
++ cols="2" cellspacing="0" cellpadding="0">
++<tr valign="top" align="left">
++<td width="11%"></td>
++<td width="89%">
+ <p><b>Block Encrypted Messages</b></p></td>
+ </table>
+ <!-- INDENTATION -->
+@@ -1508,7 +1654,7 @@
+ <tr valign="top" align="left">
+ <td width="22%"></td>
+ <td width="78%">
+-<p>Default: yes</p>
++<p>Default: auto</p>
+ <!-- INDENTATION -->
+ <p>Do you want to scan email for viruses? A few people
+ don’t have virus scanner licence and so want to
+@@ -1519,7 +1665,9 @@
+ Scanners = none" instead.<br>
+ If you want to be able to switch scanning on/off for
+ different users or different domains, set this to the
+-filename of a ruleset.</p>
++filename of a ruleset. If you set this to auto then it
++searches for and uses every available installed virus
++scanner.</p>
+ </td>
+ </table>
+ <!-- INDENTATION -->
+@@ -1999,6 +2147,61 @@
+ <tr valign="top" align="left">
+ <td width="11%"></td>
+ <td width="89%">
++<p><b>Use Stricter Phishing Net</b></p></td>
++</table>
++<!-- INDENTATION -->
++<table width="100%" border=0 rules="none" frame="void"
++ cols="2" cellspacing="0" cellpadding="0">
++<tr valign="top" align="left">
++<td width="22%"></td>
++<td width="78%">
++<p>Default: yes</p>
++<!-- INDENTATION -->
++<p>If this is set to yes, then most of the URL in a link
++must match the destination address it claims to take you to.
++This is the default as it is a much stronger test and is
++very hard to maliciously avoid. If this is set to no, then
++just the company name and country (and any names between the
++two, dependent on the specific country) must match. This is
++not as strict as it will not protect you against internal
++malicious sites based within the company being abused. For
++example, it would not find
++www.nasty.company−name.co.uk pretending to be
++www.nice.company−name.co.uk. But it will still detect
++most phishing attacks of the type www.nasty.co.jp versus
++www.nice.co.jp. Depending on the country code it knows how
++many levels of domain need to be checked. This can also be
++the filename of a ruleset.</p>
++</td>
++</table>
++<!-- INDENTATION -->
++<table width="100%" border=0 rules="none" frame="void"
++ cols="2" cellspacing="0" cellpadding="0">
++<tr valign="top" align="left">
++<td width="11%"></td>
++<td width="89%">
++<p><b>Highlight Phishing Fraud</b></p></td>
++</table>
++<!-- INDENTATION -->
++<table width="100%" border=0 rules="none" frame="void"
++ cols="2" cellspacing="0" cellpadding="0">
++<tr valign="top" align="left">
++<td width="22%"></td>
++<td width="78%">
++<p>Default: yes</p>
++<!-- INDENTATION -->
++<p>If a phishing fraud is detected, do you want to highlight
++the tag with a message stating that the link may be to a
++fraudulent web site. This can also be the filename of a
++ruleeset.</p>
++</td>
++</table>
++<!-- INDENTATION -->
++<table width="100%" border=0 rules="none" frame="void"
++ cols="2" cellspacing="0" cellpadding="0">
++<tr valign="top" align="left">
++<td width="11%"></td>
++<td width="89%">
+ <p><b>Phishing Safe Sites File</b></p></td>
+ </table>
+ <!-- INDENTATION -->
+@@ -2026,6 +2229,35 @@
+ <tr valign="top" align="left">
+ <td width="11%"></td>
+ <td width="89%">
++<p><b>Country Sub−Domains List</b></p></td>
++</table>
++<!-- INDENTATION -->
++<table width="100%" border=0 rules="none" frame="void"
++ cols="2" cellspacing="0" cellpadding="0">
++<tr valign="top" align="left">
++<td width="22%"></td>
++<td width="78%">
++<p>Default: %etc−dir%/country.domains.conf</p>
++</td>
++</table>
++<!-- INDENTATION -->
++<table width="100%" border=0 rules="none" frame="void"
++ cols="2" cellspacing="0" cellpadding="0">
++<tr valign="top" align="left">
++<td width="11%"></td>
++<td width="89%">
++<p>This file lists all the countries that use
++2nd−level and 3rd−level domain names to classify
++distinct types of website within their country. This cannot
++be the name of a ruleset, it is just a simple
++setting.</p></td>
++</table>
++<!-- INDENTATION -->
++<table width="100%" border=0 rules="none" frame="void"
++ cols="2" cellspacing="0" cellpadding="0">
++<tr valign="top" align="left">
++<td width="11%"></td>
++<td width="89%">
+ <p><b>Allow IFrame Tags</b></p></td>
+ </table>
+ <!-- INDENTATION -->
+@@ -2317,7 +2549,7 @@
+ <tr valign="top" align="left">
+ <td width="11%"></td>
+ <td width="89%">
+-<p><b>Allow Object Codebase Tags</b></p></td>
++<p><b>Ignored Web Bug Filenames</b></p></td>
+ </table>
+ <!-- INDENTATION -->
+ <table width="100%" border=0 rules="none" frame="void"
+@@ -2325,7 +2557,7 @@
+ <tr valign="top" align="left">
+ <td width="22%"></td>
+ <td width="78%">
+-<p>Default: no</p></td>
++<p>Default:</p></td>
+ </table>
+ <!-- INDENTATION -->
+ <table width="100%" border=0 rules="none" frame="void"
+@@ -2333,12 +2565,70 @@
+ <tr valign="top" align="left">
+ <td width="28%"></td>
+ <td width="72%">
++<p>This is a list of filenames (or parts of filenames) that
++may appear in the filename of a web bug URL. They are only
++checked in the filename, not any directories or hostnames in
++the URL of the possible web bug. If it appears, then the web
++bug is assumed to be a harmless "spacer" for page
++layout purposes and not a real web bug at all. It should be
++a space− and/or comma−separated list of filename
++parts. Note: Use this with care, as spammers may use this to
++circumvent the web bug trap. It is disabled by default
++because of this problem. This can also be the filename of a
++ruleset.</p>
++</td>
++</table>
++<!-- INDENTATION -->
++<table width="100%" border=0 rules="none" frame="void"
++ cols="2" cellspacing="0" cellpadding="0">
++<tr valign="top" align="left">
++<td width="11%"></td>
++<td width="89%">
++<p><b>Web Bug Replacement</b></p></td>
++</table>
++<!-- INDENTATION -->
++<table width="100%" border=0 rules="none" frame="void"
++ cols="2" cellspacing="0" cellpadding="0">
++<tr valign="top" align="left">
++<td width="22%"></td>
++<td width="78%">
++<p>Default:
++http://www.sng.ecs.soton.ac.uk/mailscanner/images/1x1spacer.gif</p>
++<!-- INDENTATION -->
++<p>When a web bug is found, what image do you want to
++replace it with? By replacing it with a real image, the page
++layout still works properly, so the formatting and layout of
++the message is correct. The following is a harmless
++untracked 1x1 pixel transparent image. If this is not
++specified, the the old value of
++"MailScannerWebBug" is used, which of course is
++not an image and may well upset layout of the email. This
++can also be the filename of a ruleset.</p>
++</td>
++</table>
++<!-- INDENTATION -->
++<table width="100%" border=0 rules="none" frame="void"
++ cols="2" cellspacing="0" cellpadding="0">
++<tr valign="top" align="left">
++<td width="11%"></td>
++<td width="89%">
++<p><b>Allow Object Codebase Tags</b></p></td>
++</table>
++<!-- INDENTATION -->
++<table width="100%" border=0 rules="none" frame="void"
++ cols="2" cellspacing="0" cellpadding="0">
++<tr valign="top" align="left">
++<td width="22%"></td>
++<td width="78%">
++<p>Default: no</p>
++<!-- INDENTATION -->
+ <p>Do you want to allow <Object Codebase=...> tags in
+ email messages? This is a bad idea as it leaves you
+ unprotected against various Microsoft−specific
+ security vulnerabilities. But if your users demand it, you
+ can do it. This can also be the filename of a ruleset.
+-Possible values:</p></td>
++Possible values:</p>
++</td>
+ </table>
+ <!-- TABS -->
+ <table width="100%" border=0 rules="none" frame="void"
+@@ -4826,7 +5116,7 @@
+ <tr valign="top" align="left">
+ <td width="22%"></td>
+ <td width="78%">
+-<p>Default: no</p>
++<p>Default: yes</p>
+ <!-- INDENTATION -->
+ <p>Do you want to detect spam using the very good
+ SpamAssassin package? You must have installed SpamAssassin
+@@ -6117,7 +6407,7 @@
+ <tr valign="top" align="left">
+ <td width="11%"></td>
+ <td width="89%">
+-<p><b>SpamAssassin Default Rules Dir</b></p></td>
++<p><b>SpamAssassin Local State Dir</b></p></td>
+ </table>
+ <!-- INDENTATION -->
+ <table width="100%" border=0 rules="none" frame="void"
+@@ -6133,10 +6423,38 @@
+ <tr valign="top" align="left">
+ <td width="28%"></td>
+ <td width="72%">
++<p>The rules created by the "sa−update" tool
++are searched for here. This directory contains the
++spamassassin/3.001001/updates_spamassassin_org directory
++structure beneath it. Only un−comment this setting
++once you have proved that the sa−update cron job has
++run successfully and has created a directory structure under
++the spamassassin directory within this one and has put some
++*.cf files in there. Otherwise it will ignore all your
++current rules!</p>
++</td>
++</table>
++<!-- INDENTATION -->
++<table width="100%" border=0 rules="none" frame="void"
++ cols="2" cellspacing="0" cellpadding="0">
++<tr valign="top" align="left">
++<td width="11%"></td>
++<td width="89%">
++<p><b>SpamAssassin Default Rules Dir</b></p></td>
++</table>
++<!-- INDENTATION -->
++<table width="100%" border=0 rules="none" frame="void"
++ cols="2" cellspacing="0" cellpadding="0">
++<tr valign="top" align="left">
++<td width="22%"></td>
++<td width="78%">
++<p>Default:</p>
++<!-- INDENTATION -->
+ <p>This tells MailScanner where to look for the default
+ rules. If this is set it adds to the list of places that are
+ searched. MailScanner will always look at the following
+-places (even if this option is not set):</p></td>
++places (even if this option is not set):</p>
++</td>
+ </table>
+ <!-- TABS -->
+ <table width="100%" border=0 rules="none" frame="void"
+@@ -6223,8 +6541,8 @@
+ <table width="100%" border=0 rules="none" frame="void"
+ cols="5" cellspacing="0" cellpadding="0">
+ <tr valign="top" align="left">
+-<td width="11%"></td>
+-<td width="20%">
++<td width="22%"></td>
++<td width="9%">
+
+ <p>%d</p>
+ </td>
+@@ -6236,8 +6554,8 @@
+ <td width="54%">
+ </td>
+ <tr valign="top" align="left">
+-<td width="11%"></td>
+-<td width="20%">
++<td width="22%"></td>
++<td width="9%">
+
+ <p>%5.2f</p>
+ </td>
+@@ -6249,8 +6567,8 @@
+ <td width="54%">
+ </td>
+ <tr valign="top" align="left">
+-<td width="11%"></td>
+-<td width="20%">
++<td width="22%"></td>
++<td width="9%">
+
+ <p>%05.1f</p>
+ </td>
+@@ -6261,24 +6579,59 @@
+ </td>
+ <td width="54%">
+ </td>
++</table>
++<!-- INDENTATION -->
++<table width="100%" border=0 rules="none" frame="void"
++ cols="2" cellspacing="0" cellpadding="0">
+ <tr valign="top" align="left">
+ <td width="11%"></td>
+-<td width="20%">
+-
+-<p><b>Debug</b></p>
+-</td>
+-<td width="1%"></td>
+-<td width="14%"></td>
+-<td width="54%">
+-</td>
++<td width="89%">
++<p><b>SpamAssassin Cache Timings</b></p></td>
++</table>
++<!-- INDENTATION -->
++<table width="100%" border=0 rules="none" frame="void"
++ cols="2" cellspacing="0" cellpadding="0">
++<tr valign="top" align="left">
++<td width="22%"></td>
++<td width="78%">
++<p>Default: 1800,300,10800,172800,600</p></td>
+ </table>
+ <!-- INDENTATION -->
+ <table width="100%" border=0 rules="none" frame="void"
+ cols="2" cellspacing="0" cellpadding="0">
+ <tr valign="top" align="left">
++<td width="32%"></td>
++<td width="68%">
++<p>Do not change this unless you absolutely have to, these
++numbers have been carefully calculated. They affect the
++length of time that different types of message are stored in
++the SpamAssassin cache which can be configured earlier in
++this file (look for "Cache"). The numbers are all
++set in seconds. They are:<br>
++1. Non−Spam cache lifetime = 30 minutes<br>
++2. Spam (low scoring) cache lifetime = 5 minutes<br>
++3. High−Scoring spam cache lifetime = 3 hours<br>
++4. Viruses cache lifetime = 2 days<br>
++5. How often to check the cache for expired messages = 10
++minutes</p>
++</td>
++</table>
++<!-- TABS -->
++<table width="100%" border=0 rules="none" frame="void"
++ cols="5" cellspacing="0" cellpadding="0">
++<tr valign="top" align="left">
+ <td width="11%"></td>
+-<td width="89%">
+-<p>Default: no</p></td>
++<td width="7%">
++
++<p><b>Debug</b></p>
++</td>
++<td width="4%"></td>
++<td width="16%">
++
++<p>Default: no</p>
++</td>
++<td width="62%">
++</td>
+ </table>
+ <!-- INDENTATION -->
+ <table width="100%" border=0 rules="none" frame="void"
+@@ -6424,6 +6777,31 @@
+ a "side effect" of doing something useful such as
+ logging lots of information about the batch of messages to a
+ file or an SQL database.</p>
++</td>
++</table>
++<!-- INDENTATION -->
++<table width="100%" border=0 rules="none" frame="void"
++ cols="2" cellspacing="0" cellpadding="0">
++<tr valign="top" align="left">
++<td width="11%"></td>
++<td width="89%">
++<p><b>Always Looked Up Last After Batch</b></p></td>
++</table>
++<!-- INDENTATION -->
++<table width="100%" border=0 rules="none" frame="void"
++ cols="2" cellspacing="0" cellpadding="0">
++<tr valign="top" align="left">
++<td width="22%"></td>
++<td width="78%">
++<p>Default: no</p>
++<!-- INDENTATION -->
++<p>This option is intended for people who want to log
++per−batch information. This is evaluated after the
++"Always Looked Up Last" configuration option for
++each message in the batch. This is looked up once for the
++entire batch. Its value is completely ignored, it is purely
++there to have side effects. If you want to use it, read
++CustomConfig.pm.</p>
+ </td>
+ </table>
+ <!-- INDENTATION -->
Index: files/patch-docs:man:MailScanner.8
===================================================================
RCS file: files/patch-docs:man:MailScanner.8
diff -N files/patch-docs:man:MailScanner.8
--- files/patch-docs:man:MailScanner.8 13 Apr 2006 16:42:25 -0000 1.28
+++ /dev/null 1 Jan 1970 00:00:00 -0000
@@ -1,37 +0,0 @@
---- ../MailScanner-install-4.52.2.orig/docs/man/MailScanner.8 Thu Apr 13 09:25:25 2006
-+++ docs/man/MailScanner.8 Thu Apr 13 09:25:39 2006
-@@ -1,10 +1,10 @@
--.TH "MailScanner" "8" "4.49.7" "Julian Field" "Mail"
-+.TH "MailScanner" "8" "4.52.2" "Julian Field" "Mail"
- .SH "NAME"
- .LP
- MailScanner \- Virus/Spam Scanner for Sendmail, Exim and Postfix
- .SH "SYNOPSIS"
- .LP
--\fBMailScanner\fR [\fI\-v\fR] [\fIconfigfile\fR]
-+\fBMailScanner\fR [\fI\-v\fR] [\fI\-\-lint\fR] [\fI\-\-debug\fR] [\fI\-\-debug\-sa\fR] [\fI\-\-help\fR] [\fIconfigfile\fR]
-
- .SH "DESCRIPTION"
- .LP
-@@ -29,6 +29,21 @@
- \fB\-v\fR
- Prints version information for Mailscanner and all used perl\-modules.
-
-+.TP
-+\fB\-\-lint\fR
-+Checks config file, print what virus scanners you have chosen to use and check SpamAssassin configuration as well.
-+
-+.TP
-+\fB\-\-debug\fR
-+Starts MailScanner in debug mode. See MailScanner.conf "Debug=yes".
-+
-+.TP
-+\fB\-\-debug\-sa\fR
-+Starts MailScanner in debug spamassassin mode. See MailScanner.conf "Debug SpamAssassin=yes".
-+
-+.TP
-+\fB\-\-lint\fR
-+Test MailScanner config and SpamAssassin config.
- .SH "MTA SETUP"
- .LP
- It is important that your MTA only queues incoming mail and does not deliver it automatically. You need two mail queues (incoming and outgoing). Moreover you should setup two instances of your MTA. One that accepts incoming mail and puts it to an incoming queue and one that sends out mail that resides in the outgoing queue.
Index: files/patch-docs:man:MailScanner.8.html
===================================================================
RCS file: files/patch-docs:man:MailScanner.8.html
diff -N files/patch-docs:man:MailScanner.8.html
--- files/patch-docs:man:MailScanner.8.html 13 Apr 2006 16:42:25 -0000 1.21
+++ /dev/null 1 Jan 1970 00:00:00 -0000
@@ -1,407 +0,0 @@
---- ../MailScanner-install-4.52.2.orig/docs/man/MailScanner.8.html Thu Apr 13 09:25:25 2006
-+++ docs/man/MailScanner.8.html Thu Apr 13 09:25:42 2006
-@@ -1,168 +1,236 @@
--<!-- Creator : groff version 1.19 -->
--<!-- CreationDate: Wed Jan 4 13:45:56 2006 -->
--<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
--"http://www.w3.org/TR/html4/loose.dtd">
--<html>
--<head>
--<meta name="generator" content="groff -Thtml, see www.gnu.org">
--<meta http-equiv="Content-Type" content="text/html; charset=US-ASCII">
--<meta name="Content-Style" content="text/css">
--<title>MailScanner</title>
--</head>
--<body>
--
--<h1 align=center>MailScanner</h1>
--<a href="#NAME">NAME</a><br>
--<a href="#SYNOPSIS">SYNOPSIS</a><br>
--<a href="#DESCRIPTION">DESCRIPTION</a><br>
--<a href="#MTA SETUP">MTA SETUP</a><br>
--<a href="#SEE ALSO">SEE ALSO</a><br>
--
--<hr>
--<a name="NAME"></a>
--<h2>NAME</h2>
--<!-- INDENTATION -->
--<table width="100%" border=0 rules="none" frame="void"
-- cols="2" cellspacing="0" cellpadding="0">
--<tr valign="top" align="left">
--<td width="11%"></td>
--<td width="89%">
--<p>MailScanner − Virus/Spam Scanner for Sendmail, Exim
--and Postfix</p>
--</td>
--</table>
--<a name="SYNOPSIS"></a>
--<h2>SYNOPSIS</h2>
--<!-- INDENTATION -->
--<table width="100%" border=0 rules="none" frame="void"
-- cols="2" cellspacing="0" cellpadding="0">
--<tr valign="top" align="left">
--<td width="11%"></td>
--<td width="89%">
--<p><b>MailScanner</b> [<i>−v</i>]
--[<i>configfile</i>]</p>
--</td>
--</table>
--<a name="DESCRIPTION"></a>
--<h2>DESCRIPTION</h2>
--<!-- INDENTATION -->
--<table width="100%" border=0 rules="none" frame="void"
-- cols="2" cellspacing="0" cellpadding="0">
--<tr valign="top" align="left">
--<td width="11%"></td>
--<td width="89%">
--<p><b>MailScanner</b> starts the main MailScanner process.
--[<i>configfile</i>] should point to a valid MailScanner
--configuration file (see MailScanner.conf(5) for details).
--The default location for this file depends on the operating
--system.</p>
--<!-- INDENTATION -->
--<p>Linux: /etc/MailScanner/MailScanner.conf</p>
--<!-- INDENTATION -->
--<p>FreeBSD: /usr/local/etc/MailScanner/MailScanner.conf</p>
--<!-- INDENTATION -->
--<p>Other: /opt/MailScanner/etc/MailScanner.conf</p>
--<!-- INDENTATION -->
--<p>The main process then spawns <i>n</i> number of child
--processes. <i>n</i> is configured in [<i>configfile</i>]
--with the option "Max Children". Each process waits
--for messages to appear in the "Incoming Queue
--Dir", processes these messages and then puts them in
--the "Outgoing Queue Dir". You may need to adjust
--the configuration of your MTA (or the startup of your MTA)
--to make it work with MailScanner.</p>
--</td>
--</table>
--<!-- TABS -->
--<table width="100%" border=0 rules="none" frame="void"
-- cols="4" cellspacing="0" cellpadding="0">
--<tr valign="top" align="left">
--<td width="11%"></td>
--<td width="3%">
--
--<p><b>−v</b></p>
--</td>
--<td width="8%"></td>
--<td width="78%">
--
--<p>Prints version information for Mailscanner and all used
--perl−modules.</p>
--</td>
--</table>
--<a name="MTA SETUP"></a>
--<h2>MTA SETUP</h2>
--<!-- INDENTATION -->
--<table width="100%" border=0 rules="none" frame="void"
-- cols="2" cellspacing="0" cellpadding="0">
--<tr valign="top" align="left">
--<td width="11%"></td>
--<td width="89%">
--<p>It is important that your MTA only queues incoming mail
--and does not deliver it automatically. You need two mail
--queues (incoming and outgoing). Moreover you should setup
--two instances of your MTA. One that accepts incoming mail
--and puts it to an incoming queue and one that sends out mail
--that resides in the outgoing queue.</p>
--<!-- INDENTATION -->
--<p>A common setup for Sendmail could look like this:</p>
--<!-- INDENTATION -->
--<p>1. Verify that you already have one queue (e.g. in
--/var/spool/mqueue).</p>
--<!-- INDENTATION -->
--<p>2. Create a second queue (e.g. /var/spool/mqueue.in) and
--apply the same owner/group/mode.</p>
--<!-- INDENTATION -->
--<p>3. Change your sendmail startup from</p>
--<!-- INDENTATION -->
--<p>sendmail −bd −q15m (or similar)</p>
--<!-- INDENTATION -->
--<p>to</p>
--<!-- INDENTATION -->
--<p>sendmail −bd −OPrivacyOptions=noetrn
--−ODeliveryMode=queueonly
--−OQueueDirectory=/var/spool/mqueue.in<br>
--sendmail −q15m</p>
--<!-- INDENTATION -->
--<p>A similar setup for Exim could look like this:</p>
--<!-- INDENTATION -->
--<p>1. Create two queues (e.g. /var/spool/exim.in and
--/var/spool/exim.out) with appropriate owner/group/mode (e.g.
--owner=mailnull, group=mail, mode=750).</p>
--<!-- INDENTATION -->
--<p>2. Create two exim configurations (e.g.
--/usr/local/etc/exim/configure.in,
--/usr/local/etc/exim/configure.out).</p>
--<!-- INDENTATION -->
--<p>3. Make sure that the incoming exim configuration only
--queues mails and never delivers mail itself. This can be
--achieved by using the Exim config option "queue_only =
--true" and/or a special router definition (Exim 4
--syntax):</p>
--<!-- INDENTATION -->
--<p>defer_router:<br>
--driver = manualroute<br>
--self = defer<br>
--transport = remote_smtp<br>
--route_list = * 127.0.0.1 byname<br>
--verify = false</p>
--<!-- INDENTATION -->
--<p>4. Start two exim instances:</p>
--<!-- INDENTATION -->
--<p>exim −C /usr/local/etc/exim/configure.in<br>
--exim −C /usr/local/etc/exim/configure.out</p>
--</td>
--</table>
--<a name="SEE ALSO"></a>
--<h2>SEE ALSO</h2>
--<!-- INDENTATION -->
--<table width="100%" border=0 rules="none" frame="void"
-- cols="2" cellspacing="0" cellpadding="0">
--<tr valign="top" align="left">
--<td width="11%"></td>
--<td width="89%">
--<p>MailScanner.conf(5)</p>
--</td>
--</table>
--<hr>
--</body>
--</html>
-+<!-- Creator : groff version 1.19 -->
-+<!-- CreationDate: Thu Apr 13 09:24:53 2006 -->
-+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
-+"http://www.w3.org/TR/html4/loose.dtd">
-+<html>
-+<head>
-+<meta name="generator" content="groff -Thtml, see www.gnu.org">
-+<meta http-equiv="Content-Type" content="text/html; charset=US-ASCII">
-+<meta name="Content-Style" content="text/css">
-+<title>MailScanner</title>
-+</head>
-+<body>
-+
-+<h1 align=center>MailScanner</h1>
-+<a href="#NAME">NAME</a><br>
-+<a href="#SYNOPSIS">SYNOPSIS</a><br>
-+<a href="#DESCRIPTION">DESCRIPTION</a><br>
-+<a href="#MTA SETUP">MTA SETUP</a><br>
-+<a href="#SEE ALSO">SEE ALSO</a><br>
-+
-+<hr>
-+<a name="NAME"></a>
-+<h2>NAME</h2>
-+<!-- INDENTATION -->
-+<table width="100%" border=0 rules="none" frame="void"
-+ cols="2" cellspacing="0" cellpadding="0">
-+<tr valign="top" align="left">
-+<td width="11%"></td>
-+<td width="89%">
-+<p>MailScanner − Virus/Spam Scanner for Sendmail, Exim
-+and Postfix</p>
-+</td>
-+</table>
-+<a name="SYNOPSIS"></a>
-+<h2>SYNOPSIS</h2>
-+<!-- INDENTATION -->
-+<table width="100%" border=0 rules="none" frame="void"
-+ cols="2" cellspacing="0" cellpadding="0">
-+<tr valign="top" align="left">
-+<td width="11%"></td>
-+<td width="89%">
-+<p><b>MailScanner</b> [<i>−v</i>]
-+[<i>−−lint</i>] [<i>−−debug</i>]
-+[<i>−−debug−sa</i>]
-+[<i>−−help</i>] [<i>configfile</i>]</p>
-+</td>
-+</table>
-+<a name="DESCRIPTION"></a>
-+<h2>DESCRIPTION</h2>
-+<!-- INDENTATION -->
-+<table width="100%" border=0 rules="none" frame="void"
-+ cols="2" cellspacing="0" cellpadding="0">
-+<tr valign="top" align="left">
-+<td width="11%"></td>
-+<td width="89%">
-+<p><b>MailScanner</b> starts the main MailScanner process.
-+[<i>configfile</i>] should point to a valid MailScanner
-+configuration file (see MailScanner.conf(5) for details).
-+The default location for this file depends on the operating
-+system.</p>
-+<!-- INDENTATION -->
-+<p>Linux: /etc/MailScanner/MailScanner.conf</p>
-+<!-- INDENTATION -->
-+<p>FreeBSD: /usr/local/etc/MailScanner/MailScanner.conf</p>
-+<!-- INDENTATION -->
-+<p>Other: /opt/MailScanner/etc/MailScanner.conf</p>
-+<!-- INDENTATION -->
-+<p>The main process then spawns <i>n</i> number of child
-+processes. <i>n</i> is configured in [<i>configfile</i>]
-+with the option "Max Children". Each process waits
-+for messages to appear in the "Incoming Queue
-+Dir", processes these messages and then puts them in
-+the "Outgoing Queue Dir". You may need to adjust
-+the configuration of your MTA (or the startup of your MTA)
-+to make it work with MailScanner.</p>
-+</td>
-+</table>
-+<!-- TABS -->
-+<table width="100%" border=0 rules="none" frame="void"
-+ cols="4" cellspacing="0" cellpadding="0">
-+<tr valign="top" align="left">
-+<td width="11%"></td>
-+<td width="9%">
-+
-+<p><b>−v</b></p>
-+</td>
-+<td width="2%"></td>
-+<td width="78%">
-+
-+<p>Prints version information for Mailscanner and all used
-+perl−modules.</p>
-+</td>
-+<tr valign="top" align="left">
-+<td width="11%"></td>
-+<td width="9%">
-+
-+<p><b>−−lint</b></p>
-+</td>
-+<td width="2%"></td>
-+<td width="78%">
-+
-+<p>Checks config file, print what virus scanners you have
-+chosen to use and check SpamAssassin configuration as
-+well.</p>
-+</td>
-+</table>
-+<!-- INDENTATION -->
-+<table width="100%" border=0 rules="none" frame="void"
-+ cols="2" cellspacing="0" cellpadding="0">
-+<tr valign="top" align="left">
-+<td width="11%"></td>
-+<td width="89%">
-+<p><b>−−debug</b></p></td>
-+</table>
-+<!-- INDENTATION -->
-+<table width="100%" border=0 rules="none" frame="void"
-+ cols="2" cellspacing="0" cellpadding="0">
-+<tr valign="top" align="left">
-+<td width="22%"></td>
-+<td width="78%">
-+<p>Starts MailScanner in debug mode. See MailScanner.conf
-+"Debug=yes".</p>
-+</td>
-+</table>
-+<!-- INDENTATION -->
-+<table width="100%" border=0 rules="none" frame="void"
-+ cols="2" cellspacing="0" cellpadding="0">
-+<tr valign="top" align="left">
-+<td width="11%"></td>
-+<td width="89%">
-+<p><b>−−debug−sa</b></p></td>
-+</table>
-+<!-- INDENTATION -->
-+<table width="100%" border=0 rules="none" frame="void"
-+ cols="2" cellspacing="0" cellpadding="0">
-+<tr valign="top" align="left">
-+<td width="22%"></td>
-+<td width="78%">
-+<p>Starts MailScanner in debug spamassassin mode. See
-+MailScanner.conf "Debug SpamAssassin=yes".</p>
-+</td>
-+</table>
-+<!-- TABS -->
-+<table width="100%" border=0 rules="none" frame="void"
-+ cols="5" cellspacing="0" cellpadding="0">
-+<tr valign="top" align="left">
-+<td width="11%"></td>
-+<td width="9%">
-+
-+<p><b>−−lint</b></p>
-+</td>
-+<td width="2%"></td>
-+<td width="73%">
-+
-+<p>Test MailScanner config and SpamAssassin config.</p>
-+</td>
-+<td width="5%">
-+</td>
-+</table>
-+<a name="MTA SETUP"></a>
-+<h2>MTA SETUP</h2>
-+<!-- INDENTATION -->
-+<table width="100%" border=0 rules="none" frame="void"
-+ cols="2" cellspacing="0" cellpadding="0">
-+<tr valign="top" align="left">
-+<td width="11%"></td>
-+<td width="89%">
-+<p>It is important that your MTA only queues incoming mail
-+and does not deliver it automatically. You need two mail
-+queues (incoming and outgoing). Moreover you should setup
-+two instances of your MTA. One that accepts incoming mail
-+and puts it to an incoming queue and one that sends out mail
-+that resides in the outgoing queue.</p>
-+<!-- INDENTATION -->
-+<p>A common setup for Sendmail could look like this:</p>
-+<!-- INDENTATION -->
-+<p>1. Verify that you already have one queue (e.g. in
-+/var/spool/mqueue).</p>
-+<!-- INDENTATION -->
-+<p>2. Create a second queue (e.g. /var/spool/mqueue.in) and
-+apply the same owner/group/mode.</p>
-+<!-- INDENTATION -->
-+<p>3. Change your sendmail startup from</p>
-+<!-- INDENTATION -->
-+<p>sendmail −bd −q15m (or similar)</p>
-+<!-- INDENTATION -->
-+<p>to</p>
-+<!-- INDENTATION -->
-+<p>sendmail −bd −OPrivacyOptions=noetrn
-+−ODeliveryMode=queueonly
-+−OQueueDirectory=/var/spool/mqueue.in<br>
-+sendmail −q15m</p>
-+<!-- INDENTATION -->
-+<p>A similar setup for Exim could look like this:</p>
-+<!-- INDENTATION -->
-+<p>1. Create two queues (e.g. /var/spool/exim.in and
-+/var/spool/exim.out) with appropriate owner/group/mode (e.g.
-+owner=mailnull, group=mail, mode=750).</p>
-+<!-- INDENTATION -->
-+<p>2. Create two exim configurations (e.g.
-+/usr/local/etc/exim/configure.in,
-+/usr/local/etc/exim/configure.out).</p>
-+<!-- INDENTATION -->
-+<p>3. Make sure that the incoming exim configuration only
-+queues mails and never delivers mail itself. This can be
-+achieved by using the Exim config option "queue_only =
-+true" and/or a special router definition (Exim 4
-+syntax):</p>
-+<!-- INDENTATION -->
-+<p>defer_router:<br>
-+driver = manualroute<br>
-+self = defer<br>
-+transport = remote_smtp<br>
-+route_list = * 127.0.0.1 byname<br>
-+verify = false</p>
-+<!-- INDENTATION -->
-+<p>4. Start two exim instances:</p>
-+<!-- INDENTATION -->
-+<p>exim −C /usr/local/etc/exim/configure.in<br>
-+exim −C /usr/local/etc/exim/configure.out</p>
-+</td>
-+</table>
-+<a name="SEE ALSO"></a>
-+<h2>SEE ALSO</h2>
-+<!-- INDENTATION -->
-+<table width="100%" border=0 rules="none" frame="void"
-+ cols="2" cellspacing="0" cellpadding="0">
-+<tr valign="top" align="left">
-+<td width="11%"></td>
-+<td width="89%">
-+<p>MailScanner.conf(5)</p>
-+</td>
-+</table>
-+<hr>
-+</body>
-+</html>
Index: files/patch-docs:man:MailScanner.conf.5
===================================================================
RCS file: files/patch-docs:man:MailScanner.conf.5
diff -N files/patch-docs:man:MailScanner.conf.5
--- files/patch-docs:man:MailScanner.conf.5 13 Apr 2006 16:42:25 -0000 1.29
+++ /dev/null 1 Jan 1970 00:00:00 -0000
@@ -1,150 +0,0 @@
---- ../MailScanner-install-4.52.2.orig/docs/man/MailScanner.conf.5 Thu Apr 13 09:25:25 2006
-+++ docs/man/MailScanner.conf.5 Thu Apr 13 09:25:46 2006
-@@ -1,4 +1,4 @@
--.TH "MailScanner.conf" "5" "4.50.1" "Julian Field" "Mail"
-+.TH "MailScanner.conf" "5" "4.52.2" "Julian Field" "Mail"
- .SH "NAME"
- .LP
- MailScanner.conf \- Main configuration for MailScanner
-@@ -364,6 +364,22 @@
- Should we use a TNEF decoder (external or Perl module)? This should be "yes" unless the scanner you are using (Sophos, McAfee) has the facility built\-in. However, if you set it to "no", then the filenames within the TNEF attachment will not be checked against the filename rules.
-
- .TP
-+\fBUse TNEF Contents\fR
-+Default: replace
-+.br
-+When the TNEF (winmail.dat) attachments are expanded, should the attachments contained in there be added to the list of attachments in the message? If you set this to "add" or "replace" then recipients of messages sent in "Outlook Rich Text Format" (TNEF) will be able to read the attachments if they are not using Microsoft Outlook.
-+.br
-+.RS 7
-+.IP \(bu 4
-+no: Leave winmail.dat TNEF attachments alone.
-+.IP \(bu 4
-+add: Add the contents of winmail.dat as extra attachments, but also still include the winmail.dat file itself. This will result in TNEF messages being doubled in size.
-+.IP \(bu 4
-+replace: Replace the winmail.dat TNEF attachment with the files it contains, and delete the original winmail.dat file itself. This means the message stays the same size, but is usable by non\-Outlook recipients.
-+.RE
-+
-+
-+.TP
- \fBDeliver Unparsable TNEF\fR
- Default: no
- .br
-@@ -423,6 +439,12 @@
- The maximum length of time the "unrar" command is allowed to run for 1 RAR archive (in seconds)
-
- .TP
-+\fBFind UU\-Encoded Files\fR
-+Default: no
-+.br
-+A few viruses store their infected data in UU\-encoded files, to try to catch out virus scanners. This rarely succeeds at all. Setting this option to yes means that you can apply filename and filetype checks to the contents of UU\-encoded files. This may occasionally be useful, in which case you should set to yes. This can also be the filename of a ruleset.
-+
-+.TP
- \fBBlock Encrypted Messages\fR
- Default: no
- .br
-@@ -521,7 +543,7 @@
- .SH "Virus scanning and vulnerability testing"
- .TP
- \fBVirus Scanning\fR
--Default: yes
-+Default: auto
- .br
-
- .br
-@@ -529,7 +551,7 @@
- .br
- NOTE: Switching this to no completely disables all virus\-scanning functionality. If you just want to switch of actual virus scanning, then set "Virus Scanners = none" instead.
- .br
--If you want to be able to switch scanning on/off for different users or different domains, set this to the filename of a ruleset.
-+If you want to be able to switch scanning on/off for different users or different domains, set this to the filename of a ruleset. If you set this to auto then it searches for and uses every available installed virus scanner.
-
- .TP
- \fBVirus Scanners\fR
-@@ -686,6 +708,23 @@
- .br
- While detecting "Phishing" attacks, do you also want to point out links to numeric IP addresses. Genuine links to totally numeric IP addresses are very rare, so this option is set to "yes" by default. If a numeric IP address is found in a link, the same phishing warning message is used as in the Find Phishing Fraud option above. This value cannot be the name of a ruleset, only a simple yes or no.
-
-+.TP
-+\fBUse Stricter Phishing Net\fR
-+Default: yes
-+.br
-+
-+.br
-+If this is set to yes, then most of the URL in a link must match the destination address it claims to take you to. This is the default as it is a much stronger test and is very hard to maliciously avoid. If this is set to no, then just the company name and country (and any names between the two, dependent on the specific country) must match. This is not as strict as it will not protect you against internal malicious sites based within the company being abused. For example, it would not find www.nasty.company\-name.co.uk pretending to be www.nice.company\-name.co.uk. But it will still detect most phishing attacks of the type www.nasty.co.jp versus www.nice.co.jp. Depending on the country code it knows how many levels of domain need to be checked. This can also be the filename of a ruleset.
-+
-+
-+.TP
-+\fBHighlight Phishing Fraud\fR
-+Default: yes
-+.br
-+
-+.br
-+If a phishing fraud is detected, do you want to highlight the tag with a message stating that the link may be to a fraudulent web site. This can also be the filename of a ruleeset.
-+
-
- .TP
- \fBPhishing Safe Sites File\fR
-@@ -695,6 +734,15 @@
- .br
- There are some companies, such as banks, that insist on sending out email messages with links in them that are caught by the "Find Phishing Fraud" test described above. This is the name of a file which contains a list of link destinations which should be ignored in the test. This may, for example, contain the known websites of some banks. See the file itself for more information. This can only be the name of the file containing the list, it *cannot* be the filename of a ruleset.
-
-+.TP
-+\fBCountry Sub\-Domains List\fR
-+Default: %etc\-dir%/country.domains.conf
-+.br
-+
-+.br
-+.TP
-+This file lists all the countries that use 2nd\-level and 3rd\-level domain names to classify distinct types of website within their country. This cannot be the name of a ruleset, it is just a simple setting.
-+
-
- .TP
- \fBAllow IFrame Tags\fR
-@@ -1682,7 +1730,7 @@
- .SH "SpamAssassin"
- .TP
- \fBUse SpamAssassin\fR
--Default: no
-+Default: yes
- .br
-
- .br
-@@ -2113,6 +2161,22 @@
- .RE
-
- .TP
-+\fBSpamAssassin Cache Timings\fR
-+Default: 1800,300,10800,172800,600
-+.br
-+Do not change this unless you absolutely have to, these numbers have been carefully calculated. They affect the length of time that different types of message are stored in the SpamAssassin cache which can be configured earlier in this file (look for "Cache"). The numbers are all set in seconds. They are:
-+.br
-+1. Non\-Spam cache lifetime = 30 minutes
-+.br
-+2. Spam (low scoring) cache lifetime = 5 minutes
-+.br
-+3. High\-Scoring spam cache lifetime = 3 hours
-+.br
-+4. Viruses cache lifetime = 2 days
-+.br
-+5. How often to check the cache for expired messages = 10 minutes
-+
-+.TP
- \fBDebug\fR
- Default: no
- .br
-@@ -2167,6 +2231,15 @@
-
- .br
- The value of the option is actually never used, but it is evaluated at the end of processing a batch of messages. It is designed to be used in conjunction with a Custom Function. The Custom Function should then be written to have a "side effect" of doing something useful such as logging lots of information about the batch of messages to a file or an SQL database.
-+
-+
-+.TP
-+\fBAlways Looked Up Last After Batch\fR
-+Default: no
-+.br
-+
-+.br
-+This option is intended for people who want to log per\-batch information. This is evaluated after the "Always Looked Up Last" configuration option for each message in the batch. This is looked up once for the entire batch. Its value is completely ignored, it is purely there to have side effects. If you want to use it, read CustomConfig.pm.
-
- .TP
- \fBDeliver in Background\fR
>Release-Note:
>Audit-Trail:
>Unformatted:
More information about the freebsd-ports-bugs
mailing list