Exim4 won’t send message

clamavexim

My exim4 don't send any message. The logs says

2011-03-09 15:59:57 1PxKrl-00038i-BT malware acl condition: clamd: ClamAV returned /var/spool/exim4/scan/1PxKrl-00038i-BT: lstat() failed: Permission denied. ERROR

I supose that clamav (running clamd) does'nt have access rights on the mentioned file, but clamav is in the same group as Debian-exim (running exim4). Even changing the folder permissions to a+rwx has no effect.

Any idea where to look for failure reason ?

Best Answer

Directory permissions on /var/spool/exim4/scan should be 750, and owned by the exim user and its primary group (on my FreeBSD systems, these are mailnull and mail, respectively).

If your clamav user has Debian-exim as a supplementary group - that is, if Debian-exim is not its primary group, then you need "AllowSupplementaryGroups yes" in your clamd.conf (and clamd must be started by root).

Related Solutions

Debian Squeeze and exim4: cannot send mail

Make sure that /var/log/exim4 is owned an writable by Debian-exim:

chmod -R u+rw /var/log/exim4
chown -R Debian-exim /var/log/exim4

Edit exim4 Message-ID for releasing blocked mail by Mailscanner

See the "077I" at the start of the line? The "I" is a header flag, you shouldn't be changing that. But the "077" is the number of bytes in that header. Since you are changing the number of characters without changing the count, Exim sees it as a format error.

From http://exim.org/exim-html-current/doc/html/spec_html/ch55.html:

A header may occupy several lines of the file, and to save effort when reading it in, each header is preceded by a number and an identifying character. The number is the number of characters in the header, including any embedded newlines and the terminating newline.

Update the number to reflect the new number of characters and you should be fine.

Best Answer

Related Solutions

Debian Squeeze and exim4: cannot send mail

Edit exim4 Message-ID for releasing blocked mail by Mailscanner

Related Topic