Secure and Deliverable Email
The security concerns to consider when sending email include the server and software used for sending messages, domain records for publishing keys and IDs, encrypted channel between the mail client and the server, certificates for message signing and user behavior.
This section is a series of articles discussing various way to create a robust system for sending email. The objective is to improve email deliverability for my domains while making it more difficult for spammers to use my domains in forged email headers.
I test my mail setup using actual account on the three leading email providers.
Received-SPF: pass (google.com: domain of jj@example.com designates xx.xx.xx.xx as permitted sender)
Authentication-Results: mx.google.com; spf=pass (google.com: domain of jj@example.com designates xx.xx.xx.xx as permitted sender)
dkim=pass header.i=@example.com
Received-SPF: pass (domain of example.com designates xx.xx.xx.xx as permitted sender)
X-YMailISG: cRwf...
X-Originating-IP: [xx.xx.xx.xx]
Authentication-Results: mta1221.mail.sk1.yahoo.com from=example.com;
domainkeys=neutral (no sig); from=example.com;
dkim=pass (ok)
Authentication-Results: hotmail.com;
sender-id=pass (sender IP is xx.xx.xx.xx) header.from=jj@example.com;
dkim=pass header.d=example.com; x-hmca=pass X-SID-PRA: jj@example.com
X-SID-Result: Pass
X-DKIM-Result: Pass
X-AUTH-Result: PASS
X-Message-Status: n:n
Be the first to comment. Leave a comment