Your message to [Selsey Town Council request email] couldn't be
delivered.
gill.jennings wasn't found at selseytowncouncil.gov.uk.
request-837678-3ec7a. . . Office 365 gill.jennings
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/1/2022 11:26:26 AM
Sender Address: [FOI #837678 email]
Recipient [Selsey Town Council request email]
Address:
Subject: Freedom of Information request - Climate Change Agenda
2022
Error Details
Reported error: 550 5.1.10 RESOLVER.ADR.RecipientNotFound; Recipient
[Selsey Town Council request email] not found by SMTP
address lookup
DSN generated by: DB6PR07MB3318.eurprd07.prod.outlook.com

Message Hops
HOP TIME FROM TO WITH RELAY
(UTC) TIME
3/1/2022 local (Exim 4.89) (envelope-from
1 11:26:26 foi owl.ukcod.org.uk <[FOI #837678 email]>) *
AM
3/1/2022 esmtps
2 11:26:26 owl.ukcod.org.uk starling.ukcod.org.uk (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) *
AM (Exim 4.89) (envelope-from
<[FOI #837678 email]>)
3/1/2022 Microsoft SMTP Server (version=TLS1_2,
3 11:26:27 mailer102.ukcod.org.uk DB5EUR03FT032.mail.protection.outlook.com cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) 1 sec
AM
3/1/2022 Microsoft SMTP Server (version=TLS1_2,
4 11:26:27 DB5EUR03FT032.eop-EUR03.prod.protection.outlook.com DB6PR07CA0192.outlook.office365.com cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) *
AM
3/1/2022 Microsoft SMTP Server (version=TLS1_2,
5 11:26:27 DB6PR07CA0192.eurprd07.prod.outlook.com DB6PR07MB3318.eurprd07.prod.outlook.com cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) *
AM

Original Message Headers

Received: from DB6PR07CA0192.eurprd07.prod.outlook.com (2603:10a6:6:42::22) by
DB6PR07MB3318.eurprd07.prod.outlook.com (2603:10a6:6:1e::30) with Microsoft
SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id
15.20.5038.10; Tue, 1 Mar 2022 11:26:27 +0000
Received: from DB5EUR03FT032.eop-EUR03.prod.protection.outlook.com
(2603:10a6:6:42:cafe::6e) by DB6PR07CA0192.outlook.office365.com
(2603:10a6:6:42::22) with Microsoft SMTP Server (version=TLS1_2,
cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.5038.9 via Frontend
Transport; Tue, 1 Mar 2022 11:26:27 +0000
Authentication-Results: spf=pass (sender IP is 46.43.39.102)
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 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
DB5EUR03FT032.mail.protection.outlook.com (10.152.20.162) with Microsoft SMTP
Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id
15.20.5017.22 via Frontend Transport; Tue, 1 Mar 2022 11:26:27 +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=3Tf6kF5aewJFRPfvpTIxUm3doqn7cSYy/rbX369GSgs=; b=WJTHjCcFId/X+JoV/wa694e3k
hJP0drHocCVSqOEfNocFAt6F6Vtk7J0XLjsEgjlVH99GR8kopA2Mm24vt6nE7L0pOD8CBcmK3us+k
zKh0q8FvlnJgNzWLEP0V8t3y6YzqwG4prWNv3BytROXo+q8njJ6rWhtbLdgU0zB+AQFEQGNWKb61c
Z45JrNg9NBzFXfmBAud9mKF2Ckd11M0C1UBV1gb9xPKJR20ZTcYJeLW1uju8v089xzBPelhahccQu
4ap5DEcYZsvp29KH/v0luuOPeG7UF2tBYx+KVpztlcAZawS+adhX/9B39NRI/N6VzKvSjxh9CBmHr
gEba0T4FA==;
Received: from owl.ukcod.org.uk ([2001:41c8:20:60e::6c:10]:55442)
by starling.ukcod.org.uk with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256)
(Exim 4.89)
(envelope-from <[FOI #837678 email]>)
id 1nP0eA-0007i1-MX
for [Selsey Town Council request email]; Tue, 01 Mar 2022 11:26:26 +0000
Received: from foi by owl.ukcod.org.uk with local (Exim 4.89)
(envelope-from <[FOI #837678 email]>)
id 1nP0eA-0005M8-J5
for [Selsey Town Council request email]; Tue, 01 Mar 2022 11:26:26 +0000
Date: Tue, 01 Mar 2022 11:26:26 +0000
From: Jessica Thomas <[FOI #837678 email]>
To: FOI requests at Selsey Town Council <[Selsey Town Council request email]>
Message-ID: <[email address]>
Subject: Freedom of Information request - Climate Change Agenda 2022
MIME-Version: 1.0
Content-Type: text/plain;
charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Return-Path: [FOI #837678 email]
X-EOPAttributedMessage: 0
X-EOPTenantAttributedMessage: a2e4b13c-f239-4952-8189-d3af74c50b28:0
X-MS-PublicTrafficType: Email
X-MS-Office365-Filtering-Correlation-Id: 5ee30b07-34ab-4b5d-5abc-08d9fb765342
X-MS-TrafficTypeDiagnostic: DB6PR07MB3318:EE_

References

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