Matt:

Correct, however it is SPAMD that makes the call to the SQL database if I am not mistaken, and there is a convention of passing username with in the message. What I want to have happen is each time SPAMd runs a distributed spam check I would like it to take the To: address, use that to make it's query to the SQL database, and then perform the actual filter process using userprefs held in the SQL database. Since I am using scalix, there isn't any real users, and no procmail. It is all LDAP.

Quoting from SPAMd man page.

 -q, --sql-config
Turn on SQL lookups even when per-user config files have been dis-
           abled with -x. this is useful for spamd hosts which donât have
userâs home directories but do want to load user preferences from
           an SQL database.

If your spamc client does not support sending the "User:" header, like "exiscan", then the SQL username used will always be nobody.

Since my spamc doesn't get called from procmail, rather it is getting called from a sendmail milter to the SPAMd sock, I need SPAMd to use the to: address as the user.

HFC


Matt Kettler wrote:

Henry F. Camacho Jr wrote:
Matt:

Thanks, yeah, ideally as each peice of email is being scanned by
SPAMc/SPAMd it would change users and grab the userprefs from the SQL
database.

Ok, well then pass it to spamc..

why are you trying to pass spamd a per-message parameter?

That can't and won't ever work because spamd doesn't get called on a per-message
basis, spamc does.

Attachment: smime.p7s
Description: S/MIME Cryptographic Signature

Reply via email to