<html>
<font size=3>At 08:46 AM 9/5/00 +0200, Zeljko Vrba wrote:<br>
<blockquote type=cite cite>Temporary solution is to disable delivery to
people which are subscribed from<br>
broken domains; however with 80 lists this is tedious, slow and
error-prone.<br>
<br>
Now I'm going to dig into the sources and possibly implement a timeout
when<br>
communicating with sendmail.<br>
<br>
The best solution would be that qrunner remebers broken domains: that way
it<br>
would only wait for the first message to such a domain; for other
messages it<br>
wouldn't even try delivery (in one run). So the "lockup"
wouldn't last Q*3min<br>
(Q is the total number of people from broken domains), but only D*3min
(the<br>
number of different broken domains). In my case Q > 20, D=2.<br>
</font></blockquote><br>
The *correct* solution it adjust your *sendmail* timeouts to match what
you want<br>
it to do. Sendmail can be told to remember broken domains, and all
of that.<br>
Never force the mail list manager to do what the MTA is supposed to
do;<br>
conversely, don't complain to the mailing list manager if the MTA isn't
configured right.<br>
There's about 80 gazillion timeout settings in sendmail, all of which
default to Big Numbers<br>
if you don't tweak them; and it also defaults to dns validating every
address it's given.<br>
If your sendmail usage doesn't match that profile, adjust sendmail!
That's why there's<br>
all those knobs and dials on the box. Heck, 8.11.0 has *6* separate
resolver timeouts.<br>
You also want to look at nocanonify, and be sure you aren't basing your
relay rules<br>
on hostname lookups.</html>