But still I have not found where the time spent between the socket is established and courier respond with "220 <server> Ready". Can you give me some advice or hint ? /Lars
_____ From: Holmstr�m Lars Sent: Mon 2/16/2004 7:38 AM To: Mitch (WebCob); Holmstr�m Lars; [EMAIL PROTECTED] Subject: RE: [courier-users] delay in HELO response I added some loggin to couriertcpd in order to understand where the time is spent. So far I found out that 50% of my problem was related to the BLACKLIST statement in esmtpd. I have run with a certain configuration for the last 10 months but suddenly some of the servers listed in BLACKLIST has increased their responsetime. Obviously the BLACKLIST check is also done for local clients, which was exactly why some of my users complained. I have the following suggestions: 1) It would be useful to being able to exclude a netblock or certain addresses from the BLACKLIST checking. Like in my case, all users sits together with the mailserver behind a NAT/PAT box. I do not see any reason for asking ordb for a RFC1918 address. 2) In order to find this problem it would have been very useful to being able to add some timing information to the maillog for how long time things actually takes, instead of only when a certain activity started. I am thinking of a kind of verbose level in the logging. This may for example be DNS lookup - 10 ms Ident lookup - 50 ms BLACKLIST lookup 237000 ms etc. /Lars ------------------------------------------------------- SF.Net is sponsored by: Speed Start Your Linux Apps Now. Build and deploy apps & Web services for Linux with a free DVD software kit from IBM. Click Now! http://ads.osdn.com/?ad_id56&alloc_id438&op=click _______________________________________________ courier-users mailing list [EMAIL PROTECTED] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
