1

Topic: Spamassassin local.cf does not appear to be being used

==== Required information ====
- iRedMail version (check /etc/iredmail-release):  0.9.7 MYSQL edition
- Linux/BSD distribution name and version:  Ubuntu 16.04.4 LTS
- Store mail accounts in which backend (LDAP/MySQL/PGSQL): MySQL
- Web server (Apache or Nginx): Apache
- Manage mail accounts with iRedAdmin-Pro?  No
- [IMPORTANT] Related original log or error message is required if you're experiencing an issue.
====

The spamassassin local.cf located at /etc/mail/spamassassin does not appear to be being used when incoming mail is scanned.  The incoming mail IS scanned, and processed and X-Spam headers are added. 

Can some one please point me to the setting or settings that might be the cause of /etc/mail/spamassassin/local.cf not actually being used?

----

Spider Email Archiver: On-Premises, lightweight email archiving software developed by iRedMail team. Supports Amazon S3 compatible storage and custom branding.

2

Re: Spamassassin local.cf does not appear to be being used

What do you mean "not used"?

3

Re: Spamassassin local.cf does not appear to be being used

I added the following line to local.cf:

add_header all Foo _HOSTNAME_

The header is not added to the email.  When I send the message to spamassassin manually, the line is added.

4

Re: Spamassassin local.cf does not appear to be being used

Please turn on SpamAssassin debug in Amavisd config file (SpamAssassin is called by Amavisd) and try again, check spamassassin to see why it doesn't work:
https://docs.iredmail.org/debug.amavisd.html

5

Re: Spamassassin local.cf does not appear to be being used

Well, doing this showed me that the local.cf file was actually being used after all.  Thanks!

Jun  3 08:47:08 dragonix amavis[52898]: (52898-01) fwd: scanner provided a header field X-Spam-Foo, inhibited by %allowed_added_header_fields