On Jun 4, 2005, at 2:20 PM, Scott wrote:
Adding -nodnslookup eliminates the delay entirely. However, I'd
rather not leave it disabled like that.
Each of these mail servers is running bind and references itself
for DNS lookups.
Configure the host the way that you want it, then use tcpdu
Jay Lee wrote:
Scott said:
This Friday at about 3pm PST I had 5 different courier servers ranging
in verions from 0.47 to 0.50 simultaneously start taking about 30+ seconds
to initiate an SMTP session remotely (from inside or outside the network).
Connecting from the localhost is no trouble at
Scott said:
> This Friday at about 3pm PST I had 5 different courier servers ranging
> in verions from 0.47 to 0.50 simultaneously start taking about 30+ seconds
> to initiate an SMTP session remotely (from inside or outside the network).
> Connecting from the localhost is no trouble at all. They
Thomas von Hassel wrote:
On Jun 4, 2005, at 21:22, Scott wrote:
This Friday at about 3pm PST I had 5 different courier servers
ranging in verions from 0.47 to 0.50 simultaneously start taking
about 30+ seconds to initiate an SMTP session remotely (from inside
or outside the network). Conn
On Jun 4, 2005, at 21:22, Scott wrote:
This Friday at about 3pm PST I had 5 different courier servers
ranging in verions from 0.47 to 0.50 simultaneously start taking
about 30+ seconds to initiate an SMTP session remotely (from inside
or outside the network). Connecting from the localhost
This Friday at about 3pm PST I had 5 different courier servers ranging
in verions from 0.47 to 0.50 simultaneously start taking about 30+
seconds to initiate an SMTP session remotely (from inside or outside the
network). Connecting from the localhost is no trouble at all. They're
all serviced
