Skip to content

docs: record DMARC shipped at p=none - #60

Open
abiassi wants to merge 1 commit into
mainfrom
docs/dmarc-shipped
Open

abiassi wants to merge 1 commit into
mainfrom
docs/dmarc-shipped

Conversation

@abiassi

@abiassi abiassi commented Jul 25, 2026

Copy link
Copy Markdown
Collaborator

Docs-only. Records the DMARC records added to DNS on 2026-07-25 (no code change).

What was added to DNS

Record Value Why
_dmarc.deepbreathingexercises.com TXT v=DMARC1; p=none; rua=mailto:hi@abiassi.com; fo=1 The policy. Monitoring only.
deepbreathingexercises.com._report._dmarc.abiassi.com TXT v=DMARC1 RFC 7489 §7.1 external-destination authorization. Without it, Google/Microsoft/Yahoo silently decline to send reports to an address on a different domain.

Both verified live via 8.8.8.8. DKIM and SPF confirmed unchanged.

Both domains are on Vercel DNS under the amorimferreiras-projects scope, not darkmatterai — noted in the backlog because it is not where you would look first.

Why p=none

Enforces nothing, so there is no deliverability risk. Both alignment legs already pass:

  • DKIMd=deepbreathingexercises.com matches the From header domain exactly.
  • SPF — the envelope domain send.deepbreathingexercises.com (Resend custom MAIL FROM) shares an organizational domain with the apex, so it aligns under the default relaxed policy. The apex has no SPF record of its own and does not need one.

So p=quarantine would not break existing mail. Left at p=none anyway to gather evidence first rather than assume.

Measure after 2026-08-08

Read the aggregate reports at hi@abiassi.com, confirm every legitimate sending source passes, then raise to p=quarantine. Do not jump straight to p=reject.

Published _dmarc on the apex plus the RFC 7489 external-destination
authorization on abiassi.com, which is the part that is easy to miss —
without it reporters silently decline to send aggregate reports to a
different domain.

Notes that both alignment legs already pass (DKIM d= matches the apex
exactly; SPF's send. subdomain aligns under the default relaxed policy),
so raising to p=quarantine is safe once ~2 weeks of reports confirm no
legitimate sender is failing. Measure-after date set to 2026-08-08.
@vercel

vercel Bot commented Jul 25, 2026

Copy link
Copy Markdown
Contributor

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
deepbreathing-tmmj Ready Ready Preview, Comment Jul 25, 2026 8:04am

Request Review

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant