[Okta Webinar] Learn how to a build a cloud-first strategyRegister Now


Relay extremely slow then bombs from Exchange 2010

Posted on 2011-04-18
Medium Priority
Last Modified: 2012-05-11
We run a VBScript through scheduled tasks on a Windows 2003 server that uses cdo.message to send mail  to external email addresse via a relay set up on our Exchange 2010 server.
I have a Receive connector set up on the hub transport using an ip address assigned to one of the ports on a quad nic......different ip address than the server itself but still using smtp port 25.
We ran this process on our Exchange 2003 server and it worked fine, relaying on the average of 50 - 100 messages at a time in about 10 - 15 seconds.
Through the Exchange 2010 server, we may send out 4 messages successfully one day, 20 messages successfully the next day, 10 messages successfully the next, etc and then it just stops sending.. the scheduled task appears to be running but the mail send doesn't complete.
I found this Exchange shell command that fixed others having the same problem:
Set-ReceiveConnector "Connector Name" -MaxAcknowledgementDelay 0
....this appeared to have worked the first time we ran the process after I entered the command, but every time since it has bombed.
I also found a reference to the ESMTP Inspect parameter on the firewall that fixed a similar issue, but my problem still remains....
Any help\direction would be appreciated.....
Question by:ccherman3
  • 2
LVL 16

Expert Comment

ID: 35446492
I'm on this question, I'm an expert in another zone, but was having a very similar issue that I still haven't solved yet...


That's where we got to with a similar issue

Accepted Solution

ccherman3 earned 0 total points
ID: 35708524
We've been working with Microsoft on this issue for the past week and I'm sorry to say that the issue has not been resolved....
Both the Exchange and Scripting teams have worked on it and the conclusion was that they didn't know what is causing the problem, and if they did know, they probably would not have a fix for it.
They suggested keep running the relay off of a 2003 server......so that's what we're doing for now.
There you have it......how do you suggest this case be closed ??

Author Closing Comment

ID: 36253555
After consulting with Microsft, they stated there is no fix for this issue.....recommendation is to relay off of a 2003 server.

Expert Comment

ID: 37837711
Try this,
Set-ReceiveConnector "Connector Name" -MaxAcknowledgementDelay 0

Featured Post

What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

Question has a verified solution.

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

Are you looking for the options available for exporting EDB files to PST? You may be confused as they are different in different Exchange versions. Here, I will discuss some options available.
With so many activities to perform, Exchange administrators are always busy in organizations. If everything, including Exchange Servers, Outlook clients, and Office 365 accounts work without any issues, they can sit and relax. But unfortunately, it…
In this Experts Exchange video Micro Tutorial, I'm going to show how small business owners who use Google Apps can save money by setting up what is called a catch-all email address in their Gmail accounts. By using the catch-all feature, small busin…
Whether it be Exchange Server Crash Issues, Dirty Shutdown Errors or Failed to mount error, Stellar Phoenix Mailbox Exchange Recovery has always got your back. With the help of its easy to understand user interface and 3 simple steps recovery proced…
Suggested Courses

834 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