Remote MX, O365

Ian Durey

• April 01, 2019 14:12

One of my users decided to move his email to O365 while keeping his website on the cPanel server, now other users (using other domains) on the same server can't email him. I'm sure this has to do with a messed up MX record somewhere. I've set the MX record to "remote" and userdomain-com.mail.protection.outlook.com but local users are still getting "retry timeout exceeded" errors on emails to userdomain.com. Can someone point me in the right direction on this?

• 

  Ian Durey

  • April 01, 2019 23:00

  After doing some more reading I believe the solution is to create a manualroute in the POSTMAILCOUNT section of exim config: o365_route: driver = manualroute domains = +userdomain.com transport = remote_smtp route_list = * userdomain-com.mail.protection.outlook.com
  Does that seem right?

  0
• 

  Ian Durey

  • April 02, 2019 12:59

  I am still getting "host lookup did not complete" on this, so clearly I'm not doing something right. Any help is appreciated.

  0
• 

  keat63

  • April 02, 2019 13:17

  I did something similar about a year ago. The domain was hosted on my server, but the emails were all being handled by Google, so a similar scenario. I had to add a few MX entries in the DNS zone for the particular domain.

  0
• 

  keat63

  • April 02, 2019 13:17

  Incidentally, I wasn't aware of any issues, and it ran like this for a year, maybe more before the domain was migrated away. How long did you wait for the DNS changes to propagate. This could take 24-48 hours (although a 2 is usually enough I find)

  0
• 

  Ian Durey

  • April 02, 2019 14:39

  Thanks for your reply. I do have the MX record configured properly. It has been like that for several days. I wonder if the issue could be that this domain happens to be the "main" domain of the server?

  0
• 

  keat63

  • April 02, 2019 14:44

  Do you have a CNAME entry for 'mail' in the DNS zone Whilst I have these for all the domains on my server, I don't have a mail entry in the DNS zone for that particular domain. Maybe if you left this behind, it's having some bearing on delivery.

  0
• 

  keat63

  • April 02, 2019 14:48

  Also, do you have access to the domain properties at registra level. Maybe you could let the registra handle the NS records and make the DNS changes at that end ?

  0
• 

  cPanelLauren

  • April 02, 2019 19:47

  If you've properly modified the MX records for the domain to point to Office 365 and added the DNS records they request I'd suggest ensuring that the domain is no longer present in /etc/localdomains and ensure it is present in /etc/remotedomains. The router or any exim customization shouldn't be necessary for this to function.

  0
• 

  Ian Durey

  • April 02, 2019 21:59

  ensure it is present in /etc/remotedomains. The router or any exim customization shouldn't be necessary for this to function.

  
  Confirmed it is in /etc/remotedomains, still getting "host lookup did not complete".

  0
• 

  Ian Durey

  • April 03, 2019 01:08

  I believe this has been resolved. The user domain was referencing ns1.userdomain.com and ns2.userdomain.com but didn't have corresponding A records, so the DNS zone didn't actually exist and DNS lookups were failing. I created A records for ns1.userdomain.com and ns2.userdomain.com and looks like DNS is resolving now. Thanks to those who replied.

  0
• 

  cPanelLauren

  • April 03, 2019 01:54

  That sounds about right, I'm glad you were able to find a solution! Thank you for letting us know.

  0

Please sign in to leave a comment.