On Wed, Jun 1, 2022 at 6:27 AM Alessandro Vesely <ves...@tana.it> wrote:
> > The point of domain level authentication, stressed by DMARC by requiring > alignment, is that hosting domains provide mail servers for both incoming > and > outgoing messages. The old habit of sending out mail through ISPs had to > be > abandoned. If Fastmail was contracted by Verisign to send mail for *.name > users, they could virtualize their service as well. > > DMARC makes no such request of anyone deploying DMARC to support use of their domain. I spent years working for SparkPost, and while we sent billions of messages on behalf of our customers, we most assuredly did not require that we accept any inbound mail for them, and a number of them deployed DMARC just fine. The act of DKIM-signing messages using a domain aligned with the domain in the visible From: header requires no hosting of inbound mail for that domain, but will result in a DMARC pass if the DKIM signature validates. Even in the cases where the Return-Path domain aligned with the From: domain, it was a subdomain of the From: domain (e.g., bounces.foo.com for Return-Path, foo.com for From) so that asynchronous bounces could be captured and suppressed. We never accepted mail for per...@foo.com, or roleacco...@foo.com. -- *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
