- Newest
- Most votes
- Most comments
Hi THere
Can you provide some details on how your application is sending mail? Is it using some sort of keep alive to hold a connection open to the SMTP server? If so, you might want to try limiting that. Also, do you have any retry/backoff in your application code?
See https://docs.aws.amazon.com/ses/latest/dg/troubleshoot-smtp.html#troubleshoot-smtp-response-codes
You should retry SMTP requests that receive 400 errors. We recommend that you implement a system that retries requests with progressively longer wait times (for example, wait 5 seconds before retrying, then wait 10 seconds, and then wait 30 seconds). If the third retry doesn't succeed, wait 20 minutes, and then repeat the process. To see an example of an implementation that uses an exponential retry policy, see How to handle a "Throttling - Maximum sending rate exceeded" error on the AWS Messaging and Targeting Blog.
Relevant content
- asked 2 years ago
- asked 5 years ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 2 years ago
Thank you Matt! I am using https://listmonk.app/. I will refer the developer to your comment.
I believe you need to reduce the concurrency. One other thing to check is the application server you are sending from. The OS or other factors could be limiting the number of network connections causing a timeout. Is it possible to add more resources to your application server and see if it helps?
Also, it looks like you can use listmonk-messenger to interface with the SES API instead of using the SMTP endpoint of SES, might be worth looking in to. See https://github.com/joeirimpan/listmonk-messenger
Per the help text at https://demo.listmonk.app/admin/settings
My SES limit is 120/s so I had my concurrency and message_rate to 10x10. I tried lowering concurrency to 5 (5x10) and still got the errors. https://github.com/knadh/listmonk/issues/1717#issuecomment-2016906048
My server usage is very low but I'll contact the provider to ask if this error may be due to a limit they have.
I checked listmonk-messenger and SES API vs SMTP endpoint of SES, but it doesn't look like it would be worth the trouble https://github.com/joeirimpan/listmonk-messenger/issues/71.