Evan Platt wrote: > At 11:30 AM 10/9/2006, you wrote: > > > spamc is a small executable that hands off the message to spamd for > > processing. > > Ahh ok. > > > > You can run it from the command line the same way you do with > > spamassassin. > > > > spamc < inputfile > outputfile > > > > You also might want to check the process that is running to see > > exactly what settings it is using. > > > > ps -ef | grep spamd > > > For macs, the -ef doesn't work. ps aux is I believe the equivilant: > > root 57 0.0 2.7 43692 14196 ?? Ss 10:35AM 0:06.62 > /opt/local/bin/perl -T -w /opt/local/bin/spamd
That is the process you want, but I don't see any options shown. I'm not sure if it is just not showing them or if you are not using any options. My output from 'ps -ef' looks like this: root 2905 1 0 Oct04 ? 00:00:28 /usr/bin/spamd -d -m 4 --max-conn-per-child=50 -r /var/run/spamd/spamd.pid -u mailuser -x --virtual-config-dir=/home/mailuser/%d/%l/spamassassin > Ok, it appears spamc definitely isn't using network tests. > > Just ran a message through spamc and spamassassin: > > spamc: > > X-Spam-Level: * > X-Spam-Status: No, score=1.6 required=5.0 > tests=EXTRA_MPART_TYPE,INFO_TLD, UPPERCASE_25_50 > autolearn=no version=3.1.6 > > spamassasin: > > X-Spam-Level: ************* > X-Spam-Status: Yes, score=13.3 required=5.0 tests=DNS_FROM_RFC_WHOIS, > EXTRA_MPART_TYPE,INFO_TLD,UPPERCASE_25_50,URIBL_AB_SURBL, > URIBL_JP_SURBL,URIBL_OB_SURBL,URIBL_WS_SURBL autolearn=no > version=3.1.6 > > I called both spamc and spamassassin with the full path. Network tests are definitely missing. There are two ways to turn off network tests. The first is with the '-L' option to spamd. The second is with config options in local.cf. Using the config options should affect both spamd and spamassassin, so based on the behavior, I would say that it looks like you still have the '-L' option on spamd. Or else they are reading their configuration from different directories. One thing you can do is to add the '-D' option to spamd. This will cause it to log lots of debugging stuff that may help you figure out why it is not running network tests. This will be written to syslog by default. This will log LOTS of stuff, so you may want to turn it on, let one or two messages come through, and then turn it off again. You can then read through the debug info and look for problems. If you can't see anything wrong, post it here and see if we can. -- Bowie
