Knowing precisely how the MX checks are scheduled should help a lot with email migrations (assuming that's really how they work :->).
The biggest hassle for us when migrating customers is not being able to configure the aliases and catch-all rules before the MX records have been changed. We have to wait for the MX change to be noticed and then sit there entering aliases as fast as we can type. These are both things that are controlled via the mailadmin interface. Of course, there could be rules and things that are only accessible via the mailbox settings, but it would help us immensely if we could access the new boxes via the mailadmin interface before they were "live." (I realize this may not be easy since it depends a lot on how the database tables are currently organized.) -dpm -- David P. Maynard OutServ.net, Inc. -- Coordinated IT Operations Solutions Email: [EMAIL PROTECTED], Tel: +1 512 977 8918, Fax: +1 512 853 9476 -- -----Original Message----- From: Bruce Dorland [mailto:[EMAIL PROTECTED] Sent: Monday, March 01, 2004 10:14 AM To: Todd Jagger Cc: [EMAIL PROTECTED] Subject: RE: saturday email product question [...] The policy itself is certainly not ideal and there are options we're looking at currently. One option that we're working on right now is that all mail would be treated as non-local mail. This would eliminate most of the issues that I noted. I'd be interested in any other thoughts you or anyone has too.
