My app's sign-up and password reset emails are not arriving. How do I fix it?
Short answer: Most AI-built apps send email through a starter mail service that was never meant for real customers. Supabase, a database service many AI-built apps use, only emails its own team members by default and caps the rate at a handful of messages an hour. The fix is to connect a proper sending service, such as Resend, verify your domain with a few DNS records (SPF, DKIM and DMARC), and send yourself a test.
Your customers cannot get the sign-up or password reset email from your app, and you need to know which setting is wrong.
I'm Ranjit, and I run Blur Studio: 15+ years building software, 120 apps taken live, and clients who have gone on to raise $10M+. I build AI systems and processes that help businesses do a lot more with a lot less time. I also work differently from most of what else is out there, more on that further down this page. Say hello.
Why your app's emails are missing
There are two separate problems that look the same from where you sit. In the first, the email is never sent. In the second, it is sent but lands in spam or is rejected. Work out which one you have before touching anything.
| What you see | Likely cause |
|---|---|
| Works for you and your team, fails for customers | The starter mail service only delivers to team addresses |
| Works at first, then stops for everyone | A message limit has been reached |
| Arrives in spam, mostly at Gmail | Your domain is not verified with the sending service |
| Link inside the email opens the wrong page or fails | The app's web address setting is wrong, not email delivery |
| Nothing arrives anywhere, even for you | The email step in the app is broken or switched off |
The starter mail service trap
AI app builders usually connect your app to Supabase for logins. Supabase's docs say its built-in mail server is not meant for production. Unless you set up your own server, it will only deliver to addresses that belong to your project's team. It also has a strict rate limit, listed as 2 messages per hour as of November 2026, and it comes with no promise of delivery or uptime. The limit can change without notice.
That is why the app works while you test. You and your team are on the list. Real customers are not, so their sign-up emails never leave. Lovable (an AI app builder) and Bolt (a similar one) both commonly produce apps in this state. The fix is the same: use your own sending service.
What SPF, DKIM and DMARC are, in plain words
- SPF is a public note on your domain listing which services may send mail for you.
- DKIM is a digital signature on each message that proves it was not changed on the way.
- DMARC is a rule that tells inboxes what to do when a message fails both checks, and sends you reports.
Each is a record you add in your domain's DNS settings. DNS is the address book of the internet, kept by whoever sells you the domain name, often called your registrar, or by a service such as Cloudflare.
Google, the biggest mailbox provider, requires every sender to Gmail addresses to set up SPF or DKIM, to keep spam complaints below 0.3 percent and to send over a secure connection. Senders of more than 5,000 messages a day to Gmail must set up all three, including DMARC. A small app will not hit 5,000 a day, but setting up all three is cheap and removes the guesswork.
Step by step: get your emails working
- Pick a sending service. A transactional email service is built for messages that a user triggers, such as a password reset. Resend is one; its free plan allows 100 emails a day and the Pro plan is $20 a month for 50,000 emails a month, as of November 2026. Others exist. Choose one with a free test tier and clear instructions for your platform.
- Add your domain to it. Resend says you must send from a domain you own, not a shared or public one. It suggests using a subdomain such as
mail.yourbusiness.com, so a problem with one kind of email does not harm another. - Copy the records it shows you. The service lists the exact SPF and DKIM records for your domain. Do not type them by hand. Copy and paste each name and value.
- Add them in your DNS settings. Log in to where your domain is managed, find DNS records and add each one. Watch for a common slip: some registrars add your domain on the end of the name automatically, so you end up with
mail.yourbusiness.com.yourbusiness.com. If so, enter only the first part. - Wait and verify. Google's SPF help page says SPF can take up to 48 hours to start working, though many changes show sooner. The service shows a verified status when it can see the records.
- Add a DMARC record. Add a TXT record named
_dmarcwith the valuev=DMARC1; p=none; rua=mailto:you@yourbusiness.com;. Thep=nonepart means "just report". Resend's guide says to move to a stricter setting, quarantine or reject, only after you know your messages are all passing. - Connect the service to your app. In Supabase this is the custom SMTP setting under authentication, where you paste the host, port, user name and password the service gives you. Use the From address on your verified domain. If you built the app with an AI tool, you can ask it where the email settings live, but make the change yourself in the dashboard and keep passwords out of the chat.
- Send tests. Trigger a real sign-up and a real password reset to a Gmail address, an Outlook address and one on your own domain. Check the inbox and the spam folder. Click each link.
- Look at the headers. In Gmail, open the message, choose "Show original" and look for SPF, DKIM and DMARC all marked PASS.
If the password reset still fails
If the email arrives but the link breaks, the problem is in the app, not in email. Check these:
- The web address: the link uses the address the app has stored as its site address. If you moved to your own domain, update it. See putting your AI-built app online under your own domain.
- Old preview links: some builders send links that point at a test address that no longer exists.
- Expired or used links: reset links work once and expire. A mail scanner that opens the link first can use it up. Test with a fresh request.
- Templates edited by the AI: if the email text was rewritten, the link placeholder may have been removed. Compare against the default template.
Keep it working
- Use a separate sender for marketing. Never send promotions from the address that sends password resets. My guide on why cold emails land in spam explains the reasons, and how to set up cold email without harming your main domain shows the setup.
- Watch your sending service's dashboard. Bounces and complaints show up there first.
- Re-test after any change to your domain, your host or your login settings.
- Add it to your launch checklist. Email is one of the items in making a vibe-coded app production ready, and sign-in rules belong next to it in the security checklist.
When to hire help
Do it yourself if you own the domain, can log in to the DNS settings and the service gives you copy and paste records. Get help if any of these is true:
- You do not know who controls your domain, or the person who bought it has left.
- Your domain already sends other mail, such as your team inbox, and you are not sure how to add to its SPF record without breaking it. Ask your sending service how to add its entry to the SPF record you already have.
- Tests pass but real customers still report problems.
- The login system itself, not only the email, is failing for users.
If the app was built on Lovable, a developer who knows the tool will usually fix this quickly. My note on hiring a Lovable developer covers what to ask.
How I'd approach this
I treat email as part of the app's launch, not an extra. Before a single real customer signs up, I would have a proper sending service on a subdomain, three DNS records in place, and screenshots of the test results.
If you are in a rush, do just this: connect a sending service, verify the domain and send three real tests. That solves most cases. Fixes of this size usually take a short job, and my fixes and finishes start around $1,500 when the problem turns out to be wider than email. If you would like me to look at it, a short call is enough to tell which kind of problem you have.
Questions people ask
Why do my app's emails work for me but not for customers?
Supabase's built-in mail server only delivers to addresses that belong to your project's team unless you set up your own server. That means you receive the email while customers do not. Connect a proper sending service and verify your domain. See production readiness for what else to check.
Do I need SPF, DKIM and DMARC for a small app?
Google requires SPF or DKIM for everyone who sends to Gmail, and all three for senders above 5,000 messages a day. Adding all three is a small job and gives inboxes the signals they use to trust you.
How long do DNS changes take?
Google's SPF help page says it can take up to 48 hours for SPF to start working, and many changes show much sooner. Your sending service will show a verified status once it can see the records. If it stays unverified after two days, check for a doubled domain name in the record name or a typo in the value.
Can I just send from a Gmail or Outlook address?
No. Google's sender guidelines say not to impersonate Gmail From: headers, and that doing so might hurt delivery. Use a From address on a domain you own and have verified with your sending service.
My password reset email arrives but the link does not work. Is that a spam issue?
Usually not. It is more often the site address stored in your app's login settings, an expired link or an edited template. See putting your app under your own domain.
Should I use the same service for marketing emails and app emails?
Use separate subdomains at least. Resend recommends separate subdomains for different sending purposes so a complaint about a promotion does not hurt your password resets. My guide on cold emails landing in spam goes deeper.
More in this topic: Problem solving: AI-built and no-code apps (26 guides) →