Your message to [email address] couldn't be delivered.
dgodleski wasn't found at boundbrook-nj.org.
0100017a8c468a33-95d. . . Office 365 dgodleski
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/9/2021 5:17:51 PM
Date:
Sender [email address]
Address:
Recipient [email address]
Address:
Subject: OPRA request - Permit Search for 231 Thompson Avenue, Bound Brook, NJ
Error Details
Reported error: 550 5.1.10 RESOLVER.ADR.RecipientNotFound; Recipient [email address] not
found by SMTP address lookup
DSN generated by: PH0PR15MB4925.namprd15.prod.outlook.com

Message Hops
HOP TIME FROM TO WITH RELAY
(UTC) TIME
7/9/2021
1 5:17:51 [54.240.48.101] inbound.appriver.com ESMTPS *
PM
7/9/2021
2 5:17:54 inbound.appriver.com PIPE 3 sec
PM
7/9/2021
3 5:17:54 [10.168.233.3] stdel503.appriver.com ESMTP *
PM
7/9/2021
4 5:17:54 stdel503.appriver.com MW2NAM10FT011.mail.protection.outlook.com Microsoft SMTP Server *
PM
7/9/2021 Microsoft SMTP Server (version=TLS1_2,
5 5:17:55 MW2NAM10FT011.eop-nam10.prod.protection.outlook.com MWHPR19CA0068.outlook.office365.com cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) 1 sec
PM
7/9/2021 Microsoft SMTP Server (version=TLS1_2,
6 5:17:55 MWHPR19CA0068.namprd19.prod.outlook.com PH0PR15MB4925.namprd15.prod.outlook.com cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) *
PM

Original Message Headers

Received: from MWHPR19CA0068.namprd19.prod.outlook.com (2603:10b6:300:94::30)
by PH0PR15MB4925.namprd15.prod.outlook.com (2603:10b6:510:c4::11) with
Microsoft SMTP Server (version=TLS1_2,
cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.4308.22; Fri, 9 Jul
2021 17:17:55 +0000
Received: from MW2NAM10FT011.eop-nam10.prod.protection.outlook.com
(2603:10b6:300:94:cafe::16) by MWHPR19CA0068.outlook.office365.com
(2603:10b6:300:94::30) with Microsoft SMTP Server (version=TLS1_2,
cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.4308.20 via Frontend
Transport; Fri, 9 Jul 2021 17:17:55 +0000
Authentication-Results: spf=softfail (sender IP is 8.19.118.152)
smtp.mailfrom=bounce.requests.opramachine.com; boundbrook-nj.org; dkim=pass
(signature was verified) header.d=requests.opramachine.com;boundbrook-nj.org;
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.152 as permitted
sender)
Received: from stdel503.appriver.com (8.19.118.152) by
MW2NAM10FT011.mail.protection.outlook.com (10.13.154.237) with Microsoft SMTP
Server id 15.20.4308.20 via Frontend Transport; Fri, 9 Jul 2021 17:17:54
+0000
X-Note: Xit Build: 3/16/2017 5:09:20 PM UTC (2.6.15.0) XIT_SCAN_PASSED
Received: from [10.168.233.3] (HELO inbound.appriver.com)
by stdel503.appriver.com (CommuniGate Pro SMTP 6.2.15)
with ESMTP id 63612381 for [email address]; Fri, 09 Jul 2021 12:17:54 -0500
X-Note: This Email was scanned by AppRiver SecureTide
X-Note-AR-ScanTimeLocal: 07/09/2021 1:17:54 PM
X-Note: SecureTide Build: 6/17/2021 4:04:58 PM UTC (2.18.14.0)
X-Note: Filtered by 10.60.1.74
X-Note-AR-Scan: None - PIPE
X-Note: CGHH cor:0709171754360-232608649-76642
Received: by inbound.appriver.com (CommuniGate Pro PIPE 6.2.15)
with PIPE id 232608649; Fri, 09 Jul 2021 13:17:54 -0400
Received: from [54.240.48.101] (HELO a48-101.smtp-out.amazonses.com)
by inbound.appriver.com (CommuniGate Pro SMTP 6.2.15)
with ESMTPS id 232608632 for [email address]; Fri, 09 Jul 2021 13:17:51 -0400
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/simple;
s=75ht6uujunbugea7bv75tq6udjzjx55y; d=requests.opramachine.com;
t=1625851071;
h=Date:From:To:Message-ID:Subject:Mime-Version:Content-Type:Content-Transfer-Encoding;
bh=SP3wzCdQhiUeOYhR2phfvdHACtD8vNRN7npX9z5WgD0=;
b=C8N7L9h2Vq1b3au+f5i2uYbe9MuJ3uB3Th6Vw5IJhmENIi/stYWbCAmP8txx6K8x
XjWu9vEisLjB2LRo1M6XpIa9Dhqf7GNB8xibJ9czozYMa7ePfQfXK7ZdvOw8XrngYOk
k0fTQ8dXHxXg2iFqGpbAXyB3Z22w3RHxyGVQeS+Q=
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/simple;
s=ug7nbtf4gccmlpwj322ax3p6ow6yfsug; d=amazonses.com; t=1625851071;
h=Date:From:To:Message-ID:Subject:Mime-Version:Content-Type:Content-Transfer-Encoding:Feedback-ID;
bh=SP3wzCdQhiUeOYhR2phfvdHACtD8vNRN7npX9z5WgD0=;
b=BCA1kjH7Ck/pI6U3F0NBO6Fm6iuo89CqHOk4e2xEWVIGije2Y6b1V2Uf7JzSkauM
cnG0//cC3scTtgljEp973b3Es27GLjiUA+xe4AElI5gpwbzQ2jAdTxlhQcNewKBxtuT
9CMzJu71d5ITYNz1EygLwICMHEX47EITUXQWTGzI=
Date: Fri, 9 Jul 2021 17:17:51 +0000
From: Karen Williams <[OPRA #24507 email]>
To: OPRA requests at Bound Brook Borough <[email address]>
Message-ID: <[email address]>
Subject: OPRA request - Permit Search for 231 Thompson Avenue, Bound Brook, NJ
MIME-Version: 1.0
Feedback-ID: 1.us-east-1.Cy+CdIBOIzrBJluvD+AwZTYIIvgMdz3Pedsyi9/dX4g=:AmazonSES
X-SES-Outgoing: 2021.07.09-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: 07/09/2021 1:17:51 PM
X-Note: SecureTide Build: 6/17/2021 4:04:58 PM UTC (2.18.14.0)
X-Note: Filtered by 10.60.1.74
X-Policy: boundbrook-nj.org
X-Primary: [email address]
X-Note-Sender: [email address]
X-Note-Envelope-Recip: FAILURE,DELAY, <[email address]>
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.303425 p=-0.0526316 Source Normal
X-Signature-Violations: 0-0-0-4656-c
X-Note-419: 31.2547 ms. Fail:2 Chk:1428 of 1428 total
X-Note: VSCH-CT/SI: 2-1428/SG:1 7/9/2021 1:17:16 PM
X-Note: Spam Tests Failed:
X-Country-Path: United States of America->
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: G838 G841 G842 G843 G861 G862 G863 G999 G1000 G1006 G1279 G1333
X-Note: Encrypt Rule Hits:
X-Note: Mail Class: VALID
Return-Path:
[email address]
X-EOPAttributedMessage: 0
X-EOPTenantAttributedMessage: c1671e78-ea93-426b-8b56-3f429b0a82c1:0
X-MS-PublicTrafficType: Email
X-MS-Office365-Filtering-Correlation-Id: f9754546-04a4-4e7f-d702-08d942fd7d92
X-MS-TrafficTypeDiagnostic: PH0PR15MB4925:

References

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