Migrate to Cloud

DKIM – the technology pioneered by Google is a major weapon against fighting spam. SPF is also another tool that helps us achieve the same goal. Here is the quick steps to enable both.

1.  SPF aka Sender Policy Framework  uses the DNS TXT field

Example:

dig agileblaze.com txt

;; ANSWER SECTION:
agileblaze.com. 300 IN TXT "v=spf1 ip4:52.205.101.12 ip4:52.202.71.86 include:_spf.google.com ~all"
agileblaze.com. 300 IN TXT "google-site-verification=C2mB_M1y9wd9wo8jMdzqSQt-nYUo_oJhlNs4H8rM5u4"
 

Tools to verify SPF

http://www.kitterman.com/spf/validate.html

Checking to see if there is a valid SPF record.

Found v=spf1 record for agileblaze.com:
v=spf1 ip4:52.205.101.12 ip4:52.202.71.86 include:_spf.google.com ~all

evaluating…
SPF record passed validation test with pySPF (Python SPF library)!

Domain Keys – DKIM

Domain keys also can be added in the TXT field. Unlike SPF, domain keys uses cryptography infrastructure. We will have to add the txt field in the following format

<selector>._domainkey.domain.TLD

In this example we are using the following,

agileblaze._domainkey.agileblaze.com

Generation of the the keys and Verification can be done with http://dkimcore.org/tools/

Once the keys are ready, just add them to the DNS records and forget SPAM!