SpamAssassin Configuration (user_prefs) ignored

[cev]

Hi

Since around a day all the settings I set in cPanel under "SpamAssassin Configuration" don't get used by SpamAssassin. Those are the same information that are in the file /home/username/.spamassassin/user_prefs.

I don't find any errors in any of the logs.

Has anyone an idea where this could be disabled and how to enable the use of user_prefs again?

Thanks.
Rony

[cpanelnick]

Try restarting spamd

/etc/rc.d/init.d/exim restart

[cev]

Hi Nick

Thanks for your reply.

I tried to reinstall exim, reinstall Spamassassin and it didn't made any difference.

However since early today it works again, don't know exactly why.

Rony

[sparek-3]

I seem to be having a similar problem. Sometimes the user_prefs file is read other times it is not.

cPanel 11 - SpamAssassin ignoring user_prefs

I am wondering if it has anything to with the fact that the spam condition in Exim caches values:

http://www.exim.org/exim-html-curren...ECTscanspamass

"The spam condition caches its results. If you call it again with the same user name, it does not scan again, but rather returns the same values as before."

I'm not exactly sure what that line means.

I did adjust the exim.conf file to include a header with the value of $acl_m1, the user that the spam condition is running as. In both instances (when the user_prefs file is read and when it is not) it reports the same value (the correct user).

I don't know if this is a bug in exim, a bug in SpamAssassin, or maybe its not really a bug at all. I have completely reset the exim configs to the default to test this. And like I said, sometimes the whitelists are read properly and a known spam message is allowed through, other times the whitelists appear to be completely ignored.

Running the latest Release 11.6.0-RELEASE_15032

[sparek-3]

Turns out that this appears to be a permission problem. At least that has seemed to fix the issue on my servers.

The permissions on the /home/<user>/.spamassassin directory are set to 700. This needs to be set to 755 so that Exim can open the user_prefs file in that directory. I noticed this when I did some debugging last night and I made that adjustment and it has been working ever since.