Ok. So spamd died at about 6 am one morning about two weeks ago. My users just loved their inboxes that day. Shortly after having fixed it I decided to look into making spamd a bit more fault tolerant.
I read that spamc will connect in round-robin fashion to remote spamd's if the hostname argument to -d resolves to multiple IP addresses. I had a few Sun Ultra 5s sitting around, so I installed FreeBSD 5.2 on three of them and then installed SpamAssassin. The three machine do essentially nothing else other than run spamd, sshd, and NFS mounting of user's home directories (for ~/.spamassassin). In addition to user home directories I mount, via NFS, /usr/local/etc/mail/spamassassin/ and /usr/local/share/spamassassin/ on each machine. This way I can install .cf files in one place and they all have them. A script I wrote and run via cron on each machine restarts spamd if it dies or if any file in either configuration directory is newer than the /var/run/spamd.pid file. (If you are interested in the script let me know and I will mail it to you.) This is great for altering rules, installing SARE rules, local.cf, etc. The script runs every 3 minutes and emails me when it restarts spamd. Great! but... I have some problems with the ~/.spamassassin/bayes_* files. On FreeBSD/Sparc64 these are : [FreeBSD/Sparc64]; file bayes_* bayes_seen: Berkeley DB 1.85 (Hash, version 2, big-endian) bayes_toks: Berkeley DB 1.85 (Hash, version 2, big-endian) Unfortunately nearly all my clients are Linux/i386. [Linux/i386]; sa-learn --dump all Cannot open bayes databases /homes/hogsett/.spamassassin/bayes_* R/O: tie failed: Cannot open bayes databases /homes/hogsett/.spamassassin/bayes_* R/O: tie failed: Any suggestions about how I can still use sa-learn for the Linux/i386 client side while still using these FreeBSD/Sparc64 boxes for spamd? Thanks - Mike
