Bid Tabulation Results for Brunswick Road Improvements
Dear Cedar Grove Township,
This is a request for public records made under OPRA and the common law right of access. Please acknowledge receipt of this message.
Records requested:
Please send the final and compiled bid tabulation (Bid Tally), including all quantities and unit pricing for each bidder, for Brunswick Road Improvements that was submitted on 5/7/2024.
Below is an example of the format we are looking for that the engineer usually creates at the completion of the bid:
| | |
| BIDDER 1 | BIDDER 2 |
————————————————————————————————
Item | Description | QNT | UNIT | AMOUNT | UNIT | AMOUNT |
| | | | |
| | | | |
| | | | |
| | | | |
Please send all documents electronically.
Thanks,
PPA
Your message to [Cedar Grove Township request email] couldn't be delivered.
townclerk wasn't found at cedargrovenj.org.
0100018f58b0005c-135. . . Office 365 townclerk
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/8/2024 2:51:20 PM
Date:
Sender [email address]
Address:
Recipient [Cedar Grove Township request email]
Address:
Subject: OPRA request - Bid Tabulation Results for Brunswick Road Improvements
Error Details
Error: 550 5.1.10 RESOLVER.ADR.RecipientNotFound; Recipient [Cedar Grove Township request email]
not found by SMTP address lookup
Message rejected by: PH0PR09MB11374.namprd09.prod.outlook.com
Notification Details
Sent by: PH0PR09MB11374.namprd09.prod.outlook.com
Message Hops
HOP TIME FROM TO WITH RELAY
(UTC) TIME
5/8/2024
1 2:51:21 a48-100.smtp-out.amazonses.com mx-inbound13-219.us-east-2a.ess.aws.cudaops.com 1 sec
PM
5/8/2024 Microsoft SMTP Server (version=TLS1_2,
2 2:51:22 outbound-ip76a.ess.barracuda.com DS4PEPF00000170.mail.protection.outlook.com cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) 1 sec
PM
5/8/2024 Microsoft SMTP Server (version=TLS1_2,
3 2:51:24 DS4PEPF00000170.namprd09.prod.outlook.com DM6PR09CA0020.outlook.office365.com cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) 2 sec
PM
5/8/2024 Microsoft SMTP Server (version=TLS1_2,
4 2:51:24 DM6PR09CA0020.namprd09.prod.outlook.com PH0PR09MB11374.namprd09.prod.outlook.com cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) *
PM
Original Message Headers
Received: from DM6PR09CA0020.namprd09.prod.outlook.com (2603:10b6:5:160::33)
by PH0PR09MB11374.namprd09.prod.outlook.com (2603:10b6:510:2aa::18) with
Microsoft SMTP Server (version=TLS1_2,
cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.7544.46; Wed, 8 May
2024 14:51:24 +0000
Received: from DS4PEPF00000170.namprd09.prod.outlook.com
(2603:10b6:5:160:cafe::cc) by DM6PR09CA0020.outlook.office365.com
(2603:10b6:5:160::33) with Microsoft SMTP Server (version=TLS1_2,
cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.7544.46 via Frontend
Transport; Wed, 8 May 2024 14:51:24 +0000
Authentication-Results: spf=softfail (sender IP is 209.222.82.240)
smtp.mailfrom=bounce.requests.opramachine.com; dkim=fail (body hash did not
verify) header.d=requests.opramachine.com;dmarc=fail action=none
header.from=requests.opramachine.com;
Received-SPF: SoftFail (protection.outlook.com: domain of transitioning
bounce.requests.opramachine.com discourages use of 209.222.82.240 as
permitted sender)
Received: from outbound-ip76a.ess.barracuda.com (209.222.82.240) by
DS4PEPF00000170.mail.protection.outlook.com (10.167.18.196) with Microsoft
SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id
15.20.7544.18 via Frontend Transport; Wed, 8 May 2024 14:51:22 +0000
Received: from a48-100.smtp-out.amazonses.com (a48-100.smtp-out.amazonses.com [54.240.48.100]) by mx-inbound13-219.us-east-2a.ess.aws.cudaops.com (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Wed, 08 May 2024 14:51:21 +0000
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/simple;
s=75ht6uujunbugea7bv75tq6udjzjx55y; d=requests.opramachine.com;
t=1715179880;
h=Date:From:To:Message-ID:Subject:Mime-Version:Content-Type:Content-Transfer-Encoding;
bh=VRg/CmGwzMNwX9lckk4TDug5b59N2muqaE1AAXmyknA=;
b=ko3Nus/mRGHziGA/F0/N/gORVkIxXDv7wyQcePhBQsvP8s0Izn9TPUqOH80k7eYQ
FrOJcd5E3xeXPcSdizGe0UDMFRHsI7oDthF8Rk0YicWHWHc7+Snlih+HrLEgAUHiEUr
ppNi9DvUdH/5HbXPVaJelo2YEIr8DUvXOPtPCj/E=
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/simple;
s=ug7nbtf4gccmlpwj322ax3p6ow6yfsug; d=amazonses.com; t=1715179880;
h=Date:From:To:Message-ID:Subject:Mime-Version:Content-Type:Content-Transfer-Encoding:Feedback-ID;
bh=VRg/CmGwzMNwX9lckk4TDug5b59N2muqaE1AAXmyknA=;
b=BiY8Mg/uL7ETH9/9C2svQj4rIY9pBYueHXowy0XF9zIAc8FqHh/hGKJ7pRG+QOzO
2cy/PmGZ6SFgd3F4Q0UwEBiedx2SdYQSwBkp5JuYYr7ofARxx2YCM3M24g8dXJclbsq
GrtKi12yY3NZJcIhozNRJV9Lr9O/9lCATKRkq7yQ=
Date: Wed, 8 May 2024 14:51:20 +0000
From: Maddie Baisley <[OPRA #61534 email]>
To: OPRA requests at Cedar Grove Township <[Cedar Grove Township request email]>
Message-ID: <[email address]>
Subject: OPRA request - Bid Tabulation Results for Brunswick Road Improvements
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: 2024.05.08-54.240.48.100
X-BESS-ID: 1715179880-103547-12630-15199-1
X-BESS-VER: 2019.1_20240429.2309
X-BESS-Apparent-Source-IP: 54.240.48.100
X-BESS-Parts: H4sIAAAAAAACA4uuVkqtKFGyUioBkjpK+cVKVkbGxsZAVgZQ0DI5NdEwxdgsxc
TExMw0LcnUyMAwOcnU0NzMKM082dxCqTYWAMsUU7lBAAAA
X-BESS-Spam-Status: SCORE=0.00 using account:ESS187825 scores of QUARANTINE_LEVEL=0.0 KILL_LEVEL=5.0 tests=
Received-SPF: pass (mx-inbound13-219.us-east-2a.ess.aws.cudaops.com: domain of [email address] designates 54.240.48.100 as permitted sender)
X-BESS-Spam-Score: 0.00
Authentication-Results-Original: mx-inbound13-219.us-east-2a.ess.aws.cudaops.com; spf=pass (sender IP is
54.240.48.100)
smtp.mailfrom=[email address];
dkim=fail (nil) header.d=nil; dmarc=none action=
header.from=[OPRA #61534 email]
X-BESS-Spam-Report: Code version 3.2, rules version 3.2.2.256110 [from cloudscan13-
204.us-east-2a.ess.aws.cudaops.com]
Rule breakdown below
pts rule name description
---- ---------------------- --------------------------------
X-BESS-BRTS-Status: 1
Return-Path:
[email address]
X-EOPAttributedMessage: 0
X-EOPTenantAttributedMessage: ab2a865a-fba6-49a9-9605-c56b308d0248:0
X-MS-PublicTrafficType: Email
X-MS-TrafficTypeDiagnostic: DS4PEPF00000170:EE_|PH0PR09MB11374:EE_
X-MS-Office365-Filtering-Correlation-Id: 4d653740-bcf2-4679-7489-08dc6f6e5426
References
Visible links
1. https://go.microsoft.com/fwlink/?LinkId=...
2. https://go.microsoft.com/fwlink/?LinkId=...
3. https://go.microsoft.com/fwlink/?LinkId=...