aboutsummaryrefslogtreecommitdiffstats
path: root/docs/running/holding_pen.md
diff options
context:
space:
mode:
authorDave Whiteland <dave@mysociety.org>2015-03-03 18:24:24 +0000
committerDave Whiteland <dave@mysociety.org>2015-03-03 18:24:24 +0000
commitadaf4b533a66a03336e5d0a354ff6fb020b8afcc (patch)
tree34a58174ce3ebf161e94e9d164166c5fa0a14712 /docs/running/holding_pen.md
parent8e68ef7d568e02c2d2e96209960034e7266413bc (diff)
link to managing requests from holding pen explanation
Diffstat (limited to 'docs/running/holding_pen.md')
-rw-r--r--docs/running/holding_pen.md3
1 files changed, 2 insertions, 1 deletions
diff --git a/docs/running/holding_pen.md b/docs/running/holding_pen.md
index 24d8079b0..bceec7346 100644
--- a/docs/running/holding_pen.md
+++ b/docs/running/holding_pen.md
@@ -67,7 +67,8 @@ There are several reasons why a message might end up in the holding pen:
the sender, or simply deleting it). Responses may be rejected for various
reasons &mdash; for example, if a response is sent from an unrecognised
email address for a request whose *Allow new responses from* setting is
- `authority_only`.
+ `authority_only`. See instructions on
+ [how to manage requests]({{site.baseurl}}docs/running/requests/) for details.
## What to do: redeliver or delete