FYI: Another attempt at describing From: rewriting
Hi,
Douglas Foster posted this draft to the IETF.
For discussion, see: https://mailarchive.ietf.org/arch/msg/dmarc/Fp1nnmBc242kxvxM7seVwoQ6ccU
Best Ale
---------- Forwarded message --------- From: <internet-drafts@ietf.org> Date: Sun, Oct 3, 2021 at 8:14 PM Subject: New Version Notification for draft-fosterd-dmarc-compliant-mailing-lists-00.txt To: Douglas Foster <dougfoster.emailstandards@gmail.com>
A new version of I-D, draft-fosterd-dmarc-compliant-mailing-lists-00.txt has been successfully submitted by Douglas Foster and posted to the IETF repository.
Name: draft-fosterd-dmarc-compliant-mailing-lists Revision: 00 Title: DMARC Compliant Mailing Lists Document date: 2021-10-03 Group: Individual Submission Pages: 10 URL: https://www.ietf.org/archive/id/draft-fosterd-dmarc-compliant-mailing-lists-... Status: https://datatracker.ietf.org/doc/draft-fosterd-dmarc-compliant-mailing-lists... Html: https://www.ietf.org/archive/id/draft-fosterd-dmarc-compliant-mailing-lists-... Htmlized: https://datatracker.ietf.org/doc/html/draft-fosterd-dmarc-compliant-mailing-...
Abstract: Mailing Lists often make changes to a message before it is retransmitted. This invalidates DKIM signatures, causing a DMARC test on the RFC5322.From addres to fail. A DMARC-compliant mailing list is one which uses member alias addresses to identify the document as sent by a specific author via the mechanism of the list. An appropriate aliasing mechanism will not only prevent DMARC FAIL, but will also allow messages between members, will look natural to senders and recipients, and will allow list organization domains to advance to p=reject. This document describes an aliasing approach which meets these goals.
The IETF Secretariat
participants (1)
-
Alessandro Vesely