doesn't sound like a bad idea... maybe for simplicity, just a global timeout exceeded threshold which would log the offending blacklists name... might be simpler...
If you are volunteering to path, I'm sure there would be interest from some - I've seen this problem crop up before - particularly by people who use more than a couple blacklists... m/ > -----Original Message----- > From: Holmstr�m Lars [mailto:[EMAIL PROTECTED] > Sent: Sunday, February 15, 2004 11:44 PM > To: Mitch (WebCob); Holmstr�m Lars; [EMAIL PROTECTED] > Subject: RE: [courier-users] delay in HELO response > > > May be a treshold value for each BLACKLIST entry would make sense. If > reached, a message is printed in maillog ? > /Lars > > -----Original Message----- > From: Mitch (WebCob) [mailto:[EMAIL PROTECTED] > Sent: Monday, February 16, 2004 8:27 AM > To: Holmstr�m Lars; [EMAIL PROTECTED] > Subject: RE: [courier-users] delay in HELO response > > I've heard of that on the list before... if a blacklist goes down or stops > responding, it can add a significant amount of time to startup. > > > -----Original Message----- > > From: [EMAIL PROTECTED] > > [mailto:[EMAIL PROTECTED] Behalf Of > > Holmstr�m Lars > > Sent: Sunday, February 15, 2004 10:41 PM > > To: Holmstr�m Lars; Mitch (WebCob); Holmstr�m Lars; > > [EMAIL PROTECTED] > > Subject: RE: [courier-users] delay in HELO response > > > > > > 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 > > > > _____ > ------------------------------------------------------- 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
