improve workflow for dealing with holding pen emails

[mysociety]

improve workflow for dealing with holding pen emails

[bjh21]

Other plausible heuristics:

• look for matching subject lines, either in outgoing requests or in other incoming messages
• find other messages with the same broken destination address (since authorities often reuse their typos)

[hsenag]

It would also be helpful to have a diagnostic message as to why the message ended up in the holding pen.

[sebbacon]

Opened separate issue for diagnostic message

[sebbacon]

The guessed request should have a button next to it to just accept that guess. Right now you have to cut and paste to another box.

Isn't that what the "redliver to another request" field is doing? If I look at something in the holding pen right now, I see a guessed request at the top, and then under "Actions":

id or url_title of request:    [education_2]  <redeliver to another request>

(Where education_2 is the url_name of the guessed request)

[skenaja]

That was introduced in this commit:

sebbacon@b537056

I added this comment to the commit which would also be useful:
"Could you also append in the name of the requester & the authority to the text of the guessed request?"

[hsenag]

The pre-population does indeed fulfill that requirement nicely.

[sebbacon]

@skenaja, do you mean in addition to making request text appear inline with guessed email, as per issue #110?

[skenaja]

yep - the proposal in #110 would satisfy this

it might be worth separately considering reducing the length of the hash to 3-4 chars (which would reduce authority typos), most of the spam requests attract is due to email addresses being exposed through google's OCR of scanned docs, rather than brute force guesses.

[sebbacon]

Closing, as I've captured the other suggestions in issue #110, issue #117, issue #118, issue #119, issue #120