--On Sunday, October 20, 2013 3:39 AM +0200 Karsten Bräckelmann
<[email protected]> wrote:
There is. Install SA, run sa-update. See the INSTALL file.
On this topic it is worth pointing out, that the Mail-SpamAssassin
tarball contains everything necessary but the actual rules files. That
includes the most basic .pre files.
Yes, but I was thinking if you didn't even have the .pre files, there's no
way to bootstrap.
In any case, I have something put together now that uses the .pre files
that ship with the tarball.
However, this has opened up a question to me as to whether or not my
current configuration (which was designed by someone else long ago) is
optimal.
Currently, we store everything (.pre files and rules) in
/opt/zimbra/conf/spamassassin:
zimbra@zre-ldap001:~/conf/spamassassin$ ls
10_default_prefs.cf 20_freemail.cf 20_ratware.cf 25_pyzor.cf
30_text_pl.cf 72_active.cf
STATISTICS-set0-72_scores.cf.txt
10_hasbase.cf 20_freemail_domains.cf 20_uri_tests.cf
25_razor2.cf 30_text_pt_br.cf 72_scores.cf
STATISTICS-set1-72_scores.cf.txt
20_advance_fee.cf 20_head_tests.cf 20_vbounce.cf
25_replace.cf 50_scores.cf 73_sandbox_manual_scores.cf
STATISTICS-set2-72_scores.cf.txt
20_aux_tlds.cf 20_html_tests.cf 23_bayes.cf 25_spf.cf
60_adsp_override_dkim.cf active.list
STATISTICS-set3-72_scores.cf.txt
20_body_tests.cf 20_imageinfo.cf 25_accessdb.cf
25_textcat.cf 60_awl.cf init.pre
user_prefs.template
20_compensate.cf 20_mailspike.cf 25_antivirus.cf 25_uribl.cf
60_shortcircuit.cf languages v310.pre
20_dnsbl_tests.cf 20_meta_tests.cf 25_asn.cf
30_text_de.cf 60_whitelist.cf local.cf
v312.pre
20_drugs.cf 20_net_tests.cf 25_dcc.cf
30_text_fr.cf 60_whitelist_dkim.cf MIRRORED.BY
v320.pre
20_dynrdns.cf 20_phrases.cf 25_dkim.cf
30_text_it.cf 60_whitelist_spf.cf regression_tests.cf
v330.pre
20_fake_helo_tests.cf 20_porn.cf 25_hashcash.cf
30_text_nl.cf 60_whitelist_subject.cf sa-update-pubkey.txt
v340.pre
And we have SA built with:
my $DEF_RULES_DIR = '/opt/zimbra/conf/spamassassin';
my $LOCAL_RULES_DIR = '/opt/zimbra/conf/spamassassin';
I'm wondering if there's a better layout strategy than this. I.e., keep
the .pre files in a specific location (/opt/zimbra/conf/spamassassin) and
keep the rule files + updates in /opt/zimbra/data/spamassassin (our
generalized data location for app specific data).
Any opinions on that?
--Quanah
--
Quanah Gibson-Mount
Architect - Server
Zimbra, Inc.
--------------------
Zimbra :: the leader in open source messaging and collaboration
