Your message to [Washington Borough request email] couldn't be delivered.
akilduff wasn't found at washingtonboro-nj.org.
0100018e19367a27-979. . . 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 3/7/2024 1:59:44 PM
Date:
Sender [email address]
Address:
Recipient [Washington Borough request email]
Address:
Subject: OPRA request - Bid Tabulation Results for 2023 Washington Township Road Program - Phase 1
Error Details
Error: 550 5.1.10 RESOLVER.ADR.RecipientNotFound; Recipient
[Washington Borough request email] not found by SMTP address lookup
Message rejected by: PH0PR13MB5268.namprd13.prod.outlook.com
Notification Details
Sent by: PH0PR13MB5268.namprd13.prod.outlook.com

Message Hops
HOP TIME FROM TO WITH RELAY
(UTC) TIME
3/7/2024
1 1:59:53 [54.240.8.79] inbound.appriver.com ESMTPS 9 sec
PM
3/7/2024
2 1:59:57 inbound.appriver.com PIPE 4 sec
PM
3/7/2024
3 1:58:03 [172.31.255.215] server215.appriver.com ESMTP *
PM
3/7/2024 Microsoft SMTP Server (version=TLS1_2, 1 min,
4 1:59:49 server215.appriver.com BN8NAM12FT093.mail.protection.outlook.com cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) 46 sec
PM
3/7/2024 Microsoft SMTP Server (version=TLS1_2,
5 1:59:50 BN8NAM12FT093.eop-nam12.prod.protection.outlook.com BN9PR03CA0111.outlook.office365.com cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) 1 sec
PM
3/7/2024 Microsoft SMTP Server (version=TLS1_2,
6 1:59:50 BN9PR03CA0111.namprd03.prod.outlook.com PH0PR13MB5268.namprd13.prod.outlook.com cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) *
PM

Original Message Headers

Received: from BN9PR03CA0111.namprd03.prod.outlook.com (2603:10b6:408:fd::26)
by PH0PR13MB5268.namprd13.prod.outlook.com (2603:10b6:510:db::8) with
Microsoft SMTP Server (version=TLS1_2,
cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.7362.26; Thu, 7 Mar
2024 13:59:50 +0000
Received: from BN8NAM12FT093.eop-nam12.prod.protection.outlook.com
(2603:10b6:408:fd:cafe::e3) by BN9PR03CA0111.outlook.office365.com
(2603:10b6:408:fd::26) with Microsoft SMTP Server (version=TLS1_2,
cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.7362.27 via Frontend
Transport; Thu, 7 Mar 2024 13:59:50 +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
BN8NAM12FT093.mail.protection.outlook.com (10.13.183.111) with Microsoft SMTP
Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id
15.20.7386.9 via Frontend Transport; Thu, 7 Mar 2024 13:59:49 +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 7.1.6)
with ESMTP id 29297635 for [Washington Borough request email]; Thu, 07 Mar 2024 08:58:03 -0500
X-Note: This Email was scanned by AppRiver SecureTide
X-Note-AR-ScanTimeLocal: 03/07/2024 8:59:57 AM
X-Note: SecureTide Build: 2/14/2024 2:12:58 PM UTC (2.41.3.0)
X-Note: Filtered by 10.60.0.247
X-Note-AR-Scan: None - PIPE
X-Note: CGHH cor:0307135957402-22542297-875302
Received: by inbound.appriver.com (CommuniGate Pro PIPE 7.1.1)
with PIPE id 22542297; Thu, 07 Mar 2024 08:59:57 -0500
Received: from [54.240.8.79] (HELO a8-79.smtp-out.amazonses.com)
by inbound.appriver.com (CommuniGate Pro SMTP 7.1.1)
with ESMTPS id 22542285 for [Washington Borough request email]; Thu, 07 Mar 2024 08:59:53 -0500
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/simple;
s=75ht6uujunbugea7bv75tq6udjzjx55y; d=requests.opramachine.com;
t=1709819984;
h=Date:From:To:Message-ID:Subject:Mime-Version:Content-Type:Content-Transfer-Encoding;
bh=u+zx5jISGa/ayzYvmpOtqkoe4Eao3qRIeMW9eZlGt+E=;
b=n5uRTa9Ih12DG+a3Ul5qy20+drpGRwnjvrlpDytUl4MoePC4YVUFW8d+V7tjrXlH
YFVbYtRR8pcLhMTSo70DsBxCxIdl1HNG7Y2h2TKAGBqlltvIrWyYcXzw6fM5hle1SyW
0++ObXsia8MzGXMGXXDVUByEfbFv4E3ssb1wxPqU=
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/simple;
s=224i4yxa5dv7c2xz3womw6peuasteono; d=amazonses.com; t=1709819984;
h=Date:From:To:Message-ID:Subject:Mime-Version:Content-Type:Content-Transfer-Encoding:Feedback-ID;
bh=u+zx5jISGa/ayzYvmpOtqkoe4Eao3qRIeMW9eZlGt+E=;
b=fCQsLmUs8IwECE2S5Bx1Oq9umLYYYNVMGlJerHvCcdJWpttMxCxI0zQWedwHtyZy
DyY2xS2DojWoE4lxDW8L5tNpwwU3cH1yJzukymUNfk45kJSur80Y3jXm1rRLT6PsJvG
GtrAvhGeBz62W3xWCnSvzw44EYnwizimyc3wvzsg=
Date: Thu, 7 Mar 2024 13:59:44 +0000
From: Maddie Baisley <[OPRA #59254 email]>
To: OPRA requests at Washington Borough <[Washington Borough request email]>
Message-ID: <[email address]>
Subject: OPRA request - Bid Tabulation Results for 2023 Washington Township
Road Program - Phase 1
MIME-Version: 1.0
Feedback-ID: 1.us-east-1.Cy+CdIBOIzrBJluvD+AwZTYIIvgMdz3Pedsyi9/dX4g=:AmazonSES
X-SES-Outgoing: 2024.03.07-54.240.8.79
Content-Type: text/plain;
charset=UTF-8
Content-Transfer-Encoding: 7bit
X-Note: This Email was scanned by AppRiver SecureTide
X-Note-AR-ScanTimeLocal: 03/07/2024 8:59:53 AM
X-Note: SecureTide Build: 2/14/2024 2:12:58 PM UTC (2.41.3.0)
X-Note: Filtered by 10.60.0.247
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.79 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.79, Ugly c=0.184641 p=0 Source Normal
X-Signature-Violations: 0-0-0-5749-c
X-Note-419: 15.6171 ms. Fail:0 Chk:1432 of 1432 total
X-Note: VSCH-CT/SI: 0-1432/SG:1 3/7/2024 8:59:44 AM
X-Note: Spam Tests Failed:
X-Country-Path: United States of America->LOCAL
X-Note-Sending-IP: 54.240.8.79
X-Note-Reverse-DNS: a8-79.smtp-out.amazonses.com
X-Note-Return-Path: [email address]
X-Note: User Rule Hits:
X-Note: Global Rule Hits: G387 G389 G390 G391 G408 G409 G410 G554 G555 G561 G778 G816 G1010
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: BN8NAM12FT093:EE_|PH0PR13MB5268:EE_
X-MS-Office365-Filtering-Correlation-Id: 45022e9c-2cf5-4b88-8478-08dc3eaedacf

References

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