On Wed, Dec 14, 2005 at 11:36:11AM -0800, Justin Mason wrote: > Duncan Findlay writes:
> >Right. I also don't see any need to split the rules out of the main > >package -- spamassassin just needs to be smart enough to use the right > >set of rules -- either where sa-update drops them or where they are > >installed by default. > > So you're suggesting we'd have: > > /usr/share/spamassassin/72_active.cf: base, released copy of > rule updates > /etc/mail/spamassassin/sa_update.cf: override of that default set > > ?? Yes, except that I'd argue /etc/ isn't the right place for it either. I'm really thinking it should go in /var/lib somewhere. But that would mean we'd have the following: /etc/spamassassin | /etc/mail/spamassassin - site config /usr/share/spamassassin | ... - default rules /var/lib/spamassassin - sa-update drop directory > I could go for that. We'd have to modify the Mail::SpamAssassin code > to recognise the 72_active.cf file somehow and allow it to be ignored > in the system rules dir, if it appears in the site rules dir. Are we going to be consolidating all the rules to one file? It would make it tougher for users to read and play with, if that's a concern. -- Duncan Findlay
signature.asc
Description: Digital signature
