After upgrade to MS 4.74 mails are stuck in queue.

memmas memmas at otenet.gr
Wed Jan 7 17:12:41 GMT 2009


Now it's running, Something went wrong when copying old configs to new 
MailScanner probably.
MailScanner --lint gave some errors but it's working.
I'm upgrading from 4.73.4-2. My system was up and running before the 
upgrade with same versions of clamav and spamassassin.
I 'm using Clamd not the Mail::ClamAV perl module
Spamassassin 3.2.5 perl 5.10.0 slackware packages


MailScanner --debug still stucks though.
The output of MailScanner --lint was:

Trying to setlogsock(unix)
Read 848 hostnames from the phishing whitelist
Read 4020 hostnames from the phishing blacklist
Checking version numbers...
Version installed (4.74.15) does not match version stated in
MailScanner.conf file (4.74.13), you may want to run 
upgrade_MailScanner_conf
to ensure your MailScanner.conf file contains all the latest settings.

MailScanner setting GID to  (76)
MailScanner setting UID to  (76)

Checking for SpamAssassin errors (if you use it)...
Using SpamAssassin results cache
Connected to SpamAssassin cache database
config: failed to parse line, skipping, in 
"/etc/mail/spamassassin/local.cf": razorhome = /var/spool/MailScanner/razor/
config: failed to parse line, skipping, in 
"/etc/mail/spamassassin/local.cf": logfile = razor-agent.log
SpamAssassin reported an error.
I have found clamd scanners installed, and will use them all by default.
Using locktype = posix
MailScanner.conf says "Virus Scanners = auto"
Found these virus scanners installed: clamd
===========================================================================
Filename Checks: Windows/DOS Executable (1 eicar.com)
Other Checks: Found 1 problems
Virus and Content Scanning: Starting
ERROR::Permissions Problem. Clamd was denied access to 
/var/spool/MailScanner/incoming/18354
===========================================================================

If any of your virus scanners (clamd)
are not listed there, you should check that they are installed correctly
and that MailScanner is finding them correctly via its virus.scanners.conf.
--------------------------------

thanks

Kai Schaetzl wrote:
> might be helpful to know from which version you upgraded and how you make 
> postfix and mailscanner work together. (I remember there where at least 
> two methods in the past.) You had these already running for a while with 
> your last MS setup?
> postfix 2.5.5
> ClamAV 0.94.2
> Spamassassin 3.2.5
>
> Kai
>
>   



More information about the MailScanner mailing list