No Logging to Syslog: MailScanner 4.65.3-1 on Solaris 9

shuttlebox shuttlebox at
Mon Nov 12 08:18:17 GMT 2007

On Nov 12, 2007 3:09 AM, Mr jeremy pennington
<jeremypennington at> wrote:
> I upgraded to MailScanner 4.65.3-1 last night and since then MailScanner has not logged any messages to syslog. MailWatch shows messages are being processed as normal and I have verified they are.  So I tried copying from the prior version installed (which was 4.54.6) to the new version and restarting MailScanner. This time the standard start up messages were recorded to syslog, but no messages were logged about mail being processed, in fact this disabled mail from being processed (it just stayed in the queue). So I reverted back and everything seems to be working again, except no logs from MailScanner are appearing in syslog. Any thoughts?

Look in for "setlogsock" and compare the differences between
the working version and the new. My guess is that the socket type has
changed. You will also find the same settings in the autoupdate
scripts for the virus scanners.

Also make sure that the syslog daemon listens to remote connections.

# netstat -a | grep syslog
      *.syslog                            Idle

As a Solaris user you might find it handy to check out the Blastwave
collection of software, I package MailScanner and it automagically
solves all dependencies for you. Clam, SpamAssassin and so on is also


More information about the MailScanner mailing list