[Ietf-dkim] Re: DKIM2 / DMARC Sender Policy Proposal
Steffen Nurpmeso <steffen@sdaoden.eu> Tue, 17 November 2026 19:36 UTC
Received: from sdaoden.eu (sdaoden.eu [217.144.132.164]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange x25519 server-signature ECDSA (prime256v1) server-digest SHA256) (No client certificate requested) by mx.ietf.org (Postfix) with ESMTPS id 87FCA4B; Tue, 17 Nov 2026 19:36:01 +0000 (UTC)
Authentication-Results: mx.ietf.org; dkim=pass header.d=sdaoden.eu header.s=citron header.b=XRF2yrza; spf=pass (mx.ietf.org: domain of steffen@sdaoden.eu designates 217.144.132.164 as permitted sender) smtp.mailfrom=steffen@sdaoden.eu; dmarc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sdaoden.eu; s=citron; t=1794944154; x=1795610820; h=date:author:from:to:cc:subject: message-id:in-reply-to:references:mail-followup-to:openpgp:blahblahblah: author:from:subject:date:to:cc:resent-author:resent-date:resent-from: resent-sender:resent-to:resent-cc:resent-reply-to:resent-message-id: in-reply-to:references:mime-version:content-type: content-transfer-encoding:content-disposition:content-id: content-description:message-id:mail-followup-to:openpgp:blahblahblah; bh=XZHzibWMyKoS/5Vu/hjG0MLOvbA9u6i9S/4jCoOkHW8=; b=XRF2yrzaXs1SKgvzRnE3B+4pRWeIHIefDfSHypwIc+/lRtN58i1N34NhCd3iu+XE7ERtVlZf 89Blyl6NaRvHKDIgcDBd3fXg2yhptWwQ1pxNxp9wDWwNk6Ji683yWoXyOj+cHC2Ehfj5buDbp1 dufCO0oV9usxbO8/4PE7SHQV26Lvds6PIp98exT3iNr/xtl3zz8suYwQp7edbI1K2zRGWQFPFM rYRSozTO7fOPnghxicfgOXfpOCsXLiTo0Pg6ZVAlAaKZ5WoNowbc8XSjCfDu6vuIg4tOaHRIo+ UbS6ibf7u0KKP6KqfQBbPZ5arCVSovY5GQcvuz4BZuMztQTg==
Date: Tue, 17 Nov 2026 20:22:04 +0100
Author: Steffen Nurpmeso <steffen@sdaoden.eu>
From: Steffen Nurpmeso <steffen@sdaoden.eu>
To: ietf-dkim@ietf.org, mailmaint@ietf.org
Message-ID: <20261117192204.pejmt4c8@steffen%sdaoden.eu>
In-Reply-To: <69B1C299-4F50-46B0-9248-88E28D13FAEA@episteme.net>
References: <CAHEDGu8h9wyukuj+yDT+LQH-hk32iPbdrQ4sxny6KoKMYYyzxQ@mail.gmail.com> <CAAFsWK3jepdeMzQi5Whs4chDF2daAR0-5ED672WaLP73MG1VTw@mail.gmail.com> <CAAFsWK1K-1br3fOrr5=tc-GahaJwki8=cGH2g=pxfKre=auViw@mail.gmail.com> <CAMhUCqLk3+hZbqKOZ5234BJo=dhX0Gn8VV1xRNAOQenjFZvdxg@mail.gmail.com> <CAAFsWK0FLF2zb06Uc_UmhsWT3tNTkhLBYAu_qLLtjpowr5N93A@mail.gmail.com> <PR3P193MB050519ADCD0C265556254325D1BE2@PR3P193MB0505.EURP193.PROD.OUTLOOK.COM> <CAAFsWK1ucEx2uDqQq9zSAQtYdZb5gqeAizwQczNryNug6H6dhA@mail.gmail.com> <CAAFsWK3-S9krHyGBBJ6hkUROfyXGsGsNqddyjfkez8=4qw0A_g@mail.gmail.com> <CAMhUCqJxq_22UU3kGew2GoedcxpAgUMFxq7o1M5GcmdFb=_H0w@mail.gmail.com> <CAHEDGu_jzhmoY4U+OreBp3PbvS4cb-LExNrY+vjXQ8Ddx=gKYQ@mail.gmail.com> <CAAFsWK2Td43CdLa9=XnEBb2Uuy2bfCcAuO2y3=THkESw0yzh1w@mail.gmail.com> <CAHEDGu-11sgVCWoFYPVvxLdjO7GatboW7d03+DwZf0O0qqHTJg@mail.gmail.com> <20261103221405.783EA126BFE0A@ary.qy> <2259974203161dc6c3c4510752d81e9d@itb.it> <CAAFsWK2LJonZpXuMA1VDt5WUjLr-NaoDwof8o79Uj3w3r0DDnQ@mail.gmail.com> <adb351394493404da7ef73125bbdff82@itb.it> <PR3P193MB0505310533203CBCB56F1C75D1712@PR3P193MB0505.EURP193.PROD.OUTLOOK.COM> <G7rCIFn1LE9qFAou@highwayman.com> <50B2FB80-167F-4B1A-91CC-0BBB8694FC57@episteme.net> <CAHEDGu-GFi5aeWJySSsmWpmnsrehvU2ayVnwUcVJDktjROqoOA@mail.gmail.com> <69B1C299-4F50-46B0-9248-88E28D13FAEA@episteme.net>
Mail-Followup-To: ietf-dkim@ietf.org, mailmaint@ietf.org, Steffen Nurpmeso <steffen@sdaoden.eu>
User-Agent: s-nail v14.10.0-alpha-90-g309bc3e99a
OpenPGP: id=EE19E1C1F2F7054F8D3954D8308964B51883A0DD; url=https://ftp.sdaoden.eu/steffen.asc; preference=signencrypt
BlahBlahBlah: Any stupid boy can crush a beetle. But all the professors in the world can make no bugs.
X-Spamd-Bar: ----------------
Message-ID-Hash: OZXQGYWQZDYYUE7PQHG4SZ2BZJYI6UCL
X-Message-ID-Hash: OZXQGYWQZDYYUE7PQHG4SZ2BZJYI6UCL
X-MailFrom: steffen@sdaoden.eu
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; loop; banned-address; header-match-ietf-dkim.ietf.org-0; emergency; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: Steffen Nurpmeso <steffen@sdaoden.eu>
X-Mailman-Version: 3.3.10
Precedence: list
Subject: [Ietf-dkim] Re: DKIM2 / DMARC Sender Policy Proposal
List-Id: IETF DKIM List <ietf-dkim.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-dkim/Zru_S6Ctk2B-uoTj8Kl_VZujVGQ>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-dkim>
List-Help: <mailto:ietf-dkim-request@ietf.org?subject=help>
List-Owner: <mailto:ietf-dkim-owner@ietf.org>
List-Post: <mailto:ietf-dkim@ietf.org>
List-Subscribe: <mailto:ietf-dkim-join@ietf.org>
List-Unsubscribe: <mailto:ietf-dkim-leave@ietf.org>
Pete Resnick wrote in
<69B1C299-4F50-46B0-9248-88E28D13FAEA@episteme.net>:
...
|[Again, this part not as chair; obviously if the WG disagrees with this,
|I make the call as chair that I am myself "in the rough".]
|
|Let's call the downside "the Yahoo problem" (sorry Richard). Back when
|Yahoo implemented p=reject, it wasn't because they really wanted to
In my opinion this totally misses the overall point.
The overall point is that DMARC destructed email proper, and the
heard claim "it is not even an official standard" was in the
meantime counteracted by entire hordes of engineers which
implemented successors officially.
Yes. Email as a "natural" type of communication, as an
"electronic mail", as envisioned and implemented and usable for
decades, was sacrificed for the operational needs of some business
giants that only offer and use a certain aspect of email. Many
engineers, within gremiums of engineers, working alongside
engineers, happily jumped on that train and are willing to defend
the very nature of that destruction, often surely not even
realizing the sacrification as such.
But it is that, DMARC defined, in a narrow-minded and context
free, context in respect to the development of written paper mail
to electronic mail, defined as out-of-scope
o evaluation of anything other than RFC5322.From;
and
o Messages bearing a single RFC5322.From field containing multiple
addresses (and, thus, multiple domain names to be evaluated) are
typically rejected because the sorts of mail normally protected by
DMARC do not use this format;
and
o Messages with an RFC5322.From field that contains no meaningful
domains, such as RFC 5322 [MAIL]'s "group" syntax, are typically
ignored.
I reckon that RFC 5322.bis still contains
~"If the from field contains more than one mailbox specification
in the mailbox-list, then the sender field, containing the field
name "Sender" and a single mailbox specification, MUST appear in
the message."
is more caused by hesitation than by real-life email as can be
seen in at least the western world.
Anyhow all this made impossible the, for example in Germany,
century old form of "common letters", where many people write
a letter as a unity. Regarding computers, for example, there was
a globe-wide such letter regarding the european digital security
act. Of course, since public discourse is worse than under the
Nazis, i have heard this is true for many Western countries, btw.
(Granted Paul Sethe wrote in a famous letter to the German
magazine in 1965 "freedom of press is the freedom of 200 rich
men", and even more regarding oasis' of freedom, but that is all
off-topic, is it), this letter missed people from many countries,
but Western, many US americans, they were there.
This is no longer possible with email!
Instead, a single person in a single-address RFC5322.from message
may attach a PDF containing such a letter.
But even S/MIME or OpenPGP plus a good DKIM (thus not that DKIM2)
covered email message will be usable.
Yesterday yes.
Not today.
Not tomorrow.
So i do not call this "the yahoo problem".
I call this a vision-free, value disregarding, and existing
technology devaluing mis- and overengineering.
--steffen
|
|Der Kragenbaer, The moon bear,
|der holt sich munter he cheerfully and one by one
|einen nach dem anderen runter wa.ks himself off
|(By Robert Gernhardt)
- [Ietf-dkim] DKIM2 / DMARC Sender Policy Proposal Wei Chuang
- [Ietf-dkim] Re: DKIM2 / DMARC Sender Policy Propo… Todd Herr
- [Ietf-dkim] Re: DKIM2 / DMARC Sender Policy Propo… Wei Chuang
- [Ietf-dkim] Re: DKIM2 / DMARC Sender Policy Propo… Emanuel Schorsch
- [Ietf-dkim] Re: DKIM2 / DMARC Sender Policy Propo… Wei Chuang
- [Ietf-dkim] Re: DKIM2 / DMARC Sender Policy Propo… Wei Chuang
- [Ietf-dkim] Re: DKIM2 / DMARC Sender Policy Propo… John Levine
- [Ietf-dkim] Re: DKIM2 / DMARC Sender Policy Propo… Al Iverson
- [Ietf-dkim] Re: DKIM2 / DMARC Sender Policy Propo… Wei Chuang
- [Ietf-dkim] Re: DKIM2 / DMARC Sender Policy Propo… Todd Herr
- [Ietf-dkim] Re: DKIM2 / DMARC Sender Policy Propo… Wei Chuang
- [Ietf-dkim] R: Re: DKIM2 / DMARC Sender Policy Pr… MCN-IETF
- [Ietf-dkim] Re: DKIM2 / DMARC Sender Policy Propo… Wei Chuang
- [Ietf-dkim] Re: DKIM2 / DMARC Sender Policy Propo… Wei Chuang
- [Ietf-dkim] Re: DKIM2 / DMARC Sender Policy Propo… Al Iverson
- [Ietf-dkim] Re: DKIM2 / DMARC Sender Policy Propo… Emanuel Schorsch
- [Ietf-dkim] Re: DKIM2 / DMARC Sender Policy Propo… Wei Chuang
- [Ietf-dkim] Re: DKIM2 / DMARC Sender Policy Propo… Emanuel Schorsch
- [Ietf-dkim] Re: DKIM2 / DMARC Sender Policy Propo… Wei Chuang
- [Ietf-dkim] R: Re: DKIM2 / DMARC Sender Policy Pr… MCN-IETF
- [Ietf-dkim] Re: R: Re: DKIM2 / DMARC Sender Polic… Wei Chuang
- [Ietf-dkim] Re: DKIM2 / DMARC Sender Policy Propo… Richard Clayton
- [Ietf-dkim] Re: DKIM2 / DMARC Sender Policy Propo… Wei Chuang
- [Ietf-dkim] Re: DKIM2 / DMARC Sender Policy Propo… Richard Clayton
- [Ietf-dkim] Re: DKIM2 / DMARC Sender Policy Propo… John Levine
- [Ietf-dkim] Re: DKIM2 / DMARC Sender Policy Propo… Wei Chuang
- [Ietf-dkim] Re: DKIM2 / DMARC Sender Policy Propo… Wei Chuang
- [Ietf-dkim] Re: DKIM2 / DMARC Sender Policy Propo… Wei Chuang
- [Ietf-dkim] Re: DKIM2 / DMARC Sender Policy Propo… Emanuel Schorsch
- [Ietf-dkim] Re: DKIM2 / DMARC Sender Policy Propo… Wei Chuang
- [Ietf-dkim] Re: DKIM2 / DMARC Sender Policy Propo… Tero Kivinen
- [Ietf-dkim] Re: DKIM2 / DMARC Sender Policy Propo… Wei Chuang
- [Ietf-dkim] Re: DKIM2 / DMARC Sender Policy Propo… Emanuel Schorsch
- [Ietf-dkim] Re: DKIM2 / DMARC Sender Policy Propo… Wei Chuang
- [Ietf-dkim] Re: DKIM2 / DMARC Sender Policy Propo… Emanuel Schorsch
- [Ietf-dkim] R: Re: DKIM2 / DMARC Sender Policy Pr… MCN-IETF
- [Ietf-dkim] Re: R: Re: DKIM2 / DMARC Sender Polic… John Levine
- [Ietf-dkim] Re: R: Re: DKIM2 / DMARC Sender Polic… Vittorio
- [Ietf-dkim] Re: R: Re: DKIM2 / DMARC Sender Polic… Wei Chuang
- [Ietf-dkim] Re: R: Re: DKIM2 / DMARC Sender Polic… Vittorio
- [Ietf-dkim] R: Re: R: Re: DKIM2 / DMARC Sender Po… MCN-IETF
- [Ietf-dkim] Re: R: Re: R: Re: DKIM2 / DMARC Sende… Richard Clayton
- [Ietf-dkim] Re: DKIM2 / DMARC Sender Policy Propo… Pete Resnick
- [Ietf-dkim] Re: DKIM2 / DMARC Sender Policy Propo… Emanuel Schorsch
- [Ietf-dkim] Re: DKIM2 / DMARC Sender Policy Propo… John Levine
- [Ietf-dkim] Re: DKIM2 / DMARC Sender Policy Propo… Pete Resnick
- [Ietf-dkim] Re: DKIM2 / DMARC Sender Policy Propo… Richard Clayton
- [Ietf-dkim] Re: DKIM2 / DMARC Sender Policy Propo… Bron Gondwana
- [Ietf-dkim] Re: DKIM2 / DMARC Sender Policy Propo… G.W. Haywood
- [Ietf-dkim] Re: DKIM2 / DMARC Sender Policy Propo… Bron Gondwana
- [Ietf-dkim] Re: DKIM2 / DMARC Sender Policy Propo… Richard Clayton
- [Ietf-dkim] Re: DKIM2 / DMARC Sender Policy Propo… Wei Chuang
- [Ietf-dkim] Re: DKIM2 / DMARC Sender Policy Propo… John Levine
- [Ietf-dkim] Re: DKIM2 / DMARC Sender Policy Propo… Wei Chuang
- [Ietf-dkim] Re: DKIM2 / DMARC Sender Policy Propo… Steffen Nurpmeso
- [Ietf-dkim] Re: DKIM2 / DMARC Sender Policy Propo… Steffen Nurpmeso
- [Ietf-dkim] Re: R: Re: R: Re: DKIM2 / DMARC Sende… John Levine
- [Ietf-dkim] Re: R: Re: DKIM2 / DMARC Sender Polic… Taavi Eomäe
- [Ietf-dkim] Re: R: Re: DKIM2 / DMARC Sender Polic… John Levine
- [Ietf-dkim] Re: DKIM2 / DMARC Sender Policy Propo… Wei Chuang
- [Ietf-dkim] Re: DKIM2 / DMARC Sender Policy Propo… Emanuel Schorsch