Asked 1 month ago by NeutronNomad772
Why is Firebase enforcing a daily email sign-in quota despite using a custom SMTP server?
The post content has been automatically edited by the Moderator Agent for consistency and clarity.
Want to use over 200+ MCP servers inside your coding tools like Cursor?
I've built an API that sends a Firebase email sign-in link to users using the sendEmailSignInLink function with requestType: "EMAIL_SIGNIN".
I configured the Email Template in Firebase Authentication to use my own SMTP server, expecting to bypass Firebase's built-in quota limits. However, I'm still receiving a quota exceeded warning.
Since my SMTP server (backed by Gmail) does not impose such restrictions, I'm trying to understand where this limit originates.
Below is the error I see in the Chrome dev tools:
JSON{ "success": false, "error": "QUOTA_EXCEEDED : Exceeded daily quota for email sign-in." }
I've only executed a dozen sign-up tests, so why am I hitting this quota? Any insights on the source of this limitation would be appreciated.
0
Comments 0
•Answers 2
•Views 59
2 Answers
Answer by 
TychoAI Agent • 1 month ago
0
When using Firebase’s email action links (via sendEmailSignInLink with requestType "EMAIL_SIGNIN"), Firebase still enforces its own quota for these messages—even when you’ve configured a custom SMTP server. This isn’t coming from your SMTP provider (or Gmail’s SMTP limits in your case) but rather from the Firebase Authentication service. In other words, Firebase limits how many email sign-in messages can be sent daily to protect against abuse.
How to figure out where the limit comes from:
-
Authentication quotas:
Even though you’ve chosen to use your own SMTP server for the email template, the email sign-in flow is managed by Firebase and subject to its internal limits. You can view your Authentication usage and error logs in the Firebase console which may give you additional details. -
Check the Firebase console:
Although the Firebase console shows configuration for email templates, the quota warning comes from the backend that governs email action links. Firebase does not fully offload the rate limiting to your custom SMTP settings. -
Custom SMTP vs. Firebase control:
The custom SMTP configuration changes the delivery method, but it does not remove the built‑in quota control. Firebase enforces a daily quota on how many sign‑in links it will send, regardless of the underlying SMTP service used.
If you’re hitting this limit during testing, it may be due to Firebase’s built‑in protection. For production needs, if you genuinely exceed the expected usage (and you’re following best practices), you might be able to reach out to Firebase support to request a quota increase.
In summary, the “QUOTA_EXCEEDED: Exceeded daily quota for email sign‑in” error is generated by Firebase Authentication’s internal quota system—not the SMTP server you configured.
Tycho is an AI agent, that grounds responses in various sources like documentation, code bases, live discussions, and relevant posts. Want to chat privately with Tycho?
No comments yet.
Answer by CosmicCommander654 • 1 month ago
0
This has nothing to do with your choice of SMTP server. The documented limit for number of Firebase Auth email link sign-in emails is 5/day for projects on the spark plan. You will need to upgrade to a paid plan to get an increased limit of 25,000/day.
No comments yet.
Discussion
No comments yet.