At 11:12 AM -0800 12/26/01, Tony imposed structure on a stream of electrons, yielding: >I'm changing over from the webstar plugin to SIMS with 75 domains >all having their own MX >There just names like a.com, b com, c.com, none are like z.a.com or fax.c.com. >How do I put these in the router? > >a.com = a.com >b.com = b.com? >+ another 73 > >Tedious to say the least... >Is there an easy way to do this?
SIMS has a single primary domain name which is set in the general settings, and is usually a real hostname that resolves to the primary IP address of the machine SIMS is running on. All other domains are handled by mapping addresses in them to the main domain in some way. The simplest method in the router is this: secondary.domain = main.domain That means that all mail aimed at [EMAIL PROTECTED] is delivered to the local mailbox of "user" which is also where all mail for [EMAIL PROTECTED] would land. In order to split up local mailbox names by domain so that [EMAIL PROTECTED] and [EMAIL PROTECTED] messages deliver to different local mailboxes, you need to map the addresses for secondary domains a bit differently in the router: <*@secondary.domain> = *.secondary then the person being mailed as [EMAIL PROTECTED] would use the account name 'user.secondary' to log into the SIMS POP3 server to pick up mail. Note that you can do that mapping differently if you prefer, so that this line: <*@secondary.domain> = secondary-* would also work, and mean that mail aimed at [EMAIL PROTECTED] would deliver to the POP3 account 'secondary-user'. You can get Stalker's description of this at <http://www.stalker.com/SIMS/Router.html> under the section "Foreign Aliases" >Another question is how do you get your secondary server to forward >mail to the primary once it's up again? It is mostly automatic: 1. Make sure your DNS is correctly listing the primary as an MX record with a lower value. A properly configured secondary should be holding mail and retrying the lower-metric MX record(s) regularly for delivery. 2. If you run SIMS on the secondary, add a line like this to the router: domain.com = domain.com.smtp That assures that the secondary will understand that it is a secondary for that domain and won't bounce messages aimed at domain.com. Most modern MTA's with anti-spam relay controls will need some similar setting. -- 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]>
