It looked as being the solution ....
There were a broken router that forced a timeout when looking the
in-addr.arpa virtual domain, used to log the connections ...
of couse as you wrote a timeout in resolv become a timeout in the reply of
smtp !!!
On Mon, 29 Mar 1999, Paul Mansfield wrote:
> On Sun, 28 Mar 1999, Leonardo Boselli wrote:
> > It worked until this night, this morning it became slow and started
> > to "refuse" mail ...
> > well, not to refuse, only to wait 45 to 70 seconds from
> > acknowlwedge of connection to the prompt, forcing most UA to
> > timeout.
>
> We've had this when resolvers get broken.
>
> How *long* is it taking to do resolving? What's in your resolv.conf?
>
> > This from any machine, dns is ok, and line too .
>
> If you "dig @localhost xyz.com", how long does it take?
>
> Another problem might be the identd - try fiddling with the option
> rfc1413_query_timeout (we set ours to 15s).
>
> > I tried to let it start from inetd instead that as a daemon but the
> > result changed only thet it was a bit more slow.
> > The load of machine is very low, and there remain about 70 MB free
> > after having exim running.
> > it is 2.05 on a debian 2.1 ...
> > What can i do to avoid this slowness (after the prompt has come,
> > the program run regular !!!)
>
> Paul
>
>
> --
> *** Exim information can be found at http://www.exim.org/ ***
>
>
--
*** Exim information can be found at
http://www.exim.org/ ***
