The following mailets utilize Redis for rate-limiting computations: GlobalRateLimit, PerRecipientRateLimit, and PerSenderRateLimiter.
Currently, the lecture library (utilized by the ratelimitj library) connects to Redis with a default timeout of 60 seconds. This default timeout is quite long for a mailet.
The mailet supports configuration with the redisTimeoutException parameter, which defaults to None.
Eg: <redisTimeoutException>5000</redisTimeoutException>
Why?
The following mailets utilize Redis for rate-limiting computations:
GlobalRateLimit
,PerRecipientRateLimit
, andPerSenderRateLimiter
. Currently, thelecture
library (utilized by theratelimitj
library) connects to Redis with a default timeout of 60 seconds. This default timeout is quite long for a mailet.Ref: https://github.com/linagora/tmail-backend/issues/1013
How
The mailet supports configuration with the
redisTimeoutException
parameter, which defaults toNone
. Eg:<redisTimeoutException>5000</redisTimeoutException>
Dod