Security
servers to let it through, but to send a deliverability report to the sending domain.
• p=quarantine: if an email fails SPF and DKIM, it goes to spam and the domain owner is alerted.
• p=reject: if an email fails, recipient mail servers will reject it. Tis is the most secure policy.
The impact of DMARC on email deliverability Te importance of email deliverability can hardly be overstated. Beyond the messages you send within your email client, you probably use other platforms that send emails via your domain. It could be for marketing, billing, CRM, ticketing systems, etc. Quite simply, without a DMARC policy, you risk emails being sent
from these services not being delivered as they could be flagged and rejected.
Weak DMARC policies are putting businesses at risk A policy of p=none (where emails that fail SPF and DKIM still go through) will improve deliverability. However, more is needed to solve the bigger problem of security. Attackers can spoof domains, which means sending emails that
appear to be from that domain. It’s easy to do, making phishing attacks much more convincing. Tose emails may fail SPF or DKIM – but if your DMARC policy is p=none, they’ll get through anyway. Tis makes your domain (and the trust your contacts have in it)
an attack vector. Te reputational damage could be catastrophic if your domain is used in a successful phishing attack. Tis affects every business, including yours and those of all your clients.
Why you can’t go straight to p=reject Te most secure policy is p=reject – but you can’t go straight to it on
day one. Everything you use to send emails has to be recorded in your DNS. Otherwise, it will fail SPF, DKIM or both. And if your DMARC policy is p=reject, those legitimate emails won’t reach their recipients. Generally, the best practice is to begin at p=none and reach
p=reject as part of a managed process. This allows you to monitor email traffic and ensure you have all the correct records. However, manually doing so can be labour-intensive, especially if you’re managing multiple customer domains. But there’s a better way.
What’s the solution? If you’re providing a managed DMARC service to clients, you need something MSP-friendly to manage your customers’ policies efficiently and at scale. That’s why we partnered with Sendmarc, our DMARC
management vendor. Their platform streamlines the process of implementing DMARC policies, and they promise to get any domain to p=reject within 90 days. It does this through multiple integrations and automation that
eliminate most manual work. So, not only can you provide this vital layer of protection to your clients but also do it in a way that’s commercially viable for you.
An opportunity for the channel Your clients need DMARC, and Sendmarc offers an MSP- friendly way to provide it. If you’re not providing a managed DMARC service, you’re missing out on revenue. You’re missing an opportunity to add another string to your bow. You’re missing an essential layer of security from your stack. And you’re giving competitors a chance to take your place.
www.pcr-online.biz
July/August 2024 | 25
Page 1 |
Page 2 |
Page 3 |
Page 4 |
Page 5 |
Page 6 |
Page 7 |
Page 8 |
Page 9 |
Page 10 |
Page 11 |
Page 12 |
Page 13 |
Page 14 |
Page 15 |
Page 16 |
Page 17 |
Page 18 |
Page 19 |
Page 20 |
Page 21 |
Page 22 |
Page 23 |
Page 24 |
Page 25 |
Page 26 |
Page 27 |
Page 28 |
Page 29 |
Page 30 |
Page 31 |
Page 32 |
Page 33 |
Page 34 |
Page 35 |
Page 36 |
Page 37 |
Page 38 |
Page 39 |
Page 40 |
Page 41 |
Page 42 |
Page 43 |
Page 44 |
Page 45 |
Page 46 |
Page 47 |
Page 48 |
Page 49 |
Page 50 |
Page 51 |
Page 52
