Email problems after latest yum update (Centos 4.x)

General Discussion of atomic repo and development projects.

Ask for help here with anything else not covered by other forums.
outrage
Forum User
Forum User
Posts: 9
Joined: Thu Aug 30, 2007 1:33 pm

Email problems after latest yum update (Centos 4.x)

Unread post by outrage »

Hey Scott,

Just thought I'd let you know I had a real problem with email since the last Yum update.
The update seemed to go fine with no errors, however the following day I had a client complaining he couldn't use email.

I checked it out and sure enough, no domains could send or recieve email.
I had done a recent Plesk update too and thought it may be related to some of the issues with 8.4

I decided I was barking up the wrong tree after a while and checked the mail log to discover loads of ClamAV errors.

I eventually got the email back up and running but only after removing ClamAV and QMail Scanner.
I haven't dared re-install them yet.

Maybe it's just me but thought you should know :)
Highland
Forum Regular
Forum Regular
Posts: 674
Joined: Mon Apr 10, 2006 12:55 pm

Unread post by Highland »

I ran into the same problem but I thought it was just me. My RHEL5 box updated just fine.
kwebdesign
Forum User
Forum User
Posts: 93
Joined: Sun Feb 13, 2005 2:24 pm
Location: TN

Unread post by kwebdesign »

I had (possibly) this same problem, and when I tried to restart clamd, it complained about not being able to read the log file. I changed the owner of all the files in /var/log/clamav/ to be clamav:clamav, and that fixed it.

I've read elsewhere that these logs need to be owned by qscand, but my install is working fine after making this change. YMMV.

If I remember correctly, there were also several .conf files that had to be renamed on install (because they were installed as .conf.rpmnew), due to obsoleted options in the old files.

I suspect that if you uninstalled it, you would be able to re-install in it would be fine.

EDIT: I have since re-set the owner of my clamav log files back to qscand. I think the key is that after the update and replacement of the .conf files, you need to run qmail-scanner-reconfigure to set the user for clamav to run as back to qscand.
amit290
Forum User
Forum User
Posts: 14
Joined: Thu Nov 22, 2007 11:24 am

Unread post by amit290 »

I had a problem as well (CentOS5). I upgraded to 8.4.0, and then did a yum update. During the yum update i spotted an error message half way through, but everything seemed fine. I was able to send / receive e-mails from domains outside (from hotmail yahoo etc.). Its only when I got a phone call that I found there was a problem.

The problem was it wouldnt send e-mails via port 587, but 25 was fine. Moving the old conf files with the new ones (rpmnew), and then doing:
/usr/bin/qmail-scanner-reconfigure

sorted it. I also did a restart just to be sure there were no problems

/sbin/service clamd restart

and

tail -f /var/log/clamav/clamd.log
mrgastix
Forum User
Forum User
Posts: 6
Joined: Thu Feb 07, 2008 1:04 pm

Unread post by mrgastix »

I had similar problem. The only problem for me was clamd unable to accept two config lines in clamd.conf file.

So I needed to comment out lines 300 and 315:
#ArchiveMaxCompressionRatio 300
#ArchiveBlockMax no

Clamd then started OK.

edit: Using Plesk 8.3, CentOS 5 and this only started after today's full update.
Post Reply