Difference between revisions of "DKIM"
Jump to navigation
Jump to search
(drafting) |
|||
| Line 1: | Line 1: | ||
| + | You can help prevent spoofing by adding a digital signature to outgoing message headers using the DKIM standard. This involves using a private domain key to encrypt your domain's outgoing mail headers, and adding a public version of the key to the domain's DNS records. Recipient servers can then retrieve the public key to decrypt incoming headers and verify that the message really comes from your domain and hasn't been changed along the way. | ||
| + | |||
| + | Google Apps' digital signature conforms to the DomainKeys Identified Mail (DKIM) standard. | ||
== Email authentication == | == Email authentication == | ||
Revision as of 15:50, 14 February 2016
You can help prevent spoofing by adding a digital signature to outgoing message headers using the DKIM standard. This involves using a private domain key to encrypt your domain's outgoing mail headers, and adding a public version of the key to the domain's DNS records. Recipient servers can then retrieve the public key to decrypt incoming headers and verify that the message really comes from your domain and hasn't been changed along the way.
Google Apps' digital signature conforms to the DomainKeys Identified Mail (DKIM) standard.
Email authentication[edit | edit source]
- If a message was correctly DKIM signed, a 'signed-by' header with the sending domain will appear.
- If a message was SPF authenticated, a 'mailed-by' header with the domain name will appear.
- If no authentication information exists, there will be no signed-by or mailed-by headers.
If you're a sending domain[edit | edit source]
