Go evening experts. I have signed up for Office 365 so I can push shared calendars, email from the office to my Windows phone. I went through the domain verification and changing of the MX records at Godaddy. After I did this and I tried to download my mail from godaddy to 365 nothing happened. When I sent a test email I got a "too many hops" error (see below):
VA3EHSMHS015.bigfish.com #554 5.4.6 Hop count exceeded - possible mail loop ##rfc822;
I deleted all of the MX records at godaddy and put the one listing for 365. It also had me put a CNAME entry and a TXT entry in.
I just have basic webmail from godaddy that I POP in Outlook now. I believe I am just missing a step that I can't figure out. Looking for some expert advise.
Also, is it possible to just POP my godaddy mail into 365? I tried and it didn't work.
Thanks...
Web ServersMicrosoft 365OutlookWindows Phone
Last Comment
ss6766
8/22/2022 - Mon
kevinhigg
What's the TTL for your DNS zone / records? It seems plausible enough that this is what's happening:
- You made the DNS change, but MX records were previously resolved / cached.
- You send a test message from _____, it resolves incorrectly to deliver to the GoDaddy server.
- GoDaddy's MX receives the message, with authoritative access to your DNS zone, and bounces the message to MS.
- One of the MX's at MS has previously routed mail to your domain (first bullet), and cached resolution.
- It kindly forwards the message to GoDaddy as it believes is appropriate. Repeat.
The steps may happen in a different order, but this seems as it may be what's causing the routing loop. If this is the case, and your mail is properly registered / configured for Office 365, when the TTL expires the issue would likely go away. You may be able to predict how long this would take by reviewing the time to live (TTL) for your DNS zone / records. As for migrating your mail, once you're connected to your profile in 365, you should be able to move mail from your PST (previous POP config). Best of luck!
justinoleary911
office 365 will not inter operate with other email services. You need to set up your office 365 account like a brand new account, using only the office 365 dns and other host records. then you can migrate your email from the godaddy servers to the 365 servers using migrationwiz.com to do a cloud to cloud migration. Office 365 can only be in a hybrid email scenario with exchange 2010 premise based, its not supported in any other configuration. Ive done this exact migration from godaddy email to 365 before and this is the only way it will work perfectly. What 365 plan do you have?
ss6766
ASKER
I signed up for the Exchange only ($4/seat) plan. The TTL is 1HR as 365 instructed. Maybe I wasn't clear that I want this to be shared with GoDaddy so at first I put in the 0 record to point to 365 and left the 10 record to point to GD. When that didn't work I took out the 10 record all together.
Justin: do I need to take out the email records that point to GD under CNAME? I would still like to be able to use GD webmail in a pinch, but that is not a requirement. That's why I set 365 to shared.
It sounds like you want to be able to send and receive email from godaddy email services and office 365 at the same time. Am I correct? If so this is not possible, I would delete any and all records that pertain to godaddy email and keep the 365 dns, office 365 is the exchange 2010 platform hosted, its 100x better than any mail server you're going to use. you dont want 2 mx totally different mx records, this means mail could go to godaddy sometimes then to 365 sometimes, I actually dont think it will even work. You can have multiple MX records if they both are pointing to the same server not just random services.
ss6766
ASKER
Thanks for the tip. I will try this over the weekend. I don't want to lose anymore mail as I change the MX record.
To clarify: I should remove the following from the CNAME
Still got the too many hops error. Very frustrated. Can I just forward my mail from GD to 365? If so how do I set 365 to send through GD (as I don't want my new 365 email address visible to anyone getting or sending email to me).
Sorry to be a pain, but I am about to just cancel the 365 and go back the way I was!
ok in the plan that you have the plan 1. the only records you need in place are the 3 records I said above. the A record you have inplace looks like its for godaddy email, so you can delete it. anything with the secureserver.net in the address is godaddy.
Now your asking if it will screw up the forwarding, what exactly are you trying to forward?
I thought you just wanted to use office 365 email.
ss6766
ASKER
Here is my convoluted setup:
I started with XYZ.net, have had email for 15 years. Used to have a website. I changed a while back to XYZ123.com. I have a website at XYZ123.com. I want everyone who types XYZ.net to be redirected to XYZ123.com. I have GD forwarding (redirecting) XYZ.net to XYZ123.com. I do not want to lose that. I don't know what part of the domain records (if any) are in charge of redirection.
Most of my mail still goes to XYZ.net which is why I wanted the 365 exchange.
Again, pardon my ignorance and many thanks for the help
justinoleary911
ok i get it. as far as people going to the new website with the old address theres a record called a URL redirect record which takes of the website redirection.
Now because you still receive email from both xyz.net and xyz123.com. what you can do is add both domains to the office 365 account and then you can receive email on both domains with an email alias. We have clients that have this they had an older domain and a newer one and they needed to receive email from both and office 365 allows this to happen. Under the admin account for 365 is where you add the domains just add both for email and your good to go. Nothing changes as far as the DNS records you need to add to godaddy. Exactly the records i said to add above are still the only records you need.
- You made the DNS change, but MX records were previously resolved / cached.
- You send a test message from _____, it resolves incorrectly to deliver to the GoDaddy server.
- GoDaddy's MX receives the message, with authoritative access to your DNS zone, and bounces the message to MS.
- One of the MX's at MS has previously routed mail to your domain (first bullet), and cached resolution.
- It kindly forwards the message to GoDaddy as it believes is appropriate. Repeat.
The steps may happen in a different order, but this seems as it may be what's causing the routing loop. If this is the case, and your mail is properly registered / configured for Office 365, when the TTL expires the issue would likely go away. You may be able to predict how long this would take by reviewing the time to live (TTL) for your DNS zone / records. As for migrating your mail, once you're connected to your profile in 365, you should be able to move mail from your PST (previous POP config). Best of luck!