How to deal with "Daily user sending quota exceeded"
Second day in row, mainly because few a highly voted topics (40+) where was long discussion (20+ posts), we reached limits in Google Mail (2000 emails per day). So whole system stopped to be working because no email can be send.
Is there any suggestion how to deal with it? Were you thinking about sending just one email to all subscribers with all people set as "cc"? Or any suggested service that may serve as SMTP server?
Just asking because discussion in topic with more then 100+ votes (we already have such) fill our limit really fast so we need an alternative solution. Thanks for your feedback!
EDIT: one additional question. All these emails with status "5.4.5 Daily user sending quota exceeded. e62sm31767617wma.11 - gsmtp" - they will be send later automatically or they will never be send?
The issue is related more to using gmail as email sender, so as an option would be using any other SMTP server, preferably the one that is installed where UseResponse self-hosted is used.
All emails won't be sent for the 2nd time to not bump users, so there should be system to identify if email is bumped by the server or not, but this would require our investigation in order to make email queue.
The reason to not send as one email is security - if we do CC, it would disclose customers emails between each other, but I think we need to come up with some tweak with notifications for 4.0 release. I'll put it in plans.
The issue is related more to using gmail as email sender, so as an option would be using any other SMTP server, preferably the one that is installed where UseResponse self-hosted is used.
All emails won't be sent for the 2nd time to not bump users, so there should be system to identify if email is bumped by the server or not, but this would require our investigation in order to make email queue.
The reason to not send as one email is security - if we do CC, it would disclose customers emails between each other, but I think we need to come up with some tweak with notifications for 4.0 release. I'll put it in plans.
I'm well aware that this is not a problem of UR, but our self-hosted configuration. I just wanted to get some tip & trick from UR team as they are definitely more experienced with these "SMTP stuff".
Thank you for info about "send for second time". I'll then delete added topic and write post again so email will be send, not a big problem.
And "CC" - I though better "BCC", sorry. Anyway any improvement that may reduce amount of send emails should be welcome. Thank you.
I'm well aware that this is not a problem of UR, but our self-hosted configuration. I just wanted to get some tip & trick from UR team as they are definitely more experienced with these "SMTP stuff".
Thank you for info about "send for second time". I'll then delete added topic and write post again so email will be send, not a big problem.
And "CC" - I though better "BCC", sorry. Anyway any improvement that may reduce amount of send emails should be welcome. Thank you.
Hello Jirka,
We have organized the meeting about the issue you have with daily limit, but we can't find the way to send less emails on one action. The advised option to send as bcc would increase the limit on simultaneous users to be included in the list, so it's not an option.
I think there should be another approach in logical way here
Hello Jirka,
We have organized the meeting about the issue you have with daily limit, but we can't find the way to send less emails on one action. The advised option to send as bcc would increase the limit on simultaneous users to be included in the list, so it's not an option.
I think there should be another approach in logical way here
Hello Stas, sorry I've completely forget to answer.
We were also thinking about this and also not aware of any simple solution. For now, I'm just disabling subscribed users (these that are inactive) in case any topic going to be too long and risky (because of this limit). For now it happen just twice, so not a huge problem, but I think it will need some improvement in future. Or maybe we are only company that has a lot of users and use limited email service? :).
Have a nice day and thanks for keeping this in mind.
Hello Stas, sorry I've completely forget to answer.
We were also thinking about this and also not aware of any simple solution. For now, I'm just disabling subscribed users (these that are inactive) in case any topic going to be too long and risky (because of this limit). For now it happen just twice, so not a huge problem, but I think it will need some improvement in future. Or maybe we are only company that has a lot of users and use limited email service? :).
Have a nice day and thanks for keeping this in mind.
You are not the only company with tons of users and subscribers. Others just use internal smtp server without any limits or email service that have more daily limits.
I'll keep this topic in mind for 4.0 release, maybe we'll come up with solution, but unsubscribing users is not an option and is not convenient to use
You are not the only company with tons of users and subscribers. Others just use internal smtp server without any limits or email service that have more daily limits.
I'll keep this topic in mind for 4.0 release, maybe we'll come up with solution, but unsubscribing users is not an option and is not convenient to use
So no solution?
So no solution?
You can consider an alternative SMTP service like BREVO: https://www.brevo.com/products/transactional-email/
You can consider an alternative SMTP service like BREVO: https://www.brevo.com/products/transactional-email/
Replies have been locked on this page!