8 messages in net.sourceforge.lists.courier-maildropRE: [maildropl] How to get extra info...
FromSent OnAttachments
Dan HorneSep 28, 2005 2:28 pm 
Jay LeeSep 28, 2005 2:47 pm 
Jay LeeSep 28, 2005 2:49 pm 
Dan HorneSep 29, 2005 6:44 am 
Dan HorneSep 29, 2005 6:45 am 
Jay LeeSep 29, 2005 7:10 am 
Dan HorneSep 29, 2005 7:14 am 
Jay LeeSep 29, 2005 7:17 am 
Actions with this message:
Paste this link in email or IM:
Paste this link in email or IM:
Atom feed for this thread
Paste this URL into your reader:
Subject:RE: [maildropl] How to get extra info from MySQL db into filtersActions...
From:Dan Horne (da@taisweb.net)
Date:Sep 29, 2005 7:14:57 am
List:net.sourceforge.lists.courier-maildrop

Dan Horne <> wrote on Thursday, September 29, 2005 9:43 AM:

I can call spamc from maildrop?

OK, replying to my own post, I have changed maildroprc to have the following xfilter line:

exception { xfilter "/usr/local/bin/spamc -u $LOGNAME " }

... And I set the following flags to start spamd with (in the rc.d startup script in FreeBSD):

spamd_flags=${spamd_flags:-"-c -d -r ${spamd_pidfile} --virtual-config-dir=/home/vmail/%d/%l/.spamassassin "}

... Which **SHOULD** (I think) work. Indeed maildrop calls spamc, the mail gets scanned, etc. However the maillog reports:

spamd: handle_user unable to find user: use@example.com spamd: still running as root: user not specified with -u, not found, or set to root, falling back to nobody at /usr/local/bin/spamd line 1147, <GEN10> line 4.

So it looks like maildrop is doing its job (it is passing the correct user to spamc with the $LOGNAME variable). Therefore, unless anyone has further suggestions on how to fix this error, I will take this particular problem to the spamassassin list.

Thanks for your help.