Custom SMTP enabled in Dashboard but Auth still uses Supabase built-in mailer #50125
Replies: 4 comments
|
That log line is the giveaway. mail_from = noreply@mail.app.supabase.io means the built-in mailer handled the send, so the auth server did not have your SMTP config loaded at send time even though the dashboard shows it saved. A few things worth testing, roughly in order of what usually fixes it:
Also confirm the test you run is password recovery itself, since that is the flow your log shows, and watch the auth log live while you trigger it. If it still emits mail.app.supabase.io after a clean re-entry, then your ticket is exactly right, give them the event timestamp and ask them to check the effective SMTP config on the auth server for your ref. They can see it directly. |
|
Hi @Amir-Mirzaei, |
|
You can check what Auth is actually running with, rather than what the dashboard shows: Look at
If the four fields do match what you saved, also check Authentication → Auth Hooks. With a Send Email hook enabled, SMTP is never used. On the earlier reply about a TLS fallback: there’s no evidence that Auth silently falls back to the built-in mailer when the TLS handshake fails. Toggling SMTP off and on to clear a cache probably won’t change anything. The config/auth output will tell you more. What do those four |
|
The log line mail_from = noreply@mail.app.supabase.io means the built-in sender handled that message, so the settings Auth is running with are not the ones the dashboard shows. Before anything else, read what is actually stored: call GET /v1/projects/{ref}/config/auth on the Management API with a personal access token and look at smtp_host, smtp_admin_email, smtp_user and smtp_port. If they are empty or different from what you saved, something wrote the project config after you did. The usual one is a deploy or CI step that runs supabase config push, which replaces the project's settings with your local supabase/config.toml, so put the SMTP block in that file too. If the four fields match what you saved, check Authentication, Auth Hooks next, because an enabled Send Email hook means SMTP is not used. https://supabase.com/docs/reference/cli/supabase-config-push After the right sender shows in the log, check it the way a new customer would: VibeFix, which I'm building, signs up to your live app with a real inbox and tells you if a stranger gets through. Free check: https://vibe-fixer.com/?src=gh-50125 |
Uh oh!
There was an error while loading. Please reload this page.
Hi, I’m having an issue with Custom SMTP on Supabase Auth.
Project ref:
onaqqlmlfntwxgfudgjr
Custom SMTP is enabled in Authentication → Emails with:
Resend side is working correctly:
So Resend/DNS are confirmed working.
However, Supabase Auth still sends password recovery emails using the built-in mailer.
Auth log shows:
event = mail.send
mail_from = noreply@mail.app.supabase.io
mail_type = recovery
This is after re-saving Custom SMTP multiple times and refreshing the dashboard.
So the issue seems to be that the hosted Auth backend is not applying the saved Custom SMTP configuration.
Has anyone seen this before?
Is there a way to verify the effective server-side Auth SMTP config, or force a reload/reapply of the Custom SMTP settings?
I already opened Supabase ticket:
SU-466814
All reactions