Bergan County - OPRA Request
Dear Cresskill Borough,
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:
1) A list of all properties with taxes that are delinquent in amounts of at least $1,500 and beyond that date back to 2021 or prior years. Please include full property location, owner name, amounts, and Class 2 & 1 properties only, if possible.
2) A separate list of all properties with Utilities that are delinquent in amounts of at least $250 and beyond, that date back to 2021 or prior. Please include full property location, owner name, amounts, and Class 2 & 1 properties only, if possible.
3) A list of all properties with open liens in amounts of at least $500 and beyond, that date back to 2021 or prior years. Please include full property location, owner name, amounts, and Class 2 & 1 properties only.
4) A list of all properties that are currently vacant or abandoned. If the
property used to be vacant and no longer is, please do not include. Please include full property location, owner name, and Class 2 & 1 properties only, if possible.
5) A list of all properties that have received code violations for high grass/junk/unkept property that are still active or open. Please do not include closed cases, and provide the type of violation. Also, please include full property location, owner name, and Class 2 & 1 properties only, if possible.
6) A list of all garage sales, applied for this year. Please include owner name, full property address, and date, if possible.
***Please Include Full Property Address for all lists.
If possible, please put all lists in separate Excel files. If up-to-date
data is not available, please provide the most recently available.
I appreciate your time and efforts.
Yours faithfully,
S. Carrero
Your message to [Cresskill Borough request email] couldn't be delivered.
bnasuto wasn't found at cresskillboro.org.
0100018217c93e4e-461. . . Office 365 bnasuto
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/19/2022 6:47:20 PM
Date:
Sender [email address]
Address:
Recipient [Cresskill Borough request email]
Address:
Subject: OPRA request - Bergan County - OPRA Request
Error Details
Reported error: 550 5.1.10 RESOLVER.ADR.RecipientNotFound; Recipient [Cresskill Borough request email] not
found by SMTP address lookup
DSN generated by: DM5PR22MB0058.namprd22.prod.outlook.com
Message Hops
HOP TIME FROM TO WITH RELAY
(UTC) TIME
7/19/2022 Microsoft SMTP Server (version=TLS1_2,
1 6:47:22 a48-108.smtp-out.amazonses.com MW2NAM04FT039.mail.protection.outlook.com cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) 2 sec
PM
7/19/2022 Microsoft SMTP Server (version=TLS1_2,
2 6:47:22 MW2NAM04FT039.eop-NAM04.prod.protection.outlook.com MW4PR03CA0086.outlook.office365.com cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) *
PM
7/19/2022 Microsoft SMTP Server (version=TLS1_2,
3 6:47:22 MW4PR03CA0086.namprd03.prod.outlook.com DM5PR22MB0058.namprd22.prod.outlook.com cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) *
PM
Original Message Headers
Received: from MW4PR03CA0086.namprd03.prod.outlook.com (2603:10b6:303:b6::31)
by DM5PR22MB0058.namprd22.prod.outlook.com (2603:10b6:3:56::22) with
Microsoft SMTP Server (version=TLS1_2,
cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.5438.23; Tue, 19 Jul
2022 18:47:22 +0000
Received: from MW2NAM04FT039.eop-NAM04.prod.protection.outlook.com
(2603:10b6:303:b6:cafe::a0) by MW4PR03CA0086.outlook.office365.com
(2603:10b6:303:b6::31) with Microsoft SMTP Server (version=TLS1_2,
cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.5438.23 via Frontend
Transport; Tue, 19 Jul 2022 18:47:22 +0000
Authentication-Results: spf=pass (sender IP is 54.240.48.108)
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: Pass (protection.outlook.com: domain of
bounce.requests.opramachine.com designates 54.240.48.108 as permitted sender)
receiver=protection.outlook.com; client-ip=54.240.48.108;
helo=a48-108.smtp-out.amazonses.com; pr=C
Received: from a48-108.smtp-out.amazonses.com (54.240.48.108) by
MW2NAM04FT039.mail.protection.outlook.com (10.13.30.110) with Microsoft SMTP
Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id
15.20.5458.17 via Frontend Transport; Tue, 19 Jul 2022 18:47:22 +0000
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/simple;
s=drvjftetwukgvxxawhtk3luf3y2o3amm; d=requests.opramachine.com;
t=1658256441;
h=Date:From:To:Message-ID:Subject:Mime-Version:Content-Type:Content-Transfer-Encoding;
bh=r5BOWvWV4rsBJeUde39Fw9QCNGZD4YYitnftLiRalW8=;
b=RQwM5+ILkkx1yyUZHgtr2qig5q3eOIFRUfkpsPpT5ZMXKI+SzYWP5nuMbxaIcbgO
fu6GSnMWvqWgmnqbZPG7OJFzGJR8cog27lAk2k1b7nXVDs1UJQTBdTOUmuM9S4tQ1Fz
DNTtDm6S9VgAtVawF9kHYZdpV+us+gux1H7PPgq4=
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/simple;
s=6gbrjpgwjskckoa6a5zn6fwqkn67xbtw; d=amazonses.com; t=1658256441;
h=Date:From:To:Message-ID:Subject:Mime-Version:Content-Type:Content-Transfer-Encoding:Feedback-ID;
bh=r5BOWvWV4rsBJeUde39Fw9QCNGZD4YYitnftLiRalW8=;
b=eaQhq0/IbQL/0qWhyGUA1izwmmcAvYaUncPxalDmOATmIYsYvdesO1tItDvcShjQ
W5E9Ac7rCl6tm1ld8FFHcc1B0ZthBd/jESPfjGcJG1uDwcLS+hhptl9+xVASQcSyIB2
7U6ms+7TGm4EfwcyxF1KEwetsUCbNSLM0mOOLh8w=
Date: Tue, 19 Jul 2022 18:47:20 +0000
From: "S. Carrero" <[OPRA #34028 email]>
To: OPRA requests at Cresskill Borough <[Cresskill Borough request email]>
Message-ID: <[email address]>
Subject: OPRA request - Bergan County - OPRA Request
MIME-Version: 1.0
Content-Type: text/plain;
charset=UTF-8
Content-Transfer-Encoding: 7bit
Feedback-ID: 1.us-east-1.Cy+CdIBOIzrBJluvD+AwZTYIIvgMdz3Pedsyi9/dX4g=:AmazonSES
X-SES-Outgoing: 2022.07.19-54.240.48.108
Return-Path:
[email address]
X-EOPAttributedMessage: 0
X-EOPTenantAttributedMessage: 82dad6cc-2f61-4522-89b2-4f5a56289de7:0
X-MS-PublicTrafficType: Email
X-MS-Office365-Filtering-Correlation-Id: f68112c5-9d25-44e7-7490-08da69b71da1
X-MS-TrafficTypeDiagnostic: DM5PR22MB0058: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=...