Your message to [email address] couldn't be delivered.
j.wilcox wasn't found at lawnside.net.
010001822c6d3c1e-a8d. . . Office 365 j.wilcox
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 7/23/2022 6:58:52 PM
Date:
Sender [email address]
Address:
Recipient [email address]
Address:
Subject: OPRA request - OPRA request for Borough Engineer Contract, etc. and closed session
resolution and minutes
Error Details
Reported error: 550 5.1.10 RESOLVER.ADR.RecipientNotFound; Recipient [email address] not found
by SMTP address lookup
DSN generated by: MWHPR11MB1965.namprd11.prod.outlook.com

Message Hops
HOP TIME FROM TO WITH RELAY
(UTC) TIME
7/23/2022 Microsoft SMTP Server (version=TLS1_2,
1 6:58:53 a8-30.smtp-out.amazonses.com DM6NAM10FT059.mail.protection.outlook.com cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) 1 sec
PM
7/23/2022 Microsoft SMTP Server (version=TLS1_2,
2 6:58:53 DM6NAM10FT059.eop-nam10.prod.protection.outlook.com DM6PR02CA0045.outlook.office365.com cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) *
PM
7/23/2022 Microsoft SMTP Server (version=TLS1_2,
3 6:58:54 DM6PR02CA0045.namprd02.prod.outlook.com MWHPR11MB1965.namprd11.prod.outlook.com cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) 1 sec
PM

Original Message Headers

Received: from DM6PR02CA0045.namprd02.prod.outlook.com (2603:10b6:5:177::22)
by MWHPR11MB1965.namprd11.prod.outlook.com (2603:10b6:300:110::15) with
Microsoft SMTP Server (version=TLS1_2,
cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.5458.19; Sat, 23 Jul
2022 18:58:54 +0000
Received: from DM6NAM10FT059.eop-nam10.prod.protection.outlook.com
(2603:10b6:5:177:cafe::6d) by DM6PR02CA0045.outlook.office365.com
(2603:10b6:5:177::22) with Microsoft SMTP Server (version=TLS1_2,
cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.5458.19 via Frontend
Transport; Sat, 23 Jul 2022 18:58:53 +0000
Authentication-Results: spf=pass (sender IP is 54.240.8.30)
smtp.mailfrom=bounce.requests.opramachine.com; dkim=pass (signature was
verified) header.d=requests.opramachine.com;dmarc=pass action=none
header.from=requests.opramachine.com;
Received-SPF: Pass (protection.outlook.com: domain of
bounce.requests.opramachine.com designates 54.240.8.30 as permitted sender)
receiver=protection.outlook.com; client-ip=54.240.8.30;
helo=a8-30.smtp-out.amazonses.com; pr=C
Received: from a8-30.smtp-out.amazonses.com (54.240.8.30) by
DM6NAM10FT059.mail.protection.outlook.com (10.13.153.71) with Microsoft SMTP
Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id
15.20.5458.17 via Frontend Transport; Sat, 23 Jul 2022 18:58:53 +0000
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/simple;
s=drvjftetwukgvxxawhtk3luf3y2o3amm; d=requests.opramachine.com;
t=1658602732;
h=Date:From:To:Message-ID:Subject:Mime-Version:Content-Type:Content-Transfer-Encoding;
bh=/Ga1vZdhLD6ckTPKPqS4viRWWX/6rNO4EGc7gffR90A=;
b=QdEzzNxyv1OHWzYHlTlEPenNHU6gOH3RZ7eBaA61u6wbypZl6vGmT4dJk48d16Td
9cjU/jnm85d6vAl4emxar1AtBFi2tN60wOUWg524Y8EanOrzByiT3hm7tz2guq/R3rf
qw4rjzwBNDPdryxnI2SBKbqxm4jA0cGUmYPYZXnQ=
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/simple;
s=6gbrjpgwjskckoa6a5zn6fwqkn67xbtw; d=amazonses.com; t=1658602732;
h=Date:From:To:Message-ID:Subject:Mime-Version:Content-Type:Content-Transfer-Encoding:Feedback-ID;
bh=/Ga1vZdhLD6ckTPKPqS4viRWWX/6rNO4EGc7gffR90A=;
b=Rhr37q/2CACfTkHOOLCMs6mmhyhJk0ZQ/7Iixow0y55EnntUgHfWXpnN6dog9PfK
laPYOL8A4LbSigMnm3PIRO+ngA/BF+Y6XFoie3KzDkLsOfkabCpqIHNt+dUinM7stpP
71siIq+apLD2+4qtO1oIV5+5v9LH2V8+TnqOldKE=
Date: Sat, 23 Jul 2022 18:58:52 +0000
From: John Paff <[OPRA #34149 email]>
To: OPRA requests at Lawnside Borough <[email address]>
Message-ID: <[email address]>
Subject: OPRA request - OPRA request for Borough Engineer Contract, etc. and
closed session resolution and minutes
MIME-Version: 1.0
Content-Type: text/plain;
charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Feedback-ID: 1.us-east-1.Cy+CdIBOIzrBJluvD+AwZTYIIvgMdz3Pedsyi9/dX4g=:AmazonSES
X-SES-Outgoing: 2022.07.23-54.240.8.30
Return-Path:
[email address]
X-EOPAttributedMessage: 0
X-EOPTenantAttributedMessage: 2c43b1dc-83ca-40cd-b1e3-431ee3bcab2f:0
X-MS-PublicTrafficType: Email
X-MS-Office365-Filtering-Correlation-Id: da7973d7-19c3-412c-c8fb-08da6cdd6351
X-MS-TrafficTypeDiagnostic: MWHPR11MB1965: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=...