Skip to content
Get a quote

Lovable email problem

Lovable app not sending emails: sign-ups, resets and contact forms

Customers say the confirmation email never came, password resets go nowhere, or the contact form says sent and nothing reaches your inbox. Yet the emails you send to yourself arrive. In a Lovable app, mail goes through Lovable Emails, Supabase Auth on your own Supabase project, or a connector such as Resend, and the Supabase and Resend paths each have a default that stops mail to real users. Here they are in the vendors’ words, or hand it over at a fixed price.

Rather hand it over? App Fix Ticket: One reproducible bug in an existing mobile or web app, diagnosed and fixed.

Pay $450 for a DiagnosisAsk a question first

Full refund if Simon can’t take it on once he sees your project, or if you cancel before work starts. Refund terms.

Short answer

Find which service sends the email. On your own Supabase project with no custom SMTP, Supabase sends auth emails only to your team’s addresses, 2 an hour, so add a custom SMTP server. With Resend, the test sender onboarding@resend.dev reaches only the Resend account owner, so add and verify your domain. If mail lands in spam, set SPF, DKIM and DMARC for the sending domain. For a contact form, check the backend function that sends it has its email API key.

Rather not fix it yourself? App Fix Ticket starts with a fixed-price diagnosis, then a fixed price for the fix before any fix work.

Why the emails don’t arrive, and the fix

  1. 01

    Supabase only emails your team

    “Unless you configure a custom SMTP server for your project, Supabase Auth will refuse to deliver messages to addresses that are not part of the project's team.” Supabase, Send emails with custom SMTP

    A Lovable app on your own Supabase project uses Supabase’s built-in email server until you add your own. That server delivers only to the email addresses of people on the project’s team, which is why your own test sign-ups work. Set up custom SMTP in the Supabase dashboard with an email provider.

  2. 02

    The built-in server allows 2 emails an hour

    “Currently this value is set to 2 messages per hour.” Supabase, Send emails with custom SMTP

    Even to your team, the built-in server sends only 2 messages an hour. Supabase says it is not meant for production use.

  3. 03

    Resend is still on the test sender

    “Resend’s shared test address, onboarding@resend.dev, delivers only to the email address of the Resend account owner.” Lovable, Resend integration

    If the app sends through the Resend connector from onboarding@resend.dev, only the Resend account owner gets the mail. Change the sender to an address on your own domain once that domain is verified. For sign-up confirmations and password resets, Lovable’s Resend page points to the built-in Lovable Emails instead.

  4. 04

    The domain isn’t verified

    “Resend delivers email to your app’s users only from a domain you have verified in Resend.” Lovable, Resend integration

    Add the domain in Resend, add the DNS records it lists at your DNS provider, and wait for it to show as verified on the Domains page before sending to customers.

  5. 05

    The emails land in spam

    “Work with your email sending service to configure DKIM, DMARC and SPF for your sending domain. This will significantly increase the deliverability of your messages.” Supabase, Send emails with custom SMTP

    Ask customers to check spam. If the mail is there, set SPF, DKIM and DMARC records for the domain you send from. Lovable also says mail from your own domain is more likely to reach the inbox; its custom email domain needs a paid workspace plan and a domain whose DNS you can manage.

  6. 06

    The contact form has no working sender

    A contact form needs backend code that calls an email service with an API key. Lovable says to keep that key secret and never share it publicly. If the key is missing or the function fails, nothing is sent. Check the function’s logs after a test submit.

Checked against the vendor’s docs on : Supabase docs: Send emails with custom SMTP; Lovable docs: Resend integration; Lovable docs: Custom emails; Resend docs: Domains; Resend docs: Why are my emails going to spam?.

Rather hand it over?

Fixed scope, fixed price, paid upfront. The work happens in writing; no call needed.

“Very responsive, attentive to fixing bugs, and completed the project as needed! Thank you!”
A buyer in the United States, July 2022. Shopify on Fiverr
All 127 Fiverr reviews

Related: Supabase email address not authorized · Supabase auth emails going to spam · Lovable edge function secret missing · Hire a Lovable developer

Questions

More on this error

Why do the emails reach me but not my customers?

Both test setups only send to you. Supabase’s built-in email server delivers only to the project’s team, and Resend’s onboarding@resend.dev sender delivers only to the Resend account owner.

Do I need a paid Lovable plan for my own email domain?

For Lovable’s custom emails, yes. Lovable says the workspace must be on a paid plan and you must own a domain and manage its DNS settings.

Can you fix it for me?

If one bug is the whole problem, the App Fix Ticket covers it: a written diagnosis first, then the fix. If the app has more going on, the Launch Check is a written check of the whole app. Each issue found is rated critical, high, medium or low, with where it is and how it was confirmed. No issues worth fixing, no charge. If the Launch Check finds nothing rated medium or higher, Simon refunds the full $450. You keep the report either way. This applies to the first 10 Launch Checks bought after October 30, 2026.

A different error?

Describe it and get a written quote

Send the error and what you were doing. You get a written scope, a fixed price and a timeline; Simon replies by email, usually within one business day.

Describe your problem All fixes