Your message to [Washington Borough request email] couldn't be delivered.
akilduff wasn't found at washingtonboro-nj.org.
01000189473692e7-c6d. . . 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 7/11/2023 11:08:26 PM
Date:
Sender [email address]
Address:
Recipient [Washington Borough request email]
Address:
Subject: OPRA request - Network Blade LLC - Contracts, Vendor History Reports and Invoices
Error Details
Error: 550 5.1.10 RESOLVER.ADR.RecipientNotFound; Recipient
[Washington Borough request email] not found by SMTP address lookup
Message rejected by: CH0PR13MB4617.namprd13.prod.outlook.com
Notification Details
Sent by: CH0PR13MB4617.namprd13.prod.outlook.com

Message Hops
HOP TIME FROM TO WITH RELAY
(UTC) TIME
7/11/2023
1 11:09:02 [54.240.8.95] inbound.appriver.com ESMTPS 36 sec
PM
7/11/2023
2 11:09:02 inbound.appriver.com PIPE *
PM
7/11/2023
3 11:08:01 [10.168.232.249] stdel502.appriver.com ESMTPS *
PM
7/11/2023 Microsoft SMTP Server (version=TLS1_2,
4 11:08:27 stdel502.appriver.com DM6NAM12FT078.mail.protection.outlook.com cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) 26 sec
PM
7/11/2023 Microsoft SMTP Server (version=TLS1_2,
5 11:08:28 DM6NAM12FT078.eop-nam12.prod.protection.outlook.com SJ0P220CA0030.outlook.office365.com cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) 1 sec
PM
7/11/2023 Microsoft SMTP Server (version=TLS1_2,
6 11:08:29 SJ0P220CA0030.NAMP220.PROD.OUTLOOK.COM CH0PR13MB4617.namprd13.prod.outlook.com cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) 1 sec
PM

Original Message Headers

Received: from SJ0P220CA0030.NAMP220.PROD.OUTLOOK.COM (2603:10b6:a03:41b::6)
by CH0PR13MB4617.namprd13.prod.outlook.com (2603:10b6:610:de::8) with
Microsoft SMTP Server (version=TLS1_2,
cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.6565.31; Tue, 11 Jul
2023 23:08:29 +0000
Received: from DM6NAM12FT078.eop-nam12.prod.protection.outlook.com
(2603:10b6:a03:41b:cafe::74) by SJ0P220CA0030.outlook.office365.com
(2603:10b6:a03:41b::6) with Microsoft SMTP Server (version=TLS1_2,
cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.6565.32 via Frontend
Transport; Tue, 11 Jul 2023 23:08:28 +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
DM6NAM12FT078.mail.protection.outlook.com (10.13.179.142) with Microsoft SMTP
Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id
15.20.6609.6 via Frontend Transport; Tue, 11 Jul 2023 23:08:27 +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 1511133554 for [Washington Borough request email]; Tue, 11 Jul 2023 18:08:01 -0500
X-Note: This Email was scanned by AppRiver SecureTide
X-Note-AR-ScanTimeLocal: 07/11/2023 7:09:02 PM
X-Note: SecureTide Build: 6/13/2023 4:02:02 PM UTC (2.30.1.0)
X-Note: Filtered by 10.168.233.60
X-Note-AR-Scan: None - PIPE
X-Note: CGHH cor:0711230902710-132133691-713669
Received: by inbound.appriver.com (CommuniGate Pro PIPE 7.1.1)
with PIPE id 132133691; Tue, 11 Jul 2023 19:09:02 -0400
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 132133686 for [Washington Borough request email]; Tue, 11 Jul 2023 19:09:02 -0400
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/simple;
s=cofuhmhcsf5ualrhpbcimprdgtodlfak; d=requests.opramachine.com;
t=1689116906;
h=Date:From:To:Message-ID:Subject:Mime-Version:Content-Type:Content-Transfer-Encoding;
bh=WfnotbAHiUUxY5rkTmp+UELvsjWRBga3tWFAZpNGNkI=;
b=o25vMpzEufc9TO3JlzBv5nm+WeLV2NxZ95wrxxtX4JLue1vuOBtDtRu3bvOdFqe6
rygf4u7cRQN9e8CQ8WeuYkmOrykMADaKRg2sCMHNtB3GHjxaQaw/wli94UbBb+IyC8T
0QLXNd+WDh1+5D+bIs4HpNsVfcJod7Aku60CuxR8=
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/simple;
s=224i4yxa5dv7c2xz3womw6peuasteono; d=amazonses.com; t=1689116906;
h=Date:From:To:Message-ID:Subject:Mime-Version:Content-Type:Content-Transfer-Encoding:Feedback-ID;
bh=WfnotbAHiUUxY5rkTmp+UELvsjWRBga3tWFAZpNGNkI=;
b=ODciQyXgTMewmBOPbRJfgSKuPRKg8wegAG+bNm9tgts3LDPUsdjyap7KWHirseZO
CyO8JAjqjelelDxjRH270oB+pVh+FDpSOgijfUSiZzx+/2V3fh1S0d3aaNyOdYOWZgB
63mxk6E7SU+QFt5054wySNESNJweiztUD8ekoU5s=
Date: Tue, 11 Jul 2023 23:08:26 +0000
From: "G.R." <[OPRA #48480 email]>
To: OPRA requests at Washington Borough <[Washington Borough request email]>
Message-ID: <[email address]>
Subject: OPRA request - Network Blade LLC - Contracts, Vendor History Reports
and Invoices
MIME-Version: 1.0
Feedback-ID: 1.us-east-1.Cy+CdIBOIzrBJluvD+AwZTYIIvgMdz3Pedsyi9/dX4g=:AmazonSES
X-SES-Outgoing: 2023.07.11-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: 07/11/2023 7:09:02 PM
X-Note: SecureTide Build: 6/13/2023 4:02:02 PM UTC (2.30.1.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.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.331706 p=-0.2 Source Normal
X-Signature-Violations: 0-0-0-5566-c
X-Warn: FINGERPRINT 20012020sdsmb
X-Note-419: 15.6263 ms. Fail:2 Chk:1438 of 1438 total
X-Note: VSCH-CT/SI: 2-1438/SG:1 7/11/2023 7:08:35 PM
X-Warn: FINGERPRINT 20012020sdsmb
X-Note: Spam Tests Failed: FINGERPRINT
X-Country-Path: United States of America->
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: G327 G329 G330 G331 G348 G349 G350 G430 G492 G493 G499 G691 G729 G916
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: DM6NAM12FT078:EE_|CH0PR13MB4617:EE_
X-MS-Office365-Filtering-Correlation-Id: be0d4864-200e-47c3-97ed-08db8263bc8c

References

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