<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>ttul</author><text>The interesting technology these days is not DKIM but rather DMARC. DKIM allows you to sign messages so that others know that the message originated from the owner of the domain. DMARC allows you to express what you want receivers to do when someone is spoofing your domain.&lt;p&gt;If you operate your own domain and you are worried about spoofing, implementing DMARC will put a stop to it with all the major email receivers (Gmail, Yahoo!, Microsoft, etc.), since they all respect DMARC.&lt;p&gt;But the really cool thing about DMARC is that it lets you receive feedback reports from email receivers with copies of these spoofed messages along with aggregate statistics showing you where spoofed email is originating.</text><parent_chain></parent_chain></comment><story><title>DKIM Demystified</title><url>https://www.20i.com/blog/dkim-demystified/</url></story>
<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>yrro</author><text>Whenever I send mail to a Debian mailing list, I receive notifications of DKIM policy violations. I&amp;#x27;ve never figured out whether the problem is on my side or theirs...&lt;p&gt;[edit] having done a bit more research, I think the problem lies with the BTS: &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;bugs.debian.org&amp;#x2F;cgi-bin&amp;#x2F;bugreport.cgi?bug=754809&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;bugs.debian.org&amp;#x2F;cgi-bin&amp;#x2F;bugreport.cgi?bug=754809&lt;/a&gt;</text><parent_chain></parent_chain></comment><story><title>DKIM Demystified</title><url>https://www.20i.com/blog/dkim-demystified/</url></story>