On Tuesday 06 July 2004 10:03 CET Daniel Quinlan wrote:
> "Malte S. Stretz" <[EMAIL PROTECTED]> writes:
> > Well, all I can say is that I have a sucky upstream DNS-server and with
> > 2.6x a check often took 30-60 seconds. Without Razor and stuff.
>
> This is most likely due to the MX test.
>
> > But this was hopefully improved with the new timout code.
>
> The timeout code is basically unchanged since 2.60.  I think your
> problem is something else.  15 seconds is the longest possible timeout
> for DNSBL rules and is very unlikely due to the scaling timeout code
> (see the rbl_timeout documentation in Mail::SpamAssassin::Conf).

Wasn't the scaling timeout introduced for 3.x?

Anyway, since I upgraded to 3.x I haven't seen any checks taking that long 
anymore, so whatever it was, I take it as fixed :)

Cheers,
Malte

-- 
[SGT] Simon G. Tatham: "How to Report Bugs Effectively"
      <http://www.chiark.greenend.org.uk/~sgtatham/bugs.html>
[ESR] Eric S. Raymond: "How To Ask Questions The Smart Way"
      <http://www.catb.org/~esr/faqs/smart-questions.html>

Reply via email to