Supabase "Error sending confirmation email" (and "email rate limit exceeded"): How to Fix It
Supabase "Error sending confirmation email" usually means the built-in email sender hit its limits or your SMTP settings are wrong. Causes and fixes.
Supabase shows "Error sending confirmation email" when its login system (Supabase Auth) tried to send the sign-up email and the email service didn't accept it. On a new project the usual reason is the built-in email service: it's for testing only, sends just a couple of emails an hour, and only to people on your Supabase team. The real fix is to connect your own email service (Resend, Postmark, Amazon SES and similar) under custom SMTP. If you already did that, the cause is almost always a typo in those settings or a sender address your email service hasn't approved.
Checked against Supabase's docs on custom SMTP, Auth rate limits, Auth error codes and its troubleshooting guides, plus the Supabase Auth source code and Resend's Supabase guide, in November 2026.
You'll usually see one of these in your app, or in your browser's developer console when someone signs up:
AuthApiError: Error sending confirmation email
AuthApiError: email rate limit exceeded
The first is a server error (HTTP 500). The second is a "too many requests" error (HTTP 429, error code over_email_send_rate_limit). The same problems also show up as "Error sending recovery email" on password resets, and "Error sending magic link email" for magic links.
This guide assumes you can open the project in the Supabase dashboard. If you built the app in Lovable, Bolt or a similar tool and connected your own Supabase project, that's where these settings live.
Why it happens on new projects
Every Supabase project comes with a built-in email sender so you can try things out. Supabase's SMTP guide says plainly that it "is not meant for production use", and lists its limits:
| Limit on the built-in sender | What it means for you |
|---|---|
| Only sends to your team | Emails only go to addresses that are members of your Supabase organisation. Anyone else gets an "Email address not authorized" error |
| About 2 emails per hour | The current limit for the whole project. Supabase says it "can change without notice" |
| No guarantee | No promise that emails arrive, or that the service is up |
So a few test sign-ups in a row will trigger "email rate limit exceeded", and a real user signing up with their own address will never get the email. Nothing is wrong with your app. The built-in sender was never meant to handle real users.
One more test-time trap: Supabase rejects example and test domains, so signing up as test@example.com fails with an "email address invalid" error. Use a real inbox you control.
The fix: connect your own email service
You need an account with a transactional email service. These are the ones Supabase lists as working: Resend, Amazon SES, Postmark, Twilio SendGrid, ZeptoMail and Brevo. If you're unsure which, Resend vs SendGrid vs Postmark: Which Email API for Your App? compares the common ones.
1. Set up your sending domain with the email service
Every one of these services makes you prove you own the domain you send from. They give you a few DNS records (SPF, DKIM and usually DMARC) to add where your domain is managed. Until the domain is verified, the service refuses your emails, and Supabase reports that as "Error sending confirmation email". How to Send Email From Your App Without Landing in Spam explains what each record does.
Supabase also recommends a separate subdomain for login emails, such as auth.yourapp.com, so a marketing campaign that annoys people can't hurt the emails your users need to log in.
2. Copy the SMTP details into Supabase
In the Supabase dashboard, open Authentication, find the email settings, and open SMTP Settings. Turn on custom SMTP and fill in:
- Sender email: an address on your verified domain, such as
no-reply@auth.yourapp.com - Sender name: your app's name
- Host, Port, Username, Password: from your email service
For example, Resend's Supabase guide gives host smtp.resend.com, port 465, username resend, and your Resend API key as the password. Other services have their own values on their SMTP settings page.
3. Raise the email rate limit
Once custom SMTP is on, Supabase sends to anyone, but starts you at a deliberately low limit: "a low rate-limit of 30 messages per hour is imposed" to protect your new sender's reputation. If you expect more sign-ups than that, go to Authentication > Rate Limits and raise the email limit to something that matches your traffic and what your email service allows.
4. Test with a real address
Sign up with an email address outside your team. If the email arrives, you're done.
Still getting "Error sending confirmation email"?
Then Supabase reached your email service and something went wrong in between. Supabase's own advice is to start with the logs: in the dashboard, open Logs and choose the Auth logs, and look at the entry from the failed sign-up. Its 500 error troubleshooting guide says log messages mentioning gomail mean Auth is struggling to talk to your email service, and that the usual reasons are a domain not set up correctly with the provider, the wrong port, the provider rate-limiting you, or the provider being down.
Work through these in order:
- Sender address. It must be on the domain you verified with the email service.
you@gmail.comas the sender won't work. - Credentials. Re-paste the username and password. Many services want an SMTP password or API key here, not your account login password.
- Host and port. Use the bare host name (
smtp.resend.com, nothttps://...) and the port your service lists, usually 465 or 587. - Your email service's own logs. Once Supabase hands the email over, Supabase can't see what happens next. The service's dashboard shows whether it rejected, bounced or suppressed the message. A suppression list (addresses that bounced before) is a common reason one particular user never gets anything.
- The email template. The troubleshooting guide notes that broken templates (an unclosed tag or variable) can also cause these errors. If you edited the confirmation template, paste back a simple version and test again.
Still getting "email rate limit exceeded"?
- On the built-in sender: you hit the project-wide limit of about 2 per hour. Wait, or set up custom SMTP.
- On custom SMTP: you hit the limit in Authentication > Rate Limits. Raise it.
- "For security purposes, you can only request this after 37 seconds." This is a separate, per-user limit: by default Supabase waits 60 seconds before sending the same person another confirmation or reset email. Show a countdown on the "resend email" button instead of letting people click it repeatedly.
If your limits keep running out and you don't recognise the sign-ups, bots may be creating accounts. Supabase suggests turning on CAPTCHA protection, and says: "Do not disable email confirmations under pressure."
The email arrives, but the link is wrong
Two common follow-on problems:
- The link opens
localhost:3000. Go to Authentication > URL Configuration and change the Site URL to your live address. Add any other addresses your app uses (such as preview URLs) to Redirect URLs. Supabase's docs call the Site URL "critical for email confirmations and password resets." - The link says it has expired or is invalid as soon as it's clicked. Supabase's production checklist warns that some email services' link tracking can "overwrite or deform" confirmation links, and recommends turning link tracking off in your email service. Company email scanners that open links before the user does can also use up the one-time link.
Can I just turn email confirmation off?
Supabase lets you switch off Confirm email under the Email provider settings, and people do this to get unblocked. It's fine for a private test project. For a live app it means anyone can sign up with someone else's email address, so treat it as temporary and set up custom SMTP instead. Password Reset and Email Verification Flows Done Right explains why verification matters.
If you're moving a builder app onto a real domain, custom SMTP is one of the items on the list in How to Deploy a Lovable App to Production. EasySpawn hosts the app itself with a database, SSL and your own domain, but your login emails still go through whichever email service you connect, so this setup is needed either way. EasySpawn is pre-launch; join the waitlist if you want to try it.
Related: What Is Supabase? A Beginner's Guide to the Backend Behind Many AI-Built Apps · Resend vs SendGrid vs Postmark: Which Email API for Your App? · Password Reset and Email Verification Flows Done Right · How to Send Email From Your App Without Landing in Spam
Keep reading
"new row violates row-level security policy" in Supabase: How to Fix It
Supabase (Postgres) blocked an insert or update because no RLS policy allows it. Why it happens, how to write an INSERT policy with WITH CHECK, the user_id default trick, the hidden SELECT-after-insert problem, storage uploads, and why you must never 'fix' it by disabling RLS.
Why Does My App Work Locally but Not in Production?
The app runs perfectly on your machine and breaks the moment it's deployed. It's almost always one of about a dozen causes — missing environment variables, localhost URLs, a filesystem that doesn't persist. How to find which one, in the order most likely to be it.