On Fri, 25 Oct 2002, Daniel Liston wrote:
> 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? Look for spamd, specifically the address it's listening on: # linux netstat -ntl | egrep 783 # most everything else netstat -na | egrep LISTEN | egrep 783 Alternately, use: lsof -n -iTCP:783 Compare that address to the address spamc is using (see below). > 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. strace on Linux, truss on Solaris... I'm using the following in .procmailrc: :0fw * < 100000 | /usr/bin/spamc -d localhost -p 783 It's not clear from my quick check if spamc defaults to using 127.0.0.1; either way if you specify the address everywhere, you should be able to eliminate one potential cause of confusion. I start spamd with /usr/bin/spamd --username=nobody --auto-whitelist --daemonize --vpopmail \ --create-prefs spamd defaults to listening on 127.0.0.1 (see the -i flag) and only accepts connections from 127.0.0.1 (see the -A flag) hth, -- Bob ------------------------------------------------------- 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
