Boutique Ink

Email authentication assessment
Findings excerpt · ILL–001

Illustrative example

Before enforcement,
know what sends.

A decision-ready excerpt connecting sending identity, message evidence and the next controlled change.

Illustrative exampleEntirely fictional. Domains, addresses, systems and observations below are constructed for demonstration; no client information or results are represented.

The decision to support.

01 / Scope

Can the organization advance its DMARC policy while preserving its legitimate business-email paths? This excerpt tests sender alignment and identifies what remains unresolved before that decision.

Evidence, kept in context.

02 / Evidence register
ReferenceConstructed observationSupported interpretation
E–01Published policy snapshot_dmarc.example.comv=DMARC1; p=none;
rua=mailto:dmarc@example.com
Monitoring requestedThis policy does not request quarantine or rejection. The receiving system still determines message handling.
E–02Primary mailbox pathFrom domain: example.comDKIM: pass · d=example.com
SPF: pass · mailfrom=example.com
Aligned in this sampleThe reported authenticated identities match the visible From domain. One sample does not establish every message path.
E–03CRM sending pathFrom domain: example.comDKIM: pass · d=sender.example.net
SPF: pass · mailfrom=sender.example.net
Authentication ≠ alignmentNeither reported identity aligns with example.com. No additional aligned authentication pass is assumed.
E–04Unclassified source198.51.100.42Aggregate-report observation: SPF fail; DKIM none; no confirmed business owner.Ownership unresolvedThe supplied material does not establish whether this is authorized, obsolete or unauthorized sending.

Working recommendation

Resolve the CRM alignment gap and classify the unknown source before advancing policy.

ILLUSTRATIVE EXAMPLE · Assessment excerpt, not a complete assessment01 / 02

Boutique Ink

Illustrative example
Evidence → judgment → action

Findings and recommended sequence

The record should explain
the next decision.

Priorities below apply only to this fictional scenario. Implementation depends on confirmed business ownership, platform capability and authorization.

F–01PRIORITY 1
E–03

The CRM path is not aligned.

The reported passes authenticate sender.example.net, while the visible From domain is example.com. These results do not supply an aligned pass for this message.

Authentication-Results: mx.example.org;
  dkim=pass header.d=sender.example.net header.s=mail1;
  spf=pass smtp.mailfrom=sender.example.net;
  dmarc=fail header.from=example.com
From: Billing <billing@example.com>

Receiver-added excerpt; trust and completeness are assumed for this illustration.

Recommended action

Confirm the CRM owner and examine its custom DKIM and return-path options. Agree an aligned configuration, then validate representative messages from each relevant sending mode.

Trace E–03 to F–01
Evidence E–03
The visible From domain is example.com. DKIM and SPF pass for sender.example.net.
Interpretation
Neither pass supplies an aligned identity for this message.
Next action
Confirm the CRM owner and examine its custom DKIM and return-path options. Agree an aligned configuration, then validate representative messages from each relevant sending mode.

F–02PRIORITY 1
E–04

An unknown source needs an owner.

The report observation is evidence of domain use, not proof of legitimacy or intent. The available inventory does not identify the source.

Recommended action

Reconcile the source with platform owners, historical integrations and representative message evidence. Record its classification and rationale before treating it as an enforcement exception.

Trace E–04 to F–02
Evidence E–04
Aggregate reporting shows SPF fail and DKIM none for 198.51.100.42. The business owner is unconfirmed.
Interpretation
The report shows use of the domain. The available evidence leaves authorization and intent unresolved.
Next action
Reconcile the source with platform owners, historical integrations and representative message evidence. Record its classification and rationale before treating it as an enforcement exception.

What remains uncertain.

  • The CRM’s supported signing and return-path configuration has not been verified.
  • The sample set does not cover every forwarding, application or message path.
  • Receiver filtering and final disposition are outside the sender’s control.

What the handoff should retain.

  • Sender inventory with named owners and unresolved sources.
  • Approved configuration, evidence references and test records.
  • Policy decision, dependencies, rollback responsibility and remaining work.

Next decision: Resolve F–01 and F–02, then agree the policy change, verification criteria and rollback responsibility. Implementation requires an agreed scope and a verified environment.

ILLUSTRATIVE EXAMPLE · Fictional evidence and recommendations02 / 02

Define the next step

Start with a clearer picture.

A short description of the domain, the objective and the platforms involved is enough to begin.

Request an assessment

Full message headers and DMARC aggregate reports are welcome. Please omit credentials, message bodies and their attachments, and DMARC forensic/failure reports. Full inquiry guidance