Opra Request
Dear Jackson Township,
Please accept this electronic request for public records made under OPRA and the common law right of access. I am not required to fill out an official form or use a particular software platform to submit my request per NJSA 47:1A-5(f), which states that an email from a requestor including all of the information required on the adopted form shall suffice in place of a completed form as a valid government record request.
I HAVE NOT been convicted of any indictable offense under the laws of New Jersey, any other state, or the United States.
I WILL use the requested government records for a commercial purpose.
I AM NOT seeking records in connection with a legal proceeding.
Records requested:
Tax Delinquent
- A list of all property addresses that have an unpaid property tax bill for the last 12 months. Please also include in the list or separately a list of properties whose property tax bill was liened against the property.
Water Shut Off / Utility Liens
- A list of all property addresses that have had their water bill liened against the property, have failed to pay their water bill, or have had the water shut off at any point in the last 6 months.
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.
My preferred delivery method for response(s) to this request is by E-mail as attachments. Please confirm you have received this request. If you are not the custodian of records, please forward my request to that person and provide their email address to me for future reference.
Yours faithfully,
Nathan
Your message to [Jackson Township request email] couldn't be delivered.
opra wasn't found at jacksontwpnj.net.
0100019d62dac83a-03c. . . Office 365 opra
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 4/6/2026 12:53:18 PM
Date:
Sender [email address]
Address:
Recipient [Jackson Township request email]
Address:
Subject: OPRA request - Opra Request
Error Details
Error: 550 5.1.10 RESOLVER.ADR.RecipientNotFound; Recipient [Jackson Township request email] not
found by SMTP address lookup
Message rejected by: PH8PR09MB10346.namprd09.prod.outlook.com
Notification Details
Sent by: PH8PR09MB10346.namprd09.prod.outlook.com
Message Hops
HOP TIME FROM TO WITH RELAY
(UTC) TIME
4/6/2026 Microsoft SMTP Server (version=TLS1_3,
1 12:53:19 a48-107.smtp-out.amazonses.com SA2PEPF00002252.mail.protection.outlook.com cipher=TLS_AES_256_GCM_SHA384) 1 sec
PM
4/6/2026 Microsoft SMTP Server (version=TLS1_3,
2 12:53:19 SA2PEPF00002252.namprd09.prod.outlook.com CY5PR09CA0008.outlook.office365.com cipher=TLS_AES_256_GCM_SHA384) *
PM
4/6/2026 Microsoft SMTP Server (version=TLS1_2,
3 12:53:19 CY5PR09CA0008.namprd09.prod.outlook.com PH8PR09MB10346.namprd09.prod.outlook.com cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) *
PM
Original Message Headers
Received: from CY5PR09CA0008.namprd09.prod.outlook.com (2603:10b6:930:1::16)
by PH8PR09MB10346.namprd09.prod.outlook.com (2603:10b6:510:18e::21) with
Microsoft SMTP Server (version=TLS1_2,
cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.9769.19; Mon, 6 Apr
2026 12:53:19 +0000
Received: from SA2PEPF00002252.namprd09.prod.outlook.com
(2603:10b6:930:1:cafe::fd) by CY5PR09CA0008.outlook.office365.com
(2603:10b6:930:1::16) with Microsoft SMTP Server (version=TLS1_3,
cipher=TLS_AES_256_GCM_SHA384) id 15.20.9769.32 via Frontend Transport; Mon,
6 Apr 2026 12:53:19 +0000
Authentication-Results: spf=pass (sender IP is 54.240.48.107)
smtp.mailfrom=bounce.requests.opramachine.com; dkim=pass (signature was
verified) header.d=requests.opramachine.com;dkim=pass (signature was
verified) header.d=amazonses.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.107 as permitted sender)
receiver=protection.outlook.com; client-ip=54.240.48.107;
helo=a48-107.smtp-out.amazonses.com; pr=C
Received: from a48-107.smtp-out.amazonses.com (54.240.48.107) by
SA2PEPF00002252.mail.protection.outlook.com (10.167.242.134) with Microsoft
SMTP Server (version=TLS1_3, cipher=TLS_AES_256_GCM_SHA384) id 15.20.9769.17
via Frontend Transport; Mon, 6 Apr 2026 12:53:19 +0000
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/simple;
s=cofuhmhcsf5ualrhpbcimprdgtodlfak; d=requests.opramachine.com;
t=1775479998;
h=Date:From:To:Message-ID:Subject:Mime-Version:Content-Type:Content-Transfer-Encoding;
bh=4xT2sJjrgSX5s1doMHcN5XJt6xK7J6dkFN3QIzyrL/k=;
b=qKjFoVsW3gDcVGrtgwFtEaYZCHAdZqisHq09gqbc5OjR4k83QDsusr2qFjgaauMx
sHuaejsNAwJT6v9R6G3BAEXSXj+FcDqHllm4pF7Rp+5KyIftiBlQTfvOryxw97xy8Ey
7If9OaKPswO3XuWz5axsDMbRwdCOc1m9VwOKZRhg=
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/simple;
s=224i4yxa5dv7c2xz3womw6peuasteono; d=amazonses.com; t=1775479998;
h=Date:From:To:Message-ID:Subject:Mime-Version:Content-Type:Content-Transfer-Encoding:Feedback-ID;
bh=4xT2sJjrgSX5s1doMHcN5XJt6xK7J6dkFN3QIzyrL/k=;
b=Y8N/2rkSWDHnKHfbnwm2x2W421dVVdnK1onuWRqKq2eOJtJsLCWf39Zq5qDcMoIO
dbb+OplOnqPVdJX6n1fgRS4rAAsHur7hdRoE3hsp8ey+3vDVf6pvkEarfu1oyhw88Ls
/1IKD7VcQFrVJLZoN++HWgjXSwbLgUQbEsC3i7go=
Date: Mon, 6 Apr 2026 12:53:18 +0000
From: Nathan Stallone <[OPRA #89440 email]>
To: OPRA requests at Jackson Township <[Jackson 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: quoted-printable
Feedback-ID: ::1.us-east-1.Cy+CdIBOIzrBJluvD+AwZTYIIvgMdz3Pedsyi9/dX4g=:AmazonSES
X-SES-Outgoing: 2026.04.06-54.240.48.107
Return-Path:
[email address]
X-EOPAttributedMessage: 0
X-EOPTenantAttributedMessage: ea557215-1333-403f-9dec-7f56105e1520:0
X-MS-PublicTrafficType: Email
X-MS-TrafficTypeDiagnostic: SA2PEPF00002252:EE_|PH8PR09MB10346:EE_
X-MS-Office365-Filtering-Correlation-Id: 432c622c-b6ac-4928-071f-08de93db7a72
References
Visible links
1. https://go.microsoft.com/fwlink/?LinkId=...
2. https://go.microsoft.com/fwlink/?LinkId=...
3. https://go.microsoft.com/fwlink/?LinkId=...