Supabase Auth Emails Going to Spam: SMTP Fix
Supabase auth emails going to spam? Route them through Google Workspace with custom SMTP plus SPF, DKIM, and DMARC — the exact setup that restores inbox delivery.
<!-- BRIEF SPEC (not published): Variant: PROBLEM-SOLVER | Hook: DIRECT-ANSWER | FAQ: 4 | Cover: BLUEPRINT (deep blueprint-blue, white grid, technical line-art of envelope + DNS records schematic) In-body images: (1) Screenshot-style mock of Supabase dashboard Project Settings -> Auth -> SMTP panel with fields filled. (2) Diagram of the SPF/DKIM/DMARC check flow: your domain -> Google SMTP -> Gmail inbox with three green checks. SERP structure notes (structure only): top results are GitHub README checklists and repo runbooks — config-value heavy, no narrative guide with before/after DNS blocks or a verification pass. Gap we exploit: end-to-end Workspace walkthrough with verify-it-worked steps and the app-password gotcha. Verified versions: n/a (dashboard + DNS config; no SDK code). SMTP values per community-verified GitHub discussion #5320. --> Last updated: 2026-10-10 Yes — you fix it by sending through your own mail server. Point Supabase Auth at Google Workspace with custom SMTP, add SPF, DKIM, and DMARC records for your domain, and send from an address like noreply@yourdomain.com instead of Supabase's shared mailer. That combination restores inbox delivery for signup confirmations, magic links, and password resets. Below is the exact setup: the Workspace sender, the three DNS records that prove you're legitimate, the Supabase SMTP settings, and a verification pass that confirms it worked. What the problem looks like Signup confirmations and password resets land in spam — or never arrive at all The Supabase dashboard shows the email as "sent," but Gmail or Outlook junk it silently The built-in mailer is rate-limited to roughly 3 emails per hour and, before custom SMTP is configured, only delivers to team members Your emails arrive from…