More 4.50.15 woes on FreeBSD

TCIS List Acct listacct at
Wed Feb 8 13:04:32 GMT 2006

Anthony Peacock wrote:

> This is the method I use.  When I moved to using MailScanner I already 
> had a working Sendmail server with a working virus scanner and a working 
> install of SpamAssassin.  The install script made too many assumptions 
> and messed around with a setup that already worked well and I fully 
> understood.  So I used the .tar.gz file and manually installed. Upgrades 
> take a little longer, but I do get to know all of the changes as I work 
> my way through the install.  This doesn't take too long for me now, and 
> I much more comfortable doing it this way.  If (when?) I ever get around 
> to bringing a new email server up from scratch I will probably use the 
> script, from the word go, but with my current set up that 
> would just create more problems for me.  I would certainly recommend 
> anyone setting up a mailserver for the first time to use the install 
> scripts.
> All that aside, the way that I check to make sure I have the correct 
> Perl modules installed is this.  After extracting the tar.gz file, there 
> is a directory called perl-tar which contains the MailScanner.tar.gz as 
> well as all of the required Perl modules, there is also a script called 
> CheckModuleVersion.  CheckModuleVersion can be used to compare the 
> installed module version with the required version.
> I am also perverse in that I don't use to install my Perl 
> modules (also habit from many years ago).  So I keep a directory with 
> the distributions of the modules installed on my system. So I usually 
> just copy the module .tar.gz files into this directory and do a filename 
> compare, building the ones that are newer.
> It sounds complicated, but actually is very straight forward, and gives 
> me the confidence that I know what is happening.

Couldn't have said it better myself.


Mike Bacher / listacct at
TCIS - TulsaConnect Internet Services

More information about the MailScanner mailing list