Batch Email Sending to Bypass SMTP Limits

What is a one sentence summary of your feature request?

Enable the product to send emails in configurable batches in order to comply with the maximum sending limit imposed by the client’s SMTP server.

Please describe your idea in detail. What is your problem, why do you feel this idea is the best solution, etc.

Hello,

One of our On-Premise customers would like a product enhancement regarding email delivery.

As part of their certification campaign, around 800 emails need to be sent to managers. However, since the customer changed their SMTP server, only 350 emails can be sent (a limit imposed by their server), and any emails beyond this limit fail.

Since they do not want to modify this limit for technical reasons, the customer would like the product to send emails in batches of 50 to 100 messages, with a reset between each batch. This would allow the SMTP session to remain active while resetting the counter, in order to limit network impact and reduce latency — unlike a full session close/reopen. Ideally, the customer would like the batch size to be configurable (for example, in the MailSettings section of appsettings.json).

The customer would need this enhancement during the first half of 2026 (before summer 2026). Could you confirm whether this improvement is feasible, and provide an estimated timeline?

Thank you in advance.
Kind regards

How do you currently solve the challenges you have by not having this feature?

The client will most likely have to switch back to their previous SMTP server to avoid the limitations of the new one, even though it is less secure.

Hello Raphael,

There is a MailSettings option with a default value that sets the maximum number of emails sent. I’m not sure if the limit was 20, 50 something like that. I couldn’t find it in the documentation but I remember it was added in a patch because it was mentioned in the old patch notes.

Hello Kamil,

Thank you very much for your feedback. Yes, I think you’re referring to the RatePermitLimit parameter. This parameter defines the maximum number of emails that can be sent at once. When that limit is reached, no further emails are sent, so it does not allow batch processing.

I had already considered the possibility that the client’s limitation might be related to this parameter, but in reality the issue comes from internal technical constraints on their SMTP sever, not from this setting, which is not enabled on their side.

This is why the client would like to have the ability to configure email sending in batches.

Best regards!