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

City sold properties

Frank Kelly made this OPRA request to Salem City 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.

We're waiting for Frank Kelly to read a recent response and update the status.

Frank Kelly
Unknown

Dear Salem City,

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-6(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:

1. Tax Foreclosure Sales
• A list of all properties acquired by the City of Salem through tax foreclosure then sold
• For each property, please provide:
• Property address and/or block and lot
• Name of the purchaser or transferee
• Purchase price or consideration
• Date of transfer or sale

2. Voluntary Conveyances to Avoid Tax Foreclosure
• A list of all properties where the owner executed a deed or agreement to transfer the property to the City of Salem in order to avoid tax foreclosure.
• For each property, please provide the same details listed above.

3. Any and All Sales or Deeds Transferred by the City of Salem
• A list of any and all properties sold or transferred by deed from the City of Salem to another owner during this period, whether by public auction, private sale, or other disposition.
• For each property, please provide the same details listed above.

4. Supporting Documentation
• For each of the above transactions, please also provide:
• The legal notice(s) published in connection with the sale or transfer
• Any Request for Proposals (RFPs), Requests for Qualifications (RFQs), Requests for Bids (RFBs), or similar bid solicitation documents issued in connection with the sale or transfer

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,
F Kelly

Link to this Report
Salem City

2 Attachments

Your message to [Salem City request email] couldn't be delivered.
cityclerk wasn't found at cityofsalemnj.gov.
01000198fd4f0889-1b4. . . 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 8/30/2025 11:27:51 PM
Date:
Sender [email address]
Address:
Recipient [Salem City request email]
Address:
Subject: OPRA request - City sold properties
Error Details
Error: 550 5.1.10 RESOLVER.ADR.RecipientNotFound; Recipient [Salem City request email]
not found by SMTP address lookup
Message rejected by: SJ0PR09MB9970.namprd09.prod.outlook.com
Notification Details
Sent by: SJ0PR09MB9970.namprd09.prod.outlook.com

Message Hops
HOP TIME FROM TO WITH RELAY
(UTC) TIME
8/30/2025 Microsoft SMTP Server (version=TLS1_3,
1 11:27:52 a8-87.smtp-out.amazonses.com SA2PEPF00002250.mail.protection.outlook.com cipher=TLS_AES_256_GCM_SHA384) 1 sec
PM
8/30/2025 Microsoft SMTP Server (version=TLS1_3,
2 11:27:53 SA2PEPF00002250.namprd09.prod.outlook.com DM6PR09CA0034.outlook.office365.com cipher=TLS_AES_256_GCM_SHA384) 1 sec
PM
8/30/2025 Microsoft SMTP Server (version=TLS1_2,
3 11:27:54 DM6PR09CA0034.namprd09.prod.outlook.com SJ0PR09MB9970.namprd09.prod.outlook.com cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) 1 sec
PM

Original Message Headers

Received: from DM6PR09CA0034.namprd09.prod.outlook.com (2603:10b6:5:160::47)
by SJ0PR09MB9970.namprd09.prod.outlook.com (2603:10b6:a03:447::22) with
Microsoft SMTP Server (version=TLS1_2,
cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.9073.25; Sat, 30 Aug
2025 23:27:54 +0000
Received: from SA2PEPF00002250.namprd09.prod.outlook.com
(2603:10b6:5:160:cafe::45) by DM6PR09CA0034.outlook.office365.com
(2603:10b6:5:160::47) with Microsoft SMTP Server (version=TLS1_3,
cipher=TLS_AES_256_GCM_SHA384) id 15.20.9073.25 via Frontend Transport; Sat,
30 Aug 2025 23:27:53 +0000
Authentication-Results: spf=pass (sender IP is 54.240.8.87)
smtp.mailfrom=bounce.requests.opramachine.com; dkim=timeout (key query
timeout) 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
SA2PEPF00002250.mail.protection.outlook.com (10.167.242.132) with Microsoft
SMTP Server (version=TLS1_3, cipher=TLS_AES_256_GCM_SHA384) id 15.20.9094.14
via Frontend Transport; Sat, 30 Aug 2025 23:27:52 +0000
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/simple;
s=drvjftetwukgvxxawhtk3luf3y2o3amm; d=requests.opramachine.com;
t=1756596472;
h=Date:From:To:Message-ID:Subject:Mime-Version:Content-Type:Content-Transfer-Encoding;
bh=5aK5t5SR0C88eYQzcor01jHx7Wdgh8ga0ZLQBiSbB2w=;
b=OzCbsDoPjuInooMxJ1oswoSWpd6ATQj//i/LwWk8GCpLF+bPHHlPTt6GUQII6AhC
D91mOTOex3UglNzk5p9DN7EFNzjcMdt4pPTxOSDuZS08Usg9DVflMaS+C8CcUaXdNuU
S10HeNrLIyY9RnFUEyqli0ErOtnzaqHmTnokqUJs=
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/simple;
s=6gbrjpgwjskckoa6a5zn6fwqkn67xbtw; d=amazonses.com; t=1756596472;
h=Date:From:To:Message-ID:Subject:Mime-Version:Content-Type:Content-Transfer-Encoding:Feedback-ID;
bh=5aK5t5SR0C88eYQzcor01jHx7Wdgh8ga0ZLQBiSbB2w=;
b=Ev4doo5DcKzHcU9Jw3ET9ILz7M6JOjoIam95QdIjLuaLieVqoIwPV1TdFByrtOJl
jm5s7lRF4nm+/j3SyhTRMe6vzoQBwBGQJqUgjLNw1IwiBBnrnme033GNIskUGUW0Sii
daOP1dZfXiykE/KqbUIIaL6HRQazvGHL4LIitsNY=
Date: Sat, 30 Aug 2025 23:27:51 +0000
From: Frank Kelly <[OPRA #80153 email]>
To: OPRA requests at Salem City <[Salem City request email]>
Message-ID: <[email address]>
Subject: OPRA request - City sold properties
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: 2025.08.30-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: SA2PEPF00002250:EE_|SJ0PR09MB9970:EE_
X-MS-Office365-Filtering-Correlation-Id: 57dd3b58-1318-4bf1-3d01-08dde81cd789

References

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

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