Oh never mind.. I kept scanning other how-to's and ran accross a method
for just using the individual ~/.courier file and pipe it through spamc
before maildrop.
That seems to have solved all my problems with gettig individual spam
assassin user_prefs used :)
"Per-user filtering (with courier-mta or qmail)
You need to create a per-user config file in the users home. In the
Courier MTA, it is called .courier, in qmail it is .qmail. The syntax is
the same:
|/usr/bin/spamc|/usr/bin/maildrop
"
--
Nick Ellson
CCIE# 20018
MCSE 2000, Security+, Network+
Network Hobbyist, VFR Private Pilot.
On Tue, 23 Dec 2008, Nick Ellson wrote:
>
> Trying to integrate Spam Assassin with Courier via /etc/courier/maildroprc
>
> import USER
> if ($LOGNAME ne "")
> {
> xfilter "spamc -u $LOGNAME"
> }
> else
> {
> xfilter "spamc -u $USER"
> }
>
> And my MySQL database of users uses FQDN's like "[email protected]"
>
> My default domain in mu AuthMySQL file adds @nickellson.com for those
> MTA's that use short name just fine.
>
> But when handing off to SPAMC it sends the full e-mail address and SA has
> no idea what to do with that user so it runs as nobody and nevers check
> the .spamassassin/user_prefs for my users.
>
>
> Dec 23 22:15:57 goonie spamd[23702]: spamd: handle_user unable to find
> user: '[email protected]'
>
>
>
> Has anyone else seen this behavior?
>
> Nick
>
>
>
> --
> Nick Ellson
> CCIE# 20018
> MCSE 2000, Security+, Network+
> Network Hobbyist, VFR Private Pilot.
>
>
> ------------------------------------------------------------------------------
> _______________________________________________
> courier-users mailing list
> [email protected]
> Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
>
------------------------------------------------------------------------------
_______________________________________________
courier-users mailing list
[email protected]
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
