I still wonder if there is anything special I need to put in either SIMS settings, like in the router, to allow the backup to continue to do backup server for the primary machine. Can someone answer this for me?
You should need nothing special other than a line like this in the router of the secondary:
3-rivers.com = 3-rivers.com.smtp
That says "relay mail for 3-rivers.com addresses by the normal SMTP rules (i.e. MX priority)" That will allow the secondary to deliver without itself believing that the mail it is handling is improper relay. The primary server (the one at mail.3-rivers.com which seems to call itself just '3-rivers.com') does not need to treat the secondary special in any way.
The one problem with that setup is that it protects against some pretty rare (I'd hope...) problems. Basically, the secondary will only be used when the primary is down or overloaded but the secondary is till up and accessible from the world at large. If such an outage is less than a few hours, you will have little better recovery when you get the primary back than if you had no secondary. On top of that, if you don't take great care in configuring the secondary for spam control, spam controls on the primary could kick in when you do have mail going through the secondary. Spammers have long been hitting secondary MX records first to get spam delivered, and with SIMS as the primary there's a pretty good chance that you will end up temp-banning the secondary on a regular basis as a result.
--
Bill Cole [EMAIL PROTECTED]
#############################################################
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]>
