On Thu 30/Mar/2023 01:44:42 +0200 Barry Leiba wrote:
There's no need for me to define it: I intentionally did not word my proposed text that way. I think my proposed text is clear about who MUST NOT use p=reject and why... and, as I said in my response to Scott, I'm happy to add an explicit statement that it's an issue of interoperability with existing, decades-old mail flows.


Does that mean that instead of "non-transactional mail flows" we could say "mail flows involving decades old software"?


Best
Ale

On Thu, Mar 30, 2023 at 12:36 AM Todd Herr <todd.herr=
40valimail....@dmarc.ietf.org> wrote:

On Wed, Mar 29, 2023 at 10:15 AM Barry Leiba <barryle...@computer.org>
wrote:

I'm very much against text such as this, as I think it encourages
deployments that are contrary to interoperability and to the intent of
p=reject.

I contend that p=reject (as with the similar construct in the older ADSP)
was intended for high-value domains and transactional mail, and that it was
never intended for use in domains where general users send general email.

I stand by the MUST NOT that I proposed.


I wonder if perhaps you might define "high-value domains" or restate your
position using a term other than "value" and its derivatives?

The reason I ask this is because your contention could perhaps be read as
"low-value domains MUST NOT use p=reject because their mail won't get to
its destination" and that seemingly ascribes a value to their mail that
might be considered somewhat higher than "low" in the eyes of some
beholders.


--

*Todd Herr * | Technical Director, Standards and Ecosystem
*e:* todd.h...@valimail.com
*m:* 703.220.4153

This email and all data transmitted with it contains confidential and/or
proprietary information intended solely for the use of individual(s)
authorized to receive it. If you are not an intended and authorized
recipient you are hereby notified of any use, disclosure, copying or
distribution of the information included in this transmission is prohibited
and may be unlawful. Please immediately notify the sender by replying to
this email and then delete it from your system.
_______________________________________________
dmarc mailing list
dmarc@ietf.org
https://www.ietf.org/mailman/listinfo/dmarc



_______________________________________________
dmarc mailing list
dmarc@ietf.org
https://www.ietf.org/mailman/listinfo/dmarc

_______________________________________________
dmarc mailing list
dmarc@ietf.org
https://www.ietf.org/mailman/listinfo/dmarc

Reply via email to