Your message to [Washington Borough request email] couldn't be delivered.
akilduff wasn't found at washingtonboro-nj.org.
01000189fbfb9e0d-76e. . . 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 8/16/2023 1:35:18 AM
Date:
Sender [email address]
Address:
Recipient [Washington Borough request email]
Address:
Subject: OPRA request - Bid Tabulation Results for Rock Spring Park Trail Extension
Error Details
Error: 550 5.1.10 RESOLVER.ADR.RecipientNotFound; Recipient
[Washington Borough request email] not found by SMTP address lookup
Message rejected by: SA1PR13MB5038.namprd13.prod.outlook.com
Notification Details
Sent by: SA1PR13MB5038.namprd13.prod.outlook.com

Message Hops
HOP TIME FROM TO WITH RELAY
(UTC) TIME
8/16/2023
1 1:35:34 [54.240.48.105] inbound.appriver.com ESMTPS 16 sec
AM
8/16/2023
2 1:35:37 inbound.appriver.com PIPE 3 sec
AM
8/16/2023
3 1:35:37 [10.168.232.249] stdel502.appriver.com ESMTPS *
AM
8/16/2023 Microsoft SMTP Server (version=TLS1_2,
4 1:35:22 stdel502.appriver.com BN8NAM12FT048.mail.protection.outlook.com cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) *
AM
8/16/2023 Microsoft SMTP Server (version=TLS1_2,
5 1:35:23 BN8NAM12FT048.eop-nam12.prod.protection.outlook.com BN1PR13CA0023.outlook.office365.com cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) 1 sec
AM
8/16/2023 Microsoft SMTP Server (version=TLS1_2,
6 1:35:23 BN1PR13CA0023.namprd13.prod.outlook.com SA1PR13MB5038.namprd13.prod.outlook.com cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) *
AM

Original Message Headers

Received: from BN1PR13CA0023.namprd13.prod.outlook.com (2603:10b6:408:e2::28)
by SA1PR13MB5038.namprd13.prod.outlook.com (2603:10b6:806:1a9::9) with
Microsoft SMTP Server (version=TLS1_2,
cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.6678.26; Wed, 16 Aug
2023 01:35:23 +0000
Received: from BN8NAM12FT048.eop-nam12.prod.protection.outlook.com
(2603:10b6:408:e2:cafe::29) by BN1PR13CA0023.outlook.office365.com
(2603:10b6:408:e2::28) with Microsoft SMTP Server (version=TLS1_2,
cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.6699.14 via Frontend
Transport; Wed, 16 Aug 2023 01:35:23 +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
BN8NAM12FT048.mail.protection.outlook.com (10.13.182.214) with Microsoft SMTP
Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id
15.20.6723.4 via Frontend Transport; Wed, 16 Aug 2023 01:35:22 +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 1553921719 for [Washington Borough request email]; Tue, 15 Aug 2023 20:35:37 -0500
X-Note: This Email was scanned by AppRiver SecureTide
X-Note-AR-ScanTimeLocal: 08/15/2023 9:35:37 PM
X-Note: SecureTide Build: 7/31/2023 3:20:24 PM UTC (2.30.2.0)
X-Note: Filtered by 10.168.233.61
X-Note-AR-Scan: None - PIPE
X-Note: CGHH cor:0816013537375-137148960-165376
Received: by inbound.appriver.com (CommuniGate Pro PIPE 7.1.1)
with PIPE id 137148960; Tue, 15 Aug 2023 21:35:37 -0400
Received: from [54.240.48.105] (HELO a48-105.smtp-out.amazonses.com)
by inbound.appriver.com (CommuniGate Pro SMTP 7.1.1)
with ESMTPS id 137148957 for [Washington Borough request email]; Tue, 15 Aug 2023 21:35:34 -0400
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/simple;
s=cofuhmhcsf5ualrhpbcimprdgtodlfak; d=requests.opramachine.com;
t=1692149718;
h=Date:From:To:Message-ID:Subject:Mime-Version:Content-Type:Content-Transfer-Encoding;
bh=DSOzboVY7PsjMv4IlHXhvkHAVxtgpksqa2XQZLZWb04=;
b=UM+SKihCy+kiLxfL0cVnfLZbTBB4lKooSP7PQCg6OhOP7poCjHHS3YGVIZFIh9Ch
t9lxCAT6pvBqFgdwSCddMmZ2/Hq5t21UVFO7DZbCPmn8xQQ5YZREuj5kCe6PmhbcXOJ
Ud5mWuEL2bC3qb20zDH8NZRmVv9y9ZAAWgyZn09o=
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/simple;
s=224i4yxa5dv7c2xz3womw6peuasteono; d=amazonses.com; t=1692149718;
h=Date:From:To:Message-ID:Subject:Mime-Version:Content-Type:Content-Transfer-Encoding:Feedback-ID;
bh=DSOzboVY7PsjMv4IlHXhvkHAVxtgpksqa2XQZLZWb04=;
b=CkLHwdA3urHMqpD9b3AFF7KkwOdBh7VpZEaXStOSC8Kl0xB/h+jhXDvGV0lwbOMi
H92fvB6uf4btn/Lj2dyBCM4JCwOmxP7Aii7aDT8Zzo0AigPYr3c+z1Z0X88cSuYgaLn
oPjk8FXhRh8NkbCzwQ9LLiDqpe8rbmjuC5V/j+ec=
Date: Wed, 16 Aug 2023 01:35:18 +0000
From: Maddie Baisley <[OPRA #50297 email]>
To: OPRA requests at Washington Borough <[Washington Borough request email]>
Message-ID: <[email address]>
Subject: OPRA request - Bid Tabulation Results for Rock Spring Park Trail
Extension
MIME-Version: 1.0
Feedback-ID: 1.us-east-1.Cy+CdIBOIzrBJluvD+AwZTYIIvgMdz3Pedsyi9/dX4g=:AmazonSES
X-SES-Outgoing: 2023.08.16-54.240.48.105
Content-Type: text/plain;
charset=UTF-8
Content-Transfer-Encoding: 7bit
X-Note: This Email was scanned by AppRiver SecureTide
X-Note-AR-ScanTimeLocal: 08/15/2023 9:35:34 PM
X-Note: SecureTide Build: 7/31/2023 3:20:24 PM UTC (2.30.2.0)
X-Note: Filtered by 10.168.233.61
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.105 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.105, Ugly c=0.247104 p=-0.0909091 Source Normal
X-Signature-Violations: 0-0-0-5721-c
X-Note-419: 0 ms. Fail:0 Chk:1432 of 1432 total
X-Note: VSCH-CT/SI: 0-1432/SG:1 8/15/2023 9:34:50 PM
X-Note: Spam Tests Failed:
X-Country-Path: United States of America->LOCAL
X-Note-Sending-IP: 54.240.48.105
X-Note-Reverse-DNS: a48-105.smtp-out.amazonses.com
X-Note-Return-Path: [email address]
X-Note: User Rule Hits:
X-Note: Global Rule Hits: G332 G334 G335 G336 G353 G354 G355 G497 G498 G504 G696 G734 G923
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: BN8NAM12FT048:EE_|SA1PR13MB5038:EE_
X-MS-Office365-Filtering-Correlation-Id: 21557307-ece9-4b06-3b48-08db9df90f0e

References

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