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

Opra CamCO

We're waiting for Jacob toby to read a recent response and update the status.

Dear Lawnside Borough,

We hope all is well

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) We would like a list of all properties with tax liens on them.
2) we would like a list of all municipal held liens
3) we would like a list of all tax lien investors
4) and also we would like to know if the city assigns there municipal held liens.
5)we would like a list of all vacant and abandoned properties as well

If you can provide these in excel spread sheet that would help as well

and please make sure these are all separate list
Yours faithfully,

Yours faithfully,

Jacob toby

Lawnside Borough

2 Attachments

Your message to [email address] couldn't be delivered.
j.wilcox wasn't found at lawnside.net.
01000181da196ebb-095. . . Office 365 j.wilcox
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/7/2022 7:18:28 PM
Date:
Sender [email address]
Address:
Recipient [email address]
Address:
Subject: OPRA request - Opra CamCO
Error Details
Reported error: 550 5.1.10 RESOLVER.ADR.RecipientNotFound; Recipient [email address] not found
by SMTP address lookup
DSN generated by: BN6PR11MB1905.namprd11.prod.outlook.com

Message Hops
HOP TIME FROM TO WITH RELAY
(UTC) TIME
7/7/2022 Microsoft SMTP Server (version=TLS1_2,
1 7:18:30 a8-95.smtp-out.amazonses.com MW2NAM10FT054.mail.protection.outlook.com cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) 2 sec
PM
7/7/2022 Microsoft SMTP Server (version=TLS1_2,
2 7:18:35 MW2NAM10FT054.eop-nam10.prod.protection.outlook.com MW4PR03CA0216.outlook.office365.com cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) 5 sec
PM
7/7/2022 Microsoft SMTP Server (version=TLS1_2,
3 7:18:35 MW4PR03CA0216.namprd03.prod.outlook.com BN6PR11MB1905.namprd11.prod.outlook.com cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) *
PM

Original Message Headers

Received: from MW4PR03CA0216.namprd03.prod.outlook.com (2603:10b6:303:b9::11)
by BN6PR11MB1905.namprd11.prod.outlook.com (2603:10b6:404:ff::13) with
Microsoft SMTP Server (version=TLS1_2,
cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.5417.16; Thu, 7 Jul
2022 19:18:35 +0000
Received: from MW2NAM10FT054.eop-nam10.prod.protection.outlook.com
(2603:10b6:303:b9:cafe::b7) by MW4PR03CA0216.outlook.office365.com
(2603:10b6:303:b9::11) with Microsoft SMTP Server (version=TLS1_2,
cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.5417.19 via Frontend
Transport; Thu, 7 Jul 2022 19:18:35 +0000
Authentication-Results: spf=pass (sender IP is 54.240.8.95)
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.8.95 as permitted sender)
receiver=protection.outlook.com; client-ip=54.240.8.95;
helo=a8-95.smtp-out.amazonses.com; pr=C
Received: from a8-95.smtp-out.amazonses.com (54.240.8.95) by
MW2NAM10FT054.mail.protection.outlook.com (10.13.155.191) with Microsoft SMTP
Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id
15.20.5417.15 via Frontend Transport; Thu, 7 Jul 2022 19:18:30 +0000
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/simple;
s=drvjftetwukgvxxawhtk3luf3y2o3amm; d=requests.opramachine.com;
t=1657221509;
h=Date:From:To:Message-ID:Subject:Mime-Version:Content-Type:Content-Transfer-Encoding;
bh=v8aZ3WTtWT7fLhU/YMr4ol8jVRbBBSBEcG+A135jZd4=;
b=NoqhjI0GvnMZHvhjq6ad2MDcKfylkbkEPsL3grfCwhplub4moGGh9trn8OpSL0l2
VVEZNUvRUjvaP0GENVTKGaHP2OlBYvUYGP13dnASAQAGxSjEzXstZAkD85jgQ8YQKSJ
rR+B5HTN0UWqXUSStroZpubYKeHgHs9OxelI8KCw=
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/simple;
s=6gbrjpgwjskckoa6a5zn6fwqkn67xbtw; d=amazonses.com; t=1657221509;
h=Date:From:To:Message-ID:Subject:Mime-Version:Content-Type:Content-Transfer-Encoding:Feedback-ID;
bh=v8aZ3WTtWT7fLhU/YMr4ol8jVRbBBSBEcG+A135jZd4=;
b=gRvw+wmHOLzKVXTd4vY8hEHv6zQeWQ00DX9i/aF5i/BWwXtUZ5aPp2MYY2Rzkd3N
ORnsJ9nurebggff5gq65IrNeDv9I/7Xsp5hyB/OH6fjlhoS5VBdozovT7HnqlMGwjzm
dlkHOcFTSyEOGEPswywlFh+3EihJAidnuXELSk7U=
Date: Thu, 7 Jul 2022 19:18:28 +0000
From: Jacob toby <[OPRA #33576 email]>
To: OPRA requests at Lawnside Borough <[email address]>
Message-ID: <[email address]>
Subject: OPRA request - Opra CamCO
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.07-54.240.8.95
Return-Path:
[email address]
X-EOPAttributedMessage: 0
X-EOPTenantAttributedMessage: 2c43b1dc-83ca-40cd-b1e3-431ee3bcab2f:0
X-MS-PublicTrafficType: Email
X-MS-Office365-Filtering-Correlation-Id: 08092cc1-0279-4ac1-ac88-08da604d7c08
X-MS-TrafficTypeDiagnostic: BN6PR11MB1905: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=...

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