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

Network Blade LLC - Contracts, Vendor History Reports and Invoices

We're waiting for G.R. to read a recent response and update the status.

Dear Washington Township (Burlington),

Under OPRA and the common law right of access, please provide:

1. All contracts and service level agreements between your agency and Network Blade LLC. for the period of January 1st, 2022 to the present.

2. Vendor history reports for all payments to Network Blade LLC , outlining services provided, the timeline of services, and the costs of these services for the period of January 1st, 2022 to the present.

3. Any invoices or financial statements pertaining to transactions between your agency and Network Blade LLC for the period of January 1st, 2022 to the present.

4. Any correspondence relating to the negotiation, formation, performance, or termination of the contract(s) with Network Blade LLC., specifically with Joseph Danielsen for the period of January 1st, 2022 to the present.

Please provide all records in electronic format.

Yours faithfully,

G.R.

Washington Township (Burlington)

2 Attachments

  • Attachment

    attachment.delivery status

    0K Download

  • Attachment

    OPRA request Network Blade LLC Contracts Vendor History Reports and Invoices.txt

    2K View Download

Your message to [Washington Township (Burlington) request email] couldn't be delivered.
khoffman wasn't found at wtbcnj.org.
0100018947386e6b-ed0. . . 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 7/11/2023 11:10:27 PM
Date:
Sender [email address]
Address:
Recipient [Washington Township (Burlington) request email]
Address:
Subject: OPRA request - Network Blade LLC - Contracts, Vendor History Reports and Invoices
Error Details
Error: 550 5.1.10 RESOLVER.ADR.RecipientNotFound; Recipient [Washington Township (Burlington) request email] not
found by SMTP address lookup
Message rejected by: PH0PR09MB10509.namprd09.prod.outlook.com
Notification Details
Sent by: PH0PR09MB10509.namprd09.prod.outlook.com

Message Hops
HOP TIME FROM TO WITH RELAY
(UTC) TIME
7/11/2023 esmtps (TLSv1.2:AES128-SHA:128) (Exim 4.92) (envelope-from
1 11:10:36 a8-87.smtp-out.amazonses.com mx279.antispamcloud.com <[email address]>) 9 sec
PM
7/11/2023
2 11:10:39 delivery.mtaroutes.com BL0GCC02FT015.mail.protection.outlook.com Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) 3 sec
PM
7/11/2023
3 11:10:39 BL0GCC02FT015.eop-gcc02.prod.protection.outlook.com CY4PR09CA0002.outlook.office365.com Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) *
PM
7/11/2023
4 11:10:39 CY4PR09CA0002.namprd09.prod.outlook.com PH0PR09MB10509.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 CY4PR09CA0002.namprd09.prod.outlook.com (2603:10b6:910:2::12)
by PH0PR09MB10509.namprd09.prod.outlook.com (2603:10b6:510:2ca::9) with
Microsoft SMTP Server (version=TLS1_2,
cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.6565.31; Tue, 11 Jul
2023 23:10:39 +0000
Received: from BL0GCC02FT015.eop-gcc02.prod.protection.outlook.com
(2a01:111:f400:7d05::202) by CY4PR09CA0002.outlook.office365.com
(2603:10b6:910:2::12) with Microsoft SMTP Server (version=TLS1_2,
cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.6588.20 via Frontend
Transport; Tue, 11 Jul 2023 23:10:39 +0000
Authentication-Results: spf=softfail (sender IP is 185.201.17.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.17.200 as
permitted sender)
Received: from delivery.mtaroutes.com (185.201.17.200) by
BL0GCC02FT015.mail.protection.outlook.com (10.97.10.146) with Microsoft SMTP
Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id
15.20.6588.20 via Frontend Transport; Tue, 11 Jul 2023 23:10:39 +0000
Received: from a8-87.smtp-out.amazonses.com ([54.240.8.87])
by mx279.antispamcloud.com with esmtps (TLSv1.2:AES128-SHA:128)
(Exim 4.92)
(envelope-from <[email address]>)
id 1qJMV3-0001oH-KZ
for [Washington Township (Burlington) request email]; Wed, 12 Jul 2023 01:10:36 +0200
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/simple;
s=cofuhmhcsf5ualrhpbcimprdgtodlfak; d=requests.opramachine.com;
t=1689117028;
h=Date:From:To:Message-ID:Subject:Mime-Version:Content-Type:Content-Transfer-Encoding;
bh=9kSeTISb+3pApDMJ5MIC02sQ1jB1nGAEzOEp18xZWN0=;
b=ffEYIkk8HVko/1CLJKn+j9w6eGz8v/bFhUpG/d9Dko5a8fsRbVvz491/RsozpYMm
YECCaEdzW4wfItRBNl1tXDrgGpIz+oRqviXT92YjPX6+JXghQ9zW7v9CBdlVO0oX+LA
F5gjO03BsegfANYxvaOz7+hsewMJTXS/dKXKsv7g=
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/simple;
s=224i4yxa5dv7c2xz3womw6peuasteono; d=amazonses.com; t=1689117028;
h=Date:From:To:Message-ID:Subject:Mime-Version:Content-Type:Content-Transfer-Encoding:Feedback-ID;
bh=9kSeTISb+3pApDMJ5MIC02sQ1jB1nGAEzOEp18xZWN0=;
b=HGjwVecx58y/Mxi7C3uQ7kxwWLn7MWx2YQNzvvOhr0rLjLCS2Y5qFjNAr1n7dB4H
WbsozPQRhtTgL2ZNPbYjIpOvaDM7vS0jOBBctQrn0NtaLHkVeDk/UeJwCbrzzw5FWta
icbQZ1N42V+V/KSE4RU78mJiwKPyPBCJ6wKOd0DE=
Date: Tue, 11 Jul 2023 23:10:27 +0000
From: "G.R." <[OPRA #48482 email]>
To: "OPRA requests at Washington Township (Burlington)" <[Washington Township (Burlington) request email]>
Message-ID: <[email address]>
Subject: OPRA request - Network Blade LLC - Contracts, Vendor History Reports
and Invoices
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: 2023.07.11-54.240.8.87
Received-SPF: pass (mx279.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: mx279.antispamcloud.com: domain of bounce.requests.opramachine.com designates 54.240.8.87 as permitted sender
Authentication-Results-Original: mx279.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=cofuhmhcsf5ualrhpbcimprdgtodlfak
header.a=rsa-sha256; dkim=pass header.d=amazonses.com
header.s=224i4yxa5dv7c2xz3womw6peuasteono 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.27)
X-Recommended-Action: accept
X-Filter-ID: 8G1aH+8yearZuN6N5+X5bm6KuAmzEgFjeXz34jnHp0yfWpl7iyIiJf6Cz/lU3LGHWp5aLo4d2+O1
pAoOB/piFFEQyVzDVZOlehQ3EiJLhbuCcskBOw2ewKIWFe1VA16M0Vwvpx9ZxH284rtMQWo8KrCq
gxOs6AkRF814AuLBWKh+chHz8Cv3vNnvlm6Jcwph1AbPVsPQpWrgMPTI+PazvVrRL5LV02dW8e18
tIp4kCDrLQgn5dKuWt+nsdoQVNOmvBRlDrhFGimIwFM3AuvnyPoGl6x5IEQu/7SNwo15lcqpaHov
XzKzOfbweMFmd1BwamgxOzMqNCAfXxQyKYgwkBFsLXGvD3E9vatiCDBZ2/CyJhXrYza12wV4IuMN
uf2S9UuKK2wtu8CG6m9SfMMg0CGg4z0tJVmj9THERmhX1r1EA9FGlfPqJ3/JSuTDKhBJFPaaZGXB
JmvPAG7IrHXUee2VXGdtLyog7ui50fJvZPV8gEZqpFJfVE4/FiiFe+t19yQDTlwjYb/N6j4Mx5cD
bwPxDgnhn1olNakpWoBhd8kqwLhouheFatnTwryGW8A0OevchEHB0W2sMHY3i/mBHnee18mnIajf
4sHqT81iTx5x3dBtceKX2dWiEm+7oHm9xBEeGmns8QeFADnQDTrfru3DoVlw3yvUzOmLHcM3Gyt4
Z5EnxKf8spgxXgany3blhzFYlkdAsJcdPV7DGf3giSCv9TR+UxzLZWL8hwGBjhqmtn4uTXb12xSP
9iIGnxLSXgepXw2uOkh8BWaRmYTapBzMBPe6L4bEwYPbLDDYG2mA4tGJ46r2jMzjTLG78F/ncxw3
qqhc+N6cuEg4XWh5FvX+aPGzjXzVzpiKXSJ2DW4JARXm2yTb52xLpe1DNNdHQ2hMJp461Ba0p6an
wf1FIQ5mBoFwSHK5cEbKUfZL2V2LBDMrD7q/cJogwbqzsuokWNhBO/IileRW9oQ1gzxLBIP/iPll
AFX0itjtCsd+NBPoGGuTEyKszdpB1L5CK5kbUC2hirYe1q9doORGOlKlqBxwEiTVJqDh0qKoKsXx
5lkx/qzeZeSrodSpJuGulEuDXXo7nkAZwP2dkO4e38fQnsSdX4KnX0MkDybxdQHuK0STVT+9bAYR
ByqVYVleknKUuB8nUJKNnumX/YpFMNXwDJhRV3ykeBTM6ByLE3L6BIdbLPp9n350Mbemie5JWWm/
tQItmi5QOI6ocCPzCXY/Vw==
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: BL0GCC02FT015:EE_|PH0PR09MB10509:EE_
X-MS-Office365-Filtering-Correlation-Id: 9ea3af13-2e4e-4b66-4842-08db82640ab7

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 G.R. please sign in and let everyone know.