During a recent production build using Supabase Auth, I encountered a critical issue: new user signups become effectively blocked when SMTP/email delivery is degraded or rate-limited.
While Supabase correctly prioritizes email verification for security, the current signup flow tightly couples account creation to email delivery, which creates operational risk during SMTP outages or throttling events.
This proposal suggests non-breaking improvements to make Supabase Auth signups more resilient, observable, and developer-friendly.
auth.signUp() or admin user creation succeeds at the API levelFrom the application’s perspective:
Supabase Auth currently:
This is understandable for security, but fragile operationally.
Allow user creation to complete even if verification email fails, while keeping the account in an unverified state.
User created → email verification pending → retries allowed
Provide a first-class method to resend verification emails safely.
Example:
auth.resendVerification({ email })
With:
Return explicit fields such as:
{
"email_verified": false,
"verification_sent": false,
"last_email_attempt_at": "...",
"can_retry": true
}
This allows apps to:
Emit events like:
auth.email.delivery_failedauth.email.rate_limitedSo teams can:
For certain apps (healthcare, internal tools, staged onboarding):
Account usable with limited permissions until verified
This preserves security while improving UX during outages.
This came from a real production issue while building a healthcare-grade app with Supabase Auth. The platform is excellent, but signup reliability is mission-critical and deserves extra resilience.
Happy to help iterate on this or provide implementation insights if useful.
Thanks for building Supabase 🙌
Anirudh Madhav Kulkarni proposes improvements to Supabase Auth to handle SMTP/email delivery issues during user signups. The current system tightly couples account creation with email verification, causing signups to fail if emails are not delivered. Suggested improvements include decoupling user creation from email delivery, adding a retry API, exposing verification states, and providing webhooks for email failures.
Ran into the same thing in production, so a few things that helped me while waiting for something built in:
Move off the default sender. As far as I know the built-in email service is heavily rate limited and only meant for testing, so set up custom SMTP (SES, Resend, Postmark etc.) so your limits and delivery are in your hands.
Don't make the UI depend on one email arriving. Show a "Resend email" button with a cooldown (30-60s) and a clear "check spam / wrong address?" hint, and log delivery failures yourself so you at least get a signal. This is basically a manual version of the resend flow you're proposing.
Stop bad addresses before they reach the sender. Typos, disposable domains and addresses with no mail server all bounce, and with SES a hard bounce rate of 5% puts the account under review, with sending possibly paused at 10% (AWS docs: https://docs.aws.amazon.com/ses/latest/dg/reputationdashboardmessages.html). Checking the address first, before triggering the confirmation email, keeps the bounce rate down and cuts down on retries.
Ideally the check fails open: if the check service is slow or down, let the signup continue rather than blocking it.
Disclosure: I build SentriSend (sentrisend.com), a small pre-flight check API aimed at exactly #3 and #4 for Supabase Auth hooks, so I'm biased. Happy to share what I learned about the hook setup if it's useful, whether or not you use it.