Your message to [email address] couldn't be delivered.
j.wilcox wasn't found at lawnside.net.
0100017fe2603e0a-7f4. . . 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 3/31/2022 11:47:12 PM
Date:
Sender [email address]
Address:
Recipient [email address]
Address:
Subject: OPRA request - RE: Property Record Card
Error Details
Reported error: 550 5.1.10 RESOLVER.ADR.RecipientNotFound; Recipient [email address] not found
by SMTP address lookup
DSN generated by: CH0PR11MB5379.namprd11.prod.outlook.com

Message Hops
HOP TIME FROM TO WITH RELAY
(UTC) TIME
3/31/2022 Microsoft SMTP Server (version=TLS1_2,
1 11:47:13 a48-105.smtp-out.amazonses.com BN7NAM10FT054.mail.protection.outlook.com cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) 1 sec
PM
3/31/2022 Microsoft SMTP Server (version=TLS1_2,
2 11:47:13 BN7NAM10FT054.eop-nam10.prod.protection.outlook.com BN0PR02CA0045.outlook.office365.com cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) *
PM
3/31/2022 Microsoft SMTP Server (version=TLS1_2,
3 11:47:13 BN0PR02CA0045.namprd02.prod.outlook.com CH0PR11MB5379.namprd11.prod.outlook.com cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) *
PM

Original Message Headers

Received: from BN0PR02CA0045.namprd02.prod.outlook.com (2603:10b6:408:e5::20)
by CH0PR11MB5379.namprd11.prod.outlook.com (2603:10b6:610:ba::19) with
Microsoft SMTP Server (version=TLS1_2,
cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.5123.25; Thu, 31 Mar
2022 23:47:13 +0000
Received: from BN7NAM10FT054.eop-nam10.prod.protection.outlook.com
(2603:10b6:408:e5:cafe::89) by BN0PR02CA0045.outlook.office365.com
(2603:10b6:408:e5::20) with Microsoft SMTP Server (version=TLS1_2,
cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.5123.23 via Frontend
Transport; Thu, 31 Mar 2022 23:47:13 +0000
Authentication-Results: spf=pass (sender IP is 54.240.48.105)
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.48.105 as permitted sender)
receiver=protection.outlook.com; client-ip=54.240.48.105;
helo=a48-105.smtp-out.amazonses.com;
Received: from a48-105.smtp-out.amazonses.com (54.240.48.105) by
BN7NAM10FT054.mail.protection.outlook.com (10.13.157.112) with Microsoft SMTP
Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id
15.20.5123.19 via Frontend Transport; Thu, 31 Mar 2022 23:47:13 +0000
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/simple;
s=drvjftetwukgvxxawhtk3luf3y2o3amm; d=requests.opramachine.com;
t=1648770432;
h=Date:From:To:Message-ID:Subject:Mime-Version:Content-Type:Content-Transfer-Encoding;
bh=GCa78st89/up7+zhUkaLLnj4qJGv7voITm/UKjnIB/g=;
b=TlMlhi+CJS37qVozHRaLaU5iZhBbiKitb58r8CfctKWLum3Dpfdu3xHmZktbA1Q2
9SrXsPpq5PWkYz8IudcMhRSNvtZAg+RwWCQ0KkNVOBlM7ZckKP2rLiUy0xd32CSY+aJ
ejCh0TfQe49KQjyRHtNHLSMGllM/sf/u6R8uSgV4=
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/simple;
s=6gbrjpgwjskckoa6a5zn6fwqkn67xbtw; d=amazonses.com; t=1648770432;
h=Date:From:To:Message-ID:Subject:Mime-Version:Content-Type:Content-Transfer-Encoding:Feedback-ID;
bh=GCa78st89/up7+zhUkaLLnj4qJGv7voITm/UKjnIB/g=;
b=k9E4FM1rpEzr6IBG3EWaLz1GhmFuY8OfqKmqT3Ms55s08HJAjrH/QPMOkmOAyKC8
CefhRU1tjmYOqOOz+5Ku9mtvJiPhH3M+wmUVeGzeie1DPlUUu/xxvF+YNAr0zRGL9kc
V47QqQR9qxQzPm+eg4gFfxgnIqk7SIYJJM6IR9X0=
Date: Thu, 31 Mar 2022 23:47:12 +0000
From: Marie Wilson <[OPRA #30615 email]>
To: OPRA requests at Lawnside Borough <[email address]>
Message-ID: <[email address]>
Subject: OPRA request - RE: Property Record Card
MIME-Version: 1.0
Content-Type: text/plain;
charset=UTF-8
Content-Transfer-Encoding: 7bit
Feedback-ID: 1.us-east-1.Cy+CdIBOIzrBJluvD+AwZTYIIvgMdz3Pedsyi9/dX4g=:AmazonSES
X-SES-Outgoing: 2022.03.31-54.240.48.105
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: 65fead05-5815-4d76-f71f-08da1370c7b6
X-MS-TrafficTypeDiagnostic: CH0PR11MB5379: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=...