On Dec 30, 2003, at 5:45 PM, Hans Gerber wrote:
We only want spamd to listen on '--socketpath=path'. Spamc should be invoked from within .procmailrc.
I could not get this method to work.
It does work, afaik unix-socket should be cheaper with Resources than TCP_Socket.
The socket implementation appears to be quite a bit faster, at least on my wimpy little linux system. I use "/usr/bin/spamd -dca --socketpath=/var/run/spamassassin" to launch spamd, and "/usr/bin/spamc -U /var/run/spamassassin -u $USER" to run spamc. Works well, and makes me feel a little more secure (even though spamd over TCP binds only to 127.0.0.1 by default).
As to your other question, couldn't you launch spamc as the user who's receiving the mail? It would seem fairly easy to have spamd check the UID of the process that connected through the unix socket, and that should be good enough to authenticate.
Good luck!
Brad Koehn
------------------------------------------------------- This SF.net email is sponsored by: IBM Linux Tutorials. Become an expert in LINUX or just sharpen your skills. Sign up for IBM's Free Linux Tutorials. Learn everything from the bash shell to sys admin. Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click _______________________________________________ Spamassassin-talk mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
