http://spamassassin.apache.org/full/3.3.x/doc/
All spamd options documented in:
http://spamassassin.apache.org/full/3.3.x/doc/spamd.txt
You'll have to go thru your .pre files to disable a bunch of plugins
Those rule hits your seeing now are very cheap and low scored.
On 09/16/2013 11:14 PM, Abhijeet Rastogi wrote:
On Tue, Sep 17, 2013 at 1:58 AM, Kris Deugau <kdeu...@vianet.ca> wrote:
John Hardin wrote:
Key arguments for spamd are -C (to specify the "default" rules path
(overrides and combines DEF_RULES_DIR and LOCAL_STATE_DIR) and
--siteconfig for your "site" config (could probably be pointed somewhere
empty but we found it simpler to put a minimal local.cf and local.pre
there). I can't speak to running "spamassassin" but IIRC it takes much
the same arguments for this as spamd.
If you build a local rules channel for this custom ruleset, use
--updatedir with sa-update with the same path as you specified for spamd
with -C.
I think you're quite there to the point I want but however I'm not
able to accomplish that. I tried starting spamassassin with the
following options:
/usr/bin/vendor_perl/spamd -d --pidfile /var/run/spamd.pid -c -c -x
--virtual-config-dir=/etc/mail/spamassassin -C /etc/mail/spamassassin
-u nobody -D
I also tried adding --siteconfigpath=/etc/mail/spamassassin. Thing is,
I'm not really sure about the difference between --siteconfigpath,
--configpath and --virtual-config-dir.
I could still see checks like
"HTML_IMAGE_RATIO_02,HTML_MESSAGE,MIME_HTML_ONLY" in 'X-Spam-Status:'
header. These checks are essentially defined in /var/lib/spamassassin
only.
