Websites, applications and hosting for your business.
Recommended Services
Supported Scripts
Mr. Stig matches the geometric seal of an envelope to its corresponding verification ring.

Your sending platform reports SPF pass, but the recipient reports DMARC fail. These results can coexist. A server may be authorised to send for one domain while the customer sees a different domain in the message. The decisive detail sits beside the verdict: which identity did the receiving system actually evaluate?

This matters when quotations, order notifications or business messages leave through an external platform. A reflexive instruction to add another SPF include can change DNS without resolving the mismatch. Map the message and its sending route before choosing an intervention. A green indicator in the supplier dashboard does not describe every message arriving elsewhere.

The From address, envelope and signature have different roles

The visible From supplies the domain presented as the message author. For an ordinary message with a non-empty MAIL FROM, SPF evaluates the SMTP envelope identity. DKIM verifies a signature associated with its d= signing domain. All three names can appear in one message without identifying the same domain. The role of each name matters.

DMARC needs at least one successful, aligned SPF or DKIM path. Alignment connects an authenticated domain to the From domain. Strict mode requires identical domains; relaxed mode compares their Organizational Domains. A home-made rule that simply takes the last two labels of every name is not a reliable way to establish that boundary.

RFC 9989, published in May 2026, replaces RFC 7489 and specifies a DNS Tree Walk for that determination. In an actual investigation, record the policy and the particular receiving system’s result. Publication of a revised specification does not establish that every deployed mail server has adopted an identical implementation or that a local approximation matches it.

An SPF pass that authenticates the supplier

The following is a synthetic teaching fragment. Its .example domains are fictional: this is neither a customer incident nor a delivered message or DNS test. Assume the receiver has a valid DMARC policy for shop.example and has completed the necessary lookups. These stated inputs isolate alignment rather than pretending to reproduce an entire mail system.

From: Sales <sales@shop.example>
Authentication-Results: mx.receiver.example;
 spf=pass smtp.mailfrom=vendor.example;
 dkim=none;
 dmarc=fail header.from=shop.example

SPF authenticated vendor.example, while the customer sees shop.example. Without a successful aligned DKIM signature, that SPF pass does not support the visible author. Adding authorisation to the SPF record at shop.example does not itself change the MAIL FROM chosen by the platform. Inspect the actual sender configuration instead of assuming that a DNS edit changes its identity.

With real headers, locate Authentication-Results added by the recipient’s trusted infrastructure. A similarly named field is not automatically trustworthy: earlier hops can add their own results, and arbitrary headers can be inserted. Establish who produced the verdict and where. Return-Path can help explain the envelope, but it does not replace identifying the trusted evaluation point.

Change one condition at a time

We ran five local comparisons with synthetic inputs. Authentication verdicts and organisational boundaries are declared inputs, not measurements obtained from a mail server. In the final two rows, shop.example and bounce.shop.example are explicitly assigned the same Organizational Domain. The comparison checks the alignment rules using those supplied inputs. It does not perform SPF evaluation, DKIM cryptography or DNS Tree Walk.

Authenticated identityAlignment with shop.exampleFixture DMARC result
SPF: vendor.example, no DKIMNo alignmentFail
SPF: vendor.example, DKIM d=shop.exampleStrict through DKIMPass
SPF: shop.example, no DKIMStrict through SPFPass
SPF: bounce.shop.example, no DKIMRelaxed with declared common boundaryPass
Same preceding messageStrict, different subdomainFail

The second row explains why a message can pass DMARC despite unaligned SPF: successful aligned DKIM supplies the necessary path. Conversely, two green authentication results for unrelated domains do not suffice. For each passing result, identify the domain it authenticates and check its relationship to the visible From domain.

Repair the particular sending stream

Check whether the external sender supports DKIM using the business domain and whether that signature actually validates at the recipient. Alternatively, or additionally, investigate a custom envelope sender or bounce domain that supports the required SPF alignment. Available options and exact DNS records depend on the platform. Copying settings from an unrelated supplier is not evidence of a correct configuration.

Under a strict policy, a subdomain may be insufficient even when the same business controls it. Changing alignment mode requires a deliberate decision about the intended isolation boundary. Likewise, switching to p=none does not repair message identity. The requested handling of a failure may change while the underlying failure remains. Diagnose that distinction before proposing a policy adjustment.

What counts as evidence of repair

Send a fresh real message through the stream that failed, after applying the appropriate configuration. Record the time, platform, Message-ID, recipient and relevant headers, limiting unnecessary disclosure of personal data. Compare before and after at the same evaluation point. A test from a personal mailbox does not automatically verify the store’s order notification platform or its separate sending identity.

Obtain a separate sample for each independent sender: corporate mailbox, newsletter, CRM and website. DMARC pass establishes a particular identity relationship; it does not guarantee inbox placement. If problems continue after alignment is correct, investigate the recipient’s decision, other sending signals and the message route separately. Repeated DNS changes without a new finding make the incident harder to explain and reverse.

Related Stigmahost services

With Stigmahost Web Hosting, the environment generating messages is one part of the picture. Domain management identifies responsibility for the relevant records. Before requesting a change, bring a specific failed sample and the sending platform’s name. That gives the investigation an observable mismatch to explain and a concrete result to verify after repair.

Share this Post