Your message to [Washington Borough request email] couldn't be delivered.
akilduff wasn't found at washingtonboro-nj.org.
0100018bfd29ad64-ff0. . . Office 365 akilduff
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/23/2023 5:10:48 PM
Date:
Sender [email address]
Address:
Recipient [Washington Borough request email]
Address:
Subject: Internal review of OPRA request - Bid Tabulation Results for Mt. Pleasant Road NJDOT Design
- Phase 2Paving Plus, LLC
Error Details
Error: 550 5.1.10 RESOLVER.ADR.RecipientNotFound; Recipient
[Washington Borough request email] not found by SMTP address lookup
Message rejected by: DS7PR13MB4768.namprd13.prod.outlook.com
Notification Details
Sent by: DS7PR13MB4768.namprd13.prod.outlook.com

Message Hops
HOP TIME (UTC) FROM TO WITH RELAY
TIME
1 11/23/2023 [54.240.8.95] inbound.appriver.com ESMTPS 6 sec
5:10:54 PM
2 11/23/2023 inbound.appriver.com PIPE 4 sec
5:10:58 PM
3 11/23/2023 [172.31.255.215] server215.appriver.com ESMTP *
5:09:31 PM
4 11/23/2023 server215.appriver.com DM6NAM12FT016.mail.protection.outlook.com Microsoft SMTP Server (version=TLS1_2, 1 min,
5:10:55 PM cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) 24 sec
5 11/23/2023 DM6NAM12FT016.eop-nam12.prod.protection.outlook.com SJ0PR03CA0054.outlook.office365.com Microsoft SMTP Server (version=TLS1_2, 1 sec
5:10:56 PM cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384)
6 11/23/2023 SJ0PR03CA0054.namprd03.prod.outlook.com DS7PR13MB4768.namprd13.prod.outlook.com Microsoft SMTP Server (version=TLS1_2, *
5:10:56 PM cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384)

Original Message Headers

Received: from SJ0PR03CA0054.namprd03.prod.outlook.com (2603:10b6:a03:33e::29)
by DS7PR13MB4768.namprd13.prod.outlook.com (2603:10b6:5:3a6::20) with
Microsoft SMTP Server (version=TLS1_2,
cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.7025.18; Thu, 23 Nov
2023 17:10:56 +0000
Received: from DM6NAM12FT016.eop-nam12.prod.protection.outlook.com
(2603:10b6:a03:33e:cafe::7) by SJ0PR03CA0054.outlook.office365.com
(2603:10b6:a03:33e::29) with Microsoft SMTP Server (version=TLS1_2,
cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.7025.20 via Frontend
Transport; Thu, 23 Nov 2023 17:10:56 +0000
Authentication-Results: spf=softfail (sender IP is 8.31.233.196)
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: SoftFail (protection.outlook.com: domain of transitioning
bounce.requests.opramachine.com discourages use of 8.31.233.196 as permitted
sender)
Received: from server215.appriver.com (8.31.233.196) by
DM6NAM12FT016.mail.protection.outlook.com (10.13.178.217) with Microsoft SMTP
Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id
15.20.7025.11 via Frontend Transport; Thu, 23 Nov 2023 17:10:55 +0000
X-Note: Xit Build: 6/24/2022 2:06:24 PM UTC (2.7.0.0) XIT_SCAN_PASSED
Received: from [172.31.255.215] (HELO inbound.appriver.com)
by server215.appriver.com (CommuniGate Pro SMTP 6.2.15)
with ESMTP id 1930857428 for [Washington Borough request email]; Thu, 23 Nov 2023 12:09:31 -0500
X-Note: This Email was scanned by AppRiver SecureTide
X-Note-AR-ScanTimeLocal: 11/23/2023 12:10:58 PM
X-Note: SecureTide Build: 10/20/2023 1:56:48 PM UTC (2.32.1.0)
X-Note: Filtered by 10.60.1.103
X-Note-AR-Scan: None - PIPE
Received: by inbound.appriver.com (CommuniGate Pro PIPE 7.1.1)
with PIPE id 2329418; Thu, 23 Nov 2023 12:10:58 -0500
Received: from [54.240.8.95] (HELO a8-95.smtp-out.amazonses.com)
by inbound.appriver.com (CommuniGate Pro SMTP 7.1.1)
with ESMTPS id 2329415 for [Washington Borough request email]; Thu, 23 Nov 2023 12:10:54 -0500
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/simple;
s=75ht6uujunbugea7bv75tq6udjzjx55y; d=requests.opramachine.com;
t=1700759449;
h=Date:From:To:Message-ID:Subject:Mime-Version:Content-Type:Content-Transfer-Encoding;
bh=fRg4JSYoCH/DbF53P5joHTMHToLVoTJ9huytjcDraxM=;
b=WRoqZF+9bTzmjT8JtYwsLcgkqOeqF7U/FfBlrmWPLrFD9qw/28j1MNaCo3cmODs6
HVzMHETnSJ/pGLq+2fnjgC8EKI0sDShf4X/k5n/oftTsnjil0NetDXG6QtuA3tMRWy1
nBYEF8PWI3Ht0n0ce/yqNVhSeSByt8c0LbNXkzX8=
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/simple;
s=224i4yxa5dv7c2xz3womw6peuasteono; d=amazonses.com; t=1700759449;
h=Date:From:To:Message-ID:Subject:Mime-Version:Content-Type:Content-Transfer-Encoding:Feedback-ID;
bh=fRg4JSYoCH/DbF53P5joHTMHToLVoTJ9huytjcDraxM=;
b=WTB43/hykqaKmiAvJbyfMHD0V+N3CvA5objxTNX5H8UG5A12LkKAxLZwP2/Ik+Db
VYZu5ffWKaELNtkT8E+0Iz9STSBeftuJwDSGMJZgmgDOp7pc/JtaZ6ZU4/IUN51/Vkn
6I56qh65a6kU7o6vK7AV2LYk9OSosXPbZ54hmMLY=
Date: Thu, 23 Nov 2023 17:10:48 +0000
From: Maddie Baisley <[OPRA #45667 email]>
To: OPRA requests at Washington Borough <[Washington Borough request email]>
Message-ID: <[email address]>
Subject: Internal review of OPRA request - Bid Tabulation Results for Mt.
Pleasant Road NJDOT Design - Phase 2Paving Plus, LLC
MIME-Version: 1.0
Feedback-ID: 1.us-east-1.Cy+CdIBOIzrBJluvD+AwZTYIIvgMdz3Pedsyi9/dX4g=:AmazonSES
X-SES-Outgoing: 2023.11.23-54.240.8.95
Content-Type: text/plain;
charset=UTF-8
Content-Transfer-Encoding: 7bit
X-Note: This Email was scanned by AppRiver SecureTide
X-Note-AR-ScanTimeLocal: 11/23/2023 12:10:54 PM
X-Note: SecureTide Build: 10/20/2023 1:56:48 PM UTC (2.32.1.0)
X-Note: Filtered by 10.60.1.103
X-Policy: washingtonboro-nj.org
X-Primary: [email address]
X-Note-Sender: [email address]
X-Note-Envelope-Recip: FAILURE,DELAY, <[Washington Borough request email]>
X-Virus-Scan: V-
X-Note: SPF: IP: 54.240.8.95 DOM: bounce.requests.opramachine.com ADDR: [email address]
X-Note: SPF: Pass
X-Note: DKIM: Pass: requests.opramachine.com
X-Note: DMARC: opramachine.com p=none sp=none
X-Note: DMARC: Pass
X-Note-SnifferID: 0
X-GBUdb-Analysis: 0, 54.240.8.95, Ugly c=0.303425 p=-0.0526316 Source Normal
X-Signature-Violations: 0-0-0-4094-c
X-Note-419: 0 ms. Fail:2 Chk:1432 of 1432 total
X-Note: VSCH-CT/SI: 2-1432/SG:1 11/23/2023 12:10:11 PM
X-Note: Spam Tests Failed:
X-Country-Path: United States of America->LOCAL
X-Note-Sending-IP: 54.240.8.95
X-Note-Reverse-DNS: a8-95.smtp-out.amazonses.com
X-Note-Return-Path: [email address]
X-Note: User Rule Hits:
X-Note: Global Rule Hits: G369 G371 G372 G373 G390 G391 G392 G534 G535 G541 G743 G781 G974
X-Note: Encrypt Rule Hits:
X-Note: Mail Class: VALID
Return-Path:
[email address]
X-EOPAttributedMessage: 0
X-EOPTenantAttributedMessage: 5f419903-a895-4e86-bc5b-06553b8c91d3:0
X-MS-PublicTrafficType: Email
X-MS-TrafficTypeDiagnostic: DM6NAM12FT016:EE_|DS7PR13MB4768:EE_
X-MS-Office365-Filtering-Correlation-Id: 69d829cf-7c3f-4e1e-678d-08dbec4727e3

References

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