Knowledge base
Instead of it — an SPF check
Checked whether a message with the given return address from the given IP would pass the Sender-ID check.
The command is declared deprecated: Sender-ID itself has fallen out of use, and the manual refers to check spf.
The main trap is taking its verdict for an SPF verdict. The command checked by Sender-ID rules, which have been abandoned; only check spf answers the question “will the message pass the sender check”.
What the Hub does. It does not call it.
Recommended values
When to use it:
| Question | This command or not |
|---|---|
| will the message pass the sender check | no — check spf |
| what a Sender-ID check would say | yes, but the standard is obsolete |
The purpose and deprecation come from the manual (§ 6.3.3). The split of questions is ours.
Example configuration
# instead of the deprecated check — an SPF check pmta check spf 203.0.113.10 mail.example.com sender@example.com
The argument order for check spf: the sending address, the name in the greeting, the return address.
yellow — — directive names, blue — blocks. They are highlighted the same way in the text of the card.
Compatibility
PowerMTA 6.0
described in the manual of this version · platform: any
The vendor does not state the first version for every directive — there is no note here. The name also appears in the 5.0 edition of the manual.
⇄
Related entries
1 relation
How to check on the node
Look at the sending domain’s SPF record:
dig +short TXT example.com | grep -i 'v=spf1'
No record — nothing to check: the verdict will be none.
In the Hub
- Cost of a mistake
- safe: a wrong value breaks nothing