OK - I think I have narrowed down what is happening with this, though I don't know why. I have placed my local.cf file in a non-standard directory and I am using the --siteconfigpath=path to point to that directory (where my local.cf file and my own custom rules files are located). For some reason this breaks the SURBL checks. If I run spamassassin without that directive (and use local.cf in its standard installation location), the SURBL checks work fine. Can someone else confirm this? This is with 3.0.0.
--
Chris Jett
[EMAIL PROTECTED]


Reply via email to