Permit Request 216 Johnson St -Block 37 Lot 1

This request has been withdrawn by the person who made it. There may be an explanation in the correspondence below.

Dear Ben Angeli (Custodian),

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 NOT use the requested government records for a commercial purpose.
I AM NOT seeking records in connection with a legal proceeding.

RECORDS REQUESTED:
Please provide a copy of ALL PERMITS (open and closed between Jan 1, 2020-July 7, 2026) for the property located at 216 Johnson St (Block 37, Lot 1), Salem, New Jersey 08079. .

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.

Janice Roots

Salem City

2 Attachments

  • Attachment

    attachment.delivery status

    0K Download

  • Attachment

    OPRA request Permit Request 216 Johnson St Block 37 Lot 1.txt

    2K View Download

Your message to [Salem City request email] couldn't be delivered.
cityclerk wasn't found at cityofsalemnj.gov.
0100019f94946fd4-243. . . Office 365 cityclerk
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/24/2026 2:43:03 PM
Date:
Sender [email address]
Address:
Recipient [Salem City request email]
Address:
Subject: OPRA request - Permit Request 216 Johnson St -Block 37 Lot 1
Error Details
Error: 550 5.1.10 RESOLVER.ADR.RecipientNotFound; Recipient [Salem City request email]
not found by SMTP address lookup
Message rejected by: CY2PR09MB12654.namprd09.prod.outlook.com
Notification Details
Sent by: CY2PR09MB12654.namprd09.prod.outlook.com

Message Hops
HOP TIME FROM TO WITH RELAY
(UTC) TIME
7/24/2026 Microsoft SMTP Server (version=TLS1_3,
1 2:43:04 a8-87.smtp-out.amazonses.com DS1PEPF00017E08.mail.protection.outlook.com cipher=TLS_AES_256_GCM_SHA384) 1 sec
PM
7/24/2026 Microsoft SMTP Server (version=TLS1_3,
2 2:43:05 DS1PEPF00017E08.namprd09.prod.outlook.com BL0PR0901CA0028.outlook.office365.com cipher=TLS_AES_256_GCM_SHA384) 1 sec
PM
7/24/2026 Microsoft SMTP Server (version=TLS1_2,
3 2:43:05 BL0PR0901CA0028.namprd09.prod.outlook.com CY2PR09MB12654.namprd09.prod.outlook.com cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) *
PM

Original Message Headers

Received: from BL0PR0901CA0028.namprd09.prod.outlook.com
(2603:10b6:208:1c0::38) by CY2PR09MB12654.namprd09.prod.outlook.com
(2603:10b6:930:122::19) with Microsoft SMTP Server (version=TLS1_2,
cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.21.245.12; Fri, 24 Jul
2026 14:43:05 +0000
Received: from DS1PEPF00017E08.namprd09.prod.outlook.com
(2603:10b6:208:1c0:cafe::19) by BL0PR0901CA0028.outlook.office365.com
(2603:10b6:208:1c0::38) with Microsoft SMTP Server (version=TLS1_3,
cipher=TLS_AES_256_GCM_SHA384) id 15.21.245.11 via Frontend Transport; Fri,
24 Jul 2026 14:43:05 +0000
Authentication-Results: spf=pass (sender IP is 54.240.8.87)
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.8.87 as permitted sender)
receiver=protection.outlook.com; client-ip=54.240.8.87;
helo=a8-87.smtp-out.amazonses.com; pr=C
Received: from a8-87.smtp-out.amazonses.com (54.240.8.87) by
DS1PEPF00017E08.mail.protection.outlook.com (10.167.18.165) with Microsoft
SMTP Server (version=TLS1_3, cipher=TLS_AES_256_GCM_SHA384) id 15.21.270.5
via Frontend Transport; Fri, 24 Jul 2026 14:43:04 +0000
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/simple;
s=cofuhmhcsf5ualrhpbcimprdgtodlfak; d=requests.opramachine.com;
t=1784904184;
h=Date:From:To:Message-ID:Subject:Mime-Version:Content-Type:Content-Transfer-Encoding;
bh=Cyj2mw3EAeQOLNFp9ZC0VQtP1QA9noDjjdNuAwfMWDs=;
b=ZS3+p3McdXMONdca4pluVO0uHn7Baf/WPfMeJx/vpZhD5IfjRZdsNOjhcKTWO3cI
JUGtdNkCVQbgUq88Egw100aqeck68zMeYkXPZWaV4dHRtTvZJHRgBpgVnzf59Gs/rYr
uU23CZhsTqvTOVsQwjwI1Ok938gxe0cfRBAG6zao=
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/simple;
s=224i4yxa5dv7c2xz3womw6peuasteono; d=amazonses.com; t=1784904184;
h=Date:From:To:Message-ID:Subject:Mime-Version:Content-Type:Content-Transfer-Encoding:Feedback-ID;
bh=Cyj2mw3EAeQOLNFp9ZC0VQtP1QA9noDjjdNuAwfMWDs=;
b=kFaKfR7oKyzllGbJ5Ocgs7JfwpbtrhTw+wfy5HtlZ/W9hOyeawUhCa6VjLfYgQev
GcX1E2+MgCSZB+3vEhdm56pEtc7TtdRRVfK/E+H3mYqFHnVHcedHw74oaXCRfy5Ujaa
En1hsfuKLylx22D6TRfdxSE7+DiY5IvNkY+I1Eew=
Date: Fri, 24 Jul 2026 14:43:03 +0000
From: Janice Roots <[OPRA #93707 email]>
To: OPRA requests at Salem City <[Salem City request email]>
Message-ID: <[email address]>
Subject: OPRA request - Permit Request 216 Johnson St -Block 37 Lot 1
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.07.24-54.240.8.87
Return-Path:
[email address]
X-EOPAttributedMessage: 0
X-EOPTenantAttributedMessage: b54d12cd-398f-4e84-af8a-b626e9ac133d:0
X-MS-PublicTrafficType: Email
X-MS-TrafficTypeDiagnostic: DS1PEPF00017E08:EE_|CY2PR09MB12654:EE_
X-MS-Office365-Filtering-Correlation-Id: 9b7a42d6-bb2a-408f-71a6-08dee991de96

References

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

Dear Salem City,
Please withdraw this request. Replacing with an amended request.
Thank You,
Janice Roots

Salem City

2 Attachments

  • Attachment

    attachment.delivery status

    0K Download DSN: 5.1.1 Bad destination mailbox address

  • Attachment

    Re OPRA request Permit Request 216 Johnson St Block 37 Lot 1.txt

    9K View Download

An error occurred while trying to deliver the mail to the following recipients:
[Salem City request email]