We don't know whether the most recent response to this request contains information or not – if you are Pavan Kumar please sign in and let everyone know.

Open Code, Permits & Special Info Request: 25 WOODWARD LN, BASKING RIDGE, NJ 07920

We're waiting for Pavan Kumar to read a recent response and update the status.

Hello –

Property Address : 25 WOODWARD LN, BASKING RIDGE, NJ 07920

Block : 9202 Lot : 13

AppID: 331878

Request Type: Due Diligence Only (Not for Resale)

1. For the above referenced property, please provide a Municipal Search to include:

· Special Assessments

· Open/Expired Permits

· Code Violations

· Is property scheduled for Demolition? If yes, please note the date scheduled.

· Please include any balances owed with payoffs good 30 days from the date of this letter.

Please reply directly to this email with the completed request. For any problems or issues with this request,
please contact [email address] and the issue shall be reviewed by our management/support team to be cured.

Bernards Township

2 Attachments

  • Attachment

    attachment.delivery status

    0K Download

  • Attachment

    OPRA request Open Code Permits Special Info Request 25 WOODWARD LN BASKING RIDGE NJ 07920.txt

    2K View Download

Your message to [email address] couldn't be delivered.
dszabo wasn't found at bernards.org.
010001814f1b2a22-dc8. . . Office 365 dszabo
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 6/10/2022 7:33:09 PM
Date:
Sender [email address]
Address:
Recipient [email address]
Address:
Subject: OPRA request - Open Code, Permits & Special Info Request: 25 WOODWARD LN, BASKING RIDGE, NJ
07920
Error Details
Reported error: 550 5.1.10 RESOLVER.ADR.RecipientNotFound; Recipient [email address] not found
by SMTP address lookup
DSN generated by: BY3PR09MB7426.namprd09.prod.outlook.com

Message Hops
HOP TIME FROM TO WITH RELAY
(UTC) TIME
6/10/2022
1 7:33:09 a48-107.smtp-out.amazonses.com mx-inbound13-190.us-east-2a.ess.aws.cudaops.com *
PM
6/10/2022 Microsoft SMTP Server (version=TLS1_2,
2 7:33:16 outbound-ip121a.ess.barracuda.com BL0GCC02FT042.mail.protection.outlook.com cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) 7 sec
PM
6/10/2022 Microsoft SMTP Server (version=TLS1_2,
3 7:33:16 BL0GCC02FT042.eop-gcc02.prod.protection.outlook.com BL0PR0901CA0006.outlook.office365.com cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) *
PM
6/10/2022 Microsoft SMTP Server (version=TLS1_2,
4 7:33:16 BL0PR0901CA0006.namprd09.prod.outlook.com BY3PR09MB7426.namprd09.prod.outlook.com cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) *
PM

Original Message Headers

Received: from BL0PR0901CA0006.namprd09.prod.outlook.com
(2603:10b6:208:1c0::16) by BY3PR09MB7426.namprd09.prod.outlook.com
(2603:10b6:a03:34d::11) with Microsoft SMTP Server (version=TLS1_2,
cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.5332.12; Fri, 10 Jun
2022 19:33:16 +0000
Received: from BL0GCC02FT042.eop-gcc02.prod.protection.outlook.com
(2a01:111:f400:7d05::202) by BL0PR0901CA0006.outlook.office365.com
(2603:10b6:208:1c0::16) with Microsoft SMTP Server (version=TLS1_2,
cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.5332.13 via Frontend
Transport; Fri, 10 Jun 2022 19:33:16 +0000
Authentication-Results: spf=softfail (sender IP is 209.222.82.130)
smtp.mailfrom=bounce.requests.opramachine.com; dkim=fail (body hash did not
verify) header.d=requests.opramachine.com;dmarc=fail action=none
header.from=requests.opramachine.com;
Received-SPF: SoftFail (protection.outlook.com: domain of transitioning
bounce.requests.opramachine.com discourages use of 209.222.82.130 as
permitted sender)
Received: from outbound-ip121a.ess.barracuda.com (209.222.82.130) by
BL0GCC02FT042.mail.protection.outlook.com (10.97.10.95) with Microsoft SMTP
Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id
15.20.5332.12 via Frontend Transport; Fri, 10 Jun 2022 19:33:16 +0000
Received: from a48-107.smtp-out.amazonses.com (a48-107.smtp-out.amazonses.com [54.240.48.107]) by mx-inbound13-190.us-east-2a.ess.aws.cudaops.com (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Fri, 10 Jun 2022 19:33:09 +0000
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/simple;
s=drvjftetwukgvxxawhtk3luf3y2o3amm; d=requests.opramachine.com;
t=1654889589;
h=Date:From:To:Message-ID:Subject:Mime-Version:Content-Type:Content-Transfer-Encoding;
bh=4QKw7Ed5lriaKd6Mo5H8bG978zCHmAcj+2zO/jf9Tl0=;
b=hkMtDc1eSa7LP/Jtngn+Xgts9zlzy47pObgZZwdphWyZ5/iiYB053RsLfPE0QQ7Q
7eLVwvRHZ0frAvcjVGjoAddKjPL4d61qmo57KyCadIYhssXZh7jGIW57+6XuUf6J05C
sRoKJR+7f78x2HOb/6hOiwVukUy5Au1Gsi4wN9qc=
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/simple;
s=6gbrjpgwjskckoa6a5zn6fwqkn67xbtw; d=amazonses.com; t=1654889589;
h=Date:From:To:Message-ID:Subject:Mime-Version:Content-Type:Content-Transfer-Encoding:Feedback-ID;
bh=4QKw7Ed5lriaKd6Mo5H8bG978zCHmAcj+2zO/jf9Tl0=;
b=RnhdQQMEfI2OTLy6lxMZCRnFfsr3IGSfhbi0faa4BF/zriL+ltCzWWd3eFd3Q/sl
FxRKFNAAftavXDpZYg5VqOO0GKCsUIUeglPtIixDBBBMw8YGR0vRgxHMWTjMUhmiLLe
aDikUdQQ2wibqvQqSWLmFrtpgp6qrfvYe7AXRgYU=
Date: Fri, 10 Jun 2022 19:33:09 +0000
From: Pavan Kumar <[OPRA #32538 email]>
To: OPRA requests at Bernards Township <[email address]>
Message-ID: <[email address]>
Subject: OPRA request - Open Code, Permits & Special Info Request: 25 WOODWARD
LN, BASKING RIDGE, NJ 07920
MIME-Version: 1.0
Content-Type: text/plain;
charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Feedback-ID: 1.us-east-1.Cy+CdIBOIzrBJluvD+AwZTYIIvgMdz3Pedsyi9/dX4g=:AmazonSES
X-SES-Outgoing: 2022.06.10-54.240.48.107
X-BESS-ID: 1654889589-103518-5398-10012-1
X-BESS-VER: 2019.1_20220523.1816
X-BESS-Apparent-Source-IP: 54.240.48.107
X-BESS-Spam-Status: SCORE=0.00 using domain:98918 scores of QUARANTINE_LEVEL=0.0 KILL_LEVEL=5.0 tests=
Received-SPF: pass (mx-inbound13-190.us-east-2a.ess.aws.cudaops.com: domain of [email address] designates 54.240.48.107 as permitted sender)
X-BESS-Spam-Report: Code version 3.2, rules version 3.2.2.240595 [from cloudscan23-
209.us-east-2b.ess.aws.cudaops.com]
Rule breakdown below
pts rule name description
---- ---------------------- --------------------------------
X-BESS-Spam-Score: 0.00
X-BESS-BRTS-Status: 1
Return-Path:
[email address]
X-EOPAttributedMessage: 0
X-EOPTenantAttributedMessage: b3a03588-4899-4cf4-8ce8-33dfcfff621b:0
X-MS-PublicTrafficType: Email
X-MS-Office365-Filtering-Correlation-Id: 7e6c9b1d-93ec-4810-b6e0-08da4b1810fc
X-MS-TrafficTypeDiagnostic: BY3PR09MB7426:EE_

References

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

We don't know whether the most recent response to this request contains information or not – if you are Pavan Kumar please sign in and let everyone know.