Skip to content

Move DMARC to p=quarantine - #125

Merged
bulbashenko merged 1 commit into
mainfrom
dmarc-quarantine
Oct 14, 2026
Merged

bulbashenko merged 1 commit into
mainfrom
dmarc-quarantine

Conversation

@bulbashenko

Copy link
Copy Markdown
Contributor

Step 1 of bulbashenko-com/mail#5: _dmarc.bulbashenko.com goes from p=none to p=quarantine. Everything else in the record stays the same.

Evidence. Google's aggregate report for 2026-10-13: both sources pass DMARC through the aligned v1-rsa-20261006 DKIM signature.

  • 65.109.174.215 (Stalwart): SPF and DKIM both pass.
  • A Google IPv6 relay (forwarded mail): SPF fails but DKIM passes. Quarantine will not catch it.

v1-ed25519-20261006 shows as fail at Google. Google does not verify Ed25519 DKIM, so this is noise and does not affect the result.

Before merging, check that the earlier daily reports since 2026-10-06 look the same (all policy_evaluated = pass). That is the issue's "1–2 weeks clean" condition. This PR saw only one day.

just plan: 0 to add, 1 to change (cloudflare_dns_record.dmarc_txt, content + comment), 0 to destroy. Apply: owner, just apply.

🤖 Generated with Claude Code

Step 1 of mail#5. Google's aggregate report for 2026-10-13 shows every
message from bulbashenko.com passing DMARC through the aligned RSA DKIM
signature, including one forwarded through Google where SPF fails. Only
Stalwart sends for the domain (SPF "mx -all"), so quarantine should not
affect legitimate mail. p=reject follows after a couple of clean weeks.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@bulbashenko
bulbashenko merged commit 271aa19 into main Oct 14, 2026
4 checks passed
@bulbashenko
bulbashenko deleted the dmarc-quarantine branch October 14, 2026 20:59
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