Your message to [Burpham Parish Meeting request email] couldn't be delivered.
paul wasn't found at pchallen.co.uk.
request-719785-eaa6e. . . Office 365 paul
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: 1/21/2021 9:59:36 AM
Sender Address: [FOI #719785 email]
Recipient [Burpham Parish Meeting request email]
Address:
Subject: Freedom of Information request - Byelaws relating to UAV
Flights
Error Details
Reported error: 550 5.1.10 RESOLVER.ADR.RecipientNotFound; Recipient
[Burpham Parish Meeting request email] not found by SMTP address lookup
DSN generated by: CWLP123MB3507.GBRP123.PROD.OUTLOOK.COM

Message Hops
HOP TIME FROM TO WITH RELAY
(UTC) TIME
1/21/2021 local (Exim 4.89) (envelope-from
1 9:59:36 foi owl.ukcod.org.uk <[FOI #719785 email]>) *
AM
1/21/2021 esmtps
2 9:59:37 owl.ukcod.org.uk starling.ukcod.org.uk (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) 1 sec
AM (Exim 4.89) (envelope-from
<[FOI #719785 email]>)
1/21/2021 Microsoft SMTP Server (version=TLS1_2,
3 9:59:37 mailer102.ukcod.org.uk CWLGBR01FT003.mail.protection.outlook.com cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) *
AM
1/21/2021 Microsoft SMTP Server (version=TLS1_2,
4 9:59:37 CWLGBR01FT003.eop-gbr01.prod.protection.outlook.com CWLP123CA0097.outlook.office365.com cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) *
AM
1/21/2021 Microsoft SMTP Server (version=TLS1_2,
5 9:59:37 CWLP123CA0097.GBRP123.PROD.OUTLOOK.COM CWLP123MB3507.GBRP123.PROD.OUTLOOK.COM cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) *
AM

Original Message Headers

Received: from CWLP123CA0097.GBRP123.PROD.OUTLOOK.COM (2603:10a6:401:5f::13)
by CWLP123MB3507.GBRP123.PROD.OUTLOOK.COM (2603:10a6:400:6e::14) with
Microsoft SMTP Server (version=TLS1_2,
cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3784.12; Thu, 21 Jan
2021 09:59:37 +0000
Received: from CWLGBR01FT003.eop-gbr01.prod.protection.outlook.com
(2603:10a6:401:5f:cafe::d7) by CWLP123CA0097.outlook.office365.com
(2603:10a6:401:5f::13) with Microsoft SMTP Server (version=TLS1_2,
cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3784.11 via Frontend
Transport; Thu, 21 Jan 2021 09:59:37 +0000
Authentication-Results: spf=pass (sender IP is 46.43.39.102)
smtp.mailfrom=whatdotheyknow.com; pchallen.co.uk; dkim=pass (signature was
verified) header.d=whatdotheyknow.com;pchallen.co.uk; dmarc=pass action=none
header.from=whatdotheyknow.com;
Received-SPF: Pass (protection.outlook.com: domain of whatdotheyknow.com
designates 46.43.39.102 as permitted sender) receiver=protection.outlook.com;
client-ip=46.43.39.102; helo=mailer102.ukcod.org.uk;
Received: from mailer102.ukcod.org.uk (46.43.39.102) by
CWLGBR01FT003.mail.protection.outlook.com (10.152.40.92) with Microsoft SMTP
Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id
15.20.3784.11 via Frontend Transport; Thu, 21 Jan 2021 09:59:37 +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=PNYpCNGVfuMllKUwNuSmytEu98klJEQXGdnt/LXZmQE=; b=RUuccxUSmc+ghKAEjy5seLmq5
NFHNKmahM/nirzlKGjU5BCDz7co36YkKkCPB2YzHJnMpBXoypfnuoBDmyc4JFF52t+bnyKoGSGUyK
sRT4Bdf41DiiKgiW7zccDP2KwLny7ahtUsXewjl9woteL+Mrdpwab1zvyFNjO2AaBPosg6mz2w5Sa
XE9mcwGNoQQ2LofleRqzs2oSy9jSO+/7K3VqnZWGPSDbJzrsER7ZaN0tlIc2M1gwh+pJCjSVMDyNA
N1XHYfvkLFihBW4f5R2RspkGHDhWaRmJcOTl2sqK8ofyu6FILCC2JBltijx1vre47fWMDqwtmZGJW
A4yLBbFNw==;
Received: from owl.ukcod.org.uk ([46.43.39.108]:41839)
by starling.ukcod.org.uk with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256)
(Exim 4.89)
(envelope-from <[FOI #719785 email]>)
id 1l2Wkb-00032g-1n
for [Burpham Parish Meeting request email]; Thu, 21 Jan 2021 09:59:37 +0000
Received: from foi by owl.ukcod.org.uk with local (Exim 4.89)
(envelope-from <[FOI #719785 email]>)
id 1l2Wka-0005w1-TT
for [Burpham Parish Meeting request email]; Thu, 21 Jan 2021 09:59:36 +0000
Date: Thu, 21 Jan 2021 09:59:36 +0000
From: Simon Hawkins <[FOI #719785 email]>
To: FOI requests at Burpham Parish Meeting <[Burpham Parish Meeting request email]>
Message-ID: <[email address]>
Subject: Freedom of Information request - Byelaws relating to UAV Flights
MIME-Version: 1.0
Content-Type: text/plain;
charset=UTF-8
Content-Transfer-Encoding: 7bit
Return-Path: [FOI #719785 email]
X-EOPAttributedMessage: 0
X-EOPTenantAttributedMessage: 33754f6d-9e4d-4133-9772-d9c5191dd8c9:0
X-MS-PublicTrafficType: Email
X-MS-Office365-Filtering-Correlation-Id: e6c4827b-22f2-4cd0-f8db-08d8bdf34338
X-MS-TrafficTypeDiagnostic: CWLP123MB3507:

References

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

Thank you for your enquiry.
Burpham Parish Meeting has introduced no byelaws on this matter.
Burpham Parish Meeting owns no land, so will have no policies relating to
the use of UAVs on its land.
All good wishes
Trevor Cooper, on behalf of Paul Challen, Chair of Burpham Parish Meeting

show quoted sections