# Replying too quickly ... By email?

**URL:** https://meta.discourse.org/t/replying-too-quickly-by-email/41562
**Category:** Bug
**Created:** [March 25, 2016, 2:21pm UTC](https://meta.discourse.org/t/replying-too-quickly-by-email/41562 "2016-03-25T14:21:46Z")
**Posts on this page:** 14
**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: [March 25, 2016, 2:21pm UTC](https://meta.discourse.org/t/replying-too-quickly-by-email/41562/1 "2016-03-25T14:21:46Z")

</div>

Something about this scenario doesn’t seem right. First of all, I don’t know how I could possibly reply too fast by email, but so it doesn’t even seem like a reasonable thing to block given the latency of email. And how could I reply in any faster than 5 seconds?

 ![](https://global.discourse-cdn.com/meta/original/3X/3/b/3bb340e997c9978f00e16b9dde7ffd5d3ff63b29.png)

---

<div class="post-metadata">

### Author: ![DeanMarkTaylor](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/deanmarktaylor/32/102462_2.png) [@DeanMarkTaylor](https://meta.discourse.org/u/DeanMarkTaylor)
#### Post date: [March 25, 2016, 2:24pm UTC](https://meta.discourse.org/t/replying-too-quickly-by-email/41562/2 "2016-03-25T14:24:24Z")

</div>

I’m guessing the issue is because:

- emails are collected by polling
- several emails are collected via POP3 at the same time
- you sent several emails that when processed in a queue registered as posting too quickly.

---

<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: [March 25, 2016, 2:42pm UTC](https://meta.discourse.org/t/replying-too-quickly-by-email/41562/3 "2016-03-25T14:42:55Z")

</div>

Yeah, that seems the likely culprit. But that polling queue shouldn’t be the fault of the user, no? Should email processing be exempted from the rate limit? (Or at least set much higher?)

---

<div class="post-metadata">

### Author: ![DeanMarkTaylor](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/deanmarktaylor/32/102462_2.png) [@DeanMarkTaylor](https://meta.discourse.org/u/DeanMarkTaylor)
#### Post date: [March 25, 2016, 3:21pm UTC](https://meta.discourse.org/t/replying-too-quickly-by-email/41562/4 "2016-03-25T15:21:48Z")

</div>

It should probably use the times on the emails themselves to check the frequency of replies.

---

<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: [March 25, 2016, 3:32pm UTC](https://meta.discourse.org/t/replying-too-quickly-by-email/41562/5 "2016-03-25T15:32:28Z")

</div>

Yeah, that sounds sane.

---

<div class="post-metadata">

### Author: ![sam](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/sam/32/102149_2.png) [@sam](https://meta.discourse.org/u/sam)
#### Post date: [March 31, 2016, 9:18am UTC](https://meta.discourse.org/t/replying-too-quickly-by-email/41562/7 "2016-03-31T09:18:23Z")

</div>

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: ![codinghorror](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/codinghorror/32/110067_2.png) [@codinghorror](https://meta.discourse.org/u/codinghorror)
#### Post date: [May 28, 2016, 9:39am UTC](https://meta.discourse.org/t/replying-too-quickly-by-email/41562/8 "2016-05-28T09:39:32Z")

</div>



---

<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: [May 30, 2016, 7:49am UTC](https://meta.discourse.org/t/replying-too-quickly-by-email/41562/9 "2016-05-30T07:49:30Z")

</div>



---

<div class="post-metadata">

### Author: ![sam](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/sam/32/102149_2.png) [@sam](https://meta.discourse.org/u/sam)
#### Post date: [July 1, 2016, 1:31am UTC](https://meta.discourse.org/t/replying-too-quickly-by-email/41562/10 "2016-07-01T01:31:47Z")

</div>

Note, we still want to fix this, it is not easy.

Our hosted customers no longer have this problem since emails are processed immediately and not in 5 minute batches.

---

<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: [July 1, 2016, 1:31pm UTC](https://meta.discourse.org/t/replying-too-quickly-by-email/41562/11 "2016-07-01T13:31:09Z")

</div>

> [@sam](#):
>
> emails are processed immediately

Is this something that we mere mortals can configure? 🙂

---

<div class="post-metadata">

### Author: ![erlend\_sh](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/erlend_sh/32/119475_2.png) [@erlend\_sh](https://meta.discourse.org/u/erlend_sh)
#### Post date: [July 4, 2016, 7:37am UTC](https://meta.discourse.org/t/replying-too-quickly-by-email/41562/12 "2016-07-04T07:37:43Z")

</div>

Unfortunately no, since we’re running our own email server in order to get around this, so it’s really a matter of infrastructure, not basic configuration.

---

<div class="post-metadata">

### Author: ![sam](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/sam/32/102149_2.png) [@sam](https://meta.discourse.org/u/sam)
#### Post date: [July 13, 2016, 4:05am UTC](https://meta.discourse.org/t/replying-too-quickly-by-email/41562/13 "2016-07-13T04:05:23Z")

</div>

@zogstrip I would love to see this fixed for 1.6, it’s quite harsh when it happens.

---

<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: [August 8, 2016, 8:30pm UTC](https://meta.discourse.org/t/replying-too-quickly-by-email/41562/14 "2016-08-08T20:30:06Z")

</div>

Ok, let’s try this 🌰

[https://github.com/discourse/discourse/commit/51322a46b3fabab11cfa8f29ac4f386d8227aedf](https://github.com/discourse/discourse/commit/51322a46b3fabab11cfa8f29ac4f386d8227aedf)

---

<div class="post-metadata">

### Author: ![codinghorror](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/codinghorror/32/110067_2.png) [@codinghorror](https://meta.discourse.org/u/codinghorror)
#### Post date: [August 11, 2016, 10:47pm UTC](https://meta.discourse.org/t/replying-too-quickly-by-email/41562/15 "2016-08-11T22:47:49Z")

</div>

This topic was automatically closed after 3 days. New replies are no longer allowed.
