Asked 1 month ago by GalacticTracker076
Why Does Firebase Return a QUOTA_EXCEEDED Error for Email Sign-In 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 using the sendEmailSignInLink function with requestType: "EMAIL_SIGNIN"
I then configured my own SMTP server in the Authentication templates on the Firebase console to bypass the built-in email service quota.
However, I'm still receiving the warning about exceeding the daily quota for email sign-in.
Since my SMTP server doesn't impose such limitations, I'm trying to understand where this quota is coming from.
Below is the error message from the Chrome dev tool:
JSON{ "success": false, "error": "QUOTA_EXCEEDED : Exceeded daily quota for email sign-in." }
I have only sent a dozen test email sign-in requests, not hundreds. Any insights on why this limit is being enforced?
0
Comments 0
•Answers 2
•Views 45
2 Answers
Answer by 
TychoAI Agent • 1 month ago
0
The error isn’t coming from your SMTP server—it’s coming from Firebase Authentication’s built-in safety limits on sending sign-in emails. Even though you’ve configured your own SMTP settings in the Authentication templates, Firebase still imposes a daily quota on email sign-in link requests to prevent abuse.
Here are some steps to help diagnose and handle the issue:
-
Understand the Quota
Firebase enforces limits on the number of email sign-in links sent per day, regardless of whether you’re using the built-in email service or your own SMTP server. This protection is applied by Firebase Authentication itself. -
Review Your Usage
Check if there might be unintended multiple invocations in your API that end up sending more emails than you expect. Sometimes a development loop or re-triggering the function inadvertently increases the count. -
Monitor Quotas in the Console
Visit your Google Cloud Console and review Firebase Authentication metrics. This can help you see if you’ve hit the daily threshold or if there’s another issue in the flow. -
Request a Quota Increase
If your expected usage genuinely requires more email sign-in link sends, consider submitting a request for a quota increase. Make sure your usage consistently approaches or exceeds 80% during peak periods and that you adhere to Firebase’s best practices.
Even with Gmail powering your SMTP, Firebase still applies its internal limits on email sign-in requests. This ensures that even when bypassing the default sending mechanism, the security and abuse prevention measures remain intact.
By following these steps, you should be able to pinpoint whether the issue is due to an unexpected increase in request frequency or if a quota increase is legitimately needed for your use case.
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 NeutronMariner633 • 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.