The *last* date to respond to this request is today. If the DCC fails to respond I would urge you to immediately lodge a delay complaint with the Ombudsman.

Emails to the DCC official information address have been bouncing and retrying for a few weeks (looked like they had misconfigured it to forward to another address). I have just forced a resend and it appears to have delivered OK now.
- Oliver (admin)

Just noting that re-sending the request starts the clock again.

I don't believe the DCC deserves that given the continual problems with LGOIMA's (especially those using fyi.org) and the never-ending problems with what it calls *improvements* to communications that it then uses to justify failing to do whatever it is supposed to have done.

Hi Karen,

Resending does reset the due date shown here, and I don't have a way to change that sorry. Our displayed due date is not definitive or affect legal obligations. I recommend checking with the calculator on the front page of https://www.ombudsman.parliament.nz/.

What matters is when the request was "received" by the agency, which is when it enters the "designated information system". Our logs show DCC's email server accepting our emails for delivery. Between 1 and 60 minutes later we receive two bounce messages. Whether this counts as "received" would be up to the Ombudsman.

I raised the problem with DCC on 20 March, who said they are looking into it. We have received more bounce messages and not received any update. Since I have not had any update from them, I have switched to their general contact address, not their published LGOIMA one. So far it has not bounced.

Oliver

Hi Oliver, thanks for responding.

I too contacted the DCC (on 22 March) and was informed the DCC was working with fyi to solve the problem. (As if the problem was at fyi end!)

I just checked and all the email validators I used are reporting that officialinformation@dcc.govt.nz is responding with a 451 (temporarily unavailable) so it appears nothing has been corrected.

I will try to find time to raise this again this week - the more voices, the faster the action.

In the mean-time, thank you for manually sending the requests on.

Just to close off the comments above: the issue has been resolved by DCC's IT provider. Although it initially took a few weeks, they were very helpful this week and we have confirmed through testing that the problem is resolved.

Despite the bounces we saw, I believe this should not have stopped the messages being delivered to the people who needed to receive them. But this is not something I can be certain of.