Overview
A recipient changes the email topics or delivery frequency offered by a service. This proposal concerns email preferences; it does not describe paid subscription management.
This is a proposal. Its operations and representation are still under discussion.
Proposed operations
Target: The recipient’s subscription with the specified service or list.
- Update preferences
- Set the offered topic and frequency options.
Inputs and results
Inputs. The subscription reference and selected values from the settings the service offers.
Results. The recorded settings and when they take effect, or an explanation of why the requested change was not applied.
Permissions. The preference interaction needs permission to update that recipient’s settings. An existing one-click unsubscribe route keeps its own requirements.
Human participation. The service’s email preference page, with its unsubscribe option available.
The behaviour is described here. A machine-readable representation has not yet been selected.
Switch to a weekly digest
- A service offers immediate product announcements or a weekly digest.
- The recipient selects the weekly digest.
- The service records that preference and reports when it applies.
If the selected frequency is no longer offered, the service reports the problem without silently selecting another option.
Existing standards
- One-click unsubscribe · RFC 8058
Preserve the existing unsubscribe mechanism. Its POST excludes cookies and HTTP authorization and requires recipient consent.
Versions and open questions
Initial proposal
The preference interaction is being scoped around existing email unsubscribe behaviour. No version has been assigned.
- Available settings, partial updates and when changes take effect.
- Identity binding for preference changes.
- How clients expose the existing unsubscribe route without adding MAP credential requirements.
Contribute to this definition →
Implementations
No implementation evidence has been published for this proposal.
Support declarations and test reports are supplied by their contributors. Listing them does not certify compatibility. Each targets a type version, execution profile and exact record.