Yesterday I installed amavis_new together with clamav V 0.71
under SuSE 9.0. Amavis and clamav are both running under vscan
and amavis is installed in dir /var/spool/amavis. Amavis is
configured to be running in a dual sendmail configuration.
When receiving an email, I get following entry in
Am Mit, 2004-06-16 um 13.48 schrieb Tomasz Papszun:
On Wed, 16 Jun 2004 at 13:04:45 +0200, Harald Arnold wrote:
Yesterday I installed amavis_new together with clamav V 0.71
Just for completeness: You probably mean amavisd-new (note d).
Yes correct, amavisd-new-20030616-p5 !
[...]
Socket
!!! SOLVED !!! WAS ACCESS PROBLEM !!!
I've got no idea if the socket permissions have any bad results in
your situation. They shouldn't as the user matches. I did _not_ set
them manually. The socket is created with such ones.
I must add that I use postfix (while you - sendmail). So
Am Mit, 2004-06-16 um 16.23 schrieb Harald Arnold:
!!! SOLVED !!! WAS ACCESS PROBLEM !!!
Normaly clamd is defined and runned as user clamav. But when using
amavis the user for clamd should be the same user as amavis (vscan).
/etc/clamav and /var/clamd have been owned by user clamav. When
I installed yesterday clamav (Linux). Clamd (over TCP),
clamscan and clamdscan are all working fine.
Now I want to continue with the step to install and
configurate amavis_new using clamav.
Clamd can work with sockets OR tcp. How must I
configure amavis_new and clamav to cooperate.
I would
I installed yesterday clamav (Linux). Clamd (over TCP),
clamscan and clamdscan are all working fine.
Now I want to continue with the step to install and
configurate amavis_new using clamav.
Clamd can work with sockets OR tcp. How must I
configure amavis_new and clamav to cooperate.
I would
