We don't know whether the most recent response to this request contains information or not – if you are Cllr Lorraine Yeadon please sign in and let everyone know.

Mechanical vehicles

Cllr Lorraine Yeadon made this Freedom of Information request to North Lincolnshire Council Automatic anti-spam measures are in place for this older request. Please let us know if a further response is expected or if you are having trouble responding.

We're waiting for Cllr Lorraine Yeadon to read recent responses and update the status.

Cllr Lorraine Yeadon

Dear North Lincolnshire Council,

For all mechanical vehicles involved in waste collection and street cleansing please state for years 2022/2023 : a list of all vehicles held, purchase date, cost, the actual/expected replacement date.

And for 2022/2023, the number of days vehicles were not used because of needing repair.

Yours faithfully,

Cllr Lorraine Yeadon

Information Governance Team,

Dear Cllr Lorraine Yeadon,

Thank you for your request which was received on 24th May. The estimate
response date for your request is the 22nd June.

Should you have any queries, amendments or additions relating to this
request, please remember to quote the reference number above in any future
communications.

Yours Faithfully

Information Governance Team
North Lincolnshire Council

Cllr Lorraine Yeadon

Dear Information Governance Team,

Hello,

Are you able provide an update on this yet please?

Yours sincerely,

Cllr Lorraine Yeadon

North Lincolnshire Council

2 Attachments

Your message to [email address] couldn't be delivered.
request wasn't found at ig.northlincs.gov.uk.
request-983940-58f02. . . Office 365 request
Action Required Recipient
Unknown To address
How to Fix It
The address may be misspelled or may not exist. Try one or more of the
following:
β€’Β Send the message again following these steps: In Outlook, open this
non-delivery report (NDR) and choose Send Again from the Report
ribbon. In Outlook on the web, select this NDR, then select the link
"To send this message again, click here." Then delete and retype the
entire recipient address. If prompted with an Auto-Complete List
suggestion don't select it. After typing the complete address, click
Send.
β€’Β Contact the recipient (by phone, for example) to check that the
address exists and is correct.
β€’Β The recipient may have set up email forwarding to an incorrect
address. Ask them to check that any forwarding they've set up is
working correctly.
β€’Β Clear the recipient Auto-Complete List in Outlook or Outlook on the
web by following the steps in this article: [1]Fix email delivery
issues for error code 5.1.10 in Office 365, and then send the message
again. Retype the entire recipient address before selecting Send.
If the problem continues, forward this message to your email admin. If
you're an email admin, refer to the More Info for Email Admins section
below.
Was this helpful? [2]Send feedback to Microsoft.
══════════════════════════════════════════════════════════════════════════
More Info for Email Admins
Status code: 550 5.1.10

This error occurs because the sender sent a message to an email address
hosted by Office 365 but the address is incorrect or doesn't exist at the
destination domain. The error is reported by the recipient domain's email
server, but most often it must be fixed by the person who sent the
message. If the steps in the How to Fix It section above don't fix the
problem, and you're the email admin for the recipient, try one or more of
the following:

The email address exists and is correct - Confirm that the recipient
address exists, is correct, and is accepting messages.

Synchronize your directories - If you have a hybrid environment and are
using directory synchronization make sure the recipient's email address is
synced correctly in both Office 365 and in your on-premises directory.

Errant forwarding rule - Check for forwarding rules that aren't behaving
as expected. Forwarding can be set up by an admin via mail flow rules or
mailbox forwarding address settings, or by the recipient via the Inbox
Rules feature.

Recipient has a valid license - Make sure the recipient has an Office 365
license assigned to them. The recipient's email admin can use the Office
365 admin center to assign a license (Users > Active Users > select the
recipient > Assigned License > Edit).

Mail flow settings and MX records are not correct - Misconfigured mail
flow or MX record settings can cause this error. Check your Office 365
mail flow settings to make sure your domain and any mail flow connectors
are set up correctly. Also, work with your domain registrar to make sure
the MX records for your domain are configured correctly.

For more information and additional tips to fix this issue, see [3]Fix
email delivery issues for error code 5.1.10 in Office 365.
Original Message Details
Created Date: 6/28/2023 9:41:48 AM
Sender Address: [FOI #983940 email]
Recipient Address: [email address]
Subject: Re: Freedom of Information Case FOI2023/00796
Error Details
Error: 550 5.1.10 RESOLVER.ADR.RecipientNotFound; Recipient
[email address] not found by SMTP address
lookup
Message rejected LO4P265MB6493.GBRP265.PROD.OUTLOOK.COM
by:
Notification Details
Sent by: LO4P265MB6493.GBRP265.PROD.OUTLOOK.COM

Message Hops
HOP TIME FROM TO WITH RELAY
(UTC) TIME
6/28/2023 local (Exim 4.94.2) (envelope-from
1 9:41:48 foi mstrwdtkhexa.srv.mysociety.org <[FOI #983940 email]>) *
AM
6/28/2023 esmtps (TLS1.3) tls
2 9:41:48 mstrwdtkhexa.srv.mysociety.org mslb001hexa.srv.mysociety.org TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim *
AM 4.94.2) (envelope-from
<[FOI #983940 email]>)
6/28/2023 Microsoft SMTP Server (version=TLS1_2,
3 9:41:49 mslb001hexa.srv.mysociety.org LO2GBR01FT009.mail.protection.outlook.com cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) 1Β sec
AM
6/28/2023 Microsoft SMTP Server (version=TLS1_2,
4 9:41:49 LO2GBR01FT009.eop-gbr01.prod.protection.outlook.com LO4P265CA0027.outlook.office365.com cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) *
AM
6/28/2023 Microsoft SMTP Server (version=TLS1_2,
5 9:41:49 LO4P265CA0027.GBRP265.PROD.OUTLOOK.COM LO4P265MB6493.GBRP265.PROD.OUTLOOK.COM cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) *
AM

Original Message Headers

Received: from LO4P265CA0027.GBRP265.PROD.OUTLOOK.COM (2603:10a6:600:2ae::17)
by LO4P265MB6493.GBRP265.PROD.OUTLOOK.COM (2603:10a6:600:2e4::12) with
Microsoft SMTP Server (version=TLS1_2,
cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.6521.26; Wed, 28 Jun
2023 09:41:49 +0000
Received: from LO2GBR01FT009.eop-gbr01.prod.protection.outlook.com
(2603:10a6:600:2ae:cafe::7d) by LO4P265CA0027.outlook.office365.com
(2603:10a6:600:2ae::17) with Microsoft SMTP Server (version=TLS1_2,
cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.6544.19 via Frontend
Transport; Wed, 28 Jun 2023 09:41:49 +0000
Authentication-Results: spf=pass (sender IP is 93.93.130.118)
smtp.mailfrom=whatdotheyknow.com; dkim=pass (signature was verified)
header.d=whatdotheyknow.com;dmarc=pass action=none
header.from=whatdotheyknow.com;
Received-SPF: Pass (protection.outlook.com: domain of whatdotheyknow.com
designates 93.93.130.118 as permitted sender)
receiver=protection.outlook.com; client-ip=93.93.130.118;
helo=mslb001hexa.srv.mysociety.org; pr=C
Received: from mslb001hexa.srv.mysociety.org (93.93.130.118) by
LO2GBR01FT009.mail.protection.outlook.com (10.152.42.95) with Microsoft SMTP
Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id
15.20.6544.20 via Frontend Transport; Wed, 28 Jun 2023 09:41:49 +0000
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed;
d=whatdotheyknow.com; s=2020a.mysociety; h=Content-Transfer-Encoding:
Content-Type:Mime-Version:Subject:Message-ID:To:From:Date:Sender:Reply-To:Cc:
Content-ID:Content-Description:Resent-Date:Resent-From:Resent-Sender:
Resent-To:Resent-Cc:Resent-Message-ID:In-Reply-To:References:List-Id:
List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive;
bh=1wqQFE44O4p4aOa8NMFzpo1vLClZmlgwShhi3idEEgs=; b=tiT3kViex1oQ5uP4eWXbY2/5CK
TbsxRDBw79owI4KDWwCzpK9h7vaWrHoP5qoH03hjO/I6jWVbDrvwevucepdm8Pj9DpcNMXCjXBBc4
npCaZRaMe4wS0Hgw7VIRDWhXgRVIglirtkNidvLjuc6pXgiSJE0/wPO2ZrFz3k9TliNHiUyPh+fXN
QAKrR00jpQyOpPEsoAvKHa6CwXPdbQpB2EtQilQ4VcnKBwQ60pW2tZYH5j8A5w7ClKTP8bha8qpFM
1ah5IXqfzVdRcuk8pqdzfEbPqKY8zRLEY22UnA1DZ34I9tJgvexeIKuEMqkuA1GZjD+TyFaTPdzEs
LUuxHoQA==;
Received: from mstrwdtkhexa.srv.mysociety.org ([2a00:1098:82:dd::10:1]:57732)
by mslb001hexa.srv.mysociety.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
(Exim 4.94.2)
(envelope-from <[FOI #983940 email]>)
id 1qERgK-009rUr-LL
for [email address]; Wed, 28 Jun 2023 09:41:48 +0000
Received: from foi by mstrwdtkhexa.srv.mysociety.org with local (Exim 4.94.2)
(envelope-from <[FOI #983940 email]>)
id 1qERgK-0067Rg-A6
for [email address]; Wed, 28 Jun 2023 10:41:48 +0100
Date: Wed, 28 Jun 2023 10:41:48 +0100
From: Cllr Lorraine Yeadon <[FOI #983940 email]>
To: Information Governance Team <[email address]>
Message-ID: <[email address]>
Subject: Re: Freedom of Information Case FOI2023/00796
MIME-Version: 1.0
Content-Type: text/plain;
charset=UTF-8
Content-Transfer-Encoding: 7bit
Return-Path: [FOI #983940 email]
X-EOPAttributedMessage: 0
X-EOPTenantAttributedMessage: 586655ed-2cff-4089-8197-b4c10b7b3da3:0
X-MS-PublicTrafficType: Email
X-MS-TrafficTypeDiagnostic: LO2GBR01FT009:EE_|LO4P265MB6493:EE_
X-MS-Office365-Filtering-Correlation-Id: 93d05003-4a0f-4dbd-7a64-08db77bbe52f

References

Visible links
1. https://go.microsoft.com/fwlink/?LinkId=...
2. https://go.microsoft.com/fwlink/?LinkId=...
3. https://go.microsoft.com/fwlink/?LinkId=...

Information Governance Team,

1 Attachment

  • Attachment

    Information Disclosure FOI2023 00796.odt

    638K Download

Dear Cllr Lorraine Yeadon,

I am writing in response to your request for information, that was
received on the 24th May. Please find our Information Disclosure letter
attached.

If we can be of any further assistance with regard to this request please
let us know quoting the above reference number.

Yours sincerely,

Information Governance Team
North Lincolnshire Council

We don't know whether the most recent response to this request contains information or not – if you are Cllr Lorraine Yeadon please sign in and let everyone know.