On Jan 9, 2008 6:56 PM, Jason Frisvold <[EMAIL PROTECTED]> wrote: > [snip] > > > > This happens for every mail received: unable to find user '' > > > With 3.2.3 I was running spamd as follows : > > /usr/bin/spamd -D -q -x -m5 -H --socketpath=/tmp/spamd.sock -r > /var/run/spamd.pid > > Everything seemed to work fine, I had no issues. Mail was being > classified appropriately. > > When I upgraded to 3.2.4, I got an error stating that if -q was used, > -u had to be specified. So, I switched to using -Q instead. That's > when this error cropped up and spamassassin stopped classifying mail. > After re-visiting the issue, I switched to this : > > /usr/bin/spamd -D -q -x -u nobody -m5 -H --socketpath=/tmp/spamd.sock > -r /var/run/spamd.pid > > This has resolved my problem completely. I just don't know why... >
Well, I think you're now telling spamd it should always run as nobody, I can understand why that fixes the user unknown problem. But I need spamd to run as the user the mail is intended for so I can use per-user settings. I'll have a look at the milter-setup to see if that's where the problem is cheers Stefan
