-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> Start spamd with the "--socketpath /path/to/spamd.sock" option and
> then call spamc with the "-U /path/to/spamd.sock" option. Test,
> adjust, repeat...
Can I just:
touch /var/tmp/spamd.sock
chmod 777 /var/tmp/spamd.sock
Or is there another way
--On Tuesday, September 23, 2003 6:48 AM + Jim
<[EMAIL PROTECTED]> wrote:
> spamd --socketpath=/path/to/socket/file
>
> spamc -U /path/to/socket/file
If this is the recommended configuration, then I would suggest that 2.61
change the spec file to make use of this in RPM-based installations.
Hi,
On Mon, 22 Sep 2003 23:45:35 -0500 "Mike Loiterman"
<[EMAIL PROTECTED]> wrote:
> Just reading the release notes for 2.60 and noticed this:
>
> - spamd now supports UNIX-domain sockets for low-overhead scanning,
> thanks
> to Steve Friedl for this. This is strongly recommended if you'r
On Mon, Sep 22, 2003 at 11:45:35PM -0500, Mike Loiterman wrote:
> How do I implement this?
spamd --socketpath=/path/to/socket/file
spamc -U /path/to/socket/file
---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Just reading the release notes for 2.60 and noticed this:
- spamd now supports UNIX-domain sockets for low-overhead scanning,
thanks
to Steve Friedl for this. This is strongly recommended if you're
running
spamc on the same host as the sp