At NeetoDesk, we have ensured that one rogue person doesn't disrupt the operation by overwhelming our servers.
Rate limiting per organization
If an organization receives more than 100 emails in one hour, NeetoDesk will process only the first 100 emails in an hour. The rest of the emails will be added to a queue to be processed in the next hour. In the next hour, only the first 100 emails will be processed, and the rest will be queued to be processed in the hour, after that. Please contact us if your organization needs to process more than 100 emails per hour.
Rate limiting per customer
When a customer sends more than ten emails within an hour, NeetoDesk will process the first ten emails immediately, and the remaining emails will be added to the queue to be processed in the next hour.
A customer's queue size can never be larger than 100. This means that if the queue is already at 100, more emails can't be added to it, and those emails will be discarded. Let's see an example.
Rate limiting per customer case scenario
Let's say that Joe sent 70 emails between 1 PM and 2 PM. As per the rule above, the first ten emails will be processed, and the remaining 60 emails will be added to the queue to be processed in the next hour.
Between 2 PM and 3 PM, NeetoDesk processed the first ten emails from the queue, and the queue size is now 50.
Between 3 PM and 4 PM, NeetoDesk processed the first ten emails, and now the queue size is 40. However, during this period, Joe sent another 82 emails. We know that the maximum queue size is 100. So the first 60 emails sent by Joe are added to the queue, which already has 40 emails. Now, the queue is at 100, which is the total capacity. So, the remaining 22 emails (82–60) will be discarded and not put in the queue.
Please contact us if you think you need to process more than ten emails per hour for any customer.