mysociety
When we send a rejection include some identifier of the request in the exim logs
This would have made debugging https://github.com/mysociety/sysadmin/issues/928 much easier.
[10:56:32] <gareth> what are our options there? what can exim see?
[10:56:56] <gareth> I guess To, Cc, Bcc, From, Subject?
[10:59:00] <sam> Hmm. Usually we rely on the request address, but the rejections use the generic do-not-reply one. Potentially include the numeric ID in the subject, if this isn’t too confusing I suppose?
[10:59:32] <gareth> hmm, its not ideal really. The subject is currently "Your response to an FOI request was not delivered"
[11:00:24] <sam> Can I come back to you in a bit? I’m just wading through some other code…
[11:01:05] <gareth> no worries – I'll ticket as above. I was just checking I wasn't missing something obvious like "Oh just add a header" or sthn
[11:01:28] <sam> It might be that easy, I just need to check what we can get into the logs to be sure.
Just to note including the request number in the subject line would have been useful on a few occasions recently on WhatDoTheyKnow.
On the most recent occasion, the Authority appear to have recognised the bounce message as an FOI request!
They've replied to the bounce message including their reference number, and our subject. If [xxxxxx] for the request number on WDTK was appended to the end of the subject, we would be able to reopen the request ready for the authority to try sending again. As they haven't included the full text of the auto-response, we cannot see the request email address.
We should perhaps include the request number in the subject line of these automatic messages (if known) so we can quickly locate the relevant thread and re-open it if necessary.
I would definitely agree with the request ID in the subject line. We often get emails in the WDTK support inbox along the lines of one we've just received: Subject: RE: Your response to an FOI request was not delivered Body: Auto Reply. Thank you for your email (without quoting the email)
This is desirable, but unlikely to be worked on in the next 12 months so closing for now.