This article describes the rate limits implemented by TMEMS, for both outbound and inbound mails.
Rate Limit Settings
- For inbound traffic, the rate limit is based on sender IP and recipient.
- For outbound traffic, the rate limit is based on sender IP and sender.
|Direction||By IP address||By email address|
|Inbound||500 messages per minute per sender IP address||200 messages per minute per recipient email address|
|Outbound||1,000 messages per 5 minutes per sender IP address||500 messages per 10 minutes per sender email address|
If any of these rate limits is reached, message delivery will be delayed until the rate goes below the limit at a later time. For more details on this scenario, see "Rate limit temporarily exceeded" shows as Block Reason for blocked or delayed emails.
- What will happen if the the rate limit has been reached/exceeded?
When the sender IP or the recipient triggers the TMEMS rate limits, TMEMS will temporarily reject the emails from that sender IP or to the recipient, and returns the error code 4xx.
- When will TMEMS accept the emails again?
If the email sender client follows the RFC's definition, the email sender client should re-send the emails based on their resend strategy.
- Is it possible to disable or by-pass the rate limits for inbound/outbound mails?
By-passing or disabling the rate limits for inbound/outbound mails is not recommended, because this is implemented to prevent spamming and domain attacks. However, rate limits can be temporarily disabled or by-passed for special cases, which will require evaluation by TMEMS development team including the Product PM.