Public Space Protection Orders

The request was partially successful.

Dear North Lincolnshire Council,

Public Space Protection Orders with the borough of North Lincolnshire

With regards to the above, I wish to find out how many Public Space Protection Orders are currently in force within the Council area and on what dates each order was made and came into force.

Yours faithfully,

Natalie Muir

Information Governance Team,

Dear Natalie Muir,

Thank you for your request which was received on 2nd March. The estimate
response date for your request is the 30th March.

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

Information Governance Team,

1 Attachment

  • Attachment

    Information Disclosure FOI2023 00357.odt

    638K Download

Dear Natalie Muir,

I am writing in response to your request for information, that was
received on the 2nd March. 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

Dear Information Governance Team,

Thank you for your email. I've had a look at the website and I'm not entirely sure if there is one order or four (and there are five maps in total). Would it be possible to clarify that for me?

Yours sincerely,

Natalie Muir

North Lincolnshire Council

2 Attachments

Your message to [email address] couldn't be delivered.
request wasn't found at ig.northlincs.gov.uk.
request-955997-8f69e. . . 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: 3/3/2023 4:10:17 PM
Sender Address: [FOI #955997 email]
Recipient Address: [email address]
Subject: Re: Freedom of Information - Ref: FOI2023/00357
Error Details
Reported error: 550 5.1.10 RESOLVER.ADR.RecipientNotFound; Recipient
[email address] not found by SMTP address
lookup
DSN generated by: LO6P265MB7381.GBRP265.PROD.OUTLOOK.COM

Message Hops
HOP TIME FROM TO WITH RELAY
(UTC) TIME
3/3/2023 local (Exim 4.94.2) (envelope-from
1 4:10:17 foi mstrwdtkhexa.srv.mysociety.org <[FOI #955997 email]>) *
PM
3/3/2023 esmtps (TLS1.3) tls
2 4:10:17 mstrwdtkhexa.srv.mysociety.org mslb001hexa.srv.mysociety.org TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim *
PM 4.94.2) (envelope-from
<[FOI #955997 email]>)
3/3/2023 Microsoft SMTP Server (version=TLS1_2,
3 4:10:18 mslb001hexa.srv.mysociety.org LO2GBR01FT035.mail.protection.outlook.com cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) 1 sec
PM
3/3/2023 Microsoft SMTP Server (version=TLS1_2,
4 4:10:18 LO2GBR01FT035.eop-gbr01.prod.protection.outlook.com LO2P265CA0471.outlook.office365.com cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) *
PM
3/3/2023 Microsoft SMTP Server (version=TLS1_2,
5 4:10:18 LO2P265CA0471.GBRP265.PROD.OUTLOOK.COM LO6P265MB7381.GBRP265.PROD.OUTLOOK.COM cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) *
PM

Original Message Headers

Received: from LO2P265CA0471.GBRP265.PROD.OUTLOOK.COM (2603:10a6:600:a2::27)
by LO6P265MB7381.GBRP265.PROD.OUTLOOK.COM (2603:10a6:600:326::13) with
Microsoft SMTP Server (version=TLS1_2,
cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.6156.21; Fri, 3 Mar
2023 16:10:18 +0000
Received: from LO2GBR01FT035.eop-gbr01.prod.protection.outlook.com
(2603:10a6:600:a2:cafe::5f) by LO2P265CA0471.outlook.office365.com
(2603:10a6:600:a2::27) with Microsoft SMTP Server (version=TLS1_2,
cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.6156.22 via Frontend
Transport; Fri, 3 Mar 2023 16:10:18 +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
LO2GBR01FT035.mail.protection.outlook.com (10.152.42.162) with Microsoft SMTP
Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id
15.20.6156.19 via Frontend Transport; Fri, 3 Mar 2023 16:10:18 +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=Yp4VUfvQEeKNteuGc7+4SMtq4W+pU9IshAbXr9E/Fnk=; b=LsvGGpnOx9yZY5z2YTpG3QpNl7
pxs92BmyNRCdj/8mWS48eGJo6xorWly7XLRNJC6LqQZfMor5K+w3zPDac0SCh2vkuUTXiDRQQkggO
7iab51Rs0tbygweV8fEuoHru14lGPtE0392VPyIIP1/3uzcDhU3mKdd5YxDQzu3bclE0LMCSd04H1
MYCAAm6szDlogiNzDn6EItbi568lkQc0KWDXZteeqV6yCA3RxbtiWVWwwaqd9M5rEw0UjUMcaLhV0
CcVtcrQIPQrvvfoYIRrQnWWEuAfUbDw3R3Dzko9+ewapHNTDzVhb6oPy7zw7JqzZNjgx0sxOjg/ew
iMHXbsHg==;
Received: from mstrwdtkhexa.srv.mysociety.org ([2a00:1098:82:dd::10:1]:42458)
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 #955997 email]>)
id 1pY7z8-00FIdH-Lz
for [email address]; Fri, 03 Mar 2023 16:10:17 +0000
Received: from foi by mstrwdtkhexa.srv.mysociety.org with local (Exim 4.94.2)
(envelope-from <[FOI #955997 email]>)
id 1pY7z7-00BGfl-IU
for [email address]; Fri, 03 Mar 2023 16:10:17 +0000
Date: Fri, 03 Mar 2023 16:10:17 +0000
From: Natalie Muir <[FOI #955997 email]>
To: Information Governance Team <[email address]>
Message-ID: <[email address]>
Subject: Re: Freedom of Information - Ref: FOI2023/00357
MIME-Version: 1.0
Content-Type: text/plain;
charset=UTF-8
Content-Transfer-Encoding: 7bit
Return-Path: [FOI #955997 email]
X-EOPAttributedMessage: 0
X-EOPTenantAttributedMessage: 586655ed-2cff-4089-8197-b4c10b7b3da3:0
X-MS-PublicTrafficType: Email
X-MS-TrafficTypeDiagnostic: LO2GBR01FT035:EE_|LO6P265MB7381:EE_
X-MS-Office365-Filtering-Correlation-Id: fd0fbb3a-1db6-4cdc-e7ed-08db1c01c83d

References

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

Natalie Muir left an annotation ()

Council have specified this information is available on the Council website but the information there does not specifically answer my question.