# What is RateLimiter::LimitExceeded for incoming email?

**URL:** <https://meta.discourse.org/t/what-is-ratelimiter-limitexceeded-for-incoming-email/39737>\
**Category:** Support\
**Created:** [February 17, 2016, 3:15pm UTC](https://meta.discourse.org/t/what-is-ratelimiter-limitexceeded-for-incoming-email/39737 "2016-02-17T15:15:24Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![downey](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/downey/32/166878_2.png) [@downey](https://meta.discourse.org/u/downey)\
**Post date:** [February 17, 2016, 3:15pm UTC](https://meta.discourse.org/t/what-is-ratelimiter-limitexceeded-for-incoming-email/39737/1 "2016-02-17T15:15:24Z")

</div>

Today I got an item in my “Rejected” emails log with the error:

> RateLimiter::LimitExceeded

However, there’s no description about why this occurred. Can anyone shed some light? It’s the only such instance of the error in our logs.

---

<div class="post-metadata">

**Author:** ![zogstrip](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/zogstrip/32/512781_2.png) [@zogstrip](https://meta.discourse.org/u/zogstrip)\
**Post date:** [February 17, 2016, 3:34pm UTC](https://meta.discourse.org/t/what-is-ratelimiter-limitexceeded-for-incoming-email/39737/2 "2016-02-17T15:34:34Z")

</div>

It happens when you replying to the same topic too fast and/or too often. Were you replying to a public or private post?

---

<div class="post-metadata">

**Author:** ![downey](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/downey/32/166878_2.png) [@downey](https://meta.discourse.org/u/downey)\
**Post date:** [February 17, 2016, 3:41pm UTC](https://meta.discourse.org/t/what-is-ratelimiter-limitexceeded-for-incoming-email/39737/3 "2016-02-17T15:41:20Z")

</div>

The user, a TL2, did send 2 email replies about the same time. One (which was accepted) was a reply to a PM, and one (which was rejected above) was a reply to a public topic.

---

<div class="post-metadata">

**Author:** ![tobiaseigen](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/tobiaseigen/32/539204_2.png) [@tobiaseigen](https://meta.discourse.org/u/tobiaseigen)\
**Post date:** [April 6, 2016, 3:02pm UTC](https://meta.discourse.org/t/what-is-ratelimiter-limitexceeded-for-incoming-email/39737/4 "2016-04-06T15:02:47Z")

</div>

I’m seeing a bunch of these in our logs as well.

It seems to me that rate limiting should be more generous for topics and posts contributed by email than by website. Is it?

---

<div class="post-metadata">

**Author:** ![zogstrip](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/zogstrip/32/512781_2.png) [@zogstrip](https://meta.discourse.org/u/zogstrip)\
**Post date:** [April 6, 2016, 4:18pm UTC](https://meta.discourse.org/t/what-is-ratelimiter-limitexceeded-for-incoming-email/39737/5 "2016-04-06T16:18:11Z")

</div>

> [@tobiaseigen](#):
>
> It seems to me that rate limiting should be more generous for topics and posts contributed by email than by website. Is it?

The issue is that we poll emails every 5 minutes or so and then create posts in batch, thus hitting the rate limits. The solution is unfortunately not easy

> [@Replying too quickly ... By email?](https://meta.discourse.org/t/replying-too-quickly-by-email/41562/7):
>
> That is super duper hard to do, not feasible at all the way rate limits are implemented. I think the simplest thing to do here @zogstrip is to queue the post for processing in N (30) seconds if you hit a rate limit, then if it tries N times (3) then fail out. That way its pretty easy to implement and will not involve a lot of complicated bypasses to rate limits.

---

<div class="post-metadata">

**Author:** ![zogstrip](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/zogstrip/32/512781_2.png) [@zogstrip](https://meta.discourse.org/u/zogstrip)\
**Post date:** [April 6, 2016, 4:18pm UTC](https://meta.discourse.org/t/what-is-ratelimiter-limitexceeded-for-incoming-email/39737/6 "2016-04-06T16:18:39Z")

</div>


