Avatar of ejscn
Flag for United States of America asked on

Send mail but not receive on Exchange 2013


We are about ready to start co-existence and migration from Exchange Server 2007 (Update Rollup 12) to Exchange Server 2013 SP1.  I have set up a test mailbox on the new server.  I am able to send email both internally and externally from that account, but I cannot receive mail in that account.  I have been following closely the steps outlined on the Exchange Server Deployment Assistant as well as here - http://www.msexchange.org/articles-tutorials/exchange-server-2013/migration-deployment/planning-and-migrating-small-organization-exchange-2007-2013-part11.html.  The only special things to be aware of are:

- our 2007 server does not use SSL at all.  We have added the name of this server, plus a legacy namespace to the SSL cert for the 2013 server.  The cert has been exported from the 2013 server and added as an exchange certificate, but not yet enabled.
- we have not yet enabled Outlook Anywhere on the 2007 server.
- we using a new service name (mail) for the new server and discontinuing the name used on the old server, so that is not an issue to transfer
- We are using ORF as our spam filter.  It is not going to be installed on the 2013 server until tomorrow.

We are hoping to complete all of the service-disrupting changes in the early morning hours in just a few days, following the steps outlined by Simon here: https://www.experts-exchange.com/Software/Server_Software/Email_Servers/Exchange/Q_28350139.html
We are well aware that this is going to cause an issue with our Android and Windows Phone users, and they all understand upfront that their email will be disrupted on their phones until we can re-configure their devices (our MDM solution will allow us to edit iPhone ActiveSync settings, but not Android/WP).

Sorry for the long question, and I probably didn't give all the relevant information.  I appreciate any help that you can give, or even to point me in the direction of how to troubleshoot this issue.


Avatar of undefined
Last Comment
Gareth Gudger

8/22/2022 - Mon
Gareth Gudger

Have you modified your Default Receive Connector to accept Anonymous connections?
Md. Mojahid

See the articles will help  your create or modifies your default receive connector and anonymous.


So, I have followed the instructions from Mojahid's link and have verified that the Default Receive connector (both FrontEnd and Hub Transport) allows anonymous connections, but I still cannot receive mail in the test mailbox.  Though I did not perform the shell command Get-ReceiveConnector "Relay E15MB1" | Add-ADPermission -User 'NT AUTHORITY\Anonymous Logon' -ExtendedRights MS-Exch-SMTP-Accept-Any-Recipient on the Default Receive connectors.  Do you have any other ideas?  Thank you again for your help.
This is the best money I have ever spent. I cannot not tell you how many times these folks have saved my bacon. I learn so much from the contributors.
Gareth Gudger

Can the user send messages to themselves?

Create a second user on the new server. Can the two new users send mail to each other?

Yes.  Users can send to themselves and between accounts both located on the Exchange 2013 server.

If it helps at all, I looked on the Exchange 2007 server. Attached is the error that is coming up when I try to send from either externally or a 2007 mailbox to a mailbox on the 2013 server.DNS Error from Exchange 2007 server
Gareth Gudger

See if this article applies to you. Is Exchange 2007 on the latest service pack and cumulative update?
Get an unlimited membership to EE for less than $4 a week.
Unlimited question asking, solutions, articles and more.

I don't believe this article applies to our situation.  We do not use an edge transport server, and we are on SP3, Update Rollup 12.
Gareth Gudger

Is there a smart host configured on the 2007 Send Connector?

No.  This is a dumb question, but I'm wondering from the screenshot if I need to manually create an MX record for my 2013 server?  As I'm looking in DNS, we do not have any MX records internally.

No smart hosts.nslookup.png
Your help has saved me hundreds of hours of internet surfing.
Gareth Gudger

Log in or sign up to see answer
Become an EE member today7-DAY FREE TRIAL
Members can start a 7-Day Free trial then enjoy unlimited access to the platform
Sign up - Free for 7 days
Learn why we charge membership fees
We get it - no one likes a content blocker. Take one extra minute and find out why we block content.
Not exactly the question you had in mind?
Sign up for an EE membership and get your own personalized solution. With an EE membership, you can ask unlimited troubleshooting, research, or opinion questions.
ask a question

Gareth.  Thank you so much for your persistence in helping me with this issue.  While the blog entry itself didn't solve my problem, the first comment on the post did.  We had Google public DNS set as the secondary DNS server on the NIC.  As soon as I removed that secondary DNS entry, mail flowed.  I have also noticed a significant speed increase with ActiveSync - not sure if that is real or placebo yet.
Gareth Gudger

Awesome! Glad it is resolved!