Theo Van Dinter-2 wrote: > > First, don't do that. Your own config files (and any cf files that aren't > part of the default distribution) should go into /etc/mail/spamassassin > (or > wherever you keep your site-wide configs). > > Second, as usual, run with -D and find out what's going on. > > Third, "man spamassassin" has a large amount of information about what > files/dir are used for configs. >
Ok, moved the files. Reloaded spamassassin with -D --lint and found my /etc/mail/spamassassin/70_*.cf files. Well, well. Spamassassin itself workes correctly, so I guess that I don't need the params for spamassassin, but for spamd. Example > > spamassassin < mail.txt > > Content analysis details: (10.0 points, 6.0 required) > > pts rule name description > ---- ---------------------- > -------------------------------------------------- > 10 NEOS_BLACK BODY: Blacklist Rule for testing purpose > 0.0 UPPERCASE_25_50 message body is 25-50% uppercase > 0.0 AWL AWL: From: address is in the auto white-list > > > spamc -R < mail.txt > > Content analysis details: (1.5 points, 6.0 required) > > pts rule name description > ---- ---------------------- > -------------------------------------------------- > 1.5 EMPTY_MESSAGE Message appears to have no textual parts and > no > Subject: text > > Where is the difference? What config files uses spamd? Is it that param? > -V, --virtual-config=dir Enable Virtual configs (needs -x) > --virtual-config-dir=dir Enable pattern based Virtual > configs (needs -x) > -- View this message in context: http://www.nabble.com/Spamd-and-Spamassassin-filtering-differently-tf2781676.html#a7764696 Sent from the SpamAssassin - Users mailing list archive at Nabble.com.
