Welcomelist from SPF - welcomelist_from_spf
Works similarly to welcomelist_from, except that in addition to matching a sender address, a check against the domains SPF
record must pass. The first parameter is an address to whitelist, and the second is a string to match the relays 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 whitelist 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.
Default: empty
SPF timeout - spf_timeout
How many seconds to wait for an SPF query to complete, before scanning continues without the SPF result. A numeric value
is optionally suffixed by a time unit (s, m, h, d, w, indicating seconds (default), minutes, hours, days, weeks).
Default: 5
Ignore received SPF header - ignore_received_spf_header
By default, to avoid unnecessary DNS lookups, the plugin will try to use the SPF results found in any Received-SPF
headers it finds in the message that could only have been added by an internal relay. Set this option to ignore any
Received-SPF headers present and to have the plugin perform the SPF check itself.
Default: 0
Use newest received SPF header - use_newest_received_spf_header
By default, when using Received-SPF headers, the plugin will attempt to use the oldest (bottom most) Received-SPF
headers, that were added by internal relays, that it can parse results from since they are the most likely to be
accurate. This is done so that if you have an incoming mail setup where one of your primary MXes doesn't know about a
secondary MX (or your MXes don't know about some sort of forwarding relay that SA considers trusted+internal) but SA is
aware of the actual domain boundary (internal_networks setting) SA will use the results that are most accurate. Use this
option to start with the newest (top most) Received-SPF headers, working downwards until results are successfully
parsed.
Default: 0