The email service won't be activated until the zone file is configured to Tucow's specification (inbound.domainname.tld.emailmx.com. as the *only* MX record, mail CNAME correct, etc.) Any deviation will prevent activation.
MX records are verified once per hour (I'm not sure how many minutes past the hour, I think it's :40) and activation after the MX record is verified seems to take 20-30 minutes to complete. m2 ----- Original Message ----- From: "Todd Jagger" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Saturday, February 28, 2004 1:14 PM Subject: saturday email product question > Hi, > > One of my customers is having a problem with their ISP and wants me to > move their email to the Tucows email service immediately. > > Last night I modified the authoritive nameservers to the Managed DNS > Service and we've sent a support request to have the ISP remove the > customer's zone file from their system. > > My question has to do with the statement in the email product tech admin > area that says: "As a note, inbound.domainname.tld.emailmx.com. must be > the only MX record." I understand why they want it to be the only MX > record: so the email defense system will work properly when it's brought > online. > > This is fine when a domain is new, but seems it could be problematic > when migrating an existing domain. What I've done is set the ISP's mail > server as a higher MX and the emailmx.com server as the lowest MX. > > So far the email accounts have not been activated and the notes at the > RWI still say "Verifying MX". > > Does this mean the statement quoted above is absolutely literal and that > the system checks whether the emailmx.com server is the _ONLY_ MX record > for a domain? And that unless I remove the other MX record the system > will not enable the customers mail account? > > Thanks! > tj >
