On 20/05/2026 02:40, Richard Clayton wrote:
[mailing lists] could take advantage of mechanisms being suggested
(in some circles, but not yet at the IETF) for "newsletters" to deal
with their validation problems; where the sign up mechanism uses
OAuth to determine that the request is genuine (and the mailbox
provider inherently knows that the traffic is expected).
Let me see if I understand the proposed flow correctly:
1. The user subscribes through the mailing list web interface,
2. the mailing list site redirects the user to their mailbox provider,
3. the mailbox provider authenticates the user and redirects them back
to the mailing list site with an authorization result containing an
access token.
Is that essentially the intended model?
This seems to imply a shift away from traditional subscribe-by-email
workflows, since the authorization step depends on an interactive
web/OAuth exchange.
These mechanisms do not require ARC ! he says, to bring it marginally
on-topic
Would the expectation then be that the access token is conveyed in a
message header, so that the mailbox provider can recognize the
forwarding as authorized? And would that token remain valid for the
lifetime of the subscription?
It would seem safer if the mailing list signed the relevant header
fields containing the authorization information. As you note, that does
not require ARC specifically; DKIM signing could provide the necessary
protection as well.
Best
Ale
--
_______________________________________________
dmarc mailing list -- [email protected]
To unsubscribe send an email to [email protected]