• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1678
  • Last Modified:

Exchange 2013 Internet Send Connectors VERY slow

We have a new Exchange 2013sp1 system with a single DAG serviced by two servers.  Both servers participate in the Internet send connector.  In the delivery reports we see the 02 server hand off to the 03 server and then the message goes outbound to the internet.

We have a spam a/v solution that is the Smart Host on the outbound too.  Once it gets an outbound message delivery occurs in seconds.  But getting the message from the Transport Service on one or the other Exchange 2013 server takes minutes.

We tried to create two Internet send connectors separately servicing each Exch. 13 server.  Still VERY slow on delivery.

In earlier versions of Exch. we had routing groups (2007, 2010) that combined hub transport roles together.  From what I read here: http://technet.microsoft.com/en-us/library/aa998825%28v=exchg.150%29.aspx   HT role is now transport role and mailbox transport role.

We just tried a test whereby each Internet send connector was changed to MX to go directly outbound.

Any ideas or powershell commands we can use to try and figure out why our transport service(s) are so slow?
  • 2
1 Solution
Adam FarageEnterprise ArchCommented:
Well, the transport service would not be slow but the transport agent. If you are doing outbound scanning on the Exchange server itself I bet you anything its that (unless the environment is not properly sized and the SMTP Mail.Que file does not have enough IOPS to perform).

To get mail flow statistics in Exchange 2013 is pretty easy, and I would recommend doing Get-MessageTrackingLog command..

So do this:

- Send a new message outbound, document the subject of the email (use something out there, like Message Tracking 123)
- Run the following:

Get-TransportService | Get-MessageTrackingLog -Start "00/00/00 00:00:00" -End "00/00/00 00:00:00" -MessageSubject "Message Tracking 123"

Open in new window

Now obviously enter an actual date / time in there, but I did that so you know the formatting. You can see what the time statistics are, and then you can also (and should) see the latency.

Furthermore I would recommend looking at the queues to see if the messages are getting stuck within there:

Get-TransportService | Get-Queue

Open in new window

ZENandEmailguyAuthor Commented:
Sorry for the delayed response.  We removed the outbound use of a smart host and message delivery outbound returned to normal.  Interestingly, the vendor of our smart host product showed us in the logs that once their product received the email it scanned and processed it on average of 20 seconds or less.  It was getting the message from the Send Connector on the Exch. 2013sp1 box that was the challenge.

I'm still trying to find the time to recreate the scenario to further test.  We used your suggested powershell commands and I thank you for those suggestions.  They were helpful in showing information we could use to finalize the connection decision.
ZENandEmailguyAuthor Commented:
Thanks again for taking time to send the suggested powershell scripts.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Free tool for managing users' photos in Office 365

Easily upload multiple users’ photos to Office 365. Manage them with an intuitive GUI and use handy built-in cropping and resizing options. Link photos with users based on Azure AD attributes. Free tool!

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now