[Maia-users] clamd death spiral

[Robert LeBlanc]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Aaron Bennett wrote:

> Changing clamd to run as the amavis user (and changing ownership of 
> /tmp/clamd, /var/clam, var/log/clamd, etc etc) fixed the problem, BUT...
> 
> it worked running as the clamd user for at least six months.

If clamd is running on the same host as amavisd-maia, it's generally a
good idea to use the Unix socket connection rather than the TCP socket
anyway.  TCP sockets add a lot of overhead that you really only need if
clamd is being hosted on a separate box.

If I had to hazard a guess, I'd say that a recent update of clamd closed
a permissions loophole that had been allowing you to get away with
something you shouldn't have for six months.

- --
Robert LeBlanc <rjl at renaissoft.com>
Renaissoft, Inc.
Maia Mailguard <http://www.maiamailguard.com/>

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFGHwyHGmqOER2NHewRAom2AJ9Y8ygOgXBi7g2ewjTaDkiQmU5teQCfeyoJ
1inzGSwPsqqrlerXSYBHoDI=
=dahI
-----END PGP SIGNATURE-----