---
title: "Supabase 'Email address not authorized': why and how to fix it"
description: "Supabase's built-in mailer only sends to members of your organization. Why signup and magic link fail with 'Email address not authorized', and the fix."
updated: 2026-11-21
---

# Supabase "Email address not authorized"

Signup, magic link or password reset works for you, but fails for everyone else with:

```
Email address not authorized
```

## Why

Since **26 September 2024** the built-in email service of Supabase Auth sends **only to members of your organization's team**. Every other address fails with `Email address not authorized`. It also sends at most **2 emails per hour**. It is meant for trying Supabase out, not for real users. Sources: [Supabase: custom SMTP](https://supabase.com/docs/guides/auth/auth-smtp), [announcement](https://github.com/orgs/supabase/discussions/29370).

So the error does not mean something is wrong with the address. It means the project has no custom SMTP yet.

## Fix

### For testing only: add the address to your team

*Organization settings → Team → Invite*. The invited address can now receive auth emails from the built-in mailer. This does not scale past a few testers.

### For real users: set up custom SMTP

1. Pick an email provider and **verify your domain** there (SPF and DKIM DNS records).
2. Dashboard: *Authentication → Emails → SMTP Settings*, enable custom SMTP, and enter host, port (**465** or **587**), SMTP username and password, a sender address on the verified domain, and a sender name.
3. *Authentication → Rate Limits*: after you enable custom SMTP the email limit starts at **30 per hour**. Raise it to what your provider allows.
4. Send yourself a magic link from *Authentication → Users* to confirm.

The same through the Management API:

```bash
curl -X PATCH "https://api.supabase.com/v1/projects/$PROJECT_REF/config/auth" \
  -H "Authorization: Bearer $SUPABASE_ACCESS_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "external_email_enabled": true,
    "smtp_host": "smtp.example.com",
    "smtp_port": "465",
    "smtp_user": "your-smtp-user",
    "smtp_pass": "your-smtp-password",
    "smtp_admin_email": "no-reply@yourapp.com",
    "smtp_sender_name": "Your App",
    "rate_limit_email_sent": 300
  }'
```

### During development: catch emails locally

`supabase start` includes a local mail catcher (Mailpit, previously Inbucket). Every auth email to any address shows up in the browser, with no team restriction and no limits.

## Which provider?

| Provider | Free tier | Notes |
|---|---|---|
| Resend | 3,000 / month, 100 / day | SMTP and API, official Supabase integration |
| Amazon SES | none since 07.2026, about $0.10 per 1,000 | cheapest at volume; sandbox until production access is approved |
| Brevo | 300 / day | EU company, SMTP and API |
| Fanfarly (early access) | 3,000 / month, 100 / day | `npx fanfarly supabase` sets SMTP, the rate limit and auth templates in one step; not available yet |

Disclosure: Fanfarly is built by the author of this page.

## Related

- [over_email_send_rate_limit (email rate limit exceeded)](/errors/over-email-send-rate-limit/)
- [Error sending confirmation email (500)](/errors/error-sending-confirmation-email/)
