A downgrade to SpamAssassin 3.2.3 returns functionality with per-user settings immediately. Any notes on what handle_user does and whether this is a new function of 3.2.4?
I'd like to find out more about handle_user as it seems to be specific to 3.2.4 Thanks -----Original Message----- From: Matthew Goodman [mailto:[EMAIL PROTECTED] Sent: Saturday, January 12, 2008 8:22 AM To: users@spamassassin.apache.org Subject: RE: Problem with handle_user I know that it didn't happen under 3.2.3 because A) no config files changed, and B) very clearly my per-user settings are not being processed. Vpopmail should be the user spamd runs as because the per-user settings are in a directory that is owned by vpopmail:vpopmail. Per-user files are in /var/vpopmail/domains/%d/%u/.spamassassin as stated in the command line that runs spamd. -----Original Message----- From: Matt Kettler [mailto:[EMAIL PROTECTED] Sent: Saturday, January 12, 2008 3:04 AM To: Matthew Goodman Cc: users@spamassassin.apache.org Subject: Re: Problem with handle_user Matthew Goodman wrote: > I am also having this error in my spamd.log file. > > Spamd is being run with: > > SPAMD_OPTS="-c -d -v -m 40 -s local4 -q -u vpopmail > --virtual-config-dir=/var/vpopmail/domains/%d/%l/.spamassassin/ -H > /var/vpopmail" > > And spamc is being called by qmail-scanner-2.01 with /usr/bin/spamc -t 30 > > NONE of my per-user files are being read, and every single e-mail that comes > in I get the user unknown problem. > > This didn't happen when I was using SpamAssassin 3.2.3 It should have. by passing -u vpopmail to spamd, you're telling it to *ALWAYS* scan mail as vpopmail, and ignore that which comes from spamc on a per-message basis.
