Theo Van Dinter wrote:
On Thu, Sep 30, 2004 at 01:42:51PM +0200, Maurice Lucas wrote:I had a problem a couple of months back .. probably should have submitted a but report, but I didn't take the time to narrow it down. I had two installations that were virtually identicle running. One ran SURBL both easily and as expected. The other, seemed to be working but never generated any results in the SA report log. The working system was Fedora Core 2 and the apparently non-working system was Fedora Core 1. After upgrading from the Stock Perl installation with Fedora Core 1 to the up2date release in Fedora Core 2, SpamAssassin started working as expected.
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.
The problem, I'm guessing, is that the init.pre file (loads the plugins) installs into the standard siteconfigpath directory. So if you aim somewhere else, the plugins are never enabled, so no SURBL.
I guess that I pawned it off as not properly reading the release notes, yada yada yada. But, I the bottom line is that for SURBL to work properly, there seems to be a minimum release of Perl that is necessary. A stock Fedora Core 2 works right, but a stock Fedora Core 1 doesn't (at least in my case).
Oh, and thanks guys (Theo, Justin, others) these tools are the bomb. You've made reading e-mail fun again :)
-- Doug Brott
