https://bz.apache.org/SpamAssassin/show_bug.cgi?id=8201
--- Comment #12 from Sidney Markowitz <sid...@sidney.com> ---
I'm going to try the following in a test build. I'll add this function to
t/SATest.pm
# Some Windows machines get excessive SERVFAIL responses from
# their configured nameserver during our tests
sub nameservers_for_safer_use {
my $nsprefs = '';
if ($RUNNING_ON_WINDOWS && can_use_net_dns_safely()) {
my $resolver = Net::DNS::Resolver->new;
my @nameservers = $resolver->nameservers;
foreach my $ns (@nameservers) {
$nsprefs .= "dns_server $ns\n";
}
$nsprefs .= q(
dns_server 1.1.1.1
dns_server 8.8.8.8
);
}
return $nsprefs;
}
and in the four tests that are having problems I'll add the result of calling
that to tstprefs.
That should behave the same unless a DNS query gets an error, in which case it
will try the query again on 1.1.1.1 and then 8.8.8.8.
If the Windows local subnet DNS server is the cause of the SRVFAIL errors, that
should fix it. Or even if the problem is in the Windows client, the problem is
sporadic, so this gets it to try again with a different server.
Any opinions on committing this if it works in the tests?
--
You are receiving this mail because:
You are the assignee for the bug.
