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.

nJ LBFA OPRa Request

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

Dear Washington Township (Burlington),

HI there we hope all is well

we would like the following
1.does the city / town assign your municipal Liens
2.can we have a list of all tax lien Investors
3.can we have a list of all properties that are in bankruptcy
4.can we have a list of all properties that have liens on them dating back to 2002 until today
5.can we have a list of all properties that are in probate
6.can we have a list of all vacant and abandoned properties

if you can provide in excel that would be great

Yours faithfully,

Jacob toby
3479889427

Washington Township (Burlington)

2 Attachments

Your message to [email address] couldn't be delivered.
khoffman wasn't found at wtbcnj.org.
01000185576909d0-ef1. . . Office 365 khoffman
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 12/28/2022 6:26:19 AM
Date:
Sender [email address]
Address:
Recipient [email address]
Address:
Subject: OPRA request - nJ LBFA OPRa Request
Error Details
Reported error: 550 5.1.10 RESOLVER.ADR.RecipientNotFound; Recipient [email address] not found
by SMTP address lookup
DSN generated by: SJ0PR09MB9687.namprd09.prod.outlook.com

Message Hops
HOP TIME (UTC) FROM TO WITH RELAY
TIME
1 12/28/2022 a48-101.smtp-out.amazonses.com mx214.antispamcloud.com esmtps (TLSv1.2:AES128-SHA:128) (Exim 4.92) (envelope-from 12 sec
6:26:31 AM <[email address]>)
2 12/28/2022 out15-200.antispamcloud.com DM3GCC02FT012.mail.protection.outlook.com Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) 1 sec
6:26:32 AM
3 12/28/2022 DM3GCC02FT012.eop-gcc02.prod.protection.outlook.com BL0PR0901CA0026.outlook.office365.com Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) *
6:26:32 AM
4 12/28/2022 BL0PR0901CA0026.namprd09.prod.outlook.com SJ0PR09MB9687.namprd09.prod.outlook.com Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) 1 sec
6:26:33 AM

Original Message Headers

Received: from BL0PR0901CA0026.namprd09.prod.outlook.com
(2603:10b6:208:1c0::36) by SJ0PR09MB9687.namprd09.prod.outlook.com
(2603:10b6:a03:46e::21) with Microsoft SMTP Server (version=TLS1_2,
cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.5944.16; Wed, 28 Dec
2022 06:26:33 +0000
Received: from DM3GCC02FT012.eop-gcc02.prod.protection.outlook.com
(2a01:111:f400:7d04::208) by BL0PR0901CA0026.outlook.office365.com
(2603:10b6:208:1c0::36) with Microsoft SMTP Server (version=TLS1_2,
cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.5944.17 via Frontend
Transport; Wed, 28 Dec 2022 06:26:32 +0000
Authentication-Results: spf=softfail (sender IP is 185.201.19.200)
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: SoftFail (protection.outlook.com: domain of transitioning
bounce.requests.opramachine.com discourages use of 185.201.19.200 as
permitted sender)
Received: from out15-200.antispamcloud.com (185.201.19.200) by
DM3GCC02FT012.mail.protection.outlook.com (10.97.8.114) with Microsoft SMTP
Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id
15.20.5966.17 via Frontend Transport; Wed, 28 Dec 2022 06:26:32 +0000
Received: from a48-101.smtp-out.amazonses.com ([54.240.48.101])
by mx214.antispamcloud.com with esmtps (TLSv1.2:AES128-SHA:128)
(Exim 4.92)
(envelope-from <[email address]>)
id 1pAPtQ-000B9B-Rk
for [email address]; Wed, 28 Dec 2022 07:26:31 +0100
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/simple;
s=cofuhmhcsf5ualrhpbcimprdgtodlfak; d=requests.opramachine.com;
t=1672208779;
h=Date:From:To:Message-ID:Subject:Mime-Version:Content-Type:Content-Transfer-Encoding;
bh=KAScweN0/J2HVtaeXFH6uRpMrCaYna72KiL+9L3PN6Q=;
b=ERnVw6fUmTskkMdwssdLHrqlVwxdHW6dL+N70vQdn2pybuH3TLdFj7SiXeakX++K
GXWQ81t16wGP/D8ywi8OE/+lhS340Nt6/hvTWZzkIyBeYy1nIX4frH2EzTE4Fx393tu
NxjW8Bpi3+SGJ3CMy2anf68FTf0HYW4xzT22qDPA=
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/simple;
s=6gbrjpgwjskckoa6a5zn6fwqkn67xbtw; d=amazonses.com; t=1672208779;
h=Date:From:To:Message-ID:Subject:Mime-Version:Content-Type:Content-Transfer-Encoding:Feedback-ID;
bh=KAScweN0/J2HVtaeXFH6uRpMrCaYna72KiL+9L3PN6Q=;
b=Hd1i0j3SK9eqMrWSAKzMjdTqGNVwHX6153GLX4qD9P1w38SaGy+vAzIIvb+jcJPr
UlYnwepxGXcGl2RaXIL1+vKSYfU6zPB1XwOQwfHqIBhuT5PpEmmQWzDAvVp+wfoNPbK
N4fMlk6vub1yP5IFnlmM61ju5u1Wxfg3TBc6QmxU=
Date: Wed, 28 Dec 2022 06:26:19 +0000
From: Jacob toby <[OPRA #38546 email]>
To: "OPRA requests at Washington Township (Burlington)" <[email address]>
Message-ID: <[email address]>
Subject: OPRA request - nJ LBFA 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: 2022.12.28-54.240.48.101
Received-SPF: pass (mx214.antispamcloud.com: domain of bounce.requests.opramachine.com designates 54.240.48.101 as permitted sender) client-ip=54.240.48.101; envelope-from=[email address]; helo=a48-101.smtp-out.amazonses.com;
X-SPF-Result: mx214.antispamcloud.com: domain of bounce.requests.opramachine.com designates 54.240.48.101 as permitted sender
Authentication-Results-Original: mx214.antispamcloud.com; iprev=pass
(a48-101.smtp-out.amazonses.com) smtp.remote-ip=54.240.48.101; spf=pass
smtp.mailfrom=bounce.requests.opramachine.com; dkim=pass
header.d=requests.opramachine.com header.s=cofuhmhcsf5ualrhpbcimprdgtodlfak
header.a=rsa-sha256; dkim=pass header.d=amazonses.com
header.s=6gbrjpgwjskckoa6a5zn6fwqkn67xbtw header.a=rsa-sha256; dmarc=pass
header.from=requests.opramachine.com
Authentication-Results-Original: antispamcloud.com; spf=pass
smtp.mailfrom=[email address];
dkim=pass header.i=requests.opramachine.com; dkim=pass header.i=amazonses.com
X-BelliaMAX-Class: unsure
X-BelliaMAX-Evidence: Combined (0.33)
X-Recommended-Action: accept
X-Filter-ID: 8G1aH+8yearZuN6N5+X5bm6KuAmzEgFjeXz34jnHp0xiLpFuzXpn+8vYcGm0mJfmbfafNFBigL8X
VwhS/vM3WFEQyVzDVZOlehQ3EiJLhbuCcskBOw2ewKIWFe1VA16MEDw4vUZPZRQzAevR0gJFS+rG
SsP0aJ9x9HtznBfWzRF+chHz8Cv3vNnvlm6Jcwph1AbPVsPQpWrgMPTI+PazvVrRL5LV02dW8e18
tIp4kCDrLQgn5dKuWt+nsdoQVNOmVY8sfkdE6FZZjylmwZsyA/oGl6x5IEQu/7SNwo15lcoHBLqM
Th0er0L+sqAO1yT/amgxOzMqNCAfXxQyKYgwkCejb38owtcW6htVyj2OoY6yJhXrYza12wV4IuMN
uf2S9UuKK2wtu8CG6m9SfMMg0CGg4z0tJVmj9THERmhX1r1EA9FGlfPqJ3/JSuTDKhBJFPaaZGXB
JmvPAG7IrHXUee2VXGdtLyog7ui50fJvZPX+Q+3q1x2W/AMXU3FBObBxRjIWf8reo33uAwKuMVfa
8Fw8kpUIt4l6d+QRVuCoqGHFxSQg9sSkGIYXEhQUFDy7OevchEHB0W2sMHY3i/mBHnee18mnIajf
4sHqT81iTx5x3dBtceKX2dWiEm+7oHm9xBEeGmns8QeFADnQDTrfru3DoVlw3yvUzOmLHcM3Gyt4
Z5EnxKf8spgxXgany3blhzFYlkdAsJcdPV7DGf3giSCv9TR+UxzLZWL8hwGBjhqmtn4uTXb12xSP
9iIGnxLSXgepXw2uOkh8BWaRmYTapBzMBPe6L4bEwYPbLDDYG2mA4tGJ46r2jMzjTLG78F/ncxw3
qqhc+N6cuEg4XWh5FjBZAJ8MwkZhbLlhcRwwvY9odzEOEv7ZAfMovp6fIDqQh1aK3NWhsaB4kJl4
kxgd/cVrmksKFTwtfU8kD1Kc6vvTPpuFqUUQz+mM8JAD4ECWGVM32TNA5NFqME+NGMQ3HX1IJU0Q
Bi4B2EA8yZ3A+4pqiAE5pwKylKODoBbEqRaPTChy4x9Tgi8+UBE48zjxr7RWOEaveQCQ+8btfGfG
eKsgix+0mpR/LZsD1x4LiH9K2Qbg5m3zBMcshyR7rpjyMH6m+UeFXprlCOm3BAEbJtDbI65NUp67
TX4wKu5hhnin0WU1KjCDyrGZxsAEaqBTHdNuxPWpxL5GHCQBH7aS8gUckFxLSLDtEnWVPhT/hdDs
mE2wXDfqTm12dT7SRGHKmvY4ocfmWv3Fe9Iziczdq+A=
X-Report-Abuse-To: [email address]
Return-Path:
[email address]
X-EOPAttributedMessage: 0
X-EOPTenantAttributedMessage: 76d19a3a-0f1c-4a23-ac6e-0c96af4ec07b:0
X-MS-PublicTrafficType: Email
X-MS-TrafficTypeDiagnostic: DM3GCC02FT012:EE_|SJ0PR09MB9687:EE_
X-MS-Office365-Filtering-Correlation-Id: 505b101c-13bf-4d3d-cd7a-08dae89c7653

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.