Matt:Did you see my post, I got it working just fine. spamass-milter options -u -e coupled with the following args for SPAMd made this work...
SPAMDOPTIONS="-d -m5 -q -x"The system now _IGNORES_ the user specified when the milter was called, and _READS_ the to: address and uses that for a user name in the SQL call. Tracing MySQL reveals the following:
060210 11:40:01 18 Connect [EMAIL PROTECTED] on spamassassin 18 Query select preference, value from userpref where username = '[EMAIL PROTECTED]' or username = '@GLOBAL' order
by username asc 18 QuitHopefully this helps someone having these kinds of issues with mail systems like scalix.
HFC Matt Kettler wrote:
Henry F. Camacho Jr wrote:Ok,I don't understand what Daryl and Matt are saying by the above? Remember this is a system wide installation and not just running for myJust do what Matt said and pass the username to spamc with the -uoption. It'll do exactly what you want.account. I don't know where I would set spamc -u, because procmail isn't being called. This is a sendmail installation running in a scalix environment, and there for no unix accounts, etc.It doesn't matter that the user's don't exist, you can still use -u.What I have found however, is I can have spamass-milter set with -u -e which tells spamass-milter to pass the full to:email address to spamd for each email to process which is exactly what I wanted it to do. For each email that hits sendmail, it is miltered to SA with a [EMAIL PROTECTED]spamasss-milter acts as it's own spamc, so this is effectively the same as passing using spamc with the -u parameter. spamass-milter is relatively unique in this respect. Nearly every other tool in the world that makes use of spamd does so by calling spamc. Hence our advice to pass -u when you call spamc.
smime.p7s
Description: S/MIME Cryptographic Signature