No mail transport after updating DA + SquirrelMail, SpamAssassin & ClamAV

Orbserver

Verified User
Joined
May 2, 2005
Messages
20
I updated Exim to v4.6 months ago before switching to Dovecot, which worked out fine. I was over-due for updating spamd and clamav but this time I decided to update the whole shootin' match. Scripts and RPMs were run in this order:

custom apache (all)
zend
squirrelmail
spamd
clamav

Email stopped working and at first I thought the firewall or SpamAssassin was in the way. Now it looks like something fundamental to Exim I can't figure out. With or without iptables running it's as if ports are not available or already in use or something. I'm also worried that transient mail isn't being queued (I don't know where to look).

Mail updates and customizing exim.conf have been routine until now. What's different is that this is the first full mail system update since converting to Dovecot.

If I use barebones exim.conf (exim4.conf) mail appears to send (sent copies are in IMAP folders) but the message isn't delivered in or outside of the server.

If I change exim.conf to add clamd and spamassassin entries, mail won't send. Squirrelmail or any other client displays SMTP error 451. Eliminate both spamd and clamd and no more error 451 and the message is sent (somewhere).

The 1st clamd line in exim.conf looks like:
av_scanner = clamd:127.0.0.1 3310

The 2nd clamd section look like this:
# ACL that is used after the DATA command
check_message:
# Virus Check
deny message = This message contains a virus or other malware ($malware_name)
# demime = *
malware = *
warn message = X-Antivirus-Scanner: Scanned with Exiscan. You should still use an antivirus.
accept

And the spamd section of exim.conf will either be commented out or enabled.

I even tried reverting back to a known-good exim.conf from a year ago but no help.

Help or suggestions is greatly appreciated. I'm running Fedora Core 2. I'm also running out of time. Thanks.
 
Last edited:
Are you using the exim.conf from the DA site?

If not, then you should be. If you're running Dovecot, then you need to make the changes as shown in the Dovecot posts.

You also need to make sure all the files required by the new exim.conf file exist on your server; see the README file (search these forums).

Once you've gotten that to work be sure to make the changes required to the exim.conf file so anyone caught by SpamBlocker will be able to figure out how to get unblocked.

Jeff
 
Ultimately it was a patched exim.conf for Dovecot that got delivery working. I thought it was already patched. I don't remember patching it after coverting a few months ago and my old exim config didn't work. It's hard to say what I did after updating everything.
 
Back
Top