{"id":5910,"date":"2021-03-15T11:38:49","date_gmt":"2021-03-15T11:38:49","guid":{"rendered":"https:\/\/www.threesl.com\/blog\/?p=5910"},"modified":"2023-02-16T14:34:46","modified_gmt":"2023-02-16T14:34:46","slug":"e-mail-verification","status":"publish","type":"post","link":"https:\/\/www.threesl.com\/blog\/e-mail-verification\/","title":{"rendered":"E-Mail Verification"},"content":{"rendered":"

3SL E-Mail Policies<\/h2>\n
\"Keboard
E-Mail<\/figcaption><\/figure>\n

We’ve changed our mail server slightly. Improving the e-mail verification between ourselves and mail recipients.<\/p>\n

Sender Policy Framework (SPF<\/a>), Domain Keys Identified Mail (DKIM<\/a>), and Domain-based Message Authentication, Reporting and Conformance<\/span><\/span> (DMARC<\/a>)\u00a0 have been around for a while. Here at 3SL, we’ve implemented them on our mail server.<\/p>\n

Technologies<\/h3>\n

SPF defines which addresses are permitted to send 3SL email.\u00a0 DKIM adds a Public Key Infrastructure (PKI<\/a>) signature. This verifies and authenticates email as coming from 3SL, showing its not been modified in transit, or faked. DMARC combines SPF and DKIM to authenticate the emails and reports any emails which do not conform.<\/p>\n

E-Mail Verification Result<\/h3>\n

What this means is that all emails claiming to be from 3SL should only be coming from our mail server mail.threesl.com<\/strong>.\u00a0\u00a0 This should help stop the occasional 3SL email from ending up filtered off as spam. It should also help identify fake 3SL emails as being unsolicited emails.<\/p>\n