search

lelutin / puppet-spamassassin

Install and configure spamassassin either as a service (through spamd) or for use with applications like amavisd. This is a fork of https://bitbucket.org/wyrie/puppet-spamassassin
Other
2 stars 9 forks source link

-x, --nouser-config -c, --create-prefs should be mutually exclusive #37

Open le-walton opened 1 year ago

le-walton commented 1 year ago

if spamd_nouserconfig => true, then the config option $spamd_defaults, should not have the "-c" argument.

lelutin commented 1 month ago

Hi @le-walton

I'm finally getting around to this issue. I've refreshed my memory by reading the spamd(8) page and I find no mention there of those options actually being exclusive. It's probably illogic to set them both simultaneously since -x disables what -c would have enabled to do, but as far as the documentation shows there's no reason the deamon wouldn't work with both the options set.

I don't have a spamd install handy to test my hypothesis though.

Any thoughts?

le-walton commented 4 weeks ago

So I use spamassassin as a part of a nginx / php-fpm / php application and I've set the --nouser-config and am seeing these in the logs 

Sep 17 20:48:46  spamd[457]: spamd: connection from localhost [::1]:36842 to port 783, fd 6
Sep 17 20:48:46  spamd[457]: spamd: setuid to nginx succeeded
Sep 17 20:48:46  spamd[457]: spamd: creating default_prefs: nginx/.spamassassin/user_prefs
Sep 17 20:48:46  spamd[457]: config: cannot create user preferences file nginx/.spamassassin/user_prefs: No such file or directory
Sep 17 20:48:46  spamd[457]: spamd: failed to create readable default_prefs: nginx/.spamassassin/user_prefs

Everytime the application connects to spamassassin. So it seems it's trying to create the config over and over.