Your message to [Washington Borough request email] couldn't be delivered.
akilduff wasn't found at washingtonboro-nj.org.
0100018abe1cba19-983. . . 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 9/22/2023 6:17:48 PM
Date:
Sender [email address]
Address:
Recipient [Washington Borough request email]
Address:
Subject: Internal review of OPRA request - Bid Tabulation Results for FY2021 NJDOT Bells Lake Road
Improvements Phase 2Arawak Paving Company Inc.
Error Details
Error: 550 5.1.10 RESOLVER.ADR.RecipientNotFound; Recipient
[Washington Borough request email] not found by SMTP address lookup
Message rejected by: CH0PR13MB4635.namprd13.prod.outlook.com
Notification Details
Sent by: CH0PR13MB4635.namprd13.prod.outlook.com

Message Hops
HOP TIME FROM TO WITH RELAY
(UTC) TIME
9/22/2023
1 6:17:33 [54.240.48.101] inbound.appriver.com ESMTPS *
PM
9/22/2023
2 6:17:36 inbound.appriver.com PIPE 3 sec
PM
9/22/2023
3 6:17:36 [10.168.232.249] stdel502.appriver.com ESMTPS *
PM
9/22/2023 Microsoft SMTP Server (version=TLS1_2,
4 6:17:52 stdel502.appriver.com DM6NAM12FT016.mail.protection.outlook.com cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) 16 sec
PM
9/22/2023 Microsoft SMTP Server (version=TLS1_2,
5 6:17:52 DM6NAM12FT016.eop-nam12.prod.protection.outlook.com SJ0PR13CA0092.outlook.office365.com cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) *
PM
9/22/2023 Microsoft SMTP Server (version=TLS1_2,
6 6:17:53 SJ0PR13CA0092.namprd13.prod.outlook.com CH0PR13MB4635.namprd13.prod.outlook.com cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) 1 sec
PM

Original Message Headers

Received: from SJ0PR13CA0092.namprd13.prod.outlook.com (2603:10b6:a03:2c5::7)
by CH0PR13MB4635.namprd13.prod.outlook.com (2603:10b6:610:c7::14) with
Microsoft SMTP Server (version=TLS1_2,
cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.6813.23; Fri, 22 Sep
2023 18:17:53 +0000
Received: from DM6NAM12FT016.eop-nam12.prod.protection.outlook.com
(2603:10b6:a03:2c5:cafe::c1) by SJ0PR13CA0092.outlook.office365.com
(2603:10b6:a03:2c5::7) with Microsoft SMTP Server (version=TLS1_2,
cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.6838.9 via Frontend
Transport; Fri, 22 Sep 2023 18:17:52 +0000
Authentication-Results: spf=softfail (sender IP is 8.19.118.135)
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.19.118.135 as permitted
sender)
Received: from stdel502.appriver.com (8.19.118.135) 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.6838.14 via Frontend Transport; Fri, 22 Sep 2023 18:17:52 +0000
X-Note: Xit Build: 3/16/2017 5:09:20 PM UTC (2.6.15.0) XIT_SCAN_PASSED
Received: from [10.168.232.249] (HELO inbound.appriver.com)
by stdel502.appriver.com (CommuniGate Pro SMTP 6.2.15)
with ESMTPS id 1601785366 for [Washington Borough request email]; Fri, 22 Sep 2023 13:17:36 -0500
X-Note: This Email was scanned by AppRiver SecureTide
X-Note-AR-ScanTimeLocal: 09/22/2023 2:17:36 PM
X-Note: SecureTide Build: 9/18/2023 2:05:46 PM UTC (2.31.0.0)
X-Note: Filtered by 10.168.233.60
X-Note-AR-Scan: None - PIPE
X-Note: CGHH cor:0922181736113-142802802-65278
Received: by inbound.appriver.com (CommuniGate Pro PIPE 7.1.1)
with PIPE id 142802802; Fri, 22 Sep 2023 14:17:36 -0400
Received: from [54.240.48.101] (HELO a48-101.smtp-out.amazonses.com)
by inbound.appriver.com (CommuniGate Pro SMTP 7.1.1)
with ESMTPS id 142802791 for [Washington Borough request email]; Fri, 22 Sep 2023 14:17:33 -0400
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/simple;
s=cofuhmhcsf5ualrhpbcimprdgtodlfak; d=requests.opramachine.com;
t=1695406669;
h=Date:From:To:Message-ID:Subject:Mime-Version:Content-Type:Content-Transfer-Encoding;
bh=MAo7kmuosmeh0N41YxRv++IrRKunzc6EwQ2gGJwQxXc=;
b=R2cn0xBkTOfcrg9crNcwbmx0o81FMCig9+Lf4avsRN82UH0gx+HYEjKZ3i7bF3BS
vx03ZalqQO0xOvbpibzRhETHHfFd3UvH5GFHyuBLGqKs8zNtCGTFi2AxpjpzzaXiIn8
vzXT4iRCQGtBR8/0i4IwO2Ct9BSbFV5oBPX/XzPc=
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/simple;
s=224i4yxa5dv7c2xz3womw6peuasteono; d=amazonses.com; t=1695406669;
h=Date:From:To:Message-ID:Subject:Mime-Version:Content-Type:Content-Transfer-Encoding:Feedback-ID;
bh=MAo7kmuosmeh0N41YxRv++IrRKunzc6EwQ2gGJwQxXc=;
b=TkvpkmQJcjNKiTMyXT+7oqba+v1EAgtN2SOuvnAs3Xvpfasdmw9lHFCkurGFsTNS
0fxLGs1n51Eh1MkJbzJBiXiB1ym6X3uuouVzH+9ijDFer+SlGS+648b/EqbUeQ46DNz
69UfLgAz7CV3SklD50yqRbNevjE9MKgmZsPE3NR4=
Date: Fri, 22 Sep 2023 18:17:48 +0000
From: Maddie Baisley <[OPRA #43821 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 FY2021
NJDOT Bells Lake Road Improvements Phase 2Arawak Paving Company Inc.
MIME-Version: 1.0
Feedback-ID: 1.us-east-1.Cy+CdIBOIzrBJluvD+AwZTYIIvgMdz3Pedsyi9/dX4g=:AmazonSES
X-SES-Outgoing: 2023.09.22-54.240.48.101
Content-Type: text/plain;
charset=UTF-8
Content-Transfer-Encoding: 7bit
X-Note: This Email was scanned by AppRiver SecureTide
X-Note-AR-ScanTimeLocal: 09/22/2023 2:17:34 PM
X-Note: SecureTide Build: 9/18/2023 2:05:46 PM UTC (2.31.0.0)
X-Note: Filtered by 10.168.233.60
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.48.101 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.48.101, Ugly c=0.264319 p=-0.0769231 Source Normal
X-Signature-Violations: 0-0-0-4160-c
X-Note-419: 15.615 ms. Fail:2 Chk:1432 of 1432 total
X-Note: VSCH-CT/SI: 2-1432/SG:1 9/22/2023 2:17:11 PM
X-Note: Spam Tests Failed:
X-Country-Path: United States of America->LOCAL
X-Note-Sending-IP: 54.240.48.101
X-Note-Reverse-DNS: a48-101.smtp-out.amazonses.com
X-Note-Return-Path: [email address]
X-Note: User Rule Hits:
X-Note: Global Rule Hits: G346 G348 G349 G350 G367 G368 G369 G511 G512 G518 G710 G748 G937
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_|CH0PR13MB4635:EE_
X-MS-Office365-Filtering-Correlation-Id: ba3342e3-4042-4bcb-33aa-08dbbb983c20

References

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