Jeff Chan wrote on Mon, 6 Sep 2004 18:25:48 -0700: > I assume all programs are subject to some kind of DNS lookup > timeouts either in the application or an external resolver. > RBL lookups in general should be quite fast and cached. If > something is taking longer than 120 seconds it's probably broken. > Given that name resolution on RBLs should normally take a few > milliseconds, if they're taking more than a few seconds there > could definitely be a problem somewhere. > > nscd is some kind of hostname caching program but I'm not > familiar with it. Are things better after you restarted it? > Why did it stop? Did it give any error messages? >
Thanks for the suggestions. I have been off the net for some days, so I couldn't answer earlier. It seems the problem is not DNS-related at all. When I ran sa-learn --sync I found that it took an unusually long time (two minutes or so), so it seems to be something with the journal. It seems when the time to sync has come that it takes too long and is tried repeatedly with each new message until it finally succeeds. I'll watch it and if I find any clues I'll make a new thread. But, there's still my concern about SURBL timeouts. It seems there's no way to specify SURBL timeouts. Is this true? If so, this is an absolute must to add in the URIDNSBL module. DNS timeouts for the other RBL lookups are a common theme on this list. Kai -- Kai Schätzl, Berlin, Germany Get your web at Conactive Internet Services: http://www.conactive.com IE-Center: http://ie5.de & http://msie.winware.org
