Mailing lists and mail forwarders vs. DMARC
draft-levine-dmarc-listugh-01
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | John R. Levine | ||
| Last updated | 2024-02-16 (Latest revision 2023-08-15) | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
DMARC introduced an authentication system intended to detect and deter domain name impersonation in mail message From header fields. Unfortunately, DMARC also has caused severe damage to mail forwarders and discussion lists. We describe the damage and some of the workarounds.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)