clamavconnector disturbed mailscanner

Discuss our MailScanner install script and MailScanner itself
Post Reply
tuxg
Junior Member
Posts: 21
Joined: 02 Sep 2007, 15:11

clamavconnector disturbed mailscanner

Post by tuxg »

Hi Sarah,

ClamAV and Clamavconnector addon installed by mistake by our support folks on our server where MailScanner is running.
Now, clamav is failing and getting restarted once in a while.
Currently, MailScanner and clamd are running.

What do we need to check and fix now?

Thank you.
Sarah
Moderator
Posts: 934
Joined: 09 Dec 2006, 22:49

Re: clamavconnector disturbed mailscanner

Post by Sarah »

Did you uninstall clamavconnector? You probably would then need to reinstall clamav according to the instructions on our website:
http://www.configserver.com/free/clamav.html
tuxg
Junior Member
Posts: 21
Joined: 02 Sep 2007, 15:11

Re: clamavconnector disturbed mailscanner

Post by tuxg »

ClamAV working fine since then.
Mail flow same as before.

Under cmq -> Delivery Queue, we see only the mails that couldnt be delivered. We do see a "Broken spool file - removed" message there, which we haven't seen earlier.

We have not uninstalled clamavconnector, as we would like to find out if there is an easy way to fix things so that things would not fail later on. We are in the middle of an imp project for which we cannot afford to work on mail subsys as of now. Does auto upgrade of any of mailscanner scripts or clamav would fail such a config?
Sarah
Moderator
Posts: 934
Joined: 09 Dec 2006, 22:49

Re: clamavconnector disturbed mailscanner

Post by Sarah »

If MailScanner is working OK at the moment (it is not clear from your posts whether it is or not) then I would just recommend leaving things as they are until you have the time available to look into it properly. Otherwise, you could log a ticket on our helpdesk if you'd like some help looking into it.

Regards,
Sarah
webjive
Junior Member
Posts: 11
Joined: 03 Aug 2012, 21:44

Re: clamavconnector disturbed mailscanner

Post by webjive »

I had the same issue and it was a full /var issue. Old logs lying around. Caused a fantom issue for us.
Post Reply