FuzzyOcr working but not via MailScanner

[Glenn Steen]

On 19/10/06, Glenn Steen <glenn.steen at gmail.com> wrote:
> On 19/10/06, Glenn Steen <glenn.steen at gmail.com> wrote:
> > On 19/10/06, Anthony Cartmell <ajcartmell at fonant.com> wrote:
> > > > I think you are on to something there Scott. I'll offer a guess...
> > > > Anthony, are you by any chance running Postfix?
> > >
> > > Nope, sendmail.
> >
> > OK. Was just a thought:-).
> >
> > > It seems to be a "search path" issue: MailScanner skips a lot of setup
> > > stuff that spamassassin does from the command line. From MailScanner, the
> > > whole /var/lib/spamassassin/3.001003 directory was being missed and hence
> > > a whole load of default rules.
> >
> > Are you running 3.1.3? I run 3.1.5 and have no such issues (I don't
> > have to set the MailScanner option, and it picks up/scores rules only
> > in files present in the update directory). Maybe you should upgrade
> > SA? If so, I can warmly recommend Jules excellent package:).
> >
> > > FWIW, although I have all my .cf files being read now, FuzzyOcr still
> > > isn't being called. More investigation needed...
> >
> > Updating SA might have something to do with this too... And resetting
> > to the normal MailScanner option... As it is now, any cf file in
> > /etc/mail/spamassassin isn't read, right?
> > Sort of like "the wrong fix to the right problem" or some such:-):-).
> > As usual, I might be blathering a load of garbage too:-).
> >
> (just proving my PF "roots"....)
>
> I looked at SpamAssassin.pm, and this snippet is the clicher:
> -----
> @default_rules_path = (
>   '__local_state_dir__/__version__',
>   '__def_rules_dir__',
>   '__prefix__/share/spamassassin',
>   '/usr/local/share/spamassassin',
>   '/usr/share/spamassassin',
> );
> -----
> As you can see, the normal way to find the sa-updated files is via
> "__local_state_dir__/__version__", where __local_state_dir__ defautls
> to /var/lib/spamassassin .... and __version__ is set (just above that)
> to something like 3.00100X ... If you did an upgrade (and perhaps
> didn't do an sa-update afterwards) I suppose you could end up in a
> situation where the new SA version couldn't find the updated files, I
> suppose (someone a bit more fluent (than me) in how SA is instantiated
> will probably eb able to tell if this supposition is correct).
> I suppose running sa-update should clear any such problem... And you
> might clear the FuzzyOcr problem by resetting the MailScanner option
> for site rules.
Hm, went and read the other thread you have (broken off:)... Ok, so
you set Default, not Site... Ok, I need more coffee too (not just
Scott:-):-)...
Anyway, you shouldn't need set that either. It should be automagic
(and have nothing to do with spamc/d/assassin "glue", since it is set
in the main module...). Oh well. Off to the coffee machine:-).

-- 
-- Glenn
email: glenn < dot > steen < at > gmail < dot > com
work: glenn < dot > steen < at > ap1 < dot > se