Still getting the same problem. Thanks for the tip thou. Any email i check using spamc or spamassassin works. So it must be the way the mta Sun Java System Messaging Server 6.3 is passing the headers to spamassassin. I tried launching spamd in debug mode really not enough information. Is there anyway to see what the mta is passing to spamd?
----- Original Message ----- From: Matt Kettler <[EMAIL PROTECTED]> Date: Tuesday, May 13, 2008 8:16 pm Subject: Re: spamd To: Mark Walmsley <[EMAIL PROTECTED]> Cc: users@spamassassin.apache.org > Mark Walmsley wrote: > > Spamd is not using whitelist_from_rcvd or > whitelist_from_spf in local.cf > > > > but when i run a test msg > > > > spamassassin --test-mode < 113.msg > > > > or > > > > spamassassin -D < 113.msg > > > > > > > > The whitelist_from_rcvd and whitelist_from_spf are working > > > > I've even tried setting the path. Here is how I'm launching spamd > > > > /opt/csw/bin/spamd -dl -u spamassassin --allowed- > ips=192.168.0.0/16 > > --listen-ip=192.168.1.36 --port=783 -C /opt/csw/etc/spamassassin > > > > Ditch the -C parameter from your spamd commandline. DO NOT > use this > parameter unless you really understand what it does. > > If you wish to specify a site rules directory (where local.cf > and other > local rulefiles exist) to other than the default, use the > --siteconfigpath parameter instead. > > -C does not over-ride the the site rules directory, it over- > rides the > *default* rules directory. i.e.: the location of the base ruleset. > > So, by specifying -C, you've removed all of the default rules > from SA, > including USER_IN_WHITELIST, etc, etc, etc. > > > > >
