Maaz Zindani

Loading the index…

↑↓ move↵ openesc close4072 pages
Node.js, PHP and APIs

Supabase auth emails fail: Email address not authorized, or sign-up emails stop

ErrorEmail address not authorized

Short answer

Supabase's built-in mail service only sends to members of your project's team, and only 2 messages an hour. Any other address fails with Email address not authorized. Turn on custom SMTP with a sender address, and raise the auth email rate limit, which starts at 30 an hour.

  • Applies to Supabase Auth, custom SMTP on port 587
  • Updated
  • By Maaz Zindani, Senior Software Engineer

Fix it fast

  1. 1Find out which cause you have

    Open Authentication settings for the project and see whether custom SMTP is enabled. If it is off, you are on the built-in service.

    echo 'Dashboard > Authentication > SMTP Settings (supabase.com/dashboard/project/_/auth/smtp)'
  2. 2Match what you see, then jump to its fix

    1. 1Email address not authorized for every address that is not on your organization's team.The project still uses the built-in SMTP serviceFix
    2. 2Mails work for the first few users and then stop for the rest of the hour.The email rate limit is reachedFix

What does the error look like?

  • Email address not authorized

Cause 1 of 2

The project still uses the built-in SMTP service

1Check

The built-in service sends only to pre-authorized addresses, meaning members of the project's organization team, with no delivery guarantee.

echo 'Check that SMTP Settings shows Enable custom SMTP as off'

2Fix

Enable custom SMTP and give it the host, port, user, password and a default sender address (for example no-reply@yourdomain.com).

{
  "external_email_enabled": true,
  "smtp_host": "smtp.example.com",
  "smtp_port": "587",
  "smtp_user": "<user>",
  "smtp_pass": "<password>",
  "smtp_admin_email": "no-reply@example.com",
  "smtp_sender_name": "My App"
}

3Verify

Sign up with an address outside the team; the message is delivered.

echo 'Create a test user from the app with a non-team address and check the inbox'

Confirmed by supabase.com

Did this fix it?

Cause 2 of 2

The email rate limit is reached

1Check

The built-in service allows 2 messages an hour. With custom SMTP the default is 30 messages an hour.

echo 'Dashboard > Authentication > Rate Limits (supabase.com/dashboard/project/_/auth/rate-limits)'

2Fix

Raise the email limit on the Rate Limits page to what your traffic needs. Add CAPTCHA protection so bots do not use it up.

echo 'Set the email rate limit on the Rate Limits page and enable CAPTCHA'

3Verify

A burst of test sign-ups all produce emails.

echo 'Run several sign-ups with test addresses and check delivery'

Confirmed by supabase.com

Did this fix it?

How do I stop it coming back?

  • Set up SPF, DKIM and DMARC with your email provider so auth mail does not land in spam.
  • Use a custom domain and keep auth mail on a different sender address from marketing mail.
  • Keep a backup SMTP provider ready.

Sources

How was this page made?

I drafted this page with AI assistance from the official documents listed under Sources. Every cause above names the document that confirms it. I have not reproduced this fix on a machine of my own yet, so read it as documented guidance, not a test report. Found a mistake? Tell me.

Related fixes

Back end

ng serve says it cannot determine the project or target

Cannot determine project for command.

The Angular CLI looked through angular.json for a project that defines the target you asked for (serve, build, test) and found none, or found several and could not pick one.

3 causes, each with a fix

Back end

ng serve cannot find the dev-server builder package

Could not find the implementation for builder @angular/build:dev-server

The builder named in angular.json (for example @angular-devkit/build-angular:dev-server) is looked up as an npm package starting from the workspace root.

3 causes, each with a fix

Next step

Want this handled for good?

I look after servers, apps and releases end to end. Tell me what keeps breaking.