teksolgreg
asked on
Office 365
After migrating from Gmail to O365 hosted Exchange, outside domains are receiving undeliverable bounce back messages stating Unroutable address. Remote Server returned '550 Unroutable address'
Is there a way to correct this before too many emails are lost?
Is there a way to correct this before too many emails are lost?
ASKER
Here is what was done and checked:
- Migrated from Google to O365 with migration tool
- Added all domains to O365 Admin portal
- Email accounts, set up and spelled correctly in O365 Admin portal
- Domain verification has been made in the O365 Admin portal
Old info: 123@abc.com
New info: 123@def.com
- Added record in Exchange properties through O365 Admin portal to reflect 123@abc.com as acceptable SMTP setting
Still receiving Unrouteable address
Remote Server returned '550 Unrouteable address'
- Migrated from Google to O365 with migration tool
- Added all domains to O365 Admin portal
- Email accounts, set up and spelled correctly in O365 Admin portal
- Domain verification has been made in the O365 Admin portal
Old info: 123@abc.com
New info: 123@def.com
- Added record in Exchange properties through O365 Admin portal to reflect 123@abc.com as acceptable SMTP setting
Still receiving Unrouteable address
Remote Server returned '550 Unrouteable address'
ASKER
I should preface, 123@abc.com is the same user as 123@def.com and 123@abc.com is not set up in the O365 portal.
Sorry to say, Office 365 is garbage! I switched to and from a few times! Not sure if cost is what you're looking at, but I like webhosting.net and also 123together.com.
ASKER
Customer desire. Never had any problems until today.
Just figured it out ... Intermediate hosting company.
Thanks for pitching in
Just figured it out ... Intermediate hosting company.
Thanks for pitching in
ASKER
I've requested that this question be closed as follows:
Accepted answer: 0 points for teksolgreg's comment #a39598855
Assisted answer: 100 points for padas's comment #a39598772
for the following reason:
DNS was the culprit on this one. Previous provider did not remove their DNS mail records.
The mxtoolbox is a great tool, thanks as this should be a go to tool for anyone troubleshooting mail flow.
Accepted answer: 0 points for teksolgreg's comment #a39598855
Assisted answer: 100 points for padas's comment #a39598772
for the following reason:
DNS was the culprit on this one. Previous provider did not remove their DNS mail records.
The mxtoolbox is a great tool, thanks as this should be a go to tool for anyone troubleshooting mail flow.
This might be it
Old info: 123@abc.com
New info: 123@def.com
Did you set abc.com as a domain alias?
Old info: 123@abc.com
New info: 123@def.com
Did you set abc.com as a domain alias?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
DNS reports illustrated solution
Did you check that all dns info is pointing to the correct place? http://mxtoolbox.com/
How long has it been since you made the switch?