On Mon, 18 Jul 2016 09:44:23 +0200 Michael Meskes <mes...@debian.org> wrote: > On Sat, Mar 29, 2014 at 02:12:15PM +0200, Ognyan Kulev wrote: > > I set AUTOWHITELIST=0 in /etc/default/spampd and removed the file but after > > restarting it's re-created again, with same permissions. > > That is because this option is no longer relevant with spamassassin version > 3.0 > and above. Or in other words, to get rid of it you have to configure > spamassassin. I have not yet dug into it to figure out how to configure the > correct user of the file though. > > Michael > > -- > Michael Meskes
If I could add my opinion: spampd uses /var/cache/sampd for its files and that is where it expects to find auto-whitelist. spamassassin uses /var/lib/spamassassin for its files and that is where sa-awl looks for auto-whitelist. I've sym-linked the two together as a workaround. However there is a bigger problem and that is owner:group of spampd and spamassassin are different and that creates all sorts of problems because they have to share files. It would seem to me that there is no need for spampd to have a different user:group from spamassassin; a single spam user would be helpful. I also notice that spamassassin insists on using a directory .spamassassin for its user_prefs etc. That's not great for a server which uses /var/lib/spamassassin for its configs; one has /var/lib/spamassassin/.spamassassin which is silly. Again it would be helpful if a single shared directory could be used for both these apps. Dick -- Dick Middleton
