Front page | perl.perl5.porters |
Postings from November 2013
--001a11c33fd0b3d50104ebe35986 Content-Type: text/plain; charset=ISO-8859-1 DMARC compliance requires us to make some changes to how we send out and sign mailing list messages. There are some pretty significant implications regarding reputation and spam, so this isn't going to happen overnight. While we work on it, I encourage people who send from domains with strict DMARC enforcement enabled to use a different address. (And if the encouragement doesn't work, we'll just blacklist those domains.) If anyone is an expert on DKIM and DMARC, and is willing to consult or otherwise help to make sure we don't cause ourselves bigger problems as we become compliant, please drop me an email off-list. -R --001a11c33fd0b3d50104ebe35986 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable <div dir=3D"ltr"><br>DMARC compliance requires us to make some changes to h= ow we send out and sign mailing list messages. =A0There are some pretty sig= nificant implications regarding reputation and spam, so this isn't goin= g to happen overnight. =A0While we work on it, I encourage people who send = from domains with strict DMARC enforcement enabled to use a different addre= ss. =A0(And if the encouragement doesn't work, we'll just blacklist= those domains.)<div> <br></div><div>If anyone is an expert on DKIM and DMARC, and is willing to = consult or otherwise help to make sure we don't cause ourselves bigger = problems as we become compliant, please drop me an email off-list.</div> <div><br></div><div>-R<br><div><br></div><div><br></div></div></div> --001a11c33fd0b3d50104ebe35986--Thread Previous | Thread Next