smtp re-connect delay

Posted on 2008-01-28
Medium Priority
Last Modified: 2013-11-30
Have a Dell Poweredge running SBS2003.
Sometimes, I can connect remotely using telnet on port 25 and ehlo the server.
Other times, I get no answer.

Once connected, everything seems to work well and at a good speed.
If I terminate from the server end, I can't reconnect for about 5 minutes.
If I disconnect from the client end, I can't reconnect for about 5 minutes, and the smtp sessions window continues to show me as logged in (yes... I hit refresh and yes... the seconds increment).

The problem?? We installed a Barracuda Spam Firewall. Works great until it doesn't have any email to forward for awhile. It times out (which is good). But then can't reconnect when it has more mail to forward to the server.
Question by:DP-Group
  • 3
  • 2
LVL 74

Expert Comment

by:Jeffrey Kane - TechSoEasy
ID: 20763824

So you're saying that this problem didn't exist before the Barracuda?

Also, how exactly are you watching this SMTP session?  Are you using the SBS"s POP3 Connector for email?


Author Comment

ID: 20764041
Problem did not exist before Barracuda.
However, I have a hard time blaming them when I can't connect to it directly from a PC.
When email went directly to the server, the email came from many different originators so the reconnect issue never came up. I manage quite a few SBS2003 servers with Barracuda Spam Firewall 200's and I don't have this issue anywhere else.

I am watching the session through exchange system manager.
Go to protocols, smtp, default smtp server, sessions.

Not using POP3 connector. MX record sends mail to barracuda and mail is forwarded to exchange server. I will set the exchange server to only take email from the ip address of the barracuda, but I am waiting on that until I get the smtp reconnect issue resolved.
LVL 74

Expert Comment

by:Jeffrey Kane - TechSoEasy
ID: 20764146

"However, I have a hard time blaming them when I can't connect to it directly from a PC."

Troubleshooting isn't a blame game.  If you really want to know for sure, remove the Barracuda and then see if it resolves.
But that's not really necessary... obviously the Barracuda is causing somthing to barf.... but I think what you're saying is that the fix may not be on the Barracuda.

So, if you have a number of SBS2003 servers with this setup, what's different about this one?  What AV Software is it running?  Is there any other 3rd Party SPAM filtering enabled?  


Author Comment

ID: 20766677
If I create a connection directly to the IP address of the server, I have effectively removed the Barracuda from the picture. This is where I get the intermittent inability to connect (or should I say abililty to connect as it doesn't work more than it works).

 I  still don't believe it's the Barrracuda per se. I suspect there is a setting or a corruption within exchange/server2003  that keeps SMTP from accepting connecitons from a server that just disconnected.
If I open a telnet session to any other servers, I can connect/disconnect at will. Has anyone seen this behavior anywhere else.
I use Symantec across all servers so no AV S/W issues. No other 3rd party Spam filtering. I'm sure there is a checkmark somewhere that I'm missing, but I'm stumped.


Accepted Solution

DP-Group earned 0 total points
ID: 20817875
I replaced the linksys Firewall/Router and the problem disappeared.
This makes NO sense as the Linksys worked fine when we didn't run mail thru the Barracuda.
This ends up being a compound problem.

Other servers on the net would continue to try to deliver the email until the Linksys would finally answer, whereas the Barracuda tries / fails and quits trying. I should know better than to use a Linksys in a server environment but that $80 tag gets me every time.

Featured Post

Free Tool: IP Lookup

Get more info about an IP address or domain name, such as organization, abuse contacts and geolocation.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

Question has a verified solution.

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

Microsoft Jet database engine errors can crop up out of nowhere to disrupt the working of the Exchange server. Decoding why a particular error occurs goes a long way in determining the right solution for it.
After a recent Outlook migration from a 2007 to 2010 environment, some issues with Distribution List owners were realized. In this article, I explain how that was rectified.
The video tutorial explains the basics of the Exchange server Database Availability groups. The components of this video include: 1. Automatic Failover 2. Failover Clustering 3. Active Manager
Exchange organizations may use the Journaling Agent of the Transport Service to archive messages going through Exchange. However, if the Transport Service is integrated with some email content management application (such as an antispam), the adminiā€¦
Suggested Courses

589 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