Your configuration should be able to handle that load fairly easily. Our primary environment consists of 4 machines as smtp relays and they handle ~120 messages per day. Each is Virus scanned and SA'd before being passed on. Unfortunately we can;'t drop unknown users because they are forwarded to other machines which make that decision. As for your particular case it seems that you have an issue somewhere that is causing a problem. Are these spamd machines relays or do they enevitably hold user data? Are there other process taking up time/memory that SA needs? When you say wedged do you mean that the system is freezing or just really really slow? Gary
________________________________ From: Mike Hogsett [mailto:[EMAIL PROTECTED] Sent: Wed 6/30/2004 2:56 PM To: SpamAssassin Subject: Fault Tolerance Recently I installed five machines with SpamAssassin (spamd) and use the DNS round robin method to do dumb load balancing between them. I finally finished altering all my users' .procmailrc files to include the '-d hostname.tld' argument to spamc so that they would use one of these 5 machines. Over this last weekend we experienced a huge influx of spam late at night. We had nearly 14,000 SMTP connections in a single hour. Most of these were rejected due to either of 'User unknown' or 'Domain of sender address <> does not resolve|exist'. But each of the remaining messages all needed to be piped through one of the 5 spamds. At some point one of these spamds became wedged. Many spamcs finally gave up attempting to connect to spamd due to this wedged spamd. What do others do to create fault tolerance in their spamassassin installations? - Mike
