Re: [dmarc-ietf] General Purpose Domain
On Mon 18/Mar/2024 15:24:34 +0100 Todd Herr wrote: Issue 137 has been opened for this. On Mon, Mar 18, 2024 at 9:50 AM Todd Herr wrote: On Sun, Mar 17, 2024 at 7:17 AM Alessandro Vesely wrote: On Sat 16/Mar/2024 21:07:53 +0100 Neil Anuskiewicz wrote: Unless I’m misunderstanding, a General Purpose Domain is a separate domain or at least subdomain: Doesn't have to be a subdomain. It is a domain which has human mail users. [...] I propose that rather than twist ourselves into knots trying to define "general-purpose" or "General Purpose Domain" that we instead add text to the above-quoted sentence that says "See section 8.6 (Interoperability Considerations) for further discussion of this topic." and be done with it. +1, Section 8.6 clearly says "domains that host users who might post messages to mailing lists" Best Ale -- ___ dmarc mailing list dmarc@ietf.org https://www.ietf.org/mailman/listinfo/dmarc
Re: [dmarc-ietf] General Purpose Domain
Issue 137 has been opened for this. On Mon, Mar 18, 2024 at 9:50 AM Todd Herr wrote: > On Sun, Mar 17, 2024 at 7:17 AM Alessandro Vesely wrote: > >> On Sat 16/Mar/2024 21:07:53 +0100 Neil Anuskiewicz wrote: >> > Unless I’m misunderstanding, a General Purpose Domain is a separate >> domain or at least subdomain: >> >> >> Doesn't have to be a subdomain. It is a domain which has human mail >> users. >> >> > The term "General Purpose Domain" or any variant thereof does not appear > in DMARCbis. > > There is one appearance of the term "general-purpose" at the end of > Section 7.6: > > In particular, this document makes explicit that domains for > general-purpose email SHOULD NOT deploy a DMARC policy of p=reject. > > I propose that rather than twist ourselves into knots trying to define > "general-purpose" or "General Purpose Domain" that we instead add text to > the above-quoted sentence that says "See section 8.6 (Interoperability > Considerations) for further discussion of this topic." and be done with it. > > -- > > Todd Herr | Technical Director, Standards & Ecosystem > Email: todd.h...@valimail.com > Phone: 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. > -- Todd Herr | Technical Director, Standards & Ecosystem Email: todd.h...@valimail.com Phone: 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
Re: [dmarc-ietf] General Purpose Domain
On Sun, Mar 17, 2024 at 7:17 AM Alessandro Vesely wrote: > On Sat 16/Mar/2024 21:07:53 +0100 Neil Anuskiewicz wrote: > > Unless I’m misunderstanding, a General Purpose Domain is a separate > domain or at least subdomain: > > > Doesn't have to be a subdomain. It is a domain which has human mail users. > > The term "General Purpose Domain" or any variant thereof does not appear in DMARCbis. There is one appearance of the term "general-purpose" at the end of Section 7.6: In particular, this document makes explicit that domains for general-purpose email SHOULD NOT deploy a DMARC policy of p=reject. I propose that rather than twist ourselves into knots trying to define "general-purpose" or "General Purpose Domain" that we instead add text to the above-quoted sentence that says "See section 8.6 (Interoperability Considerations) for further discussion of this topic." and be done with it. -- Todd Herr | Technical Director, Standards & Ecosystem Email: todd.h...@valimail.com Phone: 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
Re: [dmarc-ietf] General Purpose Domain
On Sat 16/Mar/2024 21:07:53 +0100 Neil Anuskiewicz wrote: Unless I’m misunderstanding, a General Purpose Domain is a separate domain or at least subdomain: Doesn't have to be a subdomain. It is a domain which has human mail users. Best Ale -- ___ dmarc mailing list dmarc@ietf.org https://www.ietf.org/mailman/listinfo/dmarc
[dmarc-ietf] General Purpose Domain
Unless I’m misunderstanding, a General Purpose Domain is a separate domain or at least subdomain: * You’d use a General Purpose Domain (GPD) exclusively for Mailing Lists * You would designate either a subdomain or a less critical org domain as your GPD. * The GPD MUST NOT have an enforcing policy of reject. That is, the policy of a GPD must remain p=none. The heading is Interoperability considerations which is a section mostly talking about indirect mail flows. The explanation’s cursory for such a common and challenging problem. I’d say start with defining the problem and solution in more depth, giving Mailing Lists its own heading under Indirect mail flows with a clearly delineated problem and solution even at the risk of some redundancy. Otherwise, I think there will be a lot of busy people who will miss the indirect mail bit entirely and many who do read it won’t grok what exactly they’re supposed to do and why. Neil ___ dmarc mailing list dmarc@ietf.org https://www.ietf.org/mailman/listinfo/dmarc
