Hi there, On Sat, 3 Aug 2013, Bob Miller wrote:
Reading that thread also got me to considering that another solution to this problem is to not put the socket in the /tmp directory, but make a custom directory and limit access to the socket via the permissions on that directory. This isn't such a bad idea in that I could use it to achieve my goal, but it seems like admitting defeat.
Heh... if it works, do it and I'm out. :)
Besides, why have the LocalSocket* settings in clamd.conf if you can't use them?
If your mail's working, at least you have more time for research. :)
This is a stock debian jesse build.
Ouch. Quoting from http://www.debian.org/releases/testing/ [QUOTE] ... the next major Debian release after wheezy is "jessie". This release started as a copy of wheezy, and is currently in a state called "testing". That means that things SHOULD NOT BREAK AS BADLY as in unstable or experimental distributions ... [/QUOTE] My emphasis on "should not break as badly". Having had more than enough trouble with 'stable', I wouldn't recommend that you use the 'testing' version of Debian for serious mail processing. Incidentally this list of open issues makes me uneasy: http://sourceforge.net/p/simscan/bugs/ -- 73, Ged. _______________________________________________ Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net http://www.clamav.net/support/ml
