Mail::SpamAssassin::Plugin::SPF(3pm) | User Contributed Perl Documentation | Mail::SpamAssassin::Plugin::SPF(3pm) |
Mail::SpamAssassin::Plugin::SPF - perform SPF verification tests
loadplugin Mail::SpamAssassin::Plugin::SPF
This plugin checks a message against Sender Policy Framework (SPF) records published by the domain owners in DNS to fight email address 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 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.
Works similarly to welcomelist_from, except that in addition to matching a sender address, a check against the domain's SPF record must pass. The first parameter is an address to welcomelist, and the second is a string to match the relay's rDNS.
Just like welcomelist_from, multiple addresses per line, separated by spaces, are OK. Multiple "welcomelist_from_spf" lines are also OK.
The headers checked for welcomelist_from_spf addresses are the same headers used for SPF checks (Envelope-From, Return-Path, X-Envelope-From, etc).
Since this welcomelist requires an SPF check to be made, network tests must be enabled. It is also required that your trust path be correctly configured. See the section on "trusted_networks" for more info on trust paths.
e.g.
welcomelist_from_spf joe@example.com fred@example.com welcomelist_from_spf *@example.com
Same as "welcomelist_from_spf", but used for the default welcomelist entries in the SpamAssassin distribution. The welcomelist score is lower, because these are often targets for spammer spoofing.
Used to remove a "welcomelist_from_spf" or "def_welcomelist_from_spf" entry. The specified email address has to match exactly the address previously used.
Useful for removing undesired default entries from a distributed configuration by a local or site-specific configuration or by "user_prefs".
Set this option to 1 to ignore any "Received-SPF" headers present and to have the plugin perform the SPF check itself.
Note that unless the plugin finds an "identity=helo", or some unsupported identity, it will assume that the result is a mfrom SPF check result. The only identities supported are "mfrom", "mailfrom" and "helo".
Use this option to start with the newest (top most) "Received-SPF" headers, working downwards until results are successfully parsed.
2024-04-12 | perl v5.38.2 |