Link to home
Start Free TrialLog in
Avatar of THUMBTECHS
THUMBTECHSFlag for United States of America

asked on

Unable to receive External Email Exchange 2013

New Exchange server, migrated domains and everything from SBS 2003 to Server 2012 and Exchange 2013.

No user is able to receive external email,  I've verified that DNS on the exchange server points to the internal DNS server.  The internal DNS server points to itself, but has the correct forwarders.  Everything should work.

Site Setup:

2012 Server Running Hyper-V
Host has on it as a VM:  DC, Exchange, RDS servers.
ASKER CERTIFIED SOLUTION
Avatar of Simon Butler (Sembee)
Simon Butler (Sembee)
Flag of United Kingdom of Great Britain and Northern Ireland image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of THUMBTECHS

ASKER

Let me check anonymous on receive, it should be there.  I haven't tried telnet and when we send, nothing happens...not even an NDR.

testexchangeconnectivity comes back clean, mxtoolbox says no PTR, which shouldn't cause it to not work.

Edit:  Telnet works just fine.  Can't email local either, so when I email "me@customer.com" from "me@customer.com" it doesn't work.
Internal email should work straight out of the box.
Are all services running?
If you look in the queue viewer (it is the only thing in the "toolbox") does it show the messages at all?

Simon.
Sorry, the client is required to run DKIM as part of the DMERC qualifications and we had a package on there that may have been interfering with it.  We uninstalled it and we're testing again.
Do you mean DMARC? If so, that doesn't require DKIM, you can use it with just SPF records. DKIM is really only a Yahoo thing and I haven't seen anything do it for Exchange 2013 yet (you can get a number of solutions for 2010).

Simon.
Simon,

I'm right there with ya regarding DMARC...I don't like it either but they're required to do it.  Its the only reason why we're putting in a physical Exchange server vs. putting them on O365.  Anyways, the issue was that when I was preparing the server on the bench, I set a static DNS lookup on the server inside exchange.   I forgot to remove that once I put the server onsite.  

So, something simple it was!
Got me thinking about simple stuff instead of the world beating, thanks for that!