On 09.09.15 13:47, Marc Richter wrote:
Regardless if it's necessary or not, I have done so. It also happens
regularly by cron (all 3 hours), along with other jobs like sa-learn,
sa-update and sa-compile.
reload should be enough, restart is rarely necessary.
Also, why do you check oftern than once a day?
On 09.09.2015 11:12 Matus wrote:
have you tried running spamassassin -D ? maybe there's somethign
invalid in SA's configuration or your user_prefs
When I issue "spamassassin --test-mode -D" as the user the filter.sh
- runs as, I get this in the long output:
dbg: config: read file /var/lib/spamassassin/.spamassassin/user_prefs
So, it tries to read the user_prefs from the daemon's home, what is
clear, because it cannot know what user the file "belongs" to, in
test-mode.
When I run that as the user (ww) the mail and desired user_prefs
belongs to, it works, so no use in that.
How can I make use of the "-D" cmdline option in the normal mail-flow
in a way it gets logged by journald? Can I simply add "-D" to the
filter.sh script and it get's caught in journald's database?
how do you plug spamassassin into your mail flow? How do you call
spamassassin? mta, mail client ... ?
--
Matus UHLAR - fantomas, uh...@fantomas.sk ; http://www.fantomas.sk/
Warning: I wish NOT to receive e-mail advertising to this address.
Varovanie: na tuto adresu chcem NEDOSTAVAT akukolvek reklamnu postu.
Enter any 12-digit prime number to continue.
