I have added custom SA rules to this file - and they work fine. If running under Ubuntu (and probably Debian), there is also a global amavis-new Spamassassin user_pref/config file under: /var/lib/amavis/.spamassassin/user_prefs. You should be able to replicate what you need done under SA via Amavis-new configuration and/or $sa_ variables/etc. You are much better off staying with amavis-new as the MTAs SA controller, though. Yes, you could hypothetically use SA as a separate content filter via Postfix/MTA/etc.
You would need to post more specific info. Without more to go on as far as what specific SA local.cf options are ignored, this is your answer. SA does observe all settings in its configuration file, but not all of them have effect on the mail being checked, as amavisd-new does its own decisions based on spam score (hits) (so for example required_hits has no effect - use tag/tag2/kill amavisd-new settings instead), and does its own header editing, and body is not modified. This is configuration-option dependent - some local.cf options may work - some may not.īut, you also have not mentioned what exact options (custom rules I assume?) you have under local.cf that are not being used (or ignored/undef'd by amavis-new). It would seem that you are probably simply being 'ignored' by amavis-new as far as SA's local.cf configuration. The FAQ may not spell out the exact "$sa_" (or other type) variables/etc you might need in /etc/amavis/conf.d/50-user, but it does go into great detail about how things are started and read. I know you saw this faq link, but the answer seems to be here. I have seen others report that they are not used at all. Is there a neat way to get amavisd to use spamc (and, hence, ensure consistency)?įirst, and to be clear: The Spamassassin configuration files ARE used - they are not 'skipped'.Why are my custom "score" values, in /etc/spamassassin/local.cf, being ignored only when spamassassin is used via amavisd-new?.I've also considered these ideas (to no avail): I originally configured with reference to (something like) this: When I place equivalent configuration in ~amavis/.spamassassin/user_prefs - it also seems to have no effect on the results of amavisd-new processing. I am perplexed because it appears that the configuration I've placed in /etc/spamassassin/local.cf (a new score for a specific rule, for example) is ignored for messages processed by amavisd, but are not ignored when I run spamc, or "spamassassin -D -t" from the amavis account. The bayes database is in ~amavis/.spamassassin/bayes_*. Postfix, spamassassin and amavisd are all running as services, and mail is delivered with spamassassin scores.
0 kommentar(er)
