mail server blow up so to speak and then wonder why /var is out of inodes and
seeing that 803,000 or so inodes are in use. Where could they posibly be in
use? Then finding 801,000+ 0 byte temp files which had been accumulating for
quite awhile in /var/spool/MailScanner/incoming/SpamAssassin-Temp.
ok sthen@
- Fixes URL used to fetch phishing-detection database; the domain that
it was hosted on lapsed. You may have a corrupt database: if the file
/var/spool/MailScanner/quarantine/phishingupdate exists, delete it
and run update_bad_phishing_sites and update_bad_phishing_emails
manually as the "run as user".
- While there update the TNEF.pm fix to improve temp file handling.
MailScanner.conf and explicitly start as that user. This avoids setuid
in perl (triggering taint mode) and so it sidesteps taint mode fallout
which has appeared recently, most likely due to the CVE-2011-1487 fix
in Perl.
Maintainer believed to be away this week, so committing now and we
can change it later if he disagrees when he returns. ok todd@
Feedback from sthen@ including adding a conflict marker as a
kludge to ensure that if a user wants to use AV support that
the correct version is installed (0.94 or newer) since it is
an optional dependency. Great job by the Clam crew for making
this such a mess. The current version of MailScanner is broken
if using 0.94 since the commandline opts were changed.
ok todd@ sthen@
MailScanner is a complete e-mail security system designed for use on
e-mail gateways. It protects against viruses, and detects attacks
against e-mail client packages (such as Outlook, Outlook Express,
Eudora). It can also detect almost all unsolicited commercial e-mail
(spam) passing through it and respond to all incidents in a wide variety
of ways.
..see http://www.mailscanner.info/ for more details.
I have included a generic spam scanner that if enabled uses dspam, as an
alternative to SpamAssassin.
Thanks to Brad Smith for helping get this ready for import. This has been
a few years in the making.
