2

When using the Email Dispatcher to send emails (using an SMTP connector), if I try to send 50 emails in quick succession I probably get an error after the 30th email because of the SMTP rate limit of 20/30 emails per minute.

This can be solved by applying a rate limit to the Email Account. However, after said limit is applied, the system checks if n emails have been sent in the last minute (if the setup limit has been reached), and if so, the email is scheduled to be sent a minute from now, not considering any other emails that may have been scheduled to the same time.

What happens then is, when said scheduled time is reached, the system may spin up multiple scheduled tasks at the same time and they all try to send their scheduled emails, causing the SMTP server to eventually start responding with code 4.3.2 Concurrent connections limit exceeded.


I suggest that the Email Dispatcher codeunit also considers any scheduled emails in the Email Outbox for the current Email Account when rescheduling an email to avoid this situation.

Category: Development
STATUS DETAILS
Needs Votes
Ideas Administrator

Thank you for this suggestion! Currently this is not on our roadmap. We are tracking this idea and if it gathers more votes and comments we will consider it in the future. Best regards, Business Central Team