Your message to [Sea Girt Borough request email] couldn't be delivered.
lcarafa wasn't found at seagirtboro.com.
0100018ba32de8bc-30a. . . Office 365 lcarafa
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 11/6/2023 5:49:36 AM
Date:
Sender [email address]
Address:
Recipient [Sea Girt Borough request email]
Address:
Subject: OPRA request - Bid Tabulation Results for Chicago Boulevard Sanitary Sewer Improvements –
Phase 1MSP Construction Corporation
Error Details
Error: 550 5.1.10 RESOLVER.ADR.RecipientNotFound; Recipient [Sea Girt Borough request email] not
found by SMTP address lookup
Message rejected by: SJ0PR09MB11105.namprd09.prod.outlook.com
Notification Details
Sent by: SJ0PR09MB11105.namprd09.prod.outlook.com

Message Hops
HOP TIME FROM TO WITH RELAY
(UTC) TIME
11/6/2023 Microsoft SMTP Server (version=TLS1_2,
1 5:49:37 a48-107.smtp-out.amazonses.com BL0GCC02FT031.mail.protection.outlook.com cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) 1 sec
AM
11/6/2023 Microsoft SMTP Server (version=TLS1_2,
2 5:49:38 BL0GCC02FT031.eop-gcc02.prod.protection.outlook.com DM6PR09CA0004.outlook.office365.com cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) 1 sec
AM
11/6/2023 Microsoft SMTP Server (version=TLS1_2,
3 5:49:38 DM6PR09CA0004.namprd09.prod.outlook.com SJ0PR09MB11105.namprd09.prod.outlook.com cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) *
AM

Original Message Headers

Received: from DM6PR09CA0004.namprd09.prod.outlook.com (2603:10b6:5:160::17)
by SJ0PR09MB11105.namprd09.prod.outlook.com (2603:10b6:a03:50f::11) with
Microsoft SMTP Server (version=TLS1_2,
cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.6954.28; Mon, 6 Nov
2023 05:49:38 +0000
Received: from BL0GCC02FT031.eop-gcc02.prod.protection.outlook.com
(2a01:111:f400:7d05::204) by DM6PR09CA0004.outlook.office365.com
(2603:10b6:5:160::17) with Microsoft SMTP Server (version=TLS1_2,
cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.6954.28 via Frontend
Transport; Mon, 6 Nov 2023 05:49:38 +0000
Authentication-Results: spf=pass (sender IP is 54.240.48.107)
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.107 as permitted sender)
receiver=protection.outlook.com; client-ip=54.240.48.107;
helo=a48-107.smtp-out.amazonses.com; pr=C
Received: from a48-107.smtp-out.amazonses.com (54.240.48.107) by
BL0GCC02FT031.mail.protection.outlook.com (10.97.10.147) with Microsoft SMTP
Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id
15.20.6977.16 via Frontend Transport; Mon, 6 Nov 2023 05:49:37 +0000
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/simple;
s=75ht6uujunbugea7bv75tq6udjzjx55y; d=requests.opramachine.com;
t=1699249777;
h=Date:From:To:Message-ID:Subject:Mime-Version:Content-Type:Content-Transfer-Encoding;
bh=Q53lki0cqunNbi5CrU2bdR4Lttjb1UuMJj+DWv5szAM=;
b=aJCEncpAvEF1OJXj010Ymi/RbG+CRNUE7N5lE80GQlvukv6cZdtF6s2sZ7AKMlN5
H8QK5qphrCh3OxICm2301u8ecKH1HZNH7yCUaqfDb/gNLDzhoP8k+bKBGcV+XFxsluk
UNOmHEEBw8UnmTmmV6zMTC7kNTGFyZEYBP49faSY=
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/simple;
s=224i4yxa5dv7c2xz3womw6peuasteono; d=amazonses.com; t=1699249777;
h=Date:From:To:Message-ID:Subject:Mime-Version:Content-Type:Content-Transfer-Encoding:Feedback-ID;
bh=Q53lki0cqunNbi5CrU2bdR4Lttjb1UuMJj+DWv5szAM=;
b=QwCRotJEQIKpVF/ijIUSuyZvXsuZH09qLaxEMqU1xHqI4gBNn3oEQILl3OahtBSr
fqvGleXXWjt9eiSIlcC/Z1G/WWw7t6EAIHG8U2vExKeBsnj9o2uA3NJMXvmRfdvSZFQ
wK7gJqZHECLaG79wPXg2Ph9fncboqJC+oL1hAi6s=
Date: Mon, 6 Nov 2023 05:49:36 +0000
From: Maddie Baisley <[OPRA #54964 email]>
To: OPRA requests at Sea Girt Borough <[Sea Girt Borough request email]>
Message-ID: <[email address]>
Subject: =?UTF-8?Q?OPRA_request_-_Bid_Tabulation_Results_for_Chicago_Boulev?=
=?UTF-8?Q?ard_Sanitary_Sewer_Improvements_=E2=80=93_Phase_1MSP_Construction?=
=?UTF-8?Q?_Corporation?=
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: 2023.11.06-54.240.48.107
Return-Path:
[email address]
X-EOPAttributedMessage: 0
X-EOPTenantAttributedMessage: 1903f6c0-5c4e-40f9-8091-ef8ae2617142:0
X-MS-PublicTrafficType: Email
X-MS-TrafficTypeDiagnostic: BL0GCC02FT031:EE_|SJ0PR09MB11105:EE_
X-MS-Office365-Filtering-Correlation-Id: b778d921-61bc-45a8-4470-08dbde8c29a5

References

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