Email sending limits on HENNGE Email DLP service

for Google Workspace / for Microsoft 365

日本語のご案内はこちらをご確認ください。
中文的文章請點擊這裡

To keep the systems stable, the HENNGE Email DLP service has the following sending limits per tenant as well as per user. The limits are equally applied regardless of the service you are using (Google Workspace/Microsoft 365) and the email destination (Internal destination/External destination.)

If a user or tenant exceeds the email sending limits, an error message will be sent to Google Workspace/Microsoft 365 from the Email DLP service.

We appreciate your understanding as this is required to provide a stable service.  If you have any questions, please feel free to contact a HENNGE Customer Success Guide.

1. Rate-limiting

1.1.
[Error Code]  450 (temporary error)
[Error Message]
 Peak SMTP relay limit exceeded.
[Details] 
A sender address sends emails to over 600 recipients per 10 minutes window. (*1)(*2) Once the state is back to normal, the limit will automatically be removed. Emails which the restrictions were applied to will be automatically resent.

1.2.
[Error Code] 550 (permanent error)
[Error Message]  Peak SMTP relay limit exceeded.
[Details] A sender address sends emails to over 600 recipients per 10 minutes window. (*1)(*2) 
Once the state is back to normal, the limit will automatically be removed. Emails which the restrictions were applied to will NOT be automatically resent. Senders are required to resend the emails mentioned in the NDR.

2. Blacklisting

2.1.
[Error Code]  550 (permanent error)
[Error Message] We detected a high volume of bounced emails coming from [you/your organization] over a short period of time. To protect our users from spam, emails from [you/your organization] have been blocked. [You/Your organization] will be automatically unblocked in <remaining block duration>. For further assistance, please contact the system administrator.
[Details]  After the passage of <remaining block duration>,  the limit will be automatically removed. Emails which the restrictions were applied to will NOT be automatically resent. Senders are required to resend the emails mentioned in the NDR.

2.2.
[Error Code] 550 (permanent error)
[Error Message] We detected a persistently high volume of bounced emails coming from [you/your organization]. To protect our users from spam, emails from [you/your organization] have been blocked. [You/Your organization] will not be automatically unblocked. For further assistance, please contact the system administrator.
[Details] This restriction will not be automatically removed. To delist this restriction, senders need to stop sending the emails and then system administrators need to contact HENNGE Customer Success Guide. Emails which the restrictions were applied to will NOT be automatically resent. Senders are required to resend the emails mentioned in the NDR.

2.3.
[Error Code] 550 (permanent error)
[Error Message] We detected an unusual rate of unsolicited emails coming from [you/your organization]. To protect our users from spam, emails from [you/your organization] have been blocked. [You/Your organization] will not be automatically unblocked. For further assistance, please contact the system administrator.
[Details]  This restriction will not be automatically removed. To delist this restriction, senders need to stop sending the emails and then system administrators need to contact HENNGE Customer Success Guide. Emails which the restrictions were applied to will NOT be automatically resent. Senders are required to resend the emails mentioned in the NDR.

 

 

(*1)The HENNGE Email DLP service analyzes an email for each recipient. For example, if three recipients are set in an email, that will be counted as three destinations.

(*2) In the case where a user sends a large number of emails, e mail service providers (including  Google Workspace, Microsoft 365, mobile carriers, and web emails) and anti-spam email organizations (such as information providers of RBL) may black-list the sender IP address as spam. Because of this, emails sent by other users or tenants may be impacted, and that is why this safety feature is implemented.  

 

 

 

          
Was this article helpful?

Frequently Asked Questions (FAQs)