Ran into the same thing in production, so a few things that helped me while waiting for something built in: 1. Move off the default sender. As far as I know the built-in email service is heavily rate limited and only meant for testing, so set up custom SMTP (SES, Resend, Postmark etc.) so your limits and delivery are in your hands. 2. Don't make the UI depend on one email arriving. Show a "Resend email" button with a cooldown (30-60s) and a clear "check spam / wrong address?" hint, and log delivery failures yourself so you at least get a signal. This is basically a manual version of the resend flow you're proposing. 3. Stop bad addresses before they reach the sender. Typos, disposable domains and addresses with no mail server all bounce, and with SES a hard bounce rate of 5% puts the account under review, with sending possibly paused at 10% (AWS docs: https://docs.aws.amazon.com/ses/latest/dg/reputationdashboardmessages.html). Checking the address first, before triggering the confirmation email, keeps the bounce rate down and cuts down on retries. 4. Ideally the check fails open: if the check service is slow or down, let the signup continue rather than blocking it. Disclosure: I build SentriSend (sentrisend.com), a small pre-flight check API aimed at exactly #3 and #4 for Supabase Auth hooks, so I'm biased. Happy to share what I learned about the hook setup if it's useful, whether or not you use it.
Hi @zoelivvy, We experienced this exact discrepancy between signup confirmations and password resets on our Supabase projects. Because password resets work over the same SMTP credentials, your Resend connection is fine. What usually causes GoTrue to silently drop only signup confirmation emails without contacting Resend comes down to two hidden guards: The Redirect URL / SITE_URL Guard (Most Common): GoTrue validates the redirect URL before dispatching signup emails. If your SITE_URL or emailRedirectTo in signUp() does not strictly match the allowed list in Authentication -> URL Configuration -> Redirect URLs (including protocol, trailing slashes, or wildcards), GoTrue quietly aborts the email dispatch to prevent open-redirect vulnerabilities, while still returning a 200 status. User Enumeration Protection: If the test email already exists in auth.users (even as unconfirmed or soft-deleted), GoTrue returns success to the client but silently drops the dispatch. Try testing with a brand-new unique alias (e.g. test+123@yourdomain.com). If you need visibility into GoTrue's internal drops, check Logs -> Auth Logs in Supabase and filter for level:error or metadata containing mail_type:signup. Because of these silent drops and the lack of delivery telemetry in hosted GoTrue, we actually built and open-sourced SentriSend ([https://github.com/sentrisend/sentrisend](https://www.google.com/url?sa=E&q=https%3A%2F%2Fgithub.com%2Fsentrisend%2Fsentrisend) / [https://sentrisend.com](https://www.google.com/url?sa=E&q=https%3A%2F%2Fsentrisend.com)). It acts as an outbound gateway between Supabase and Resend, providing live audit logs, transparent provider errors, and HMAC-SHA-256 compliance proofs so you never have to wonder if or why an auth email was dropped. Hope the redirect URL check helps solve the signup drop!
Hi @amir-mirzaei, We ran into this exact issue across our Supabase projects. What's happening behind the scenes is that Supabase Auth (GoTrue) caches the SMTP settings in memory. If the initial TLS handshake to smtp.resend.com:587 fails or times out, GoTrue silently falls back to the default internal mailer (noreply@mail.app.supabase.io) to prevent the password recovery flow from completely crashing—without surfacing the underlying error in the dashboard. A few things that usually fix the silent fallback: Force cache reload: Toggle Custom SMTP OFF -> click Save -> wait 60 seconds -> toggle ON -> re-paste the Resend API key -> click Save. Sender Format: Ensure the Sender field is strictly matching the verified domain in Resend without trailing spaces. The Restart: If it persists, pausing and resuming the Supabase project in Project Settings forces the GoTrue container to restart and reload the SMTP environment variables. If you keep fighting hosted SMTP quirks and want guaranteed visibility, we actually open-sourced a lightweight gateway called SentriSend ([https://github.com/sentrisend/sentrisend](https://www.google.com/url?sa=E&q=https%3A%2F%2Fgithub.com%2Fsentrisend%2Fsentrisend) / [https://sentrisend.com](https://www.google.com/url?sa=E&q=https%3A%2F%2Fsentrisend.com)) that sits between Supabase and Resend. It provides live audit feeds of every delivery, automatic rate-limit retries, and pre-flight protection so you never have to guess what happened to an outbound auth email. Hope the toggle refresh gets it working for you!