<div>
The main reason that DKIM is not generally used is this: &nbsp;If it was mandated and strictly implemented by these big players, it would result in denial of otherwise valid email emanating from improperly configured sites. &nbsp;If Yahoo, gmail or Microsoft did this then their user-base would go to some other email service provider.<br />
<br />
There are just too many little &quot;mom-and-pop&quot; sites out there with email configured just barely well enough to send outgoing messages.<br />
<br />
The flip side of this is that if the big players mandated and required DKIM, it would become a worldwide standard right quick. &nbsp;But the up-front cost in lost email and lost customers would be very, very high and a customer who leaves in anger is unlikely to return.<br />
<br />
As time goes on this may change, but at this time (a) spam filtering is about good enough to handle most suspicious messages and (b) the price paid for requiring valid DKIM on all messages would be too high.
</div>


<div>
Understand, but if my DKIM is properly configured in DNS and all my outgoing mail is signed with private key, that can possible be misconfiguered on the receiving side?<br />
<br />
Thanks
</div>


<div>
When someone &quot;cookbooks&quot; a configuration from a not-necessarily-excellent example without understanding it, <u>any</u> software product can be misconfigured. &nbsp;And this is how many small sites are configured - by people who have never done this, will never do it again, and are cookbooking from an example.
</div>


<div>
Yes I understand what you are saying about the cookbooks and how no one know what they are doing...<br />
<br />
I am sure Microsoft, Google, and Yahoo have competent people to set up a DNS record and enable DKIM on their email server. The question is why aren't they doing it to protect themselves? All receiving mail server just have the burden of checking the DKIM, but that is their burden to check, they can't mess something up on their side as far as config as far as I know.....that's what I don't get,<br />
<br />
Thank you.
</div>


triphen

<div>
<div class="content wysiwyg-content">
Hello Experts,<br />
<br />
If DKIM is such a good thing to implement, why don't microsoft.com, google.com, or yahoo.com implement it?<br />
<br />
I see they all have SPF and DMARC, but not DKIM.<br />
<br />
Thank you
</div>
</div>


Hello Experts,

If DKIM is such a good thing to implement, why don't microsoft.com, google.com, or yahoo.com implement it?

I see they all have SPF and DMARC, but not DKIM.

Thank you

DKIM....should you use it?

email protection

Within Internet message handling services (MHS), a message transfer agent or mail transfer agent (MTA) or mail relay is software that transfers electronic mail messages from one computer to another using a client–server application architecture. A MTA implements both the client (sending) and server (receiving) portions of the Simple Mail Transfer Protocol (SMTP). The terms mail server, mail exchanger, and MX host may also refer to a computer performing the MTA function. The Domain Name System (DNS) associates a mail server to a domain with mail exchanger (MX) resource records containing the domain name of a host providing MTA services.