RFC 7489 obsoleted and receivers MUST now downgrade to quarantine by default
RFC 7489 has been obsoleted, requiring receivers to downgrade to quarantine by default. This change addresses interoperability issues caused by strict DMARC policies, particularly for domains using 'p=reject'. The article emphasizes the importance of applying valid DKIM signatures and suggests a phased approach for domains considering 'p=reject'.
- ▪Domains that publish 'p=reject' must not rely solely on SPF for DMARC pass and must apply valid DKIM signatures.
- ▪Mail receivers should not reject messages solely based on a 'p=reject' policy and must consider additional analysis.
- ▪Failure to adhere to these guidelines can lead to significant operational issues, including the cancellation of mailing list subscriptions.
Hacker News (Newest) files mainly under programming. We currently carry 5,306 of its stories.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
Story provenance
Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.
Record
| Original publisher | Rfc-editor |
| Canonical URL | https://www.rfc-editor.org/rfc/rfc9989.html |
| Publication time | Wed, 20 May 2026 07:47:37 +0000 |
| Retrieval time | 2026-05-20T08:05:00.822Z |
| Last seen | 2026-05-20T08:05:00.822Z |
| Headline source | Publisher (no WeSearch rewrite) |
| Excerpt source | publisher body |
| Excerpt method | First ~120 words (~800 chars) of extracted publisher body, fair-use limited. |
| Summary | WeSearch · cerebras-chat (WeSearch summarizer) |
| Summary source text | contentText |
| Citation coverage | Summary is a WeSearch-generated derivative; primary citation is the original publisher URL. |
| Cluster | _MDdm2WgXxxE |
| Cluster logic | Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison. |
| Ranking reason | Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking. |
| Publisher visit | Yes — open original |
| Substitutes article? | No — link-out required for full text |
Rights status (four layers)
WeSearch handling by dimension
| Indexing | May the item be indexed (stored, ranked, made findable)? | Allowed |
| Snippet | May a short excerpt of the publisher's text be shown? | Allowed |
| AI summary | May WeSearch generate its own short summary of the article? | Limited |
| Retrieval / RAG | May the content be exposed for third-party retrieval-augmented generation? | Not asserted |
| Model training | May the content be used to train AI models? | Not asserted |
| Commercial reuse | May the content be reused commercially? | Not permitted |
Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.
Opening excerpt (first ~120 words) tap to expand
7.4. Interoperability Considerations As discussed in "Interoperability Issues between Domain-based Message Authentication, Reporting, and Conformance (DMARC) and Indirect Email Flows" [RFC7960], the use of "p=reject" can be incompatible with and cause interoperability problems to indirect message flows such as "alumni forwarders", role-based email aliases, and mailing lists across the Internet.¶ As an example of this, a bank might send only targeted messages to account holders. Those account holders might have given their bank addresses such as "[email protected]" (an address that relays the messages to another address with a real mailbox) or "[email protected]" (a role-based address that does similar relaying for the current head of finance at the association).
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at Rfc-editor.
Discussion
0 commentsMore from Rfc-editor
.jpg&w=320)
