---
title: "Comment by Mahdi Jabinpour on \"WordPress mail lands in spam: configure SMTP, SPF, DKIM and DMARC in the right order\" | Hashnode"
description: "The destination-header test is the most useful part of this workflow. One detail worth correcting: an explicit sp tag is not required for the organizational dom"
url: "https://hashnode.com/posts/wordpress-mail-lands-in-spam-configure-smtp-spf-dkim-and-dmarc-in-the-right-order/6adc44f995df3b13ab99a29f/comment/6add13a4838a42a2d61b8c7e"
---

[Discussion](https://hashnode.com/posts/wordpress-mail-lands-in-spam-configure-smtp-spf-dkim-and-dmarc-in-the-right-order/6adc44f995df3b13ab99a29f)

Comment [WordPress mail lands in spam: configure SMTP, SPF, DKIM and DMARC in the right order](https://hashnode.com/posts/wordpress-mail-lands-in-spam-configure-smtp-spf-dkim-and-dmarc-in-the-right-order/6adc44f995df3b13ab99a29f)

[Mahdi Jabinpour](https://hashnode.com/@mahdi-lumowp)

[Oct 24](https://hashnode.com/posts/wordpress-mail-lands-in-spam-configure-smtp-spf-dkim-and-dmarc-in-the-right-order/6adc44f995df3b13ab99a29f/comment/6add13a4838a42a2d61b8c7e)

The destination-header test is the most useful part of this workflow. One detail worth correcting: an explicit sp tag is not required for the organizational domain’s p policy to cover existing subdomains. Under DMARC policy discovery, p is the fallback when no more specific policy overrides it. RFC 9989’s sp definition makes that inheritance explicit. Clarifying this would help readers avoid changing DNS based on the assumption that subdomains are otherwise uncovered.
