You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@spamassassin.apache.org by gb...@apache.org on 2022/06/13 14:03:50 UTC

svn commit: r1901879 - /spamassassin/trunk/lib/Mail/SpamAssassin/Plugin/SPF.pm

Author: gbechis
Date: Mon Jun 13 14:03:50 2022
New Revision: 1901879

URL: http://svn.apache.org/viewvc?rev=1901879&view=rev
Log:
mention Authentication-Results header in man page

Modified:
    spamassassin/trunk/lib/Mail/SpamAssassin/Plugin/SPF.pm

Modified: spamassassin/trunk/lib/Mail/SpamAssassin/Plugin/SPF.pm
URL: http://svn.apache.org/viewvc/spamassassin/trunk/lib/Mail/SpamAssassin/Plugin/SPF.pm?rev=1901879&r1=1901878&r2=1901879&view=diff
==============================================================================
--- spamassassin/trunk/lib/Mail/SpamAssassin/Plugin/SPF.pm (original)
+++ spamassassin/trunk/lib/Mail/SpamAssassin/Plugin/SPF.pm Mon Jun 13 14:03:50 2022
@@ -30,9 +30,10 @@ records published by the domain owners i
 forgery and make it easier to identify spams.
 
 It's recommended to use MTA filter (pypolicyd-spf / spf-engine etc), so this
-plugin can reuse the Received-SPF header results as is.  Otherwise
-throughput could suffer, DNS lookups done by this plugin are not
+plugin can reuse the Received-SPF and/or Authentication-Results header results as is.
+Otherwise throughput could suffer, DNS lookups done by this plugin are not
 asynchronous.
+Those headers will also help when SpamAssassin is not able to correctly detect EnvelopeFrom.
 
 =cut