Kajabi began requiring Strict DMARC on every custom email domain on February 9, 2026 — miss the April 30, 2026 deadline and your custom domain gets disabled, dropping you back to Kajabi's shared sending pool.
Kajabi now requires Strict DMARC on every custom email domain — a change that took effect February 9, 2026. If Kajabi manages your DNS, this was applied automatically: your sending address now includes a kjbm subdomain (for example you@kjbm.yourdomain.com) and no action is needed. If you manage your own DNS, go to Settings → Marketing Settings → Email Settings, click Enable Strict DMARC to get your record, add it at your DNS provider, then return to confirm propagation — your domain must include the kjbm subdomain either way. Miss the April 30, 2026 deadline and Kajabi disables your custom email domain: you can still send, but from a shared address like you@x.kajabimail.net instead of your own domain. Source: help.kajabi.com · verified 2026-07-17
p=none and a rua address, watch reports for a week, confirm this sender shows 100% pass.No. Adding SPF includes and DKIM records only adds authentication — it never blocks existing mail. The only risky step is tightening your DMARC policy, and that comes later, after reports confirm everything passes.
Send yourself a test email and inspect the headers for spf=pass, dkim=pass and dmarc=pass — or just watch your DMARCKeeper dashboard: the sender's pass rate should hit 100% within a day or two.
Yes. SPF and DKIM authenticate mail; DMARC is what tells receivers to BLOCK mail that fails, and it's the piece Gmail, Yahoo and Outlook now check for explicitly.