atom feed6 messages in net.sourceforge.lists.courier-usersRE: [courier-users] connection to cou...
FromSent OnAttachments
John BelmonteDec 10, 2003 9:32 am 
Mitch (WebCob)Dec 10, 2003 10:25 am 
Bowie BaileyDec 10, 2003 12:19 pm 
Jesse KeatingDec 10, 2003 4:15 pm 
John BelmonteDec 10, 2003 5:54 pm 
enoDec 11, 2003 6:13 pm 
Subject:RE: [courier-users] connection to courier SMTP server from certai n machines has long delay
From:Bowie Bailey (Bowi@BUC.com)
Date:Dec 10, 2003 12:19:39 pm
List:net.sourceforge.lists.courier-users

From: John Belmonte [mailto:jo@neggie.net]

I'm using Courier 0.42.2. My email client was showing a symptom of a long delay (30-40 seconds) when connecting to a Courier SMTP server. I've tracked this delay down to the SMTP server. If you just telnet to the server, the delay happens between the initial connection and when the server sends the "220 machine.example.net ESMTP" message. The puzzling thing is that the delay only occurs when I telnet from my local network. Testing from two locations outside my network, there is no delay. The only difference I notice is that the address of my local network is not ping-able from the internet, while the other locations I tested are.

I've compared the strace output of the SMTP server for the two cases. In the bad case, some connection attempt is timing out. In the good case, that connection attempt is being refused immediately. Anyone know what's going on?

It looks like an ident lookup (port 113). In the good case it is being rejected by either a firewall or the target machine. In the bad case, the request is just being ignored (probably by a firewall).

The solution is to either disable ident lookups, or fix the firewall to either accept or reject these requests rather than just dropping them.

I disabled ident lookups on my server, but I can't seem to figure out where I did it. Maybe someone else can tell you how.

Bowie