Sign-up emails not arriving? Fix auth mail
Your site works in testing. You sign up with your own address, the confirmation email arrives, and you log in. Then you launch, and real users start writing in: "I never got the email." Sign-ups pile up as unconfirmed accounts, password resets go nowhere, and most people never tell you. They just leave.
This is one of the most common quiet failures in sites built with Lovable, Bolt, Replit, v0 and Cursor, because the default email setup that works during building is usually not meant for real traffic.
The symptom
- New users say the confirmation or magic link email never arrived.
- Emails reach you and your teammates, but not outside addresses.
- Emails arrive, but in spam or the Promotions tab.
- Sign-ups work for a while, then stop after a burst of new users.
- Your auth dashboard shows users stuck as unconfirmed.
The cause
Most AI-built sites use a backend like Supabase or Firebase for login, and those services send auth emails for you. Out of the box, they use a shared, built-in email sender. That sender is fine for trying things out, but it is not designed for production. Supabase, for example, documents its built-in email service as being for testing, with a low hourly sending limit, and recent projects may only deliver it to addresses on your own team. Check your provider's current docs for the exact limits.
Three other things cause the same symptom:
- Missing domain authentication. Once you switch to your own sender address, mail without SPF, DKIM and DMARC records on your domain is much more likely to be filtered as spam or rejected.
- Wrong links inside the email. The email arrives, but the link points at localhost or a preview URL, so users think it failed. This is the Site URL and redirect setting.
- Your own code swallowing errors. If the site calls an email API for welcome or receipt emails and ignores the response, a bad API key or unverified sender fails silently.
Step-by-step diagnosis
- Test with an outside address. Sign up with a fresh Gmail or Outlook address that is not on your team. If it never arrives but your own address works, you are almost certainly on the built-in sender.
- Check the auth logs. In Supabase, look at the Auth logs for errors around sending, such as rate limit messages. Firebase and other providers have similar logs.
- Look at your SMTP setting. In your auth provider's settings, see whether a custom SMTP server is configured. If the section is empty or disabled, you are using the default.
- Check spam and the raw headers. If a test email lands in spam, open "show original" in Gmail and look for SPF, DKIM and DMARC results. Any "fail" or "none" tells you what's missing.
- Click the link in the email. Make sure it points at your live domain, not localhost or a preview address.
Fixes per builder or host
Lovable, Bolt and other Supabase-backed sites
Set up custom SMTP in your Supabase project's Auth settings, using a transactional email provider such as Resend, Postmark, SendGrid or Amazon SES. Use a sender on your own domain, like hello@yourdomain.com. Your provider will give you DNS records to add for domain verification, usually including SPF and DKIM. Add a basic DMARC record too. Then raise the auth email rate limit in Supabase to a level that fits your expected sign-ups.
While you're there, set the Site URL and redirect URLs to your live domain, and edit the email templates so the subject and wording look like your product, not a default.
v0 and Cursor projects on Next.js
If you use Supabase or another auth provider, the same custom SMTP fix applies. If your own code sends emails through an API, check that the API key is set in your production environment variables, not just locally, and log or surface any error the send call returns instead of ignoring it.
Replit
Put your email API key in Replit's Secrets for the deployment, not only the workspace. If you send through a library, make sure it awaits the send and logs failures, so a rejected email shows up in your deployment logs.
How to verify
- Sign up with two or three outside addresses on different providers and confirm each email arrives in the inbox, not spam.
- Click every link in those emails and confirm it lands on your live site and logs you in.
- Request a password reset and a magic link, not just the first confirmation.
- Check your email provider's dashboard to see each message marked delivered.
Prevention
- Switch to custom SMTP before launch, not after the first complaint.
- Keep SPF, DKIM and DMARC in place whenever you change DNS or hosts.
- Re-test sign-up from an outside address after every big change your builder's AI makes to auth.
- Watch for a rise in unconfirmed users; it's often the first sign emails have stopped.
Sign-up emails are one of many things that quietly break after a deploy. Checking the basics regularly catches them before your users give up.
