> > After a bit of digging I found that sa-update had, in fact, updated my 
> > system
> > before I read this.

On 04.01.10 15:41, Alex wrote:
> sa-update had also updated my system, and amavisd was restarted.
> However, the 72_active.cf in /usr/share/spamassassin somehow overrode
> the updated one from /var/lib/spamassassin/.
> 
> Any idea how this could happen? It was necessary for me to manually
> update the 72_active.cf in /usr/share/spamassassin for this to work.

there's something broken in your setup (amavis?). Rules from
/var/lib/spamassassin/ should override /usr/share/spamassassin

> Is there something I can do to prevent this from happening again? How
> do I troubleshoot this?
> 
> I believe the first two directories are consolidated in v3.3?

I think 3.3 does not come with standard ruleset, but keeps rules in
/var/lib/spamasassin. So there should be no /usr/share/spamassassin in 3.3.

-- 
Matus UHLAR - fantomas, uh...@fantomas.sk ; http://www.fantomas.sk/
Warning: I wish NOT to receive e-mail advertising to this address.
Varovanie: na tuto adresu chcem NEDOSTAVAT akukolvek reklamnu postu.
Microsoft dick is soft to do no harm

Reply via email to