On Sun, 13 Jun 2004, at 11:18pm, [EMAIL PROTECTED] wrote:
> xyz.com.my MX preference = 10, mailexchanger = server.xyz.com.my
> xyz.com.my MX preference = 20, mailexchange = newserver.xyz.com.my (new)
All that says is that others should first try "server", then "newserver".
If the network happens to glitch during someone's attempt to talk to
"server", then "newserver" will get the mail instead. Really, that is a
kludge. It might work out okay, but there are better ways.
I generally like to do the following when changing mail exchangers:
1. Over time, gradually reduce the TTL on the MX records to something
small (like ten minutes), so that changes will propagate quickly when
you make them. Wait for this TTL to propigate.
2. Configure the old mail exchanger(s) to forward mail to the new mail
exchanger(s).
3. Change the MX records to specify the new mail exchanger(s).
4. Make sure mail is flowing properly.
5. Put the TTL back to normal.
6. After a suitable period of time, shut down the old mail exchanger(s).
If the software on your old mail exchanger(s) does not support the concept
in step 2, you can do it with other methods (redirect TCP port 25 on a
router or firewall; use temporary software (possibly on a temporary
computer) that does).
--
Ben Scott | Net Technologies, Inc. | 978-462-8795
Network Engineer | Salisbury, MA, USA | 866-905-3049
[EMAIL PROTECTED] | http://www.ntisys.com | Fax: 978-499-7839
_________________________________________________________________
List posting FAQ: http://www.swinc.com/resource/exch_faq.htm
Web Interface:
http://intm-dl.sparklist.com/cgi-bin/lyris.pl?enter=exchange&text_mode=&lang=english
To unsubscribe send a blank email to [EMAIL PROTECTED]
Exchange List admin: [EMAIL PROTECTED]
To unsubscribe via postal mail, please contact us at:
Jupitermedia Corp.
Attn: Discussion List Management
475 Park Avenue South
New York, NY 10016
Please include the email address which you have been contacted with.
