> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> samir wrote:
>
> [snip]
>> Regarding TCP-socket, my clamd.conf looks like this:
>> # TCP port address.
>> # Default: disabled
>> #TCPSocket 3310
>
>> It is not active right now. Should it be?
>
> No.
>
>> Nothing in clamsmtpd.conf is active regarding TCP.
>
> You are missing the point, check this in clamd.conf:
>
> # Path to a local socket file the daemon will listen on.
> # Default: disabled (must be specified by a user)
> LocalSocket /tmp/clamd
>
> and this in clamsmtpd.conf:
>
> ClamAddress /tmp/clamd
>
> The point was that these two must be the same; similar situation with TCP,
> which
> you say is not being used.
> - --
> René Berber
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.5 (Cygwin)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
>
> iD8DBQFF4JeiL3NNweKTRgwRAkkbAKDSQlDeivEU2P3k5FaAf4hKXE8weQCg9CRZ
> cprjHgXBaibA8xNZ9/JTuA4=
> =v3Bh
> -----END PGP SIGNATURE-----
>
> _______________________________________________
> Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net
> http://lurker.clamav.net/list/clamav-users.html
>

Ok, I understand.

I've got the following in clamd.conf:
LocalSocket /var/run/clamav/clamd

and this in clamsmtpd.conf:
# The address clamd is listening on
ClamAddress: /var/run/clamav/clamd

/Samir

_______________________________________________
Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net
http://lurker.clamav.net/list/clamav-users.html

Reply via email to