Lloyd Zusman Wrote:
> [ ... ]
>
> I now tried AuthCourier with SpamAssassin-3.0.3, and it only
> works if I set the permissions of the /var/spool/authdaemon directory
> to 751 (they originally were 750). [ ... ]
I was wrong about this. It wasn't working for a different reason.
The call to spamc needs to be made using the -u option, passing
in Courier's idea of the user id.
In my maildroprc, I had to do this:
import USER
xfilter "/usr/bin/spamc -u $USER"
if ( /^X-Spam-(Flag|Status): *yes/ )
{
# do something appropriate with the spam
}
For "normal" users, the $USER variable is set to the unix user ID.
However, for "virtual" users, this variable gets set to the
virtual user's email address (e.g., "[EMAIL PROTECTED]"). In either
case, AuthCourier causes spamd to treat the home directory
appropriately (for "normal" users, it's the unix HOME directory;
for my "virtual" users, it's "/var/vmail/[EMAIL PROTECTED]").
The reason "-u $USER" has to be supplied to spamc is this: without
that argument, spamd will query against the "vmail" user for virtual
accounts (this is the owner of /var/vmail on my system). Even with
AuthCourier, that just returns "/var/vmail" as the home directory.
So now, it's all working.
--
Lloyd Zusman
[EMAIL PROTECTED]
God bless you.
-------------------------------------------------------
This SF.Net email is sponsored by Yahoo.
Introducing Yahoo! Search Developer Network - Create apps using Yahoo!
Search APIs Find out how you can build Yahoo! directly into your own
Applications - visit http://developer.yahoo.net/?fr=offad-ysdn-ostg-q22005
_______________________________________________
courier-users mailing list
[email protected]
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
