I was thinking along the lines of spamc trying to do the load-ballancing by determining which server out of a list it should contact, as opposed to having multiple IP addresses for an A-record. If spamc was chosing which of a list of servers it should contact, it would either have to pick randomly, or would have to have some way of "remembering" which server(s) had been picked in the past.
Mostly thinking aloud. The round-robin DNS solution appears to be the best bet. Doesn't seem to be much advantage in having spamc handle the ballancing act.
--Rich
Justin Mason wrote:
Rich Puhek said:The conceptual problem with doing round-robin spamd servers is that the mail server itself would have to maintain some state info to determine which spamd server it shoud contact (unless it randomly selected one). Given most implementations (procmail for lots of us), maintaining state info from one mail message to another would be tricky.
spamd needs very little state, apart from user preferences. Using a round-robin DNS A record, and NFS-mounted user dirs or an SQL database, this is pretty trivial, and is std practice for most big SpamAssassin-using sites ;) --j.
-- _________________________________________________________ Rich Puhek ETN Systems Inc. 2125 1st Ave East Hibbing MN 55746 tel: 218.262.1130 email: [EMAIL PROTECTED] _________________________________________________________ ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Spamassassin-talk mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
