On 07/10/03 14:02 -0400, Matt Kettler wrote: > > So in your case you might do: > > dns_available test: optonline.net > I did this:
dns_available test: 167.206.3.216 ... which is the server shown in nslookup. I also have nameserver 167.206.3.216 nameserver 167.206.7.4 nameserver 167.206.112.138 ...in /etc/resolver.conf What I was trying to fix was that the amount of time for SA to scan a message was varrying from a fraction of a second to 30-32 seconds. The dns_available test entry seems to have fixed the problem. John ------------------------------------------------------- This SF.Net email sponsored by: Parasoft Error proof Web apps, automate testing & more. Download & eval WebKing and get a free book. www.parasoft.com/bulletproofapps1 _______________________________________________ Spamassassin-talk mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
