{
  "id": 9819637,
  "title": "Mail Going to Spam After SPF DKIM DMARC Setup with Node.js Alignment Debugging",
  "url": "https://urgent.news/2026/09/25/mail-going-to-spam-after-spf-dkim-dmarc-setup-with-node-js-alignment",
  "topic": "tech",
  "section": "Tech",
  "published": "2026-09-25T19:41:42.000Z",
  "source": {
    "name": "Dev.to",
    "slug": "dev-to",
    "url": "https://dev.to/calderhayes9638/mail-going-to-spam-after-spf-dkim-dmarc-setup-with-nodejs-alignment-debugging-1e41"
  },
  "original_language": "en",
  "account": null,
  "summary": "This brief discusses the issue of mail going to spam despite having SPF, DKIM, and DMARC set up correctly with Node.js. The key takeaway is that the alignment between the visible \"From\" domain and the authenticated identity (either SPF or DKIM) is crucial. Even if all authentication mechanisms return green, if there is a misalignment, the message will still be flagged as spam. The article emphasizes the importance of debugging the receiver's evidence chain by capturing the SMTP result, comparing the \"From\" address with the SPF and DKIM domains, and correlating the decision with reputation and content signals. It also suggests treating delivery evidence as a reconciliation record, storing it in a persistent storage system like Postgres or an append-only log, and using a stable message identifier to join the send request and receiver's verdict. The article provides a sample Go code snippet for implementing alignment checks.",
  "key_points": [],
  "editors_take": null,
  "illustration": null,
  "coverage": {
    "outlets": 1,
    "also_reported_by": []
  },
  "ai_generated": true,
  "disclaimer": "Summaries, key points and the editor’s take are written by software from other outlets’ reporting and may contain errors — always check the linked original."
}