1Mail::SpamAssassin::PluUgsienr::CSoPnFt(r3i)buted Perl DMoaciulm:e:nStpaatmiAosnsassin::Plugin::SPF(3)
2
6 Mail::SpamAssassin::Plugin::SPF - perform SPF verification tests
7
9 loadplugin Mail::SpamAssassin::Plugin::SPF
10
12 This plugin checks a message against Sender Policy Framework (SPF)
13 records published by the domain owners in DNS to fight email address
14 forgery and make it easier to identify spams.
15
17 whitelist_from_spf add@ress.com
18 Use this to supplement the whitelist_from addresses with a check
19 against the domain's SPF record. Aside from the name
20 'whitelist_from_spf', the syntax is exactly the same as the syntax
21 for 'whitelist_from'.
22 Just like whitelist_from, multiple addresses per line, separated by
24 spaces, are OK. Multiple "whitelist_from_spf" lines are also OK.
25 The headers checked for whitelist_from_spf addresses are the same
27 headers used for SPF checks (Envelope-From, Return-Path, X-Enve‐
28 lope-From, etc).
29 Since this whitelist requires an SPF check to be made network tests
31 must be enabled. It is also required that your trust path be cor‐
32 rectly configured. See the section on "trusted_networks" for more
33 info on trust paths.
34 e.g.
36 whitelist_from_spf joe@example.com fred@example.com
38 whitelist_from_spf *@example.com
39 def_whitelist_from_spf add@ress.com
41 Same as "whitelist_from_spf", but used for the default whitelist
42 entries in the SpamAssassin distribution. The whitelist score is
43 lower, because these are often targets for spammer spoofing.
44
46 spf_timeout n (default: 5)
47 How many seconds to wait for an SPF query to complete, before scan‐
48 ning continues without the SPF result.
49 do_not_use_mail_spf (0⎪1) (default: 0)
51 By default the plugin will try to use the Mail::SPF module for SPF
52 checks if it can be loaded. If Mail::SPF cannot be used the plugin
53 will fall back to using the legacy Mail::SPF::Query module if it
54 can be loaded.
55 Use this option to stop the plugin from using Mail::SPF and cause
57 it to try to use Mail::SPF::Query instead.
58 do_not_use_mail_spq_query (0⎪1) (default: 0)
60 As above, but instead stop the plugin from trying to use
61 Mail::SPF::Query and cause it to only try to use Mail::SPF.
62 ignore_received_spf_header (0⎪1) (default: 0)
64 By default, to avoid unnecessary DNS lookups, the plugin will try
65 to use the SPF results found in any "Received-SPF" headers it finds
66 in the message that could only have been added by an internal
67 relay.
68 Set this option to 1 to ignore any "Received-SPF" headers present
70 and to have the plugin perform the SPF check itself.
71 Note that unless the plugin finds an "identity=helo", or some
73 unsupported identity, it will assume that the result is a mfrom SPF
74 check result. The only identities supported are "mfrom", "mail‐
75 from" and "helo".
76 use_newest_received_spf_header (0⎪1) (default: 0)
78 By default, when using "Received-SPF" headers, the plugin will
79 attempt to use the oldest (bottom most) "Received-SPF" headers,
80 that were added by internal relays, that it can parse results from
81 since they are the most likely to be accurate. This is done so
82 that if you have an incoming mail setup where one of your primary
83 MXes doesn't know about a secondary MX (or your MXes don't know
84 about some sort of forwarding relay that SA considers
85 trusted+internal) but SA is aware of the actual domain boundary
86 (internal_networks setting) SA will use the results that are most
87 accurate.
88 Use this option to start with the newest (top most) "Received-SPF"
90 headers, working downwards until results are successfully parsed.
91perl v5.8.8 2008-01-05Mail::SpamAssassin::Plugin::SPF(3)