Launch day, no emails
Your own test signups always got their email. You launch on Product Hunt, forty people sign up, and not one receives the confirmation email.
This answers: Why are my signup emails not being sent? No coding needed. 2 quick decisions.
- Who is signed in
- Debugging without panic
Step 1 of 2
Your auth logs show this for every new signup. What happened?
POST /auth/v1/signup 400error: "Email address not authorized"Why are my signup emails not being sent?
Hosted auth services include a built-in email sender for testing that only delivers to your own team's addresses, a few emails an hour, so real users receive nothing. Connect your own (custom SMTP) before launch, and add , DKIM and DMARC records for your domain so mail is not spam-foldered or rejected.
Breaks at Email service: Test-only sender refuses real users
Why AI tools write this bug
AI builders wire up sign-up using the default email sender, which works perfectly while you are the only person testing it.
How to fix it
- Connect a real (custom SMTP) to your auth service.
- Verify your sending domain with , DKIM and DMARC.
- Send from one consistent address on that domain.
- Test a real signup to Gmail and Outlook before launch.
Check your own app
Paste this into Lovable, Cursor or Claude Code:
Tell me how this project sends emails (auth confirmations, password resets, receipts): which service, from which address and domain, and whether that service has rate limits. Then list the DNS records (SPF, DKIM, DMARC) I need to add for that domain. Do not change anything.
Common questions
- Why do my emails go to spam?
- Usually because the sending domain is not authenticated. Mail providers check SPF, DKIM and DMARC records to trust a sender.