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 request Bur CO

Jacob toby made this OPRA request to Washington Township (Burlington) as part of a batch sent to 39 authorities This request has been closed to new correspondence. Contact us if you think it should be reopened.

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

Jacob toby
Unknown

Dear Washington Township (Burlington),

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.

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

Link to this Report
Washington Township (Burlington)

2 Attachments

Your message to [Washington Township (Burlington) request email] couldn't be delivered.
khoffman wasn't found at wtbcnj.org.
01000180b47190b8-efb. . . 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 5/11/2022 6:46:23 PM
Date:
Sender [email address]
Address:
Recipient [Washington Township (Burlington) request email]
Address:
Subject: OPRA request - Opra request Bur CO
Error Details
Reported error: 550 5.1.10 RESOLVER.ADR.RecipientNotFound; Recipient [Washington Township (Burlington) request email] not found
by SMTP address lookup
DSN generated by: BY5PR09MB5444.namprd09.prod.outlook.com

Message Hops
HOP TIME FROM TO WITH RELAY
(UTC) TIME
5/11/2022 esmtps (TLSv1.2:AES128-SHA:128) (Exim 4.92) (envelope-from
1 6:46:29 a8-87.smtp-out.amazonses.com mx207.antispamcloud.com <[email address]>) 6 sec
PM
5/11/2022
2 6:46:31 delivery.mtaroutes.com BL0GCC02FT018.mail.protection.outlook.com Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) 2 sec
PM
5/11/2022
3 6:46:31 BL0GCC02FT018.eop-gcc02.prod.protection.outlook.com DM5PR09CA0015.outlook.office365.com Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) *
PM
5/11/2022
4 6:46:31 DM5PR09CA0015.namprd09.prod.outlook.com BY5PR09MB5444.namprd09.prod.outlook.com Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) *
PM

Original Message Headers

Received: from DM5PR09CA0015.namprd09.prod.outlook.com (2603:10b6:4::25) by
BY5PR09MB5444.namprd09.prod.outlook.com (2603:10b6:a03:251::23) with
Microsoft SMTP Server (version=TLS1_2,
cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.5227.22; Wed, 11 May
2022 18:46:31 +0000
Received: from BL0GCC02FT018.eop-gcc02.prod.protection.outlook.com
(2a01:111:f400:7d05::208) by DM5PR09CA0015.outlook.office365.com
(2603:10b6:4::25) with Microsoft SMTP Server (version=TLS1_2,
cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.5250.13 via Frontend
Transport; Wed, 11 May 2022 18:46:31 +0000
Authentication-Results: spf=softfail (sender IP is 185.201.16.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.16.200 as
permitted sender)
Received: from delivery.mtaroutes.com (185.201.16.200) by
BL0GCC02FT018.mail.protection.outlook.com (10.97.10.138) with Microsoft SMTP
Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id
15.20.5250.13 via Frontend Transport; Wed, 11 May 2022 18:46:31 +0000
Received: from a8-87.smtp-out.amazonses.com ([54.240.8.87])
by mx207.antispamcloud.com with esmtps (TLSv1.2:AES128-SHA:128)
(Exim 4.92)
(envelope-from <[email address]>)
id 1norLs-000Nfo-0j
for [Washington Township (Burlington) request email]; Wed, 11 May 2022 20:46:29 +0200
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/simple;
s=drvjftetwukgvxxawhtk3luf3y2o3amm; d=requests.opramachine.com;
t=1652294783;
h=Date:From:To:Message-ID:Subject:Mime-Version:Content-Type:Content-Transfer-Encoding;
bh=b8Lb+KRh3RR5NsX+3EDLxWMAkWS4aje5q/dwyw9/H0Y=;
b=FJQ1GfRyH1M9cvhwuDwyPd4Ivs8XtrFlCLR9BjoUhVNN1Q2RTFjUMxCH9ewlrpIC
FfqR+QLp4VHC8tq+Wi7XZxI/R/16xVRzsBgESK8rgH+gi+Gnuy77iStlFNvhMXTPEes
deO26Gui2g59jN0/jpdRzhVThoGVnNmgRyAE1E8Q=
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/simple;
s=6gbrjpgwjskckoa6a5zn6fwqkn67xbtw; d=amazonses.com; t=1652294783;
h=Date:From:To:Message-ID:Subject:Mime-Version:Content-Type:Content-Transfer-Encoding:Feedback-ID;
bh=b8Lb+KRh3RR5NsX+3EDLxWMAkWS4aje5q/dwyw9/H0Y=;
b=d6OHKLJGdDQSQX/jU/8CkFTDEEpxPpTQs6JCW58EuOYywjMSaKrIt/Ef8DN/L0rG
fEEgeUF0PqQTph0RXyrvHvM9hPRP1HuSC2O1BXOqpFnPatLrymg9yj9ysqkZE9cv9QN
gbncyRgYOftftTV1d0aw8MPoV/NVJGAJLNIx9tnU=
Date: Wed, 11 May 2022 18:46:23 +0000
From: Jacob toby <[OPRA #31787 email]>
To: "OPRA requests at Washington Township (Burlington)" <[Washington Township (Burlington) request email]>
Message-ID: <[email address]>
Subject: OPRA request - Opra request Bur CO
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.05.11-54.240.8.87
Received-SPF: pass (mx207.antispamcloud.com: domain of bounce.requests.opramachine.com designates 54.240.8.87 as permitted sender) client-ip=54.240.8.87; envelope-from=[email address]; helo=a8-87.smtp-out.amazonses.com;
X-SPF-Result: mx207.antispamcloud.com: domain of bounce.requests.opramachine.com designates 54.240.8.87 as permitted sender
Authentication-Results-Original: mx207.antispamcloud.com; iprev=pass
(a8-87.smtp-out.amazonses.com) smtp.remote-ip=54.240.8.87; spf=pass
smtp.mailfrom=bounce.requests.opramachine.com; dkim=pass
header.d=requests.opramachine.com header.s=drvjftetwukgvxxawhtk3luf3y2o3amm
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/vM3WFEQyVzDVZOlehQ3EiJLhbuCcskBOw2ewKIWFe1VA16Ms8barXk0SpmoiCMYfv74bpV9
LfWEzG0DhKmrpd0EQrV+chHz8Cv3vNnvlm6Jcwph1AbPVsPQpWrgMPTI+PazvVrRL5LV02dW8e18
tIp4kCDrLQgn5dKuWt+nsdoQVNOmgGvSnmFfe0tRH7MKWvlioPoGl6x5IEQu/7SNwo15lcpluzxg
j+R7lJJ3bOhXX0IZamgxOzMqNCAfXxQyKYgwkLIoOS0Ddo+p2M3XOYBYBnyyJhXrYza12wV4IuMN
uf2S9UuKK2wtu8CG6m9SfMMg0CGg4z0tJVmj9THERmhX1r1EA9FGlfPqJ3/JSuTDKhBJFPaaZGXB
JmvPAG7IrHXUee2VXGdtLyog7ui50fJvZPX+mZRY9Z1BdHoAWLvjKZQQUz2FdV+3RXwReZM+8NXq
gJRVl46csyU0ab6x3joHN8CgacU1Lm/nxqJIQ8CsVCf0OevchEHB0W2sMHY3i/mBHnee18mnIajf
4sHqT81iTx5x3dBtceKX2dWiEm+7oHm9xBEeGmns8QeFADnQDTrfru3DoVlw3yvUzOmLHcM3Gytx
epTBqJNhTlGtKUkrtBWghzFYlkdAsJcdPV7DGf3giSCv9TR+UxzLZWL8hwGBjhqmtn4uTXb12xSP
9iIGnxLSXgepXw2uOkh8BWaRmYTapBzMBPe6L4bEwYPbLDDYG2mA4tGJ46r2jMzjTLG78F/ncxw3
qqhc+N6cuEg4XWh5FjBZAJ8MwkZhbLlhcRwwvY+gN2SqDAz1nY1oR9p0s14NC+Mnb84QYHLItGYH
7k8jK8VrmksKFTwtfU8kD1Kc6vvTPpuFqUUQz+mM8JAD4ECWI2wkIT+M/ODgak3UR2C3WZ83stGb
xuudPqmUmXl5t9WwphUDqJYZVf2UQOZx7+DjawWXTDxJKajrQEWvcFpmCR6irjgRtG4NErz5iDZ/
MQFximXdBlgu67T+AfJ886a6RjyRIn89hqOHhzbg59ZzeOZg0S2bj0Rbu/BtPvDF0mIrwaKs79ZG
NqxlarR/3VRmeMWi9bVSn6YpZuVcA9yv1nDl4GqJ6O7zUCVstUzd+JVrwytzyq4nhu0+m3/YUu4U
1AzCulzx6SyJORvkBYDYng==
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-Office365-Filtering-Correlation-Id: 39789ad3-2eb1-43ad-f0b6-08da337e90a0
X-MS-TrafficTypeDiagnostic: BY5PR09MB5444: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=...

Link to this Report
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.