Am 25.08.2014 um 11:37 schrieb Reindl Harald: > header contains "X-Spam-Status: Yes, score=7.5 required=5.0" > but the subject does not get [SPAM] tagging with the config > below - not sure what i am missing > > spamassassin-3.4.0-7.fc20.x86_64 > spamass-milter-0.3.2-11.fc20.x86_64 > > spamass-milter -p /run/spamass-milter/spamass-milter.sock -g sa-milt -r 8 -- > -s 1048576 > perl -T -w /usr/bin/spamd -c -H --max-children=25 --min-children=10 > --min-spare=5 --max-spare=15 > __________________________________________________ > > "/var/lib/spamass-milter/spamassassin/user_prefs" is empty > "/etc/mail/spamassassin/local.cf" is configured below > > use_bayes 1 > bayes_use_hapaxes 1 > bayes_expiry_max_db_size 300000 > bayes_auto_expire 1 > bayes_auto_learn 0 > bayes_learn_during_report 0 > report_safe 0 > skip_rbl_checks 1 > > clear_headers > add_header all Status _YESNO_, score=_SCORE_ required=_REQD_ tests=_TESTS_ > rewrite_header Subject [SPAM]
besides the permissions problem after the nightly "sa-update" the reason was simply "clear_headers" without "add_header spam Flag _YESNO" which is entirely unexpected behavior why does the software changing the subject based on a decision made by itself need a header written by itself as base for the next decision to change the subject?
signature.asc
Description: OpenPGP digital signature
