[Slackbuilds-users] spamassassin rules

[Nishant Limbachia]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 02/11/2010 12:04 PM, LukenShiro wrote:
> Hi everyone,
> 
> I'm preparing an update for spamassassin SlackBuild. New version
> (3.3.0) does not ship with SA rules any longer. Previously stock
> (default) rules were in /usr/share/spamassassin/..., local
> (modified by sysadmin) rules in /etc/mail/spamassassin/ and dynamically
> updated ones were in /var/lib/spamassassin/....somedir.... These
> directories should be recognized in new version, too.
> 
> I've a doubt concerning how to "include" rules in upcoming package;
> AFAIK in abstract terms possible choices may be the following:
> 
> 1) I could insert a "/usr/bin/sa-update" in doinst.sh, to
> _automatically_ download and install rules
> in /var/lib/spamassassin/3.003000/updates_spamassassin_org/
> (not difficult to do, problem: a user is supposed to have a working
> connection when installing/upgrading this slack package)
> 
> 2) I could allow a user to download rules file bundled with spamassassin
> source file (listing both of them in .info), and I could find a way to
> install it manually within spamassassin .SlackBuild script
> in /usr/share/spamassassin (maybe).
> 
> 3) I could create a new slack package for SA rules only (e.g.
> spamassassin_rules-3.3.0_r901671) depending on spamassassin .tgz. It
> will maybe install files in /usr/share/spamassasin
> 
> 4) I could ignore the rules problem completely :-P ... that is: I could
> put a simple warning in README about the need to run "sa-update" as root
> before using spamassassin (failure to do so means there are no rules at
> all). Not bad, as a system administrator could easily take care of
> future rules updates without waiting for SA package update.
> 
> What do you guys think about this problem?
> 
One way is to provide the rules in a separate rules directory with the
script tarball.  You can then place the rules directory in /usr/doc and
provide a note in README on installing the rules.

Ofcourse, once you start using spamassassin, you have to download the
rules via sa-update.

I think, v3.3.0 doesn't even start if you don't have rules installed.  I
have a nice cron script that checks for local and remote rules version,
updates and can email the log.  If you are interested, I can send it off
the list.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)

iEYEARECAAYFAkt0b5QACgkQeG5dog/51tUS1QCfWfGmhk+qKJtG2cLk4LhBY+X9
VpcAnAq4pIgoCKx52wcKGRG3rRi5X4h6
=80FV
-----END PGP SIGNATURE-----