You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@spamassassin.apache.org by jm...@apache.org on 2007/07/30 14:57:36 UTC
svn commit: r560957 - /spamassassin/trunk/lib/Mail/SpamAssassin/Conf.pm
Author: jm
Date: Mon Jul 30 05:57:35 2007
New Revision: 560957
URL: http://svn.apache.org/viewvc?view=rev&rev=560957
Log:
clarify documentation to note clearly that MXes must perform DNS name resolution, for whitelist_from_rcvd to work
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?view=diff&rev=560957&r1=560956&r2=560957
==============================================================================
--- spamassassin/trunk/lib/Mail/SpamAssassin/Conf.pm (original)
+++ spamassassin/trunk/lib/Mail/SpamAssassin/Conf.pm Mon Jul 30 05:57:35 2007
@@ -350,6 +350,10 @@
it will be, but for a complex network you may get better results by setting that
parameter.
+It also requires that your mail exchangers be configured to perform DNS
+reverse lookups on the connecting host's IP address, and to record the
+result in the generated Received: header.
+
e.g.
whitelist_from_rcvd joe@example.com example.com