Most of the time, I can easily get to the mail server to fix any problems. As an experiment, I removed the secondary MX records from the DNS (except for the fake ones pointing to the main server). This did cut down the spam.
In our particular case, we've never had a problem getting to our mail server physically. and, having -it- go down (as opposed to the connection) has never been our issue. In the 3 times or so I cited, it was always a connection problem between our router and the first hop, and we ended up relying on the telco to fix it, with the concomitant nightmares. That's why the secondary, which was elsewhere, was able to save us. But 95% of the time or more, it just happily accepts spam addressed to us and forwards it on.
However, I was unable to get to the main server for a while, so I re-enabled the secondaries. The spam picked back up, but not nearly in the same volume. I was going to switch the secondaries on and off depending on my schedule, but it doesn't seem to be necessary. You may find this a useful strategy.
Sounds like you're saying that by cutting your secondary for a while, there might have been some spammers who culled their databases as a result, so that when you turned secondary back on, they weren't in a position to slam you quite so much... ?
Stefan Jeglinski
############################################################# This message is sent to you because you are subscribed to the mailing list <[EMAIL PROTECTED]>. To unsubscribe, E-mail to: <[EMAIL PROTECTED]> To switch to the DIGEST mode, E-mail to <[EMAIL PROTECTED]> To switch to the INDEX mode, E-mail to <[EMAIL PROTECTED]> Send administrative queries to <[EMAIL PROTECTED]>
