Been spending some time on this problem over the last few days. On Sun, 2002-05-19 at 20:21, Craig R Hughes wrote: > Well, SA "users" don't have to be users....
Technically you are correct however spamd does uid lookups and complains lots if the lookup fails. > I'd suggest using spamd/spamc, with spamd getting its configuration from a I was heading down this route anyway purely for the performance gains. > database, then use the -u flag to spamc and pass it the domain name instead of > the username. That way, spamd will read the configuration for the SA "user" > which is actually the domain name. Then you just store the per-domain > configuration in your SQL database and you're all set. I've been having problems getting SQL support to work properly on my test system (debian) but I'll be trying to head down that route over time. Until then a slightly patched version of spamd and semi-hardcoded paths to the config files are the solution that's working for me. :) Mark -- The Flying Hamster <[EMAIL PROTECTED]> http://www.korenwolf.net/ "We've heard that a million monkeys at a million keyboards could produce the Complete Works of Shakespeare; now, thanks to the Internet, we know this is not true." - Robert Wilensky _______________________________________________________________ Don't miss the 2002 Sprint PCS Application Developer's Conference August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm _______________________________________________ Spamassassin-talk mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
