You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@spamassassin.apache.org by mm...@apache.org on 2012/05/16 15:12:04 UTC
svn commit: r1339152 - /spamassassin/trunk/lib/Mail/SpamAssassin/Conf.pm
Author: mmartinec
Date: Wed May 16 13:12:03 2012
New Revision: 1339152
URL: http://svn.apache.org/viewvc?rev=1339152&view=rev
Log:
docs detail
Modified:
spamassassin/trunk/lib/Mail/SpamAssassin/Conf.pm
Modified: spamassassin/trunk/lib/Mail/SpamAssassin/Conf.pm
URL: http://svn.apache.org/viewvc/spamassassin/trunk/lib/Mail/SpamAssassin/Conf.pm?rev=1339152&r1=1339151&r2=1339152&view=diff
==============================================================================
--- spamassassin/trunk/lib/Mail/SpamAssassin/Conf.pm (original)
+++ spamassassin/trunk/lib/Mail/SpamAssassin/Conf.pm Wed May 16 13:12:03 2012
@@ -1452,7 +1452,7 @@ SpamAssassin considers DNS resolving as
The problem is that the test can introduce some startup delay if a network
connection is down, and in some cases it can wrongly guess that DNS is
-unavailable because a test connections failed, what causes disabling several
+unavailable because a test connection failed, what causes disabling several
DNS-dependent tests.
Please note, the DNS test queries for NS records, so specify domain names,
@@ -1678,8 +1678,8 @@ See also directives I<dns_local_ports_pe
=item dns_test_interval n (default: 600 seconds)
-If dns_available is set to 'test' (which is the default), the dns_test_interval
-time in number of seconds will tell SpamAssassin how often to retest for working DNS.
+If dns_available is set to I<test>, the dns_test_interval time in number
+of seconds will tell SpamAssassin how often to retest for working DNS.
=cut