aboutsummaryrefslogtreecommitdiffstats
path: root/docs
diff options
context:
space:
mode:
authorDave Whiteland <dave@mysociety.org>2015-03-03 13:44:00 +0000
committerDave Whiteland <dave@mysociety.org>2015-03-03 13:44:00 +0000
commitcb33b7c468ab01c40e2ef03ad6511f7873a881d9 (patch)
treebc8b6fc41022e29145798cd8ff216c02eb68b777 /docs
parented551bea6c10ddc03f99dd62cf978c61acaee0bc (diff)
remove section: multiple to-addresses don't behave this way
Diffstat (limited to 'docs')
-rw-r--r--docs/running/holding_pen.md6
1 files changed, 0 insertions, 6 deletions
diff --git a/docs/running/holding_pen.md b/docs/running/holding_pen.md
index f957d4752..d791f609c 100644
--- a/docs/running/holding_pen.md
+++ b/docs/running/holding_pen.md
@@ -50,12 +50,6 @@ There are several reasons why a message might end up in the holding pen:
for example if the person at the authority accidentally loses the first
letter of the email address when they copy-and-paste it. Or if they copy
it manually and simply get it wrong.
-
-* **the message is sent to multiple (valid) email addresses and one bad one**<br>
- Sometimes an officer working for an authority may attempt to send email using
- a collection of email addresses for your site. This is allowed, and the
- response will be sent to each of them. However, if any of those addresses
- are wrong (even just one), the response will go into the holding pen.
* **there's something unusual about the way it was sent**<br>
For example, if it was delivered here because the address is in the `Bcc:`