These are the limits on the email each provider sends for you, from their documentation on 13 November 2026. Check each provider’s docs for current details.
| Provider | What the built-in sender allows |
|---|---|
| Supabase | 2 emails an hour, and only to members of the project’s team |
| Firebase | Per day on the free Spark plan: 1,000 address verifications, 150 password resets, 5 email-link sign-ins |
| Auth0 | 10 emails a minute of any type; not for production |
| Clerk | 100 emails a month per development instance, and up to 100 recipients a day per workspace (50 in its first week) |
Each section below says how to get past the limit.
Supabase
The built-in sender is for trying Supabase out. It sends at most 2 emails an hour, and only to addresses on your project’s team; anyone else gets “Email address not authorized”.
- Set up custom SMTP with a provider such as Resend, Amazon SES or Postmark: in the dashboard under Authentication → Emails, on its SMTP settings.
- Supabase then allows 30 emails an hour until you change it under Authentication → Rate Limits. Raise it for staging if your tests send more.
- Check your SMTP provider isn’t in its own sandbox: a new Resend account without a verified domain, or Amazon SES before production access, sends only to your own addresses.
More in Supabase sign-up problems.
Firebase
Firebase sends its own emails, with daily limits per project. On the free Spark plan, email-link sign-in stops after 5 emails a day, so a passwordless test suite runs out on its first morning. The limits are much higher on the Blaze plan (pay as you go).
Firebase’s docs don’t describe sending these emails through your own SMTP server. To send them yourself, create the link with the Admin SDK (generateEmailVerificationLink, generatePasswordResetLink or generateSignInWithEmailLink) and send it with your own email provider.
More in Firebase sign-up problems.
Auth0
Auth0’s built-in email provider is for testing only: it sends at most 10 emails a minute, of any type, with no custom templates or sender address. A test suite running in parallel can pass that in seconds.
Set up your own under Branding → Email Provider: switch on Use my own email provider, then pick SMTP or one of the listed providers.
More in the Auth0 guide.
Clerk
Development instances can send 100 emails a month, and each workspace has a daily cap on recipients across its development instances (50 a day for the first 7 days, then 100). Over it, sign-ups that need an email fail with dev_daily_email_recipient_limit_exceeded.
Test mode lets +clerk_test addresses verify with the code 424242 without an email, and they don’t count towards the caps. Since late October 2026, Clerk sends no email at all to those addresses in test mode, so tests that need the real email (a sign-in link, an invitation) use a normal address and count towards the cap.
Clerk has no SMTP setting. To send through your own provider, switch off Delivered by Clerk on a template and send the email from the email.created webhook.
More in the Clerk guide.
Use the allowance well
- One address per test. A new Proxy Mail QA address each run means a retry never waits for an email that went to a reused address, and every email you pay for is one you check.
- Read the delivery check before retrying. If nothing reached the address, the provider didn’t send it: retrying only uses more of the allowance.
- Keep the provider’s test shortcuts for unit tests. Fixed codes and test modes skip the email. Keep a few end-to-end tests that receive the real one, so you know your users get it.