Hey Michael (or anyone else who sees this) - I'm in the process of switching over spamd to use mysql instead of flat files for user preferences - here's my dilemma:
The doc for 2.6 (I'm using 3.04 but in principle I believe it's the same) makes not of making sure the correct username (email address/domain?) is passed to spamd, by way of procmailrc. Is this necessary, even with using the -q directive in the spamd script? I'm using qmail-scanner to tie this all together, and I haven't been able to find reference to making sure the mail gets passed through spamc/d when using the SQL settings. Is this something I have to worry about or is it as simple as your presentation shows? Matt -- Matthew Yette Senior Engineer - NOC/Operations MA Polce Consulting, Inc. [EMAIL PROTECTED] 315-838-1644 (w) 315-356-0597 (f) AIM/Yahoo: MAPolceNOC MSN: [EMAIL PROTECTED] -----Original Message----- From: Matthew Yette Sent: Tuesday, June 14, 2005 1:23 PM To: Michael Parker Cc: users@spamassassin.apache.org Subject: RE: shared SQL DB Great stuff. Thank you Michael, I'll let you know how it goes. -- Matthew Yette Senior Engineer - NOC/Operations MA Polce Consulting, Inc. [EMAIL PROTECTED] 315-838-1644 (w) 315-356-0597 (f) AIM/Yahoo: MAPolceNOC MSN: [EMAIL PROTECTED] -----Original Message----- From: Michael Parker [mailto:[EMAIL PROTECTED] Sent: Tuesday, June 14, 2005 1:17 PM To: Matthew Yette Cc: users@spamassassin.apache.org Subject: Re: shared SQL DB Matthew Yette wrote: >Care to explain how you've come to set this up? We run an ISP-type >solution w/ two identical qmail-scanner/SA/clamav servers set up for >load-balancing purposes (network edge device decides which server to >use at all times). We'd like to consolidate bayes db, auto-whitelist >settings, and logs to one location (all mysql db possibly?) so we can >generate stats and keep bayes/auto-whitelist lists current on both >machines. > > This should help with the SQL side, at least with SA proper: http://people.apache.org/~parker/presentations/ For logging, man syslog. You can send your syslogs to a remote server and parse them from there. Michael