connect failede because connected party did not properly res

Use this forum if you have installed hMailServer and want to ask a question related to a production release of hMailServer. Before posting, please read the troubleshooting guide. A large part of all reported issues are already described in detail here.
Post Reply
akerber00
New user
New user
Posts: 16
Joined: 2008-06-04 05:28

connect failede because connected party did not properly res

Post by akerber00 » 2009-12-24 00:49

Been getting this for some time since I changed ISP's. I have a static IP, and that appears to be configured ok from everything I can determine, but when sending I get this message sending from any account on my mailserver (in this case to a gmail account):

DEBUG" 2456 "2009-12-23 16:41:38.335" "Applying rule"
"DEBUG" 2456 "2009-12-23 16:41:38.335" "Performing local delivery"
"DEBUG" 2456 "2009-12-23 16:41:38.335" "Local delivery completed"
"DEBUG" 2456 "2009-12-23 16:41:38.335" "Performing external delivery"
"TCPIP" 2456 "2009-12-23 16:41:38.335" "DNS - MX Lookup: gmail.com"
"TCPIP" 2456 "2009-12-23 16:41:38.663" "DNS - MX Result: 5 IP addresses were found."
"DEBUG" 2456 "2009-12-23 16:41:38.663" "SD::_InitiateExternalConnection"
"DEBUG" 2456 "2009-12-23 16:41:38.663" "Creating session 12"
"TCPIP" 2456 "2009-12-23 16:41:38.663" "Connecting to 209.85.223.72..."
"APPLICATION" 2516 "2009-12-23 16:41:59.663" "SMTPDeliverer - Message 61589 - Connection failed: Host name: 209.85.223.72, message: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond"
"DEBUG" 2456 "2009-12-23 16:41:59.663" "SD::~_InitiateExternalConnection-5"
"DEBUG" 2456 "2009-12-23 16:41:59.663" "Ending session 12"
"DEBUG" 2456 "2009-12-23 16:41:59.663" "SD::_InitiateExternalConnection"
"DEBUG" 2456 "2009-12-23 16:41:59.663" "Creating session 13"
"TCPIP" 2456 "2009-12-23 16:41:59.663" "Connecting to 209.85.210.70..."
"APPLICATION" 2516 "2009-12-23 16:42:20.679" "SMTPDeliverer - Message 61589 - Connection failed: Host name: 209.85.210.70, message: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond"
"DEBUG" 2456 "2009-12-23 16:42:20.679" "SD::~_InitiateExternalConnection-5"
"DEBUG" 2456 "2009-12-23 16:42:20.679" "Ending session 13"
"DEBUG" 2456 "2009-12-23 16:42:20.679" "SD::_InitiateExternalConnection"
"DEBUG" 2456 "2009-12-23 16:42:20.679" "Creating session 14"
"TCPIP" 2456 "2009-12-23 16:42:20.679" "Connecting to 74.125.113.27..."
"APPLICATION" 2516 "2009-12-23 16:42:41.679" "SMTPDeliverer - Message 61589 - Connection failed: Host name: 74.125.113.27, message: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond"
"DEBUG" 2456 "2009-12-23 16:42:41.679" "SD::~_InitiateExternalConnection-5"
"DEBUG" 2456 "2009-12-23 16:42:41.679" "Ending session 14"
"DEBUG" 2456 "2009-12-23 16:42:41.679" "SD::_InitiateExternalConnection"
"DEBUG" 2456 "2009-12-23 16:42:41.679" "Creating session 15"
"TCPIP" 2456 "2009-12-23 16:42:41.679" "Connecting to 74.125.79.114..."

User avatar
martin
Developer
Developer
Posts: 6837
Joined: 2003-11-21 01:09
Location: Sweden
Contact:

Re: connect failede because connected party did not properly res

Post by martin » 2009-12-24 00:51

Well, hMailServer is unable to connect to the recipients server. Maybe your new ISP blocks outgoing traffic on port 25.

akerber00
New user
New user
Posts: 16
Joined: 2008-06-04 05:28

Re: connect failede because connected party did not properly res

Post by akerber00 » 2009-12-24 01:43

No, firewalls are all disabled. First thing I tried.

User avatar
martin
Developer
Developer
Posts: 6837
Joined: 2003-11-21 01:09
Location: Sweden
Contact:

Re: connect failede because connected party did not properly res

Post by martin » 2009-12-24 02:16

First thing you tried where? Have you contacted your ISP and asked them, or..?

Can you telnet 74.125.113.27 on port 25?

akerber00
New user
New user
Posts: 16
Joined: 2008-06-04 05:28

Re: connect failede because connected party did not properly res

Post by akerber00 » 2009-12-24 02:30

Yes, I putty'd using telnet to that ip and port. Never received text back, but the carriage return appeared to get a response as the session did a line feed.

GotNet
Normal user
Normal user
Posts: 207
Joined: 2005-04-16 20:52
Contact:

Re: connect failede because connected party did not properly res

Post by GotNet » 2009-12-24 03:21

akerber00 wrote:Yes, I putty'd using telnet to that ip and port. Never received text back, but the carriage return appeared to get a response as the session did a line feed.
But not this?
---
220 mx.google.com ESMTP 2si20401001vws.88
helo
250 mx.google.com at your service
---
Friendly folks...

Once when I was an ISP we intercepted port 25 to for spam/virus protection.

akerber00
New user
New user
Posts: 16
Joined: 2008-06-04 05:28

Re: connect failede because connected party did not properly res

Post by akerber00 » 2009-12-24 03:30

No, didnt get that. Hmm. Any ideas? According to my settings the firewall is off....

akerber00
New user
New user
Posts: 16
Joined: 2008-06-04 05:28

Re: connect failede because connected party did not properly res

Post by akerber00 » 2009-12-24 05:52

Ok, that was the hint I needed. I had ATT uverse as my new provider, and evidently they were capturing port 25, even for static IP addresses. They were capturing it at the host level, outside the house, which was the reason that turning off the firewall didnt make any difference. I called them and they turned off their capture and opened port 25 for my use. Problem resolved.

Post Reply