MailScanner Digest, Vol 20, Issue 49

Culley Morrow culleym at
Tue Aug 21 17:36:49 IST 2007

Thanks for the replies. This server is quite meager with 256mb RAM and a
30gb hard drive, all running on a 4 year old Dell desktop. Meager is putting
it mildly. I've got to make it work while it's in place, a massive
replacement is in the works though.

Clamscan was what I was meaning actually. I remember reading a while back in
the archives that it was a major stumbling point with new versions on older
systems. After an update it was running OK, but slowly getting further and
further behind in the mail delivery.

Anyway, I'll start digging through the wiki for better rules and see what I
can start filtering out.

Culley Morrow
IT Manager
Geneva Woods Pharmacy

-----Original Message-----
Message: 11
Date: Tue, 21 Aug 2007 09:55:06 +0100
From: Greg Matthews <gmatt at>
Subject: Re: New Clam, Old, Mailscanner, Ancient Kernel
To: MailScanner discussion <mailscanner at>
Message-ID: <46CAA86A.4060206 at>
Content-Type: text/plain; charset=windows-1252; format=flowed

Culley Morrow wrote:
> Ill list out the software versions below and I need a bit of assistance 
> making them work for now. I know all I need to do is upgrade the kernel 
> to 2.6 and it all works, but Id like to get them functioning As-Is 
> and then do the upgrade so I have something working to fall back on. 
> Clam AV is currently shut off since clamd as a service was so slow.

kernel upgrade probably not very important. As others have pointed out, 
there is little reason not to upgrade MS and SA. Stick as much memory in 
the box as it can handle.

> Kernel 2.4.18-bf2.4
> Mailscanner 3.27.1-1
> Clam AV 0.90.1-3etch3
> Spam Assassin 2.64-1
> Currently we are inundated with mass spam and I need to get some AV in 
> place, be it Clam or another GNU/GPL/free as in beer-ware. I need a 
> hand here if anyone wants to chime in.

if you are "inundated" then the best start you can make is to reject as 
much as possible at the MTA. As this is Debian, your MTA is probably 
(but not necessarily) exim. Look at putting in a single well regarded 
block list at the MTA, something like but do your 
research and find one that /you/ like the look of (block list 
preferences can start flame wars!). Make sure you are rejecting mail at 
the MTA for all unknown recipients and not accepting then bouncing. Set 
up your MTA to throttle incoming mail so it doesnt get overwhelmed or 
let your incoming queue build up uncontrollably.

Visit the MS wiki for tips on how to do this - dig deep, it can be a bit 
tricky to find what you are looking for. Search the archives for good 
links into the wiki.

Greg Matthews           01491 692445
Head of UNIX/Linux, iTSS Wallingford

More information about the MailScanner mailing list