OPRA Request

Nathan Stallone made this OPRA request to Cedar Grove Township Automatic anti-spam measures are in place for this older request. Please let us know if a further response is expected or if you are having trouble responding.

Response to this request is long overdue. By law, under all circumstances, Cedar Grove Township should have responded by now (details). You can complain by requesting an internal review.

Dear Cedar Grove 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:

Fire Damage List
- A list of all property addresses that the fire department has received an emergency call to in the last 90 days.

Code Violation
- A list of property addresses that have received any code violations in the last 6 months

Vacant List
- A list of all properties that the city deems to be currently vacant or abandoned.

Yours faithfully,

Nathan

Cedar Grove Township

2 Attachments

Your message to [Cedar Grove Township request email] couldn't be delivered.
townclerk wasn't found at cedargrovenj.org.
0100019128ec1ee4-ad1. . . Office 365 townclerk
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/6/2024 6:20:48 PM
Date:
Sender [email address]
Address:
Recipient [Cedar Grove Township request email]
Address:
Subject: OPRA request - OPRA Request
Error Details
Error: 550 5.1.10 RESOLVER.ADR.RecipientNotFound; Recipient [Cedar Grove Township request email]
not found by SMTP address lookup
Message rejected by: SA1PR09MB10722.namprd09.prod.outlook.com
Notification Details
Sent by: SA1PR09MB10722.namprd09.prod.outlook.com

Message Hops
HOP TIME FROM TO WITH RELAY
(UTC) TIME
8/6/2024
1 6:20:49 a8-95.smtp-out.amazonses.com mx-inbound21-144.us-east-2b.ess.aws.cudaops.com 1 sec
PM
8/6/2024 Microsoft SMTP Server (version=TLS1_2,
2 6:20:51 outbound-ip137b.ess.barracuda.com DS4PEPF0000016F.mail.protection.outlook.com cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) 2 sec
PM
8/6/2024 Microsoft SMTP Server (version=TLS1_2,
3 6:20:51 DS4PEPF0000016F.namprd09.prod.outlook.com CY5PR09CA0025.outlook.office365.com cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) *
PM
8/6/2024 Microsoft SMTP Server (version=TLS1_2,
4 6:20:52 CY5PR09CA0025.namprd09.prod.outlook.com SA1PR09MB10722.namprd09.prod.outlook.com cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) 1 sec
PM

Original Message Headers

Received: from CY5PR09CA0025.namprd09.prod.outlook.com (2603:10b6:930:1::19)
by SA1PR09MB10722.namprd09.prod.outlook.com (2603:10b6:806:372::8) with
Microsoft SMTP Server (version=TLS1_2,
cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.7828.24; Tue, 6 Aug
2024 18:20:52 +0000
Received: from DS4PEPF0000016F.namprd09.prod.outlook.com
(2603:10b6:930:1:cafe::89) by CY5PR09CA0025.outlook.office365.com
(2603:10b6:930:1::19) with Microsoft SMTP Server (version=TLS1_2,
cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.7828.27 via Frontend
Transport; Tue, 6 Aug 2024 18:20:51 +0000
Authentication-Results: spf=softfail (sender IP is 209.222.82.73)
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.73 as permitted
sender)
Received: from outbound-ip137b.ess.barracuda.com (209.222.82.73) by
DS4PEPF0000016F.mail.protection.outlook.com (10.167.18.197) with Microsoft
SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id
15.20.7849.8 via Frontend Transport; Tue, 6 Aug 2024 18:20:51 +0000
Received: from a8-95.smtp-out.amazonses.com (a8-95.smtp-out.amazonses.com [54.240.8.95]) by mx-inbound21-144.us-east-2b.ess.aws.cudaops.com (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Tue, 06 Aug 2024 18:20:49 +0000
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/simple;
s=75ht6uujunbugea7bv75tq6udjzjx55y; d=requests.opramachine.com;
t=1722968449;
h=Date:From:To:Message-ID:Subject:Mime-Version:Content-Type:Content-Transfer-Encoding;
bh=euinzgxLDAToI4ShC23ijgVuf8FbGw+iKqctoR9ECdk=;
b=b/bmNAV/fT/1nzrgEzxkwMqCOq9by1daK7MjljSoz2e9ozZjtakS1yp6Ua5+cYQG
5+Oks5+zLgAI2o9NaJrrhBTIZ26ORli1rLRaoOpZYS3G34klibArLXGL+Pw4jQPe6qW
tu1s9a8mwE05CulI3s1ajQlaabe0iDeDbJEqwFGs=
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/simple;
s=ug7nbtf4gccmlpwj322ax3p6ow6yfsug; d=amazonses.com; t=1722968449;
h=Date:From:To:Message-ID:Subject:Mime-Version:Content-Type:Content-Transfer-Encoding:Feedback-ID;
bh=euinzgxLDAToI4ShC23ijgVuf8FbGw+iKqctoR9ECdk=;
b=s9mhkCEDGa7vgqRqvxuD/v7Rcl6r5rucCzFxXs9DqrvPZ4Nw7xAjBIK2A1K4wXYv
/CSR+2KQck+1gKHoieJXbmkwpxE3lw8TLB0xvC3b2lyRstweu/yrossLFsS6qgGWhcv
fDzAcTmBcJeoKmb/+y77ktP392JZz9Lh/zdGLuU4=
Date: Tue, 6 Aug 2024 18:20:48 +0000
From: Nathan Stallone <[OPRA #64533 email]>
To: OPRA requests at Cedar Grove Township <[Cedar Grove Township request email]>
Message-ID: <[email address]>
Subject: OPRA request - 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: 2024.08.06-54.240.8.95
X-BESS-ID: 1722968449-105520-12802-18145-1
X-BESS-VER: 2019.1_20240802.1821
X-BESS-Apparent-Source-IP: 54.240.8.95
X-BESS-Parts: H4sIAAAAAAACA4uuVkqtKFGyUioBkjpK+cVKVoam5uZAVgZQ0MTMMMXS0MzI0N
zQPNHYICUp1dLAwsLQyMTQIiXFMtVEqTYWAJr8P39BAAAA
X-BESS-Spam-Status: SCORE=0.00 using account:ESS187825 scores of QUARANTINE_LEVEL=0.0 KILL_LEVEL=5.0 tests=
Received-SPF: pass (mx-inbound21-144.us-east-2b.ess.aws.cudaops.com: domain of [email address] designates 54.240.8.95 as permitted sender)
X-BESS-Spam-Score: 0.00
Authentication-Results-Original: mx-inbound21-144.us-east-2b.ess.aws.cudaops.com; spf=pass (sender IP is
54.240.8.95)
smtp.mailfrom=[email address];
dkim=none header.d=; dmarc=none
header.from=[OPRA #64533 email]
X-BESS-Spam-Report: Code version 3.2, rules version 3.2.2.258153 [from cloudscan15-
68.us-east-2a.ess.aws.cudaops.com]
Rule breakdown below
pts rule name description
---- ---------------------- --------------------------------
X-BESS-BRTS-Status: 1
Return-Path:
[email address]
X-EOPAttributedMessage: 0
X-EOPTenantAttributedMessage: ab2a865a-fba6-49a9-9605-c56b308d0248:0
X-MS-PublicTrafficType: Email
X-MS-TrafficTypeDiagnostic: DS4PEPF0000016F:EE_|SA1PR09MB10722:EE_
X-MS-Office365-Filtering-Correlation-Id: 0de3767f-bfd9-49c5-ce0b-08dcb64480df

References

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