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

OPRA Request for an addresses

We're waiting for Yael Benkel to read a recent response and update the status.

Dear Bernards Township,

This is a request for public records made under OPRA and the common law right of access. I am not required to fill out an official form. Please acknowledge receipt of this message.
Records requested:

We would like to obtain copies of the following
documents:

Information including but not limited to: police report records, arrest records, incident reports, accident reports, records of warning, past complaints, investigations of wrongdoing, records of citation, and other indicators of impropriety or fraudulent behavior for the following address located in Basking Ridge, NJ:

•49 Queen Anne Drive, Basking Ridge, NJ 07920

Please include all exhibits, notes, interviews, schedules, public comments, and other attachments filed concurrently with each disclosable document.

We request that responsive documents be produced as soon as available, on a rolling basis. If some portions of the records are exempt from mandatory disclosure, then nonexempt materials shall be disclosed after the exempt material has been redacted. If it is determined that portions of a records are exempt, please provide a copy of the remainder of the record. If you withhold any records or any portions of any records as exempt, please provide an explanation of the reasons that the relevant exemption applies and the reasons that a discretionary release of the records would not be appropriate.

Yours faithfully,
Yael Benkel
RosettiStarr, LLC

Bernards Township

2 Attachments

  • Attachment

    attachment.delivery status

    0K Download

  • Attachment

    OPRA request OPRA Request for an addresses.txt

    2K View Download

Your message to [email address] couldn't be delivered.
dszabo wasn't found at bernards.org.
010001754c69cc6b-e6a. . . 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 10/21/2020 6:26:43 PM
Date:
Sender [email address]
Address:
Recipient [email address]
Address:
Subject: OPRA request - OPRA Request for an addresses
Error Details
Reported error: 550 5.1.10 RESOLVER.ADR.RecipientNotFound; Recipient [email address] not found
by SMTP address lookup
DSN generated by: SJ0PR09MB7104.namprd09.prod.outlook.com

Message Hops
HOP TIME (UTC) FROM TO WITH RELAY
TIME
1 10/21/2020 a48-101.smtp-out.amazonses.com mx157.us-east-2b.ess.aws.cudaops.com 1 sec
6:26:44 PM
2 10/21/2020 outbound-ip62b.ess.barracuda.com DM3GCC02FT008.mail.protection.outlook.com Microsoft SMTP Server (version=TLS1_2, 1 sec
6:26:45 PM cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384)
3 10/21/2020 DM3GCC02FT008.eop-gcc02.prod.protection.outlook.com CY4PR09CA0083.outlook.office365.com Microsoft SMTP Server (version=TLS1_2, 1 sec
6:26:46 PM cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384)
4 10/21/2020 CY4PR09CA0083.namprd09.prod.outlook.com SJ0PR09MB7104.namprd09.prod.outlook.com Microsoft SMTP Server (version=TLS1_2, *
6:26:46 PM cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384)

Original Message Headers

Received: from CY4PR09CA0083.namprd09.prod.outlook.com (2603:10b6:903:c7::21)
by SJ0PR09MB7104.namprd09.prod.outlook.com (2603:10b6:a03:266::17) with
Microsoft SMTP Server (version=TLS1_2,
cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3477.22; Wed, 21 Oct
2020 18:26:46 +0000
Received: from DM3GCC02FT008.eop-gcc02.prod.protection.outlook.com
(2a01:111:f400:7d04::209) by CY4PR09CA0083.outlook.office365.com
(2603:10b6:903:c7::21) with Microsoft SMTP Server (version=TLS1_2,
cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3499.18 via Frontend
Transport; Wed, 21 Oct 2020 18:26:46 +0000
Authentication-Results: spf=softfail (sender IP is 209.222.82.239)
smtp.mailfrom=bounce.requests.opramachine.com; bernards.org; dkim=pass
(signature was verified) header.d=requests.opramachine.com;bernards.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 209.222.82.239 as
permitted sender)
Received: from outbound-ip62b.ess.barracuda.com (209.222.82.239) by
DM3GCC02FT008.mail.protection.outlook.com (10.97.8.100) with Microsoft SMTP
Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id
15.20.3499.18 via Frontend Transport; Wed, 21 Oct 2020 18:26:45 +0000
Received: from a48-101.smtp-out.amazonses.com (a48-101.smtp-out.amazonses.com [54.240.48.101]) by mx157.us-east-2b.ess.aws.cudaops.com (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NO); Wed, 21 Oct 2020 18:26:44 +0000
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/simple;
s=75ht6uujunbugea7bv75tq6udjzjx55y; d=requests.opramachine.com;
t=1603304803;
h=Date:From:To:Message-ID:Subject:Mime-Version:Content-Type:Content-Transfer-Encoding;
bh=kJkhttksOhmTu6OWO5BLSh27QbcQ1Be3xOMdcZmbY68=;
b=kEaJUfVezUe+0+pzn+Z70qaJgvP8eZ1s/JbrKlvM4/vhd5YcWZCuID9TRdU/1ls3
LOptOu4VBtg4bqCOQAZiruWjQKf889kd4kf1Z9HVYAOaiz0GyJZ7AkIB2YZUCz8JwEB
cASpW9ICV12IFynQBMJBQN/2rju2PmjH3C478J0c=
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/simple;
s=224i4yxa5dv7c2xz3womw6peuasteono; d=amazonses.com; t=1603304803;
h=Date:From:To:Message-ID:Subject:Mime-Version:Content-Type:Content-Transfer-Encoding:Feedback-ID;
bh=kJkhttksOhmTu6OWO5BLSh27QbcQ1Be3xOMdcZmbY68=;
b=GcNYYDLofnKPuIItgmfNK9uPDZX+bsC6B8lHWft1+6LFyxT3v8BkyRax6AcTRK8R
gygb5Nbz+OZEtFRqnxKm165ZtMrAkW4jjBMwy2TF0qBdHPcAAFUD2B2AGdkoiW8zE9s
ZKnQFtSUz9LVv9JxS752+6i21to/sqsvcyttOf00=
Date: Wed, 21 Oct 2020 18:26:43 +0000
From: Yael Benkel <[OPRA #18006 email]>
To: OPRA requests at Bernards Township <[email address]>
Message-ID: <[email address]>
Subject: OPRA request - OPRA Request for an addresses
MIME-Version: 1.0
Content-Type: text/plain;
charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-SES-Outgoing: 2020.10.21-54.240.48.101
Feedback-ID: 1.us-east-1.Cy+CdIBOIzrBJluvD+AwZTYIIvgMdz3Pedsyi9/dX4g=:AmazonSES
X-BESS-ID: 1603304804-893313-3868-32613-1
X-BESS-VER: 2019.1_20201020.1810
X-BESS-Apparent-Source-IP: 54.240.48.101
X-BESS-Spam-Status: SCORE=1.50 using domain:98918 scores of QUARANTINE_LEVEL=0.0 KILL_LEVEL=5.0 tests=BSF_SC0_SA616_AD_FM10d
Received-SPF: pass (mx157.us-east-2b.ess.aws.cudaops.com: domain of [email address] designates 54.240.48.101 as permitted sender)
X-BESS-Spam-Report: Code version 3.2, rules version 3.2.2.227696 [from cloudscan8-
213.us-east-2a.ess.aws.cudaops.com]
Rule breakdown below
pts rule name description
---- ---------------------- --------------------------------
1.50 BSF_SC0_SA616_AD_FM10d META: Custom Rule SA616_AD_FM10d
X-BESS-Spam-Score: 1.50
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: 30c1faa8-f972-4633-b940-08d875eeddf2
X-MS-TrafficTypeDiagnostic: SJ0PR09MB7104:

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 Yael Benkel please sign in and let everyone know.