Email Per Second Limits with SES #25
Description
Hi @ItzNotABug
I am not opening an incident as it is more of a query than an incident. I have contracted AWS SES as my SMTP provider. I have a limit of 50K/day and 14 emails per second. Something curious happens. Ghosler has managed to send 588 of the 1352 emails correctly.
I ask with ignorance. I have seen that Ghosler uses nodemailer. Is this configured in your program as infinite? https://medium.com/@susanne.lundkvist/using-nodemailer-to-send-bulk-emails-cbad289fce0e
I don't know if Nodemailer will be blocking so much mass mailing as well.
Ghosler shows this error:
[2024-01-08 17:59:39 UTC] => [ERROR] => Newsletter: Error: Message failed: 454 Throttling failure: Maximum sending rate exceeded.
It shows as if it is checking the AWS SES limit, but this is not the case. Googling I see this article from 2015 (nodemailer/nodemailer#436) also about the same "pool" issue.
If nodemailer is not the problem. Is there a way for Ghosler to detect the members that did not receive the email and do a "retry". If it detects that there are 1352 members (in my case) but only 588 emails sent. I don't know if it detects which emails could not be sent, and proceed with a retry.
Or adding some "queue" for emails.
Thanks!!
Originally posted by @viriatusX in #14 (comment)