Attachment #69568 for bug #101766

View | Details | Raw Unified | Return to bug 101766
Collapse All | Expand All




#

PORTNAME=	MailScanner
PORTVERSION=	4.55.10
PORTREVISION=	2
CATEGORIES=	mail
MASTER_SITES=	http://www.mailscanner.info/files/4/tar/
DISTNAME=	${PORTNAME}-install-${PORTVERSION}-${PATCHLEVEL}


CONFLICTS=	MailScanner-devel-[0-9]*

PATCHLEVEL=	3

USE_PERL5=	yes


SUB_FILES=	pkg-message

MAN8=		MailScanner.8
MLINKS=		MailScanner.8 mailscanner.8
MLINKS=		MailScanner.8 mailscanner.8 \
		MailScanner.conf.5 mailscanner.conf.5

.include <bsd.port.pre.mk>


RUN_DEPENDS+=	bdc:${PORTSDIR}/security/bdc
.endif

DOC_FILES=	INSTALL.FreeBSD INSTALL.OpenBSD README
ETC_FILES=	MailScanner.conf filename.rules.conf \
		filetype.rules.conf spam.assassin.prefs.conf \
		spam.lists.conf virus.scanners.conf \

	#
	# Step 6: Docs & Manpages
	#
	# Manpage
.if !defined(NOPORTDOCS)
	${MKDIR} ${DOCSDIR}
	${INSTALL_DATA} ${FILESDIR}/README.FreeBSD.port ${DOCSDIR}
	${INSTALL_DATA} ${FILESDIR}/CHANGES.port ${DOCSDIR}
	cd ${WRKSRC} && ${INSTALL_DATA} ${DOC_FILES} ${DOCSDIR}
	cd ${WRKSRC}/docs && \
		${FIND} * -type d -exec ${MKDIR} ${DOCSDIR}/{} \; && \
		${FIND} * -type f ! -name "*.orig" -exec \
			${INSTALL_DATA} {} ${DOCSDIR}/{} \;
.endif
	cd ${WRKSRC}/docs/man && \
		${INSTALL_MAN} ${MAN5} ${MAN5PREFIX}/man/man5 && \
		${INSTALL_MAN} ${MAN8} ${MAN8PREFIX}/man/man8
	# Sophos install script
	${INSTALL_SCRIPT} ${FILESDIR}/Sophos.install.freebsd ${DOCSDIR}
	cd ${WRKSRC} && ${INSTALL_DATA} ${DOC_FILES} ${DOCSDIR}
.endif	      
	cd ${FILESDIR} && \
		${INSTALL_MAN} ${MAN8} ${MAN5PREFIX}/man/man8
	${PERL} -pi -e \
		's,%%LOCALBASE%%,${LOCALBASE},g; \
		s,%%PREFIX%%,${PREFIX},g;' \

Lines 1-3 Link Here

(-)distinfo (-3 / +3 lines)
1	MD5 (MailScanner-install-4.54.6-1.tar.gz) = 417189551d855e260f044943d9317abb	1	MD5 (MailScanner-install-4.55.10-3.tar.gz) = e461e100d07d6d0aadb570b0ec66dd0c
2	SHA256 (MailScanner-install-4.54.6-1.tar.gz) = 34c65d72a766ce1687963ab91239ecd4024a3f2b156a6c634b30cae4edca035b	2	SHA256 (MailScanner-install-4.55.10-3.tar.gz) = 1d638c903045834f6055ee376181f068d6eb006024202d786bfbb98ba4047b8d
3	SIZE (MailScanner-install-4.54.6-1.tar.gz) = 8841175	3	SIZE (MailScanner-install-4.55.10-3.tar.gz) = 7047731

Lines 128-133 Link Here

(-)pkg-plist (-123 / +47 lines)
128	%%DATADIR%%/reports/ca/stored.content.message.txt.sample	128	%%DATADIR%%/reports/ca/stored.content.message.txt.sample
129	%%DATADIR%%/reports/ca/stored.filename.message.txt.sample	129	%%DATADIR%%/reports/ca/stored.filename.message.txt.sample
130	%%DATADIR%%/reports/ca/stored.virus.message.txt.sample	130	%%DATADIR%%/reports/ca/stored.virus.message.txt.sample
		131	%%DATADIR%%/reports/ca/deleted.size.message.txt.sample
		132	%%DATADIR%%/reports/ca/sender.size.report.txt.sample
		133	%%DATADIR%%/reports/ca/stored.size.message.txt.sample
131	%%DATADIR%%/reports/cy+en/deleted.content.message.txt.sample	134	%%DATADIR%%/reports/cy+en/deleted.content.message.txt.sample
132	%%DATADIR%%/reports/cy+en/deleted.filename.message.txt.sample	135	%%DATADIR%%/reports/cy+en/deleted.filename.message.txt.sample
133	%%DATADIR%%/reports/cy+en/deleted.virus.message.txt.sample	136	%%DATADIR%%/reports/cy+en/deleted.virus.message.txt.sample
Lines 152-157 Link Here
152	%%DATADIR%%/reports/cy+en/stored.content.message.txt.sample	155	%%DATADIR%%/reports/cy+en/stored.content.message.txt.sample
153	%%DATADIR%%/reports/cy+en/stored.filename.message.txt.sample	156	%%DATADIR%%/reports/cy+en/stored.filename.message.txt.sample
154	%%DATADIR%%/reports/cy+en/stored.virus.message.txt.sample	157	%%DATADIR%%/reports/cy+en/stored.virus.message.txt.sample
		158	%%DATADIR%%/reports/cy+en/deleted.size.message.txt.sample
		159	%%DATADIR%%/reports/cy+en/sender.size.report.txt.sample
		160	%%DATADIR%%/reports/cy+en/stored.size.message.txt.sample
155	%%DATADIR%%/reports/cz/deleted.content.message.txt.sample	161	%%DATADIR%%/reports/cz/deleted.content.message.txt.sample
156	%%DATADIR%%/reports/cz/deleted.filename.message.txt.sample	162	%%DATADIR%%/reports/cz/deleted.filename.message.txt.sample
157	%%DATADIR%%/reports/cz/deleted.virus.message.txt.sample	163	%%DATADIR%%/reports/cz/deleted.virus.message.txt.sample
Lines 176-181 Link Here
176	%%DATADIR%%/reports/cz/stored.content.message.txt.sample	182	%%DATADIR%%/reports/cz/stored.content.message.txt.sample
177	%%DATADIR%%/reports/cz/stored.filename.message.txt.sample	183	%%DATADIR%%/reports/cz/stored.filename.message.txt.sample
178	%%DATADIR%%/reports/cz/stored.virus.message.txt.sample	184	%%DATADIR%%/reports/cz/stored.virus.message.txt.sample
		185	%%DATADIR%%/reports/cz/deleted.size.message.txt.sample
		186	%%DATADIR%%/reports/cz/sender.size.report.txt.sample
		187	%%DATADIR%%/reports/cz/stored.size.message.txt.sample
179	%%DATADIR%%/reports/de/README.1ST.sample	188	%%DATADIR%%/reports/de/README.1ST.sample
180	%%DATADIR%%/reports/de/deleted.content.message.txt.sample	189	%%DATADIR%%/reports/de/deleted.content.message.txt.sample
181	%%DATADIR%%/reports/de/deleted.filename.message.txt.sample	190	%%DATADIR%%/reports/de/deleted.filename.message.txt.sample
Lines 201-206 Link Here
201	%%DATADIR%%/reports/de/stored.content.message.txt.sample	210	%%DATADIR%%/reports/de/stored.content.message.txt.sample
202	%%DATADIR%%/reports/de/stored.filename.message.txt.sample	211	%%DATADIR%%/reports/de/stored.filename.message.txt.sample
203	%%DATADIR%%/reports/de/stored.virus.message.txt.sample	212	%%DATADIR%%/reports/de/stored.virus.message.txt.sample
		213	%%DATADIR%%/reports/de/deleted.size.message.txt.sample
		214	%%DATADIR%%/reports/de/sender.size.report.txt.sample
		215	%%DATADIR%%/reports/de/stored.size.message.txt.sample
204	%%DATADIR%%/reports/dk/deleted.content.message.txt.sample	216	%%DATADIR%%/reports/dk/deleted.content.message.txt.sample
205	%%DATADIR%%/reports/dk/deleted.filename.message.txt.sample	217	%%DATADIR%%/reports/dk/deleted.filename.message.txt.sample
206	%%DATADIR%%/reports/dk/deleted.virus.message.txt.sample	218	%%DATADIR%%/reports/dk/deleted.virus.message.txt.sample
Lines 225-230 Link Here
225	%%DATADIR%%/reports/dk/stored.content.message.txt.sample	237	%%DATADIR%%/reports/dk/stored.content.message.txt.sample
226	%%DATADIR%%/reports/dk/stored.filename.message.txt.sample	238	%%DATADIR%%/reports/dk/stored.filename.message.txt.sample
227	%%DATADIR%%/reports/dk/stored.virus.message.txt.sample	239	%%DATADIR%%/reports/dk/stored.virus.message.txt.sample
		240	%%DATADIR%%/reports/dk/deleted.size.message.txt.sample
		241	%%DATADIR%%/reports/dk/sender.size.report.txt.sample
		242	%%DATADIR%%/reports/dk/stored.size.message.txt.sample
228	%%DATADIR%%/reports/en/deleted.content.message.txt.sample	243	%%DATADIR%%/reports/en/deleted.content.message.txt.sample
229	%%DATADIR%%/reports/en/deleted.filename.message.txt.sample	244	%%DATADIR%%/reports/en/deleted.filename.message.txt.sample
230	%%DATADIR%%/reports/en/deleted.virus.message.txt.sample	245	%%DATADIR%%/reports/en/deleted.virus.message.txt.sample
Lines 249-254 Link Here
249	%%DATADIR%%/reports/en/stored.content.message.txt.sample	264	%%DATADIR%%/reports/en/stored.content.message.txt.sample
250	%%DATADIR%%/reports/en/stored.filename.message.txt.sample	265	%%DATADIR%%/reports/en/stored.filename.message.txt.sample
251	%%DATADIR%%/reports/en/stored.virus.message.txt.sample	266	%%DATADIR%%/reports/en/stored.virus.message.txt.sample
		267	%%DATADIR%%/reports/en/deleted.size.message.txt.sample
		268	%%DATADIR%%/reports/en/sender.size.report.txt.sample
		269	%%DATADIR%%/reports/en/stored.size.message.txt.sample
252	%%DATADIR%%/reports/es/deleted.content.message.txt.sample	270	%%DATADIR%%/reports/es/deleted.content.message.txt.sample
253	%%DATADIR%%/reports/es/deleted.filename.message.txt.sample	271	%%DATADIR%%/reports/es/deleted.filename.message.txt.sample
254	%%DATADIR%%/reports/es/deleted.virus.message.txt.sample	272	%%DATADIR%%/reports/es/deleted.virus.message.txt.sample
Lines 273-278 Link Here
273	%%DATADIR%%/reports/es/stored.content.message.txt.sample	291	%%DATADIR%%/reports/es/stored.content.message.txt.sample
274	%%DATADIR%%/reports/es/stored.filename.message.txt.sample	292	%%DATADIR%%/reports/es/stored.filename.message.txt.sample
275	%%DATADIR%%/reports/es/stored.virus.message.txt.sample	293	%%DATADIR%%/reports/es/stored.virus.message.txt.sample
		294	%%DATADIR%%/reports/es/deleted.size.message.txt.sample
		295	%%DATADIR%%/reports/es/sender.size.report.txt.sample
		296	%%DATADIR%%/reports/es/stored.size.message.txt.sample
276	%%DATADIR%%/reports/fr/deleted.content.message.txt.sample	297	%%DATADIR%%/reports/fr/deleted.content.message.txt.sample
277	%%DATADIR%%/reports/fr/deleted.filename.message.txt.sample	298	%%DATADIR%%/reports/fr/deleted.filename.message.txt.sample
278	%%DATADIR%%/reports/fr/deleted.virus.message.txt.sample	299	%%DATADIR%%/reports/fr/deleted.virus.message.txt.sample
Lines 297-302 Link Here
297	%%DATADIR%%/reports/fr/stored.content.message.txt.sample	318	%%DATADIR%%/reports/fr/stored.content.message.txt.sample
298	%%DATADIR%%/reports/fr/stored.filename.message.txt.sample	319	%%DATADIR%%/reports/fr/stored.filename.message.txt.sample
299	%%DATADIR%%/reports/fr/stored.virus.message.txt.sample	320	%%DATADIR%%/reports/fr/stored.virus.message.txt.sample
		321	%%DATADIR%%/reports/fr/deleted.size.message.txt.sample
		322	%%DATADIR%%/reports/fr/sender.size.report.txt.sample
		323	%%DATADIR%%/reports/fr/stored.size.message.txt.sample
300	%%DATADIR%%/reports/hu/deleted.content.message.txt.sample	324	%%DATADIR%%/reports/hu/deleted.content.message.txt.sample
301	%%DATADIR%%/reports/hu/deleted.filename.message.txt.sample	325	%%DATADIR%%/reports/hu/deleted.filename.message.txt.sample
302	%%DATADIR%%/reports/hu/deleted.virus.message.txt.sample	326	%%DATADIR%%/reports/hu/deleted.virus.message.txt.sample
Lines 321-326 Link Here
321	%%DATADIR%%/reports/hu/stored.content.message.txt.sample	345	%%DATADIR%%/reports/hu/stored.content.message.txt.sample
322	%%DATADIR%%/reports/hu/stored.filename.message.txt.sample	346	%%DATADIR%%/reports/hu/stored.filename.message.txt.sample
323	%%DATADIR%%/reports/hu/stored.virus.message.txt.sample	347	%%DATADIR%%/reports/hu/stored.virus.message.txt.sample
		348	%%DATADIR%%/reports/hu/deleted.size.message.txt.sample
		349	%%DATADIR%%/reports/hu/sender.size.report.txt.sample
		350	%%DATADIR%%/reports/hu/stored.size.message.txt.sample
324	%%DATADIR%%/reports/it/deleted.content.message.txt.sample	351	%%DATADIR%%/reports/it/deleted.content.message.txt.sample
325	%%DATADIR%%/reports/it/deleted.filename.message.txt.sample	352	%%DATADIR%%/reports/it/deleted.filename.message.txt.sample
326	%%DATADIR%%/reports/it/deleted.virus.message.txt.sample	353	%%DATADIR%%/reports/it/deleted.virus.message.txt.sample
Lines 345-350 Link Here
345	%%DATADIR%%/reports/it/stored.content.message.txt.sample	372	%%DATADIR%%/reports/it/stored.content.message.txt.sample
346	%%DATADIR%%/reports/it/stored.filename.message.txt.sample	373	%%DATADIR%%/reports/it/stored.filename.message.txt.sample
347	%%DATADIR%%/reports/it/stored.virus.message.txt.sample	374	%%DATADIR%%/reports/it/stored.virus.message.txt.sample
		375	%%DATADIR%%/reports/it/deleted.size.message.txt.sample
		376	%%DATADIR%%/reports/it/sender.size.report.txt.sample
		377	%%DATADIR%%/reports/it/stored.size.message.txt.sample
348	%%DATADIR%%/reports/nl/deleted.content.message.txt.sample	378	%%DATADIR%%/reports/nl/deleted.content.message.txt.sample
349	%%DATADIR%%/reports/nl/deleted.filename.message.txt.sample	379	%%DATADIR%%/reports/nl/deleted.filename.message.txt.sample
350	%%DATADIR%%/reports/nl/deleted.virus.message.txt.sample	380	%%DATADIR%%/reports/nl/deleted.virus.message.txt.sample
Lines 369-374 Link Here
369	%%DATADIR%%/reports/nl/stored.content.message.txt.sample	399	%%DATADIR%%/reports/nl/stored.content.message.txt.sample
370	%%DATADIR%%/reports/nl/stored.filename.message.txt.sample	400	%%DATADIR%%/reports/nl/stored.filename.message.txt.sample
371	%%DATADIR%%/reports/nl/stored.virus.message.txt.sample	401	%%DATADIR%%/reports/nl/stored.virus.message.txt.sample
		402	%%DATADIR%%/reports/nl/deleted.size.message.txt.sample
		403	%%DATADIR%%/reports/nl/sender.size.report.txt.sample
		404	%%DATADIR%%/reports/nl/stored.size.message.txt.sample
372	%%DATADIR%%/reports/pt_br/deleted.content.message.txt.sample	405	%%DATADIR%%/reports/pt_br/deleted.content.message.txt.sample
373	%%DATADIR%%/reports/pt_br/deleted.filename.message.txt.sample	406	%%DATADIR%%/reports/pt_br/deleted.filename.message.txt.sample
374	%%DATADIR%%/reports/pt_br/deleted.virus.message.txt.sample	407	%%DATADIR%%/reports/pt_br/deleted.virus.message.txt.sample
Lines 393-398 Link Here
393	%%DATADIR%%/reports/pt_br/stored.content.message.txt.sample	426	%%DATADIR%%/reports/pt_br/stored.content.message.txt.sample
394	%%DATADIR%%/reports/pt_br/stored.filename.message.txt.sample	427	%%DATADIR%%/reports/pt_br/stored.filename.message.txt.sample
395	%%DATADIR%%/reports/pt_br/stored.virus.message.txt.sample	428	%%DATADIR%%/reports/pt_br/stored.virus.message.txt.sample
		429	%%DATADIR%%/reports/pt_br/deleted.size.message.txt.sample
		430	%%DATADIR%%/reports/pt_br/sender.size.report.txt.sample
		431	%%DATADIR%%/reports/pt_br/stored.size.message.txt.sample
396	%%DATADIR%%/reports/ro/deleted.content.message.txt.sample	432	%%DATADIR%%/reports/ro/deleted.content.message.txt.sample
397	%%DATADIR%%/reports/ro/deleted.filename.message.txt.sample	433	%%DATADIR%%/reports/ro/deleted.filename.message.txt.sample
398	%%DATADIR%%/reports/ro/deleted.virus.message.txt.sample	434	%%DATADIR%%/reports/ro/deleted.virus.message.txt.sample
Lines 417-422 Link Here
417	%%DATADIR%%/reports/ro/stored.content.message.txt.sample	453	%%DATADIR%%/reports/ro/stored.content.message.txt.sample
418	%%DATADIR%%/reports/ro/stored.filename.message.txt.sample	454	%%DATADIR%%/reports/ro/stored.filename.message.txt.sample
419	%%DATADIR%%/reports/ro/stored.virus.message.txt.sample	455	%%DATADIR%%/reports/ro/stored.virus.message.txt.sample
		456	%%DATADIR%%/reports/ro/deleted.size.message.txt.sample
		457	%%DATADIR%%/reports/ro/sender.size.report.txt.sample
		458	%%DATADIR%%/reports/ro/stored.size.message.txt.sample
420	%%DATADIR%%/reports/se/README.sample	459	%%DATADIR%%/reports/se/README.sample
421	%%DATADIR%%/reports/se/deleted.content.message.txt.sample	460	%%DATADIR%%/reports/se/deleted.content.message.txt.sample
422	%%DATADIR%%/reports/se/deleted.filename.message.txt.sample	461	%%DATADIR%%/reports/se/deleted.filename.message.txt.sample
Lines 442-447 Link Here
442	%%DATADIR%%/reports/se/stored.content.message.txt.sample	481	%%DATADIR%%/reports/se/stored.content.message.txt.sample
443	%%DATADIR%%/reports/se/stored.filename.message.txt.sample	482	%%DATADIR%%/reports/se/stored.filename.message.txt.sample
444	%%DATADIR%%/reports/se/stored.virus.message.txt.sample	483	%%DATADIR%%/reports/se/stored.virus.message.txt.sample
		484	%%DATADIR%%/reports/se/deleted.size.message.txt.sample
		485	%%DATADIR%%/reports/se/sender.size.report.txt.sample
		486	%%DATADIR%%/reports/se/stored.size.message.txt.sample
445	%%DATADIR%%/reports/sk/deleted.content.message.txt.sample	487	%%DATADIR%%/reports/sk/deleted.content.message.txt.sample
446	%%DATADIR%%/reports/sk/deleted.filename.message.txt.sample	488	%%DATADIR%%/reports/sk/deleted.filename.message.txt.sample
447	%%DATADIR%%/reports/sk/deleted.virus.message.txt.sample	489	%%DATADIR%%/reports/sk/deleted.virus.message.txt.sample
Lines 466-597 Link Here
466	%%DATADIR%%/reports/sk/stored.content.message.txt.sample	508	%%DATADIR%%/reports/sk/stored.content.message.txt.sample
467	%%DATADIR%%/reports/sk/stored.filename.message.txt.sample	509	%%DATADIR%%/reports/sk/stored.filename.message.txt.sample
468	%%DATADIR%%/reports/sk/stored.virus.message.txt.sample	510	%%DATADIR%%/reports/sk/stored.virus.message.txt.sample
469	%%PORTDOCS%%%%DOCSDIR%%/ellen2.old.jpg	511	%%DATADIR%%/reports/sk/deleted.size.message.txt.sample
470	%%PORTDOCS%%%%DOCSDIR%%/ellenweblogo.png	512	%%DATADIR%%/reports/sk/sender.size.report.txt.sample
471	%%PORTDOCS%%%%DOCSDIR%%/Book.Dec04-Aug05.pdf	513	%%DATADIR%%/reports/sk/stored.size.message.txt.sample
472	%%PORTDOCS%%%%DOCSDIR%%/COPYING	514	%%PORTDOCS%%%%DOCSDIR%%/README.FreeBSD.port
473	%%PORTDOCS%%%%DOCSDIR%%/ChangeLog	515	%%PORTDOCS%%%%DOCSDIR%%/Sophos.install.freebsd
474	%%PORTDOCS%%%%DOCSDIR%%/CHANGES.port
475	%%PORTDOCS%%%%DOCSDIR%%/FreeBSD.html
476	%%PORTDOCS%%%%DOCSDIR%%/INSTALL
477	%%PORTDOCS%%%%DOCSDIR%%/INSTALL.FreeBSD	516	%%PORTDOCS%%%%DOCSDIR%%/INSTALL.FreeBSD
478	%%PORTDOCS%%%%DOCSDIR%%/INSTALL.OpenBSD	517	%%PORTDOCS%%%%DOCSDIR%%/INSTALL.OpenBSD
479	%%PORTDOCS%%%%DOCSDIR%%/MailScannerFlyer.pdf
480	%%PORTDOCS%%%%DOCSDIR%%/QuickInstall.txt
481	%%PORTDOCS%%%%DOCSDIR%%/README	518	%%PORTDOCS%%%%DOCSDIR%%/README
482	%%PORTDOCS%%%%DOCSDIR%%/README.FreeBSD.port
483	%%PORTDOCS%%%%DOCSDIR%%/README.sql-logging
484	%%PORTDOCS%%%%DOCSDIR%%/Sophos.install.freebsd
485	%%PORTDOCS%%%%DOCSDIR%%/book.cover.gif
486	%%PORTDOCS%%%%DOCSDIR%%/building.txt
487	%%PORTDOCS%%%%DOCSDIR%%/docs.html
488	%%PORTDOCS%%%%DOCSDIR%%/donations.shtml
489	%%PORTDOCS%%%%DOCSDIR%%/downloadgraphs.shtml
490	%%PORTDOCS%%%%DOCSDIR%%/downloads.shtml
491	%%PORTDOCS%%%%DOCSDIR%%/ecs.css
492	%%PORTDOCS%%%%DOCSDIR%%/ellen2.jpg
493	%%PORTDOCS%%%%DOCSDIR%%/faq.shtml
494	%%PORTDOCS%%%%DOCSDIR%%/images/JulianField1_small.jpg
495	%%PORTDOCS%%%%DOCSDIR%%/images/bigmailscannerlogo.gif
496	%%PORTDOCS%%%%DOCSDIR%%/images/smallmailscannerlogo.gif
497	%%PORTDOCS%%%%DOCSDIR%%/images/thumb_JulianField2.jpg
498	%%PORTDOCS%%%%DOCSDIR%%/images/thumb_JulianField3.jpg
499	%%PORTDOCS%%%%DOCSDIR%%/images/thumb_JulianField4.jpg
500	%%PORTDOCS%%%%DOCSDIR%%/images/thumb_JulianField5.jpg
501	%%PORTDOCS%%%%DOCSDIR%%/index.html
502	%%PORTDOCS%%%%DOCSDIR%%/index.new.html
503	%%PORTDOCS%%%%DOCSDIR%%/install/ClamAVModule.shtml
504	%%PORTDOCS%%%%DOCSDIR%%/install/OS-virus-scan-web.htm
505	%%PORTDOCS%%%%DOCSDIR%%/install/README.trend
506	%%PORTDOCS%%%%DOCSDIR%%/install/SAVI.shtml
507	%%PORTDOCS%%%%DOCSDIR%%/install/codestatus.shtml
508	%%PORTDOCS%%%%DOCSDIR%%/install/conf.shtml
509	%%PORTDOCS%%%%DOCSDIR%%/install/exim-old.shtml
510	%%PORTDOCS%%%%DOCSDIR%%/install/exim.shtml
511	%%PORTDOCS%%%%DOCSDIR%%/install/filesnscripts.shtml
512	%%PORTDOCS%%%%DOCSDIR%%/install/gcc.shtml
513	%%PORTDOCS%%%%DOCSDIR%%/install/index.shtml
514	%%PORTDOCS%%%%DOCSDIR%%/install/linux.shtml
515	%%PORTDOCS%%%%DOCSDIR%%/install/mailscanner.shtml
516	%%PORTDOCS%%%%DOCSDIR%%/install/mcafee.shtml
517	%%PORTDOCS%%%%DOCSDIR%%/install/mcp/Message.pm.patch.3.1.1
518	%%PORTDOCS%%%%DOCSDIR%%/install/mcp/Conf.pm.patch.3.1.1
519	%%PORTDOCS%%%%DOCSDIR%%/install/mcp/PerMsgStatus.pm.patch.3.1.1
520	%%PORTDOCS%%%%DOCSDIR%%/install/mcp/Conf.pm.patch.2.55
521	%%PORTDOCS%%%%DOCSDIR%%/install/mcp/Conf.pm.patch.2.60
522	%%PORTDOCS%%%%DOCSDIR%%/install/mcp/Conf.pm.patch.2.61
523	%%PORTDOCS%%%%DOCSDIR%%/install/mcp/Conf.pm.patch.2.63
524	%%PORTDOCS%%%%DOCSDIR%%/install/mcp/Conf.pm.patch.3.0.0
525	%%PORTDOCS%%%%DOCSDIR%%/install/mcp/Conf.pm.patch.3.0.3
526	%%PORTDOCS%%%%DOCSDIR%%/install/mcp/Conf.pm.patch.3.0.4
527	%%PORTDOCS%%%%DOCSDIR%%/install/mcp/Conf.pm.patch.3.1.0
528	%%PORTDOCS%%%%DOCSDIR%%/install/mcp/Message.pm.patch.3.0.0
529	%%PORTDOCS%%%%DOCSDIR%%/install/mcp/Message.pm.patch.3.0.3
530	%%PORTDOCS%%%%DOCSDIR%%/install/mcp/Message.pm.patch.3.0.4
531	%%PORTDOCS%%%%DOCSDIR%%/install/mcp/Message.pm.patch.3.1.0
532	%%PORTDOCS%%%%DOCSDIR%%/install/mcp/PerMsgStatus.pm.patch.2.55
533	%%PORTDOCS%%%%DOCSDIR%%/install/mcp/PerMsgStatus.pm.patch.2.60
534	%%PORTDOCS%%%%DOCSDIR%%/install/mcp/PerMsgStatus.pm.patch.2.61
535	%%PORTDOCS%%%%DOCSDIR%%/install/mcp/PerMsgStatus.pm.patch.2.63
536	%%PORTDOCS%%%%DOCSDIR%%/install/mcp/PerMsgStatus.pm.patch.3.0.0
537	%%PORTDOCS%%%%DOCSDIR%%/install/mcp/PerMsgStatus.pm.patch.3.0.3
538	%%PORTDOCS%%%%DOCSDIR%%/install/mcp/PerMsgStatus.pm.patch.3.0.4
539	%%PORTDOCS%%%%DOCSDIR%%/install/mcp/PerMsgStatus.pm.patch.3.1.0
540	%%PORTDOCS%%%%DOCSDIR%%/install/mcp/index.html
541	%%PORTDOCS%%%%DOCSDIR%%/install/mime-tools-patch.txt
542	%%PORTDOCS%%%%DOCSDIR%%/install/mime-tools-patch2.txt
543	%%PORTDOCS%%%%DOCSDIR%%/install/mime-tools-patch3.txt
544	%%PORTDOCS%%%%DOCSDIR%%/install/mime-tools-patch4.txt
545	%%PORTDOCS%%%%DOCSDIR%%/install/osborne.txt
546	%%PORTDOCS%%%%DOCSDIR%%/install/other.shtml
547	%%PORTDOCS%%%%DOCSDIR%%/install/perl.shtml
548	%%PORTDOCS%%%%DOCSDIR%%/install/postfix.shtml
549	%%PORTDOCS%%%%DOCSDIR%%/install/sendmail.shtml
550	%%PORTDOCS%%%%DOCSDIR%%/install/solaris9.txt
551	%%PORTDOCS%%%%DOCSDIR%%/install/sophos.shtml
552	%%PORTDOCS%%%%DOCSDIR%%/install/spamassassin.shtml
553	%%PORTDOCS%%%%DOCSDIR%%/install/tnef.shtml
554	%%PORTDOCS%%%%DOCSDIR%%/install/zmailer.shtml
555	%%PORTDOCS%%%%DOCSDIR%%/introduction.shtml
556	%%PORTDOCS%%%%DOCSDIR%%/last-spam-logo.jpg
557	%%PORTDOCS%%%%DOCSDIR%%/mailscanner_trans.gif
558	%%PORTDOCS%%%%DOCSDIR%%/man/MailScanner.8
559	%%PORTDOCS%%%%DOCSDIR%%/man/MailScanner.8.html
560	%%PORTDOCS%%%%DOCSDIR%%/man/MailScanner.conf.5
561	%%PORTDOCS%%%%DOCSDIR%%/man/MailScanner.conf.5.html
562	%%PORTDOCS%%%%DOCSDIR%%/mrtg.shtml
563	%%PORTDOCS%%%%DOCSDIR%%/newinv4.shtml
564	%%PORTDOCS%%%%DOCSDIR%%/nextversion.shtml
565	%%PORTDOCS%%%%DOCSDIR%%/oldnews.shtml
566	%%PORTDOCS%%%%DOCSDIR%%/osdir.png
567	%%PORTDOCS%%%%DOCSDIR%%/performance.shtml
568	%%PORTDOCS%%%%DOCSDIR%%/phishing3.png
569	%%PORTDOCS%%%%DOCSDIR%%/phishingcartoon.gif
570	%%PORTDOCS%%%%DOCSDIR%%/poetry.shtml
571	%%PORTDOCS%%%%DOCSDIR%%/poweredby.google.gif
572	%%PORTDOCS%%%%DOCSDIR%%/poweredby.transtec.gif
573	%%PORTDOCS%%%%DOCSDIR%%/phishing.html
574	%%PORTDOCS%%%%DOCSDIR%%/phishing.jpg
575	%%PORTDOCS%%%%DOCSDIR%%/phishing2.jpg
576	%%PORTDOCS%%%%DOCSDIR%%/phishingnet.info/index.html
577	%%PORTDOCS%%%%DOCSDIR%%/phishingnet.info/PhishingNet.gif
578	%%PORTDOCS%%%%DOCSDIR%%/pressreleases.html
579	%%PORTDOCS%%%%DOCSDIR%%/presentations.html
580	%%PORTDOCS%%%%DOCSDIR%%/press.html
581	%%PORTDOCS%%%%DOCSDIR%%/qmail/qmail-queue.zip
582	%%PORTDOCS%%%%DOCSDIR%%/readme.shtml
583	%%PORTDOCS%%%%DOCSDIR%%/reject.html
584	%%PORTDOCS%%%%DOCSDIR%%/sobig.html
585	%%PORTDOCS%%%%DOCSDIR%%/store.html
586	%%PORTDOCS%%%%DOCSDIR%%/support.html
587	%%PORTDOCS%%%%DOCSDIR%%/transtec.logo.gif
588	%%PORTDOCS%%%%DOCSDIR%%/users.shtml
589	%%PORTDOCS%%@dirrm %%DOCSDIR%%/qmail
590	%%PORTDOCS%%@dirrm %%DOCSDIR%%/man
591	%%PORTDOCS%%@dirrm %%DOCSDIR%%/install/mcp
592	%%PORTDOCS%%@dirrm %%DOCSDIR%%/install
593	%%PORTDOCS%%@dirrm %%DOCSDIR%%/images
594	%%PORTDOCS%%@dirrm %%DOCSDIR%%/phishingnet.info
595	%%PORTDOCS%%@dirrm %%DOCSDIR%%	519	%%PORTDOCS%%@dirrm %%DOCSDIR%%
596	%%SPAMASSASSIN%%%%SPAMASSASSIN_SYMLINK%%@exec [ -e %D/etc/mail/spamassassin/mailscanner.cf ] \|\| ln -s %D/etc/MailScanner/spam.assassin.prefs.conf %D/etc/mail/spamassassin/mailscanner.cf	520	%%SPAMASSASSIN%%%%SPAMASSASSIN_SYMLINK%%@exec [ -e %D/etc/mail/spamassassin/mailscanner.cf ] \|\| ln -s %D/etc/MailScanner/spam.assassin.prefs.conf %D/etc/mail/spamassassin/mailscanner.cf
597	%%SPAMASSASSIN%%%%SPAMASSASSIN_SYMLINK%%@unexec [ -L %D/etc/mail/spamassassin/mailscanner.cf ] && rm -f %D/etc/mail/spamassassin/mailscanner.cf	521	%%SPAMASSASSIN%%%%SPAMASSASSIN_SYMLINK%%@unexec [ -L %D/etc/mail/spamassassin/mailscanner.cf ] && rm -f %D/etc/mail/spamassassin/mailscanner.cf

Lines 1-3 Link Here

(-)files/CHANGES.port (+7 lines)
		1	Version 4.55.10
		2	===============
		3	- Upgrade to MailScanner 4.55
		4	- As Julian removed the documentation from the tarball I did the same in the port.
		5	Manpage and html docs removed as well. All documentation can now be found on
		6	the web.
		7
1	Version 4.54.6_1	8	Version 4.54.6_1
2	=================	9	=================
3	- Path to gunzip in MailScanner.conf fixed	10	- Path to gunzip in MailScanner.conf fixed




.TH "MailScanner" "8" "4.52.2" "Julian Field" "Mail"
.SH "NAME"
.LP 
MailScanner \- Virus/Spam Scanner for Sendmail, Exim and Postfix
.SH "SEE ALSO"
.LP 
Please see http://www.mailscanner.info for current documentation. All current configuration options can be found at 
.br 

.br 
http://www.mailscanner.info/MailScanner.conf.index.html





--- ../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. 




--- ../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>&minus;v</i>]
-[<i>configfile</i>]</p>
+[<i>&minus;&minus;lint</i>] [<i>&minus;&minus;debug</i>]
+[<i>&minus;&minus;debug&minus;sa</i>]
+[<i>&minus;&minus;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>&minus;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&minus;modules.</p>
+</td>
+<tr valign="top" align="left">
+<td width="11%"></td>
+<td width="9%">
+
+<p><b>&minus;&minus;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>&minus;&minus;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
+&quot;Debug=yes&quot;.</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>&minus;&minus;debug&minus;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 &quot;Debug SpamAssassin=yes&quot;.</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>&minus;&minus;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>




--- ../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




--- ../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 &quot;50M&quot; instead of &quot;50000000&quot;. The
+multipliers supported are &quot;k&quot;, &quot;m&quot; and
+&quot;g&quot; 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
+&quot;add&quot; or &quot;replace&quot; then recipients of
+messages sent in &quot;Outlook Rich Text Format&quot; (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>&bull;</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>&bull;</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>&bull;</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&minus;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 &quot;gunzip&quot; 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 &quot;gunzip&quot; 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&minus;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&minus;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&minus;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&rsquo;t have virus scanner licence and so want to
@@ -1519,7 +1665,9 @@
 Scanners = none&quot; 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&minus;name.co.uk pretending to be
+www.nice.company&minus;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&minus;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&minus;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&minus;level and 3rd&minus;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 &quot;spacer&quot; for page
+layout purposes and not a real web bug at all. It should be
+a space&minus; and/or comma&minus;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
+&quot;MailScannerWebBug&quot; 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 &lt;Object Codebase=...&gt; tags in
 email messages? This is a bad idea as it leaves you
 unprotected against various Microsoft&minus;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 &quot;sa&minus;update&quot; tool
+are searched for here. This directory contains the
+spamassassin/3.001001/updates_spamassassin_org directory
+structure beneath it. Only un&minus;comment this setting
+once you have proved that the sa&minus;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 &quot;Cache&quot;). The numbers are all
+set in seconds. They are:<br>
+1. Non&minus;Spam cache lifetime = 30 minutes<br>
+2. Spam (low scoring) cache lifetime = 5 minutes<br>
+3. High&minus;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 &quot;side effect&quot; 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&minus;batch information. This is evaluated after the
+&quot;Always Looked Up Last&quot; 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 -->

Return to bug 101766

Lines 6-13 Link Here

(-)Makefile (-17 / +9 lines)
6	#	6	#
7		7
8	PORTNAME= MailScanner	8	PORTNAME= MailScanner
9	PORTVERSION= 4.54.6	9	PORTVERSION= 4.55.10
10	PORTREVISION= 2
11	CATEGORIES= mail	10	CATEGORIES= mail
12	MASTER_SITES= http://www.mailscanner.info/files/4/tar/	11	MASTER_SITES= http://www.mailscanner.info/files/4/tar/
13	DISTNAME= ${PORTNAME}-install-${PORTVERSION}-${PATCHLEVEL}	12	DISTNAME= ${PORTNAME}-install-${PORTVERSION}-${PATCHLEVEL}
Lines 52-58 Link Here
52		51
53	CONFLICTS= MailScanner-devel-[0-9]*	52	CONFLICTS= MailScanner-devel-[0-9]*
54		53
55	PATCHLEVEL= 1	54	PATCHLEVEL= 3
56		55
57	USE_PERL5= yes	56	USE_PERL5= yes
58		57
Lines 60-68 Link Here
60	SUB_FILES= pkg-message	59	SUB_FILES= pkg-message
61		60
62	MAN8= MailScanner.8	61	MAN8= MailScanner.8
63	MAN5= MailScanner.conf.5	62	MLINKS= MailScanner.8 mailscanner.8
64	MLINKS= MailScanner.8 mailscanner.8 \
65	MailScanner.conf.5 mailscanner.conf.5
66		63
67	.include <bsd.port.pre.mk>	64	.include <bsd.port.pre.mk>
68		65
Lines 109-115 Link Here
109	RUN_DEPENDS+= bdc:${PORTSDIR}/security/bdc	106	RUN_DEPENDS+= bdc:${PORTSDIR}/security/bdc
110	.endif	107	.endif
111		108
112	DOC_FILES= INSTALL INSTALL.FreeBSD INSTALL.OpenBSD README	109	DOC_FILES= INSTALL.FreeBSD INSTALL.OpenBSD README
113	ETC_FILES= MailScanner.conf filename.rules.conf \	110	ETC_FILES= MailScanner.conf filename.rules.conf \
114	filetype.rules.conf spam.assassin.prefs.conf \	111	filetype.rules.conf spam.assassin.prefs.conf \
115	spam.lists.conf virus.scanners.conf \	112	spam.lists.conf virus.scanners.conf \
Lines 271-291 Link Here
271	#	268	#
272	# Step 6: Docs & Manpages	269	# Step 6: Docs & Manpages
273	#	270	#
		271	# Manpage
274	.if !defined(NOPORTDOCS)	272	.if !defined(NOPORTDOCS)
275	${MKDIR} ${DOCSDIR}	273	${MKDIR} ${DOCSDIR}
276	${INSTALL_DATA} ${FILESDIR}/README.FreeBSD.port ${DOCSDIR}	274	${INSTALL_DATA} ${FILESDIR}/README.FreeBSD.port ${DOCSDIR}
277	${INSTALL_DATA} ${FILESDIR}/CHANGES.port ${DOCSDIR}
278	cd ${WRKSRC} && ${INSTALL_DATA} ${DOC_FILES} ${DOCSDIR}
279	cd ${WRKSRC}/docs && \
280	${FIND} * -type d -exec ${MKDIR} ${DOCSDIR}/{} \; && \
281	${FIND} * -type f ! -name "*.orig" -exec \
282	${INSTALL_DATA} {} ${DOCSDIR}/{} \;
283	.endif
284	cd ${WRKSRC}/docs/man && \
285	${INSTALL_MAN} ${MAN5} ${MAN5PREFIX}/man/man5 && \
286	${INSTALL_MAN} ${MAN8} ${MAN8PREFIX}/man/man8
287	# Sophos install script	275	# Sophos install script
288	${INSTALL_SCRIPT} ${FILESDIR}/Sophos.install.freebsd ${DOCSDIR}	276	${INSTALL_SCRIPT} ${FILESDIR}/Sophos.install.freebsd ${DOCSDIR}
		277	cd ${WRKSRC} && ${INSTALL_DATA} ${DOC_FILES} ${DOCSDIR}
		278	.endif
		279	cd ${FILESDIR} && \
		280	${INSTALL_MAN} ${MAN8} ${MAN5PREFIX}/man/man8
289	${PERL} -pi -e \	281	${PERL} -pi -e \
290	's,%%LOCALBASE%%,${LOCALBASE},g; \	282	's,%%LOCALBASE%%,${LOCALBASE},g; \
291	s,%%PREFIX%%,${PREFIX},g;' \	283	s,%%PREFIX%%,${PREFIX},g;' \

Added Link Here

(-)files/MailScanner.8 (+12 lines)
1	.TH "MailScanner" "8" "4.52.2" "Julian Field" "Mail"
2	.SH "NAME"
3	.LP
4	MailScanner \- Virus/Spam Scanner for Sendmail, Exim and Postfix
5	.SH "SEE ALSO"
6	.LP
7	Please see http://www.mailscanner.info for current documentation. All current configuration options can be found at
8	.br
9
10	.br
11	http://www.mailscanner.info/MailScanner.conf.index.html
12

Removed Link Here

(-)files/patch-docs-man-MailScanner.8 (-37 lines)
1	--- ../MailScanner-install-4.53.7.orig/docs/man/MailScanner.8 Wed May 3 21:16:27 2006
2	+++ docs/man/MailScanner.8 Wed May 3 21:33:13 2006
3	@@ -1,10 +1,10 @@
4	-.TH "MailScanner" "8" "4.49.7" "Julian Field" "Mail"
5	+.TH "MailScanner" "8" "4.52.2" "Julian Field" "Mail"
6	.SH "NAME"
7	.LP
8	MailScanner \- Virus/Spam Scanner for Sendmail, Exim and Postfix
9	.SH "SYNOPSIS"
10	.LP
11	-\fBMailScanner\fR [\fI\-v\fR] [\fIconfigfile\fR]
12	+\fBMailScanner\fR [\fI\-v\fR] [\fI\-\-lint\fR] [\fI\-\-debug\fR] [\fI\-\-debug\-sa\fR] [\fI\-\-help\fR] [\fIconfigfile\fR]
13
14	.SH "DESCRIPTION"
15	.LP
16	@@ -29,6 +29,21 @@
17	\fB\-v\fR
18	Prints version information for Mailscanner and all used perl\-modules.
19
20	+.TP
21	+\fB\-\-lint\fR
22	+Checks config file, print what virus scanners you have chosen to use and check SpamAssassin configuration as well.
23	+
24	+.TP
25	+\fB\-\-debug\fR
26	+Starts MailScanner in debug mode. See MailScanner.conf "Debug=yes".
27	+
28	+.TP
29	+\fB\-\-debug\-sa\fR
30	+Starts MailScanner in debug spamassassin mode. See MailScanner.conf "Debug SpamAssassin=yes".
31	+
32	+.TP
33	+\fB\-\-lint\fR
34	+Test MailScanner config and SpamAssassin config.
35	.SH "MTA SETUP"
36	.LP
37	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.

Removed Link Here

(-)files/patch-docs-man-MailScanner.8.html (-104 lines)
1	--- ../MailScanner-install-4.53.7.orig/docs/man/MailScanner.8.html Wed May 3 21:16:27 2006
2	+++ docs/man/MailScanner.8.html Wed May 3 21:33:15 2006
3	@@ -1,5 +1,5 @@
4	<!-- Creator : groff version 1.19 -->
5	-<!-- CreationDate: Wed Jan 4 13:45:56 2006 -->
6	+<!-- CreationDate: Wed May 3 21:32:34 2006 -->
7	<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
8	"http://www.w3.org/TR/html4/loose.dtd">
9	<html>
10	@@ -40,7 +40,9 @@
11	<td width="11%"></td>
12	<td width="89%">
13	<p><b>MailScanner</b> [<i>−v</i>]
14	-[<i>configfile</i>]</p>
15	+[<i>−−lint</i>] [<i>−−debug</i>]
16	+[<i>−−debug−sa</i>]
17	+[<i>−−help</i>] [<i>configfile</i>]</p>
18	</td>
19	</table>
20	<a name="DESCRIPTION"></a>
21	@@ -78,15 +80,81 @@
22	cols="4" cellspacing="0" cellpadding="0">
23	<tr valign="top" align="left">
24	<td width="11%"></td>
25	-<td width="3%">
26	+<td width="9%">
27
28	<p><b>−v</b></p>
29	</td>
30	-<td width="8%"></td>
31	+<td width="2%"></td>
32	<td width="78%">
33
34	<p>Prints version information for Mailscanner and all used
35	perl−modules.</p>
36	+</td>
37	+<tr valign="top" align="left">
38	+<td width="11%"></td>
39	+<td width="9%">
40	+
41	+<p><b>−−lint</b></p>
42	+</td>
43	+<td width="2%"></td>
44	+<td width="78%">
45	+
46	+<p>Checks config file, print what virus scanners you have
47	+chosen to use and check SpamAssassin configuration as
48	+well.</p>
49	+</td>
50	+</table>
51	+<!-- INDENTATION -->
52	+<table width="100%" border=0 rules="none" frame="void"
53	+ cols="2" cellspacing="0" cellpadding="0">
54	+<tr valign="top" align="left">
55	+<td width="11%"></td>
56	+<td width="89%">
57	+<p><b>−−debug</b></p></td>
58	+</table>
59	+<!-- INDENTATION -->
60	+<table width="100%" border=0 rules="none" frame="void"
61	+ cols="2" cellspacing="0" cellpadding="0">
62	+<tr valign="top" align="left">
63	+<td width="22%"></td>
64	+<td width="78%">
65	+<p>Starts MailScanner in debug mode. See MailScanner.conf
66	+"Debug=yes".</p>
67	+</td>
68	+</table>
69	+<!-- INDENTATION -->
70	+<table width="100%" border=0 rules="none" frame="void"
71	+ cols="2" cellspacing="0" cellpadding="0">
72	+<tr valign="top" align="left">
73	+<td width="11%"></td>
74	+<td width="89%">
75	+<p><b>−−debug−sa</b></p></td>
76	+</table>
77	+<!-- INDENTATION -->
78	+<table width="100%" border=0 rules="none" frame="void"
79	+ cols="2" cellspacing="0" cellpadding="0">
80	+<tr valign="top" align="left">
81	+<td width="22%"></td>
82	+<td width="78%">
83	+<p>Starts MailScanner in debug spamassassin mode. See
84	+MailScanner.conf "Debug SpamAssassin=yes".</p>
85	+</td>
86	+</table>
87	+<!-- TABS -->
88	+<table width="100%" border=0 rules="none" frame="void"
89	+ cols="5" cellspacing="0" cellpadding="0">
90	+<tr valign="top" align="left">
91	+<td width="11%"></td>
92	+<td width="9%">
93	+
94	+<p><b>−−lint</b></p>
95	+</td>
96	+<td width="2%"></td>
97	+<td width="73%">
98	+
99	+<p>Test MailScanner config and SpamAssassin config.</p>
100	+</td>
101	+<td width="5%">
102	</td>
103	</table>
104	<a name="MTA SETUP"></a>

Removed Link Here

(-)files/patch-docs-man-MailScanner.conf.5 (-223 lines)
1	--- ../MailScanner-install-4.53.7.orig/docs/man/MailScanner.conf.5 Wed May 3 21:16:27 2006
2	+++ docs/man/MailScanner.conf.5 Wed May 3 21:33:05 2006
3	@@ -1,4 +1,4 @@
4	-.TH "MailScanner.conf" "5" "4.50.1" "Julian Field" "Mail"
5	+.TH "MailScanner.conf" "5" "4.53.7" "Julian Field" "Mail"
6	.SH "NAME"
7	.LP
8	MailScanner.conf \- Main configuration for MailScanner
9	@@ -24,6 +24,10 @@
10	.br
11
12	.br
13	+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.
14	+.br
15	+
16	+.br
17	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.
18
19	.LP
20	@@ -364,6 +368,22 @@
21	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.
22
23	.TP
24	+\fBUse TNEF Contents\fR
25	+Default: replace
26	+.br
27	+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.
28	+.br
29	+.RS 7
30	+.IP \(bu 4
31	+no: Leave winmail.dat TNEF attachments alone.
32	+.IP \(bu 4
33	+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.
34	+.IP \(bu 4
35	+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.
36	+.RE
37	+
38	+
39	+.TP
40	\fBDeliver Unparsable TNEF\fR
41	Default: no
42	.br
43	@@ -405,6 +425,22 @@
44	.br
45	The maximum length of time the "file" command is allowed to run for one batch of messages (in seconds).
46
47	+.TP
48	+\fBGunzip Command\fR
49	+Default: /usr/bin/gunzip
50	+.br
51	+
52	+.br
53	+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.
54	+
55	+.TP
56	+\fBGunzip Timeout\fR
57	+Default: 50
58	+.br
59	+
60	+.br
61	+The maximum length of time the "gunzip" command is allowed to run to expand 1 attachment file (in seconds).
62	+
63
64	.TP
65	\fBUnrar Command\fR
66	@@ -423,6 +459,12 @@
67	The maximum length of time the "unrar" command is allowed to run for 1 RAR archive (in seconds)
68
69	.TP
70	+\fBFind UU\-Encoded Files\fR
71	+Default: no
72	+.br
73	+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.
74	+
75	+.TP
76	\fBBlock Encrypted Messages\fR
77	Default: no
78	.br
79	@@ -521,7 +563,7 @@
80	.SH "Virus scanning and vulnerability testing"
81	.TP
82	\fBVirus Scanning\fR
83	-Default: yes
84	+Default: auto
85	.br
86
87	.br
88	@@ -529,7 +571,7 @@
89	.br
90	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.
91	.br
92	-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.
93	+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.
94
95	.TP
96	\fBVirus Scanners\fR
97	@@ -686,6 +728,23 @@
98	.br
99	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.
100
101	+.TP
102	+\fBUse Stricter Phishing Net\fR
103	+Default: yes
104	+.br
105	+
106	+.br
107	+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.
108	+
109	+
110	+.TP
111	+\fBHighlight Phishing Fraud\fR
112	+Default: yes
113	+.br
114	+
115	+.br
116	+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.
117	+
118
119	.TP
120	\fBPhishing Safe Sites File\fR
121	@@ -695,6 +754,15 @@
122	.br
123	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.
124
125	+.TP
126	+\fBCountry Sub\-Domains List\fR
127	+Default: %etc\-dir%/country.domains.conf
128	+.br
129	+
130	+.br
131	+.TP
132	+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.
133	+
134
135	.TP
136	\fBAllow IFrame Tags\fR
137	@@ -773,6 +841,22 @@
138	.RE
139
140	.TP
141	+\fBIgnored Web Bug Filenames\fR
142	+Default:
143	+.br
144	+
145	+.br
146	+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.
147	+
148	+.TP
149	+\fBWeb Bug Replacement\fR
150	+Default: http://www.sng.ecs.soton.ac.uk/mailscanner/images/1x1spacer.gif
151	+.br
152	+
153	+.br
154	+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.
155	+
156	+.TP
157	\fBAllow Object Codebase Tags\fR
158	Default: no
159	.br
160	@@ -1682,7 +1766,7 @@
161	.SH "SpamAssassin"
162	.TP
163	\fBUse SpamAssassin\fR
164	-Default: no
165	+Default: yes
166	.br
167
168	.br
169	@@ -2076,6 +2160,15 @@
170	.RE
171
172	.TP
173	+\fBSpamAssassin Local State Dir\fR
174	+Default:
175	+.br
176	+
177	+.br
178	+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!
179	+
180	+
181	+.TP
182	\fBSpamAssassin Default Rules Dir\fR
183	Default:
184	.br
185	@@ -2113,6 +2206,22 @@
186	.RE
187
188	.TP
189	+\fBSpamAssassin Cache Timings\fR
190	+Default: 1800,300,10800,172800,600
191	+.br
192	+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:
193	+.br
194	+1. Non\-Spam cache lifetime = 30 minutes
195	+.br
196	+2. Spam (low scoring) cache lifetime = 5 minutes
197	+.br
198	+3. High\-Scoring spam cache lifetime = 3 hours
199	+.br
200	+4. Viruses cache lifetime = 2 days
201	+.br
202	+5. How often to check the cache for expired messages = 10 minutes
203	+
204	+.TP
205	\fBDebug\fR
206	Default: no
207	.br
208	@@ -2167,6 +2276,15 @@
209
210	.br
211	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.
212	+
213	+
214	+.TP
215	+\fBAlways Looked Up Last After Batch\fR
216	+Default: no
217	+.br
218	+
219	+.br
220	+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.
221
222	.TP
223	\fBDeliver in Background\fR

Removed Link Here

(-)files/patch-docs-man-MailScanner.conf.5.html (-594 lines)
1	--- ../MailScanner-install-4.53.7.orig/docs/man/MailScanner.conf.5.html Wed May 3 21:16:27 2006
2	+++ docs/man/MailScanner.conf.5.html Wed May 3 21:33:08 2006
3	@@ -1,5 +1,5 @@
4	<!-- Creator : groff version 1.19 -->
5	-<!-- CreationDate: Wed Jan 4 14:36:14 2006 -->
6	+<!-- CreationDate: Wed May 3 21:32:34 2006 -->
7	<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
8	"http://www.w3.org/TR/html4/loose.dtd">
9	<html>
10	@@ -113,6 +113,13 @@
11	<!-- INDENTATION -->
12	<p>option = value</p>
13	<!-- INDENTATION -->
14	+<p>The following optional multipliers are supported: You can
15	+write "50M" instead of "50000000". The
16	+multipliers supported are "k", "m" and
17	+"g" to denote 1 thousand, 1 million and 1 billion
18	+(10^9) in upper or lower case. You must not put any spaces
19	+between the number and the multiplier character.</p>
20	+<!-- INDENTATION -->
21	<p>Many of the options can also be the filename of a
22	ruleset, which can be used to control features depending on
23	the addresses of the message, and/or the IP address where
24	@@ -1064,6 +1071,73 @@
25	<tr valign="top" align="left">
26	<td width="11%"></td>
27	<td width="89%">
28	+<p><b>Use TNEF Contents</b></p></td>
29	+</table>
30	+<!-- INDENTATION -->
31	+<table width="100%" border=0 rules="none" frame="void"
32	+ cols="2" cellspacing="0" cellpadding="0">
33	+<tr valign="top" align="left">
34	+<td width="22%"></td>
35	+<td width="78%">
36	+<p>Default: replace<br>
37	+When the TNEF (winmail.dat) attachments are expanded, should
38	+the attachments contained in there be added to the list of
39	+attachments in the message? If you set this to
40	+"add" or "replace" then recipients of
41	+messages sent in "Outlook Rich Text Format" (TNEF)
42	+will be able to read the attachments if they are not using
43	+Microsoft Outlook.</p>
44	+</td>
45	+</table>
46	+<!-- TABS -->
47	+<table width="100%" border=0 rules="none" frame="void"
48	+ cols="4" cellspacing="0" cellpadding="0">
49	+<tr valign="top" align="left">
50	+<td width="22%"></td>
51	+<td width="1%">
52	+
53	+<p>•</p>
54	+</td>
55	+<td width="5%"></td>
56	+<td width="72%">
57	+
58	+<p>no: Leave winmail.dat TNEF attachments alone.</p>
59	+</td>
60	+<tr valign="top" align="left">
61	+<td width="22%"></td>
62	+<td width="1%">
63	+
64	+<p>•</p>
65	+</td>
66	+<td width="5%"></td>
67	+<td width="72%">
68	+
69	+<p>add: Add the contents of winmail.dat as extra
70	+attachments, but also still include the winmail.dat file
71	+itself. This will result in TNEF messages being doubled in
72	+size.</p>
73	+</td>
74	+<tr valign="top" align="left">
75	+<td width="22%"></td>
76	+<td width="1%">
77	+
78	+<p>•</p>
79	+</td>
80	+<td width="5%"></td>
81	+<td width="72%">
82	+
83	+<p>replace: Replace the winmail.dat TNEF attachment with
84	+the files it contains, and delete the original winmail.dat
85	+file itself. This means the message stays the same size, but
86	+is usable by non−Outlook recipients.</p>
87	+</td>
88	+</table>
89	+<!-- INDENTATION -->
90	+<table width="100%" border=0 rules="none" frame="void"
91	+ cols="2" cellspacing="0" cellpadding="0">
92	+<tr valign="top" align="left">
93	+<td width="11%"></td>
94	+<td width="89%">
95	<p><b>Deliver Unparsable TNEF</b></p></td>
96	</table>
97	<!-- INDENTATION -->
98	@@ -1072,8 +1146,14 @@
99	<tr valign="top" align="left">
100	<td width="22%"></td>
101	<td width="78%">
102	-<p>Default: no</p>
103	+<p>Default: no</p></td>
104	+</table>
105	<!-- INDENTATION -->
106	+<table width="100%" border=0 rules="none" frame="void"
107	+ cols="2" cellspacing="0" cellpadding="0">
108	+<tr valign="top" align="left">
109	+<td width="28%"></td>
110	+<td width="72%">
111	<p>Rich Text format attachments produced by some versions of
112	Microsoft Outlook cannot be completely decoded at present.
113	Setting this option to yes allows compatibility with the
114	@@ -1177,6 +1257,48 @@
115	<tr valign="top" align="left">
116	<td width="11%"></td>
117	<td width="89%">
118	+<p><b>Gunzip Command</b></p></td>
119	+</table>
120	+<!-- INDENTATION -->
121	+<table width="100%" border=0 rules="none" frame="void"
122	+ cols="2" cellspacing="0" cellpadding="0">
123	+<tr valign="top" align="left">
124	+<td width="22%"></td>
125	+<td width="78%">
126	+<p>Default: /usr/bin/gunzip</p>
127	+<!-- INDENTATION -->
128	+<p>Where the "gunzip" command is installed. This
129	+is used for expanding .gz files. To disable gzipped file
130	+checking, set this value to blank and the timeout to 0.</p>
131	+</td>
132	+</table>
133	+<!-- INDENTATION -->
134	+<table width="100%" border=0 rules="none" frame="void"
135	+ cols="2" cellspacing="0" cellpadding="0">
136	+<tr valign="top" align="left">
137	+<td width="11%"></td>
138	+<td width="89%">
139	+<p><b>Gunzip Timeout</b></p></td>
140	+</table>
141	+<!-- INDENTATION -->
142	+<table width="100%" border=0 rules="none" frame="void"
143	+ cols="2" cellspacing="0" cellpadding="0">
144	+<tr valign="top" align="left">
145	+<td width="22%"></td>
146	+<td width="78%">
147	+<p>Default: 50</p>
148	+<!-- INDENTATION -->
149	+<p>The maximum length of time the "gunzip" command
150	+is allowed to run to expand 1 attachment file (in
151	+seconds).</p>
152	+</td>
153	+</table>
154	+<!-- INDENTATION -->
155	+<table width="100%" border=0 rules="none" frame="void"
156	+ cols="2" cellspacing="0" cellpadding="0">
157	+<tr valign="top" align="left">
158	+<td width="11%"></td>
159	+<td width="89%">
160	<p><b>Unrar Command</b></p></td>
161	</table>
162	<!-- INDENTATION -->
163	@@ -1225,6 +1347,30 @@
164	<tr valign="top" align="left">
165	<td width="11%"></td>
166	<td width="89%">
167	+<p><b>Find UU−Encoded Files</b></p></td>
168	+</table>
169	+<!-- INDENTATION -->
170	+<table width="100%" border=0 rules="none" frame="void"
171	+ cols="2" cellspacing="0" cellpadding="0">
172	+<tr valign="top" align="left">
173	+<td width="22%"></td>
174	+<td width="78%">
175	+<p>Default: no<br>
176	+A few viruses store their infected data in UU−encoded
177	+files, to try to catch out virus scanners. This rarely
178	+succeeds at all. Setting this option to yes means that you
179	+can apply filename and filetype checks to the contents of
180	+UU−encoded files. This may occasionally be useful, in
181	+which case you should set to yes. This can also be the
182	+filename of a ruleset.</p>
183	+</td>
184	+</table>
185	+<!-- INDENTATION -->
186	+<table width="100%" border=0 rules="none" frame="void"
187	+ cols="2" cellspacing="0" cellpadding="0">
188	+<tr valign="top" align="left">
189	+<td width="11%"></td>
190	+<td width="89%">
191	<p><b>Block Encrypted Messages</b></p></td>
192	</table>
193	<!-- INDENTATION -->
194	@@ -1508,7 +1654,7 @@
195	<tr valign="top" align="left">
196	<td width="22%"></td>
197	<td width="78%">
198	-<p>Default: yes</p>
199	+<p>Default: auto</p>
200	<!-- INDENTATION -->
201	<p>Do you want to scan email for viruses? A few people
202	don’t have virus scanner licence and so want to
203	@@ -1519,7 +1665,9 @@
204	Scanners = none" instead.<br>
205	If you want to be able to switch scanning on/off for
206	different users or different domains, set this to the
207	-filename of a ruleset.</p>
208	+filename of a ruleset. If you set this to auto then it
209	+searches for and uses every available installed virus
210	+scanner.</p>
211	</td>
212	</table>
213	<!-- INDENTATION -->
214	@@ -1999,6 +2147,61 @@
215	<tr valign="top" align="left">
216	<td width="11%"></td>
217	<td width="89%">
218	+<p><b>Use Stricter Phishing Net</b></p></td>
219	+</table>
220	+<!-- INDENTATION -->
221	+<table width="100%" border=0 rules="none" frame="void"
222	+ cols="2" cellspacing="0" cellpadding="0">
223	+<tr valign="top" align="left">
224	+<td width="22%"></td>
225	+<td width="78%">
226	+<p>Default: yes</p>
227	+<!-- INDENTATION -->
228	+<p>If this is set to yes, then most of the URL in a link
229	+must match the destination address it claims to take you to.
230	+This is the default as it is a much stronger test and is
231	+very hard to maliciously avoid. If this is set to no, then
232	+just the company name and country (and any names between the
233	+two, dependent on the specific country) must match. This is
234	+not as strict as it will not protect you against internal
235	+malicious sites based within the company being abused. For
236	+example, it would not find
237	+www.nasty.company−name.co.uk pretending to be
238	+www.nice.company−name.co.uk. But it will still detect
239	+most phishing attacks of the type www.nasty.co.jp versus
240	+www.nice.co.jp. Depending on the country code it knows how
241	+many levels of domain need to be checked. This can also be
242	+the filename of a ruleset.</p>
243	+</td>
244	+</table>
245	+<!-- INDENTATION -->
246	+<table width="100%" border=0 rules="none" frame="void"
247	+ cols="2" cellspacing="0" cellpadding="0">
248	+<tr valign="top" align="left">
249	+<td width="11%"></td>
250	+<td width="89%">
251	+<p><b>Highlight Phishing Fraud</b></p></td>
252	+</table>
253	+<!-- INDENTATION -->
254	+<table width="100%" border=0 rules="none" frame="void"
255	+ cols="2" cellspacing="0" cellpadding="0">
256	+<tr valign="top" align="left">
257	+<td width="22%"></td>
258	+<td width="78%">
259	+<p>Default: yes</p>
260	+<!-- INDENTATION -->
261	+<p>If a phishing fraud is detected, do you want to highlight
262	+the tag with a message stating that the link may be to a
263	+fraudulent web site. This can also be the filename of a
264	+ruleeset.</p>
265	+</td>
266	+</table>
267	+<!-- INDENTATION -->
268	+<table width="100%" border=0 rules="none" frame="void"
269	+ cols="2" cellspacing="0" cellpadding="0">
270	+<tr valign="top" align="left">
271	+<td width="11%"></td>
272	+<td width="89%">
273	<p><b>Phishing Safe Sites File</b></p></td>
274	</table>
275	<!-- INDENTATION -->
276	@@ -2026,6 +2229,35 @@
277	<tr valign="top" align="left">
278	<td width="11%"></td>
279	<td width="89%">
280	+<p><b>Country Sub−Domains List</b></p></td>
281	+</table>
282	+<!-- INDENTATION -->
283	+<table width="100%" border=0 rules="none" frame="void"
284	+ cols="2" cellspacing="0" cellpadding="0">
285	+<tr valign="top" align="left">
286	+<td width="22%"></td>
287	+<td width="78%">
288	+<p>Default: %etc−dir%/country.domains.conf</p>
289	+</td>
290	+</table>
291	+<!-- INDENTATION -->
292	+<table width="100%" border=0 rules="none" frame="void"
293	+ cols="2" cellspacing="0" cellpadding="0">
294	+<tr valign="top" align="left">
295	+<td width="11%"></td>
296	+<td width="89%">
297	+<p>This file lists all the countries that use
298	+2nd−level and 3rd−level domain names to classify
299	+distinct types of website within their country. This cannot
300	+be the name of a ruleset, it is just a simple
301	+setting.</p></td>
302	+</table>
303	+<!-- INDENTATION -->
304	+<table width="100%" border=0 rules="none" frame="void"
305	+ cols="2" cellspacing="0" cellpadding="0">
306	+<tr valign="top" align="left">
307	+<td width="11%"></td>
308	+<td width="89%">
309	<p><b>Allow IFrame Tags</b></p></td>
310	</table>
311	<!-- INDENTATION -->
312	@@ -2317,7 +2549,7 @@
313	<tr valign="top" align="left">
314	<td width="11%"></td>
315	<td width="89%">
316	-<p><b>Allow Object Codebase Tags</b></p></td>
317	+<p><b>Ignored Web Bug Filenames</b></p></td>
318	</table>
319	<!-- INDENTATION -->
320	<table width="100%" border=0 rules="none" frame="void"
321	@@ -2325,7 +2557,7 @@
322	<tr valign="top" align="left">
323	<td width="22%"></td>
324	<td width="78%">
325	-<p>Default: no</p></td>
326	+<p>Default:</p></td>
327	</table>
328	<!-- INDENTATION -->
329	<table width="100%" border=0 rules="none" frame="void"
330	@@ -2333,12 +2565,70 @@
331	<tr valign="top" align="left">
332	<td width="28%"></td>
333	<td width="72%">
334	+<p>This is a list of filenames (or parts of filenames) that
335	+may appear in the filename of a web bug URL. They are only
336	+checked in the filename, not any directories or hostnames in
337	+the URL of the possible web bug. If it appears, then the web
338	+bug is assumed to be a harmless "spacer" for page
339	+layout purposes and not a real web bug at all. It should be
340	+a space− and/or comma−separated list of filename
341	+parts. Note: Use this with care, as spammers may use this to
342	+circumvent the web bug trap. It is disabled by default
343	+because of this problem. This can also be the filename of a
344	+ruleset.</p>
345	+</td>
346	+</table>
347	+<!-- INDENTATION -->
348	+<table width="100%" border=0 rules="none" frame="void"
349	+ cols="2" cellspacing="0" cellpadding="0">
350	+<tr valign="top" align="left">
351	+<td width="11%"></td>
352	+<td width="89%">
353	+<p><b>Web Bug Replacement</b></p></td>
354	+</table>
355	+<!-- INDENTATION -->
356	+<table width="100%" border=0 rules="none" frame="void"
357	+ cols="2" cellspacing="0" cellpadding="0">
358	+<tr valign="top" align="left">
359	+<td width="22%"></td>
360	+<td width="78%">
361	+<p>Default:
362	+http://www.sng.ecs.soton.ac.uk/mailscanner/images/1x1spacer.gif</p>
363	+<!-- INDENTATION -->
364	+<p>When a web bug is found, what image do you want to
365	+replace it with? By replacing it with a real image, the page
366	+layout still works properly, so the formatting and layout of
367	+the message is correct. The following is a harmless
368	+untracked 1x1 pixel transparent image. If this is not
369	+specified, the the old value of
370	+"MailScannerWebBug" is used, which of course is
371	+not an image and may well upset layout of the email. This
372	+can also be the filename of a ruleset.</p>
373	+</td>
374	+</table>
375	+<!-- INDENTATION -->
376	+<table width="100%" border=0 rules="none" frame="void"
377	+ cols="2" cellspacing="0" cellpadding="0">
378	+<tr valign="top" align="left">
379	+<td width="11%"></td>
380	+<td width="89%">
381	+<p><b>Allow Object Codebase Tags</b></p></td>
382	+</table>
383	+<!-- INDENTATION -->
384	+<table width="100%" border=0 rules="none" frame="void"
385	+ cols="2" cellspacing="0" cellpadding="0">
386	+<tr valign="top" align="left">
387	+<td width="22%"></td>
388	+<td width="78%">
389	+<p>Default: no</p>
390	+<!-- INDENTATION -->
391	<p>Do you want to allow <Object Codebase=...> tags in
392	email messages? This is a bad idea as it leaves you
393	unprotected against various Microsoft−specific
394	security vulnerabilities. But if your users demand it, you
395	can do it. This can also be the filename of a ruleset.
396	-Possible values:</p></td>
397	+Possible values:</p>
398	+</td>
399	</table>
400	<!-- TABS -->
401	<table width="100%" border=0 rules="none" frame="void"
402	@@ -4826,7 +5116,7 @@
403	<tr valign="top" align="left">
404	<td width="22%"></td>
405	<td width="78%">
406	-<p>Default: no</p>
407	+<p>Default: yes</p>
408	<!-- INDENTATION -->
409	<p>Do you want to detect spam using the very good
410	SpamAssassin package? You must have installed SpamAssassin
411	@@ -6117,7 +6407,7 @@
412	<tr valign="top" align="left">
413	<td width="11%"></td>
414	<td width="89%">
415	-<p><b>SpamAssassin Default Rules Dir</b></p></td>
416	+<p><b>SpamAssassin Local State Dir</b></p></td>
417	</table>
418	<!-- INDENTATION -->
419	<table width="100%" border=0 rules="none" frame="void"
420	@@ -6133,10 +6423,38 @@
421	<tr valign="top" align="left">
422	<td width="28%"></td>
423	<td width="72%">
424	+<p>The rules created by the "sa−update" tool
425	+are searched for here. This directory contains the
426	+spamassassin/3.001001/updates_spamassassin_org directory
427	+structure beneath it. Only un−comment this setting
428	+once you have proved that the sa−update cron job has
429	+run successfully and has created a directory structure under
430	+the spamassassin directory within this one and has put some
431	+*.cf files in there. Otherwise it will ignore all your
432	+current rules!</p>
433	+</td>
434	+</table>
435	+<!-- INDENTATION -->
436	+<table width="100%" border=0 rules="none" frame="void"
437	+ cols="2" cellspacing="0" cellpadding="0">
438	+<tr valign="top" align="left">
439	+<td width="11%"></td>
440	+<td width="89%">
441	+<p><b>SpamAssassin Default Rules Dir</b></p></td>
442	+</table>
443	+<!-- INDENTATION -->
444	+<table width="100%" border=0 rules="none" frame="void"
445	+ cols="2" cellspacing="0" cellpadding="0">
446	+<tr valign="top" align="left">
447	+<td width="22%"></td>
448	+<td width="78%">
449	+<p>Default:</p>
450	+<!-- INDENTATION -->
451	<p>This tells MailScanner where to look for the default
452	rules. If this is set it adds to the list of places that are
453	searched. MailScanner will always look at the following
454	-places (even if this option is not set):</p></td>
455	+places (even if this option is not set):</p>
456	+</td>
457	</table>
458	<!-- TABS -->
459	<table width="100%" border=0 rules="none" frame="void"
460	@@ -6223,8 +6541,8 @@
461	<table width="100%" border=0 rules="none" frame="void"
462	cols="5" cellspacing="0" cellpadding="0">
463	<tr valign="top" align="left">
464	-<td width="11%"></td>
465	-<td width="20%">
466	+<td width="22%"></td>
467	+<td width="9%">
468
469	<p>%d</p>
470	</td>
471	@@ -6236,8 +6554,8 @@
472	<td width="54%">
473	</td>
474	<tr valign="top" align="left">
475	-<td width="11%"></td>
476	-<td width="20%">
477	+<td width="22%"></td>
478	+<td width="9%">
479
480	<p>%5.2f</p>
481	</td>
482	@@ -6249,8 +6567,8 @@
483	<td width="54%">
484	</td>
485	<tr valign="top" align="left">
486	-<td width="11%"></td>
487	-<td width="20%">
488	+<td width="22%"></td>
489	+<td width="9%">
490
491	<p>%05.1f</p>
492	</td>
493	@@ -6261,24 +6579,59 @@
494	</td>
495	<td width="54%">
496	</td>
497	+</table>
498	+<!-- INDENTATION -->
499	+<table width="100%" border=0 rules="none" frame="void"
500	+ cols="2" cellspacing="0" cellpadding="0">
501	<tr valign="top" align="left">
502	<td width="11%"></td>
503	-<td width="20%">
504	-
505	-<p><b>Debug</b></p>
506	-</td>
507	-<td width="1%"></td>
508	-<td width="14%"></td>
509	-<td width="54%">
510	-</td>
511	+<td width="89%">
512	+<p><b>SpamAssassin Cache Timings</b></p></td>
513	+</table>
514	+<!-- INDENTATION -->
515	+<table width="100%" border=0 rules="none" frame="void"
516	+ cols="2" cellspacing="0" cellpadding="0">
517	+<tr valign="top" align="left">
518	+<td width="22%"></td>
519	+<td width="78%">
520	+<p>Default: 1800,300,10800,172800,600</p></td>
521	</table>
522	<!-- INDENTATION -->
523	<table width="100%" border=0 rules="none" frame="void"
524	cols="2" cellspacing="0" cellpadding="0">
525	<tr valign="top" align="left">
526	+<td width="32%"></td>
527	+<td width="68%">
528	+<p>Do not change this unless you absolutely have to, these
529	+numbers have been carefully calculated. They affect the
530	+length of time that different types of message are stored in
531	+the SpamAssassin cache which can be configured earlier in
532	+this file (look for "Cache"). The numbers are all
533	+set in seconds. They are:<br>
534	+1. Non−Spam cache lifetime = 30 minutes<br>
535	+2. Spam (low scoring) cache lifetime = 5 minutes<br>
536	+3. High−Scoring spam cache lifetime = 3 hours<br>
537	+4. Viruses cache lifetime = 2 days<br>
538	+5. How often to check the cache for expired messages = 10
539	+minutes</p>
540	+</td>
541	+</table>
542	+<!-- TABS -->
543	+<table width="100%" border=0 rules="none" frame="void"
544	+ cols="5" cellspacing="0" cellpadding="0">
545	+<tr valign="top" align="left">
546	<td width="11%"></td>
547	-<td width="89%">
548	-<p>Default: no</p></td>
549	+<td width="7%">
550	+
551	+<p><b>Debug</b></p>
552	+</td>
553	+<td width="4%"></td>
554	+<td width="16%">
555	+
556	+<p>Default: no</p>
557	+</td>
558	+<td width="62%">
559	+</td>
560	</table>
561	<!-- INDENTATION -->
562	<table width="100%" border=0 rules="none" frame="void"
563	@@ -6424,6 +6777,31 @@
564	a "side effect" of doing something useful such as
565	logging lots of information about the batch of messages to a
566	file or an SQL database.</p>
567	+</td>
568	+</table>
569	+<!-- INDENTATION -->
570	+<table width="100%" border=0 rules="none" frame="void"
571	+ cols="2" cellspacing="0" cellpadding="0">
572	+<tr valign="top" align="left">
573	+<td width="11%"></td>
574	+<td width="89%">
575	+<p><b>Always Looked Up Last After Batch</b></p></td>
576	+</table>
577	+<!-- INDENTATION -->
578	+<table width="100%" border=0 rules="none" frame="void"
579	+ cols="2" cellspacing="0" cellpadding="0">
580	+<tr valign="top" align="left">
581	+<td width="22%"></td>
582	+<td width="78%">
583	+<p>Default: no</p>
584	+<!-- INDENTATION -->
585	+<p>This option is intended for people who want to log
586	+per−batch information. This is evaluated after the
587	+"Always Looked Up Last" configuration option for
588	+each message in the batch. This is looked up once for the
589	+entire batch. Its value is completely ignored, it is purely
590	+there to have side effects. If you want to use it, read
591	+CustomConfig.pm.</p>
592	</td>
593	</table>
594	<!-- INDENTATION -->