And here is the solution that worked for me:Īccording to this wiki:, I added in /etc/mail/spamassassin/local.cf the following two lines: bayes_path /var/spamassassin/bayes_db/bayesĪnd I created the needed directory: /var/spamassassin/bayes_db/.However, Bayes appears to be more effective with individual user databases. For system-wide SpamAssassin use, you may want to reduce disk space usage by sharing this across all users. The default setting results in files called ~/.spamassassin/bayes_seen, ~/.spamassassin/bayes_toks, etc.īy default, each user has their own in their ~/.spamassassin directory with mode 0700/0600. Several databases will be created, with this as the base directory and filename, with _toks, _seen, etc. This is the directory and filename for Bayes databases. The bayes databases are saved in the home directory of the user which runs spamassassin: bayes_path /path/filename (default: ~/.spamassassin/bayes) Spamc only partial: # spamc -R < /path/to/spam.emlĬontent analysis details: (1.5 points, 5.0 required)Ġ.1 MISSING_MID Missing Message-Id: header Spamassassin works: # spamassassin -t < /path/to/spam.emlĬontent analysis details: (3.3 points, 5.0 required)Ġ.0 FSL_HELO_NON_FQDN_1 FSL_HELO_NON_FQDN_1Ġ.7 SPF_SOFTFAIL SPF: sender does not match SPF record (softfail)Ġ.8 BAYES_50 BODY: Bayes spam probability is 40 to 60%Ġ.5 MISSING_MID Missing Message-Id: headerĠ.0 HELO_NO_DOMAIN Relay reports its domain incorrectly This has been going on for days now and I am out of ideas. I have not managed to figure it out or find any similar reports online. I like spamc for the fact i can get it to output just the report but it seems to be missing checks: SPF, DKIM, BAYES. Then when I tried to deploy it via spamc I get partial results. I have installed and configured and trained my spamassassin and all seemed to work just fine.
0 Comments
Leave a Reply. |