Solved

Email from one company not arriving

Posted on 2016-08-17
3
90 Views
Last Modified: 2016-09-06
I switched a client company to Rackspace email last week, but my client company, smithfoods.com, does not receive email from one particular company, easyreporting.com (both names fictitious).  The domain registrar is Network Solutions.  The previous email provider was EarthLink for business.  It's been a full week since I changed the MX records, so it should have propagated by now.

I spoke with tech support at easyreporting.com, the guy that runs the Exchange server, and he says when they send mail to any address at smithfoods.com, it ends up being directed to EarthLink, the previous email provider, instead of Rackspace, the current email provider.  So it seems there is root name server on the internet that has not been updated - at least that's my best guess.  He sent from his own computer, which has never sent to smithfoods.com before.  I've seen before where the auto-saved address in Outlook will sometimes remember the old settings, but that can't be the case in this scenario.

So my questions are:
1- Is there a way to force a re-propagation of the MX records?  
2- Am I off-base in my assumptions and there might be something else causing this?
3- Can anyone offer a idea of what else might be causing this.

Thank you in advance for any info you can provide.
0
Comment
Question by:CTSLA
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 2
3 Comments
 
LVL 41

Accepted Solution

by:
Adam Brown earned 500 total points
ID: 41760384
It's possible, if your client regularly deals with the other company, that they have an Exchange send connector configured to send messages directly to earthlink for your environment. It's also possible that the Exchange server is still caching the MX record for your client's domain. They could have their own MX records defined for you in their DNS server. There are a lot of things that could cause the problems you've described. Suffice to say, though, that if this other company can't send mail to you and all others can, it's a problem with their mail server and not yours. The other admin will need to troubleshoot the issue to resolve it. There's not much you can do on your end to fix their server.

If you like, you can ask him to check his send connectors for anything sending to your domain, or have him run ipconfig /flushdns on the exchange servers. Without access to their network, it's difficult to actually determine or troubleshoot the issue, and it would be even more complicated to give recommendations to you, then for you to give them to him.
2
 

Author Comment

by:CTSLA
ID: 41760429
Adam, thank you for the ideas.  I'll offer these suggestions to the other tech tomorrow and will update this post when something changes.
0
 

Author Comment

by:CTSLA
ID: 41785190
Adam,
the company that we could not receive emails, from, easyreporting.com, also has their domain registered with Network Solutions, but their DNS is hosted by Deltacom, who was bought out by EarthLink for business.  I had several conversation with Easy Reporting's Exchange Server tech, who grudgingly agreed to bring the problem to EarthLink after I explained the possible issues (that you pointed out) and the fact that it was almost certainly an issue with his server settings or the DNS servers he was using.

It turns out, this company, easyreporting.com, did not use EarthLink's DNS servers, and instead stayed with Deltacom's DNS.  Since I'm not an EarthLink customer, they would not deal with me directly, but the tech told me it was an EarthLink issue, that they didn't have something set up right.  But I'm guessing it is more likely that Deltacom's DNS servers were no longer being updated, as EarthLink probably asked Deltacom customers to switch to their DNS servers at the time of the buyout.  That's just my guess.  The tech told me EarthLink fixed the issue without explaining exactly what it was, but I'm guessing he probably just changed his DNS servers to EarthLink instead of the outdated Deltacom DNS servers.  

Whatever it was - it is now resolved.  Thank you for your assistance.  Without it, I wouldn't have known to apply pressure to Easy Reporting to get THEIR problem resolved.
0

Featured Post

Get proactive database performance tuning online

At Percona’s web store you can order full Percona Database Performance Audit in minutes. Find out the health of your database, and how to improve it. Pay online with a credit card. Improve your database performance now!

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

How to resolve IMCEAEX NDRs in Exchange or Exchange Online related to invalid X500 addresses.
Unified and professional email signatures help maintain a consistent company brand image to the outside world. This article shows how to create an email signature in Exchange Server 2010 using a transport rule and how to overcome native limitations …
To show how to generate a certificate request in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.:  First we need to log into the Exchange Admin Center. Navigate to the Servers >> Certificates…
The basic steps you have just learned will be implemented in this video. The basic steps are shown to configure an Exchange DAG in a live working Exchange Server Environment and manage the same (Exchange Server 2010 Software is used in a Windows Ser…
Suggested Courses
Course of the Month9 days, 5 hours left to enroll

617 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question