Could iptables, ipchains, ipfw, or rcf firewall be getting in the way? Does `netstat -an | grep LISTEN` show anything on port 783? Or worse, something else already on 783? Does telnet'ing to localhost 783 give a SPAMD/1.0 message when you quit?
Sorry if these questions have been asked/answered. I did come in late. What about `strace spamc` and ctrl-C out? Any clues there? Then again, that may be a linux command. Dan Theo Van Dinter wrote:
On Fri, Oct 25, 2002 at 02:55:12PM -0500, Daniel Liston wrote:Maybe I missed part of this thread, but shouldn't the process list be checked for a daemon first? `ps -ef | grep spamd`? If it is not running, you need to start it. `spamd -d -c` seems safe enough.Yes, but he said he did a ps and saw spamd running.If it is running, but spamc is not talking to it, try using `spamassassin -P` instead of spamc just to detect results.He did, and that worked, so the likelihood is that spamc isn't talking to spamd. :)
-------------------------------------------------------
This sf.net email is sponsored by: Influence the future of Java(TM) technology. Join the Java Community Process(SM) (JCP(SM)) program now. http://ads.sourceforge.net/cgi-bin/redirect.pl?sunm0004en
_______________________________________________
Spamassassin-talk mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
