KamoCRM

The SPF card had no proxy route, so it never reached the API

Fixkamo-internal
Shipped
4 செப்டம்பர், 2026 அன்று 5:56 PM UTC
Author
kamo
Commit
c2dd2c6

The card shipped calling /api/security/domains/{id}/spf, and every request 404'd at Next.js before SecurityService ever saw it — which the card reported as "We couldn't read your domain's email settings", the same message it shows for a genuine DNS failure, so it looked like a lookup problem rather than a missing route. There is no catch-all under /api/security/domains/{id}/: verify-dns, ssl and aliases each have their own route file, and I added the endpoint without adding the fourth. This mirrors verify-dns exactly.

All changes

Like what you see shipping?

All of it arrives in your workspace on its own. Start on the free plan and read this page again in a month.

Start Free ForeverView Pricing