Repository navigation
In the config.toml file (local), if both [local_smtp] and [auth.email.smtp] have enabled = true, then [auth.email.smtp] wins during development. #7085
Description
Activity
- changed the title
[-]In the `config.toml` file (local), if both `[local_smtp]` and `[auth.email.smtp]` have `enabled = true`, then `[auth.email.smtp]` wins[/-][+]In the `config.toml` file (local), if both `[local_smtp]` and `[auth.email.smtp]` have `enabled = true`, then `[auth.email.smtp]` wins during development.[/+]on Oct 2, 2026 Hey @curiosissimoz, I would like to work on this one. Can you assign this to me
@akshat-lakhera I don't have admin permissions to assign issues.
I am new to this org can you tell me whom to mention @curiosissimoz
Describe the bug
In the
config.tomlfile (local), if both[local_smtp]and[auth.email.smtp]haveenabled = true, then[auth.email.smtp]wins during development.To Reproduce
Set up this in your
config.tomlfile:Notice that setting up a google smtp takes additional care (https://github.com/orgs/supabase/discussions/19646), but I think you can use any SMTP you want.
Expected behavior
[local_smtp]should win over[auth.email.smtp]during development, i.e. the fake SMTP should be used and not the real one. Toggling off[auth.email.smtp]during development and toggling it on before runningsupabase config pushfor production is annoying.