11 messages in net.sourceforge.lists.courier-usersRE: [courier-users] delay in HELO res...
FromSent OnAttachments
Holmström LarsFeb 14, 2004 2:05 pm 
Mitch (WebCob)Feb 14, 2004 2:50 pm 
Holmström LarsFeb 15, 2004 12:23 am 
Holmström LarsFeb 15, 2004 10:41 pm 
Holmström LarsFeb 15, 2004 10:44 pm 
Mitch (WebCob)Feb 15, 2004 11:30 pm 
Holmström LarsFeb 15, 2004 11:48 pm 
Mitch (WebCob)Feb 15, 2004 11:50 pm 
Mitch (WebCob)Feb 16, 2004 12:51 am 
Holmström LarsFeb 16, 2004 1:54 am 
Sam VarshavchikFeb 16, 2004 5:20 am 
Actions with this message:
Paste this link in email or IM:
Paste this link in email or IM:
Atom feed for this thread
Paste this URL into your reader:
Subject:RE: [courier-users] delay in HELO responseActions...
From:Holmström Lars (lars@essnet.se)
Date:Feb 15, 2004 12:23:38 am
List:net.sourceforge.lists.courier-users

I did add "-noidentlookup -nodnslookup" to TCPDOPTS in /etc/courier/esmtpd and restarted courier

It does not changed the situation.

You say "courier doesn't use your local resolver". While doing tcpdump it looks like it talk to my local DNS. Do you mean courier use the DNS server pointed out in /etcd/resolve or not ? If not, where does the reverse lookup come from ?

I also searched the past courier mailing lists for things like ident and DNS but where not successful. Do you have any more precise information when this was discussed ?

I also understand from the tcpdump that all reverse lookup and ident traffic happend before the "220 x.y Ready" message comes ?

I would like to run some strace of the couriertcpd process but has not figured out how to do this. Can some one pls advice how to do this ?

/Lars

-----Original Message----- From: Mitch (WebCob) [mailto:mit@webcob.com] Sent: Sat 2/14/2004 11:48 PM To: Holmström Lars; cour@lists.sourceforge.net Subject: RE: [courier-users] delay in HELO response

I would expect courier itself is having problems doing the reverse lookup...

iirc, courier doesn't use your local resolver, so it does its own DNS. Try turning off revser lookups and or ident - see where your problem lies. There was discussion about this before, Sam wanted performance in the reverse lookup - of course if the firewall restricts outbound queries or doesn't do stateful allows on outbound UDP you could have a problem. Unless you need it turn it off? If you need it, figure out couriers port symantecs and modify your firewall?

m/

-----Original Message----- From: cour@lists.sourceforge.net [mailto:cour@lists.sourceforge.net]On Behalf Of Holmström Lars Sent: Saturday, February 14, 2004 2:03 PM To: cour@lists.sourceforge.net Subject: [courier-users] delay in HELO response

I have a 0.44.2 installation on a RH8.0 with webmail, imap, pop3 and a few more modules.

My users, and myself, have no problem using pop3, imap and webmail, but when sending mail via SMTP I got a long delay before the mail actually is recieved by courier.

My LAN has no firewall. I have verified the DNS setup, including the reverse lookup, and can not find any obvious problem.

I used tcpdump to watch the traffic between the mailserver, the client and the DNS.

I can see that it takes approx 2 sec to forkl a new process, do the ident and the DNS lookup, but then nothing happend for about 2 minutes. This is as far as I understand before the mailserver respond with its ID_string and is ready to recieve the HELO ?

If I connect to port 25 via telnet I got exactly the same behaviour. From where the tcp-session is established (looking with netstat) until the mailserver print something in my telnet window it takes more than 2 minutes.

Can some one direct me to where to look for the problem and possibly give some good advice ?

/Lars

_______________________________________________ courier-users mailing list cour@lists.sourceforge.net Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users