On Wed, May 09, 2007 at 12:14:24AM -0500, Gabriel Millerd wrote:
>   Beyond the s/3.1.20/v3.2.0/ issue that some people cannot get past.
> I have the same issue. I had to juggle my cf/pre files entries for
> quite some time to get past the check_scan problem you describe for
> spamd to run peachy. I, like you I suspect, loaded up one single file
> with all my config entries. The v3.2 suite seems to want these in a
> number of files. Where v3.1.x was forgiving I guess.

The config code didn't really change between 3.1 and 3.2.  3.2 doesn't
care if you have one pre file or twenty.  However, what does matter is
that you have all the loadplugin lines that you need to have.  In 3.2,
the check() function was pluginized, and so you need to load a plugin
that implements the function or else you don't have a check() function.
Without that function, SA can't scan anything, and so it helpfully alerts
you to the fact that you don't have this functionality.

>  So in v3.2 if you remove all your .pre files and just have local.cf
> with all your rules you cannot sa-update, it will bomb. You need to

If you remove all your pre files, you will have broken your SA install, forget
sa-update.

In short, and I'll say it in caps so people know I mean this very seriously:

        DON'T PUT LOADPLUGIN LINES IN CF FILES, LEAVE THEM IN PRE FILES 

I only know of one good reason to put loadplugin lines in a cf file, and it
involves testing plugins from a sandbox.  I haven't come up with a reason in a
normal production install.

> # mv init.pre local.cf

Why would you do that?

> config: no configuration text or files found! please check your setup
> check: no loaded plugin implements 'check_main': cannot scan! at
> /usr/local/share/perl/5.8.8/Mail/SpamAssassin/PerMsgStatus.pm line
> 164.

Of course, you've disabled all the plugins.  sa-update can't lint anything,
and you've broken your install.

-- 
Randomly Selected Tagline:
"A CAT scan should take less time than a PET scan.  For a CAT scan,
 they're only looking for one thing, whereas a PET scan could result in
 a lot of things."               - Carl Princi, 2002/07/19

Attachment: pgpAHNzljeiKt.pgp
Description: PGP signature

Reply via email to