On Tue, 16 Feb 2016 15:47:33 -0800 Amanda Giarla wrote:
> > On Tue, Feb 16, 2016 at 3:39 PM, RW <rwmailli...@googlemail.com> > wrote: > > > On Tue, 16 Feb 2016 14:17:02 -0800 > > Amanda Giarla wrote: > > > > > > > I looked at the permission of the user_prefs file and for > > > ownership and group-ownership it is root root. should it be > > > debian-spamd debian-spamd? I did change one of the conf files > > > from nobody to debian-spamd for ownership. > > > > Having a global user_prefs is pretty much pointless. The point of > > the file is that there is one per email account - either > > ~/.spamassassin/user_prefs for unix mail accounts or a custom > > location for virtual accounts. > > I don't think I was trying to make a global user_prefs file BUT in my > confusion I may accidentally have implied such. > The user_prefs file is located at > /home/clientAccount/.spamassassin/user_prefs. Is that considered > global? If /home/clientAccount/ is a unix account home directory I'm wondering why user_prefs was owned by root, and what created it. I had a very quick look at the VestaCP installer, and everything seems to be configured with virtual users, so I doubt the spamassassin glue supports per unix user configuration. The spamd start-up configuration is the Ubuntu default, so unless it's a custom package it wont support user_prefs files for virtual users. I'd be surprised if this installation supports per user configuration beyond turning filtering off and on. It probably would then be able to find a user_prefs file in a specific home directory, but that would just represent an unnecessary location for global configuration.
