Hello community! Linagora-email-team proposes the email rate-limit feature to James.
Rate limiting is one of the common features. Examples: SaaS is one https://www.fastmail.help/hc/en-us/articles/1500000277382-Account-limits#sending/receiving, https://support.google.com/mail/answer/22839 They limit how many emails you can send/receive from/to each email account over a given period of time. We believe the rate-limiting will help James have more control of the resource and easy to dynamic config the user policy. It also complements the storage quota. We propose to set up a new maven project dedicated to rating limiting. We propose two implementations of rate limitings: in-memory (guava based) and Redis. Please note that this will take the form of extension jars, that could be dropped in one James installation, and thus is optional, and not of a runtime dependency. We will enable rate-limiting on the count of emails and total size for sending and receiving use cases. JIRA link: https://issues.apache.org/jira/browse/JAMES-3693 Best regards, Tung, TRAN VAN
