Mendlark / Guides

Supabase confirmation emails not arriving: how to fix it

Sign-up works in your Lovable or Bolt app when you test it, but real users never get the confirmation or magic-link email. Or emails stop after a few sign-ups. This is usually Supabase's built-in email service, which is only meant for testing. Here's what's going on and how to fix it.

Stuck on this? Get it fixed for €49.

Fixed in 48 hours or you don't pay. Launch deal for the first 5 customers (normally €79). You get the tested fix as a pull request, so nothing changes until you merge it.

Get it fixed for €49

1. The built-in email service is for testing only

Supabase's default email sender has two limits that catch most launches:

  • It only sends to email addresses of members of your Supabase organisation. That's why it works when you test with your own address and fails for real users.
  • It has a very low hourly rate limit, so even allowed emails stop after a handful.

Check Authentication → Emails (SMTP settings) in your project; if no custom SMTP is configured, you're on the default sender. Your project's Auth logs will show rate-limit or sending errors.

2. Set up custom SMTP

Use a transactional email provider such as Resend, Postmark, Amazon SES, SendGrid or Brevo:

  • Sign up with the provider and verify your domain (it gives you DNS records for SPF and DKIM to add at your domain registrar).
  • In Supabase, enable custom SMTP and enter the provider's host, port, username and password, plus a sender address on your verified domain (e.g. hello@yourapp.com).
  • After that, raise the email rate limit under Authentication → Rate Limits to suit your traffic.

Sending from your own verified domain also keeps emails out of spam far more reliably.

3. Fix the link inside the email

If the email arrives but the link goes to localhost:3000 or the wrong site, update Authentication → URL Configuration: set the Site URL to your live domain and add your live URLs to Redirect URLs. If your code passes emailRedirectTo, make sure it uses the live domain, not a hard-coded localhost. More in the Supabase auth redirect loop guide.

4. Links that say "expired" or "invalid" straight away

Some company email systems (like Outlook's Safe Links) open every link to scan it, which uses up the one-time link before your user clicks. If business users report this, consider sending a one-time code (OTP) in the email instead of a link, using the {{ .Token }} variable in the email template.

5. Users stuck as "unconfirmed"

Users who signed up while emails were failing are left unconfirmed and can't log in. Once SMTP works, they can request a new email from your app (Supabase's resend method), or you can confirm them manually in Authentication → Users if you trust the address.

Quick checklist

  • Custom SMTP set up with a provider and a verified domain
  • Email rate limit raised after SMTP is on
  • Site URL and Redirect URLs point at the live domain
  • Test sign-up with an address outside your Supabase team
  • Check spam and Auth logs if anything still fails

Stuck on this? Get it fixed for €49.

Fixed in 48 hours or you don't pay. Launch deal for the first 5 customers (normally €79). You get the tested fix as a pull request, so nothing changes until you merge it.

Get it fixed for €49

Still stuck?

Mendlark fixes this kind of problem for a fixed price: €49 for the first 5 builders (normally €79). We agree the problem first, test the fix and send it as a pull request. Fixed in 48 hours or you don't pay. Fix it for €49 or start with a free scan.

Not sure what else is wrong? Paste your app link into the free instant check and get a plain-English list of problems in seconds.