Hi,

I have new testing lab to play around with which is starting to drive me insane. I have exchange 2013 and outlook 2013. I can receive emails from external domains but I am unable to send emails internally or externally!

Now I would know what to look at if I couldn't send externally, But not being able to send internally has completed confused me!

anyone got any tips where to start troubleshooting for not being able to send internal mail? Once internal mail works I should then be able to get external mail working as well....

Thanks

• Edited by Casey03 Sunday, February 03, 2013 7:28 PM

You cannot send email from Outlook using the default install. You must create a Receive connector.

according to http://technet.microsoft.com/en-us/library/aa996395.aspx no additional connectors are necessary to be able to receive mails!

"In a typical installation, no additional Receive connectors are required."

• Edited by dw_at Sunday, February 10, 2013 1:09 PM

I am experiencing same problems with migration from Exchange 2007 to 2013.

I have installed one Exchange 2013 multi-role server to co-exist with Exchange 2007 and the installation was successfully done by following instructions ExDeploymentAssistant and with no errors on installation.

I can send email from Exchange 2007 test user to my 2013 test mailbox but when sending mail from 2013 test user's OWA or Outlook the messages are stuck in drafts folder in OWA and in Outlook they go to sent items but never appear in queues or anywhere. Same issue occurs also when trying to send mail to another 2013 test user located in same server and database.

I've tried to change DNS settings according to this article but this does not solve the issue for me:

http://thoughtsofanidlemind.wordpress.com/2013/03/25/exchange-2013-dns-stuck-messages/

I can send unauthenticated email using telnet from 2013 server to 2007 so there should be no problems with receive connectors.

Test-ServiceHealth cmdlet shows that everything is ok and all the services are up and running and there is no errors in event logs or anything.

This clearly is some sort of transport issue in co-existence with Exchange 2007. There is some reports to this issue where installing another Exchange 2013 mailbox role server might correct this issue but I would not like to try that first since I am running in a production environment.

• Edited by udam1 Wednesday, May 08, 2013 4:25 AM

Ok, seems that after reboot you have to restart Microsoft Exchange Mailbox Transport Submission -service and drafts folders in OWA will get empty and then you can send messages. We tested this many times and everytime when rebooting the server messages got stuck in OWA's drafts folder and Outlooks sent items. Restarting the service will correct the issue. Now we'll wait if you have to kick the service often if it stops working without reboots which I am a bit afraid it will do.

EDIT: Setting this service to Delayed Start will also fix the issue during reboot.

• Edited by udam1 Wednesday, May 08, 2013 12:22 PM

Hi I found a solution to the same exact problem you had. Double check the following:

1. disable all other network interfaces that you are not using with Exchange.

2. Make sure that you select the correct DNS setting in Server\<Excahgne server Name>

3. Make sure to create a reverse lookup zone along with configuring the DNS setting with the right IP to listen.

Those three points solved my problem

• Proposed as answer by Enjora Monday, January 20, 2014 9:49 AM

I have a single 2012 R2 domain controller and single Exchange 2013 SP1 installation.  

It looks like the internet has run out of suggestions.  I've used NSlookup with set q=mx to make sure the internal DNS server points to the only Exchange server.  I made reverse lookup zones and make a PTR record for the mail server and domain controller.  

Like badguy643, my results to test-servicehealth comes out all True.  

The results of get-transportservice | Format-list shows internalDNSservers and externalDNSservers to be correct.  Oddly enough, it says that internalDNSAdapterEnabled to be false.  But when I use set-TransportService to change the attribute, it says that it was successful but no setting was changed.  Perhaps the get-transportservice has a false negative?

I've rebooted a few times and restarted the Transport Submisison Service after waiting 10 minutes after bootup with no better results.  

What do I need to do to make my single Exchange server recognize it's own hand?  All my tests are with internal email from one mailbox to another.  I'm getting desperate enough to pay the $270 to have Microsoft fix it . 

Edit - it seems as though I'm getting an non-existent domain error on the connectivity log.  Since my logon domain is different from my email domain, it's causing this problem as it's trying to send internal email using my logon domain.  I'll have to remove the public DNS server since it doesn't want to prioritize the internal one.    

• Edited by mplichta Sunday, August 03, 2014 11:52 PM

There are several problems that can cause these symptoms.  In my case, it was because I had deleted the default receive connector operating on port 2525, which is necessary for the internal proxy of SMTP traffic between the various Exchange services.  Recreating the connector solved the issue.

: Default EX2013
AuthMechanism    : TLS, Integrated, BasicAuth,BasicAuthRequireTLS, ExchangeServer
RemoteIPRanges   : {::-ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff,
0.0.0.0-255.255.255.255}
TransportRole    : HubTransport
PermissionGroups : ExchangeUsers, ExchangeServers, ExchangeLegacyServers
MaxMessageSize   : 35 MB (36,700,160 bytes)
Port 2525

• Proposed as answer by Stoutner 1 hour 29 minutes ago

There are several problems that can cause these symptoms.  In my case, it was because I had deleted the default receive connector operating on port 2525, which is necessary for the internal proxy of SMTP traffic between the various Exchange services.  Recreating the connector solved the issue.

: Default EX2013
AuthMechanism    : TLS, Integrated, BasicAuth,BasicAuthRequireTLS, ExchangeServer
RemoteIPRanges   : {::-ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff,
0.0.0.0-255.255.255.255}
TransportRole    : HubTransport
PermissionGroups : ExchangeUsers, ExchangeServers, ExchangeLegacyServers
MaxMessageSize   : 35 MB (36,700,160 bytes)
Port 2525

• Proposed as answer by Stoutner Tuesday, July 28, 2015 5:57 AM