Sender Policy Framework or SPF validates the Vs. domain response of the SMTP server, from which the email originates.
This methodology to ensure that the email was actually sent by the server where the sender domain is configured.
The SPF settings are performed and managed by the Berkeley Internet Name Daemon (BIND) or other installed DNS service, which manages the domains and their addresses.
SPF configuration example:
v = spf1 to mx my_my_domain.com ip4: 9.110.8.1? all
SPF Official Website: link
DomainKeys Identified Mail or DKIM validates if the content of the email during your transport has not changed in your content or headers.
It also validates if e-mail attachments, if any, were not changed during transport from the sender server to the recipient server.
In the case of DKIM, a digital signature is included in all emails sent from the sending server.
This case, in the light of computer security, is extremely interesting due to the number of stakeholders used to check sent emails, from the MTA, OpenSSL, DNS.
Example of a DKIM:
DKIM-Signature: v = 1; a = rsa-sha256; d = my_domain.com; s = brisbane;
c = relaxed / simple; q = dns / txt; l = 1234; t = 1117574938; x = 1118006938;
h = from: to: subject: date: keywords: keywords;
bh = MTIzNDU2Nzg5MDEyMzQ1Njc4OTAxMjM0NTY3ODkwMTI =;
b = dzdVyOfAKCdLXdJOc9G2q8LoXSlEniSbav + yuU4zGeeruD00lszZ
VoG4ZHRNiYzR
DKIM Official Website: link