<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">
On 26 Apr 2017, at 11:31 AM, Adam Brenner <<a href="mailto:adam@solidnetwork.org" class="">adam@solidnetwork.org</a>> wrote:<br class="">
<div>
<blockquote type="cite" class=""><br class="Apple-interchange-newline">
<div class=""><span style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; display: inline !important;" class="">Sorry
for the spam if you got this message twice, but I suspect that ARIN's mailing list is not properly setup to handle domains that have DMARC records setup.</span><br style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class="">
</div>
</blockquote>
<div><br class="">
</div>
Adam - </div>
<div><br class="">
</div>
<div> Actually, it is not at all clear if it is presently possible to operate a mailing list in a </div>
<div> manner which meets both existing community expectations for mailing list behavior </div>
<div> _and_ also aligns with DMARC's expectations regarding header/sender alignment.</div>
<div> </div>
<div> As result, there is an abundance of discussion currently going on this very topic (e.g. </div>
<div> when certain large email providers began to reject based on DMARC settings), as </div>
<div> well as an Internet-wide scramble to update to mailing list management software to</div>
<div> allow for selection of a variety of new settings for message munging [all suboptimal</div>
<div> in one manner or another] entirely to work around the interoperability issues with </div>
<div> DMARC that are well-detailed in RFC 7960.</div>
<div>
<div class=""><br style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class="">
</div>
<blockquote type="cite" class="">
<div class=""><span style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; display: inline !important;" class="">I
had to disable DMARC on my entire domain to get this message posted.</span><br style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class="">
</div>
</blockquote>
<div><br class="">
</div>
Indeed - telling all receiving mail transfer agents (MTA’s) not to accept email that </div>
<div> is purportedly from your domain but coming from a different MTA, and then using </div>
<div> mailing lists that do exactly this behavior is likely to result in some issues for the </div>
<div> rather obvious reasons...</div>
<div><br class="">
</div>
<div>
<blockquote type="cite" class="">
<div class=""><span style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; display: inline !important;" class="">@John:
this should _probably_ be fixed if you want to solicit feedback from the community. :-)</span><br style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class="">
<br style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class="">
<a href="https://wiki.list.org/DEV/DMARC" style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px;" class="">https://wiki.list.org/DEV/DMARC</a><br style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class="">
<blockquote type="cite" style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px;" class="">
The DMARC authors essentially acknowledge that adopting DMARC<br class="">
requires changing mailing list habits. You cannot continue to<br class="">
run your mailing list the way you always have, in DMARC<br class="">
compatible way.</blockquote>
</div>
</blockquote>
<br class="">
</div>
<div> <chuckle> How nice. </div>
<div><br class="">
</div>
<div> The Internet has reminded the DMARC community that one must "Be liberal in what </div>
<div> you accept, and conservative in what you send”, or your solution will not be robust… </div>
<div> (the very definition of the present state of DMARC operations in the Internet today)</div>
<div><br class="">
</div>
<div> However, in regards to your specific suggestion – we are researching using DMARC </div>
<div> on ARIN’s mailing lists, and will develop a plan that attempts to accommodate it with</div>
<div> a minimum of impact to participants in the ARIN community. It is quite possible that</div>
<div> will require an additional consultation with community on this very mailing list, so you</div>
<div> might want to keep that DMARC setting turned off for a while if you wish to participate. </div>
<div><br class="">
</div>
<div>Thank you,</div>
<div>/John</div>
<div><br class="">
</div>
<div>John Curran</div>
<div>President and CEO</div>
<div>American Registry for Internet Numbers (ARIN)</div>
<div><br class="">
</div>
<div><br class="">
</div>
<div><br class="">
</div>
<div><br class="">
</div>
<div> </div>
<div><br class="">
</div>
<div><br class="">
</div>
<div><br class="">
</div>
<div><br class="">
</div>
</body>
</html>