Bid Tabulation Results for Road Improvements - Scotch Road

There was a delivery error or similar, which needs fixing by the OPRAmachine team. Can you help by finding updated contact details?

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 Road Improvements - Scotch Road that was submitted on 7/2/20.

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

Hopewell Borough

2 Attachments

  • Attachment

    attachment.delivery status

    0K Download

  • Attachment

    OPRA request Bid Tabulation Results for Road Improvements Scotch Road.txt

    2K View Download

Your message to [email address] couldn't be delivered.
michele.hovan wasn't found at hopewellboro-nj.us.
0100018840ee6cae-e13. . . Office 365 michele.hovan
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/22/2023 12:49:07 AM
Date:
Sender [email address]
Address:
Recipient [email address]
Address:
Subject: OPRA request - Bid Tabulation Results for Road Improvements - Scotch Road
Error Details
Error: 550 5.1.10 RESOLVER.ADR.RecipientNotFound; Recipient
[email address] not found by SMTP address lookup
Message rejected by: MW5PR14MB5361.namprd14.prod.outlook.com
Notification Details
Sent by: MW5PR14MB5361.namprd14.prod.outlook.com

Message Hops
HOP TIME FROM TO WITH RELAY
(UTC) TIME
5/22/2023
1 12:46:17 [54.240.48.105] inbound.appriver.com ESMTPS *
AM
5/22/2023
2 12:46:20 inbound.appriver.com PIPE 3 sec
AM
5/22/2023
3 12:46:20 [10.168.232.217] server555.appriver.com ESMTPS *
AM
5/22/2023 Microsoft SMTP Server (version=TLS1_2, 2 min,
4 12:49:11 server555.appriver.com BN8NAM11FT037.mail.protection.outlook.com cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) 51 sec
AM
5/22/2023 Microsoft SMTP Server (version=TLS1_2,
5 12:49:11 BN8NAM11FT037.eop-nam11.prod.protection.outlook.com BN9PR03CA0036.outlook.office365.com cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) *
AM
5/22/2023 Microsoft SMTP Server (version=TLS1_2,
6 12:49:12 BN9PR03CA0036.namprd03.prod.outlook.com MW5PR14MB5361.namprd14.prod.outlook.com cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) 1 sec
AM

Original Message Headers

Received: from BN9PR03CA0036.namprd03.prod.outlook.com (2603:10b6:408:fb::11)
by MW5PR14MB5361.namprd14.prod.outlook.com (2603:10b6:303:19d::5) with
Microsoft SMTP Server (version=TLS1_2,
cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.6411.28; Mon, 22 May
2023 00:49:12 +0000
Received: from BN8NAM11FT037.eop-nam11.prod.protection.outlook.com
(2603:10b6:408:fb:cafe::9f) by BN9PR03CA0036.outlook.office365.com
(2603:10b6:408:fb::11) with Microsoft SMTP Server (version=TLS1_2,
cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.6411.28 via Frontend
Transport; Mon, 22 May 2023 00:49:11 +0000
Authentication-Results: spf=softfail (sender IP is 8.19.118.134)
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 8.19.118.134 as permitted
sender)
Received: from server555.appriver.com (8.19.118.134) by
BN8NAM11FT037.mail.protection.outlook.com (10.13.177.182) with Microsoft SMTP
Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id
15.20.6411.28 via Frontend Transport; Mon, 22 May 2023 00:49:11 +0000
X-Note: Xit Build: 6/24/2022 3:06:24 PM UTC (2.7.0.0) XIT_SCAN_PASSED
Received: from [10.168.232.217] (HELO inbound.appriver.com)
by server555.appriver.com (CommuniGate Pro SMTP 6.2.15)
with ESMTPS id 1960291595 for [email address]; Sun, 21 May 2023 19:46:20 -0500
X-Note: This Email was scanned by AppRiver SecureTide
X-Note-AR-ScanTimeLocal: 05/21/2023 8:46:20 PM
X-Note: SecureTide Build: 5/10/2023 12:47:26 PM UTC (2.30.0.0)
X-Note: Filtered by 10.168.232.169
X-Note-AR-Scan: None - PIPE
X-Note: CGHH cor:0522004620361-171634955-346107
Received: by inbound.appriver.com (CommuniGate Pro PIPE 7.1.1)
with PIPE id 171634955; Sun, 21 May 2023 20:46:20 -0400
Received: from [54.240.48.105] (HELO a48-105.smtp-out.amazonses.com)
by inbound.appriver.com (CommuniGate Pro SMTP 7.1.1)
with ESMTPS id 171634952 for [email address]; Sun, 21 May 2023 20:46:17 -0400
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/simple;
s=cofuhmhcsf5ualrhpbcimprdgtodlfak; d=requests.opramachine.com;
t=1684716547;
h=Date:From:To:Message-ID:Subject:Mime-Version:Content-Type:Content-Transfer-Encoding;
bh=shCuqziANrMLgJRkL1N8pxsKwel+wcZ6fMx4aQIXSd0=;
b=U0wt9LHpznEdRiyvaWNPEZmWkwJKmz2dFqs7Tr/ts1OuciPIiuzzp4SrnpLlJyzD
zADmZnK54jm+zR2IEOov7dwwgA7K+vtt/QhqFYzYUO8UjF2p32UJVRTPFlXytLZt0Ce
S6Sm/MVzmlFIRWbb8ZbmqVRDVkRyn+nA5/utIkjU=
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/simple;
s=224i4yxa5dv7c2xz3womw6peuasteono; d=amazonses.com; t=1684716547;
h=Date:From:To:Message-ID:Subject:Mime-Version:Content-Type:Content-Transfer-Encoding:Feedback-ID;
bh=shCuqziANrMLgJRkL1N8pxsKwel+wcZ6fMx4aQIXSd0=;
b=HK3or5bVny6IgyobUHbh6m8aVEmY5oAnfpS3E12lUhoO0qY/AkDfigc1Y4o7SQnW
/vJePDV8KW1rIU9/3g9l3sicKrP9LRINI0ZsCw8+5wGZqzn4h4Ww5HGgd8mW/u5PLYK
ZJ4OQO4jHW4eF8fmz75gcTOGB+qUjb4LGImeobpM=
Date: Mon, 22 May 2023 00:49:07 +0000
From: "Ava V." <[OPRA #43444 email]>
To: OPRA requests at Hopewell Borough <[email address]>
Message-ID: <[email address]>
Subject: OPRA request - Bid Tabulation Results for Road Improvements - Scotch
Road
MIME-Version: 1.0
Feedback-ID: 1.us-east-1.Cy+CdIBOIzrBJluvD+AwZTYIIvgMdz3Pedsyi9/dX4g=:AmazonSES
X-SES-Outgoing: 2023.05.22-54.240.48.105
Content-Type: text/plain;
charset=UTF-8
Content-Transfer-Encoding: 7bit
X-Note: This Email was scanned by AppRiver SecureTide
X-Note-AR-ScanTimeLocal: 05/21/2023 8:46:17 PM
X-Note: SecureTide Build: 5/10/2023 12:47:26 PM UTC (2.30.0.0)
X-Note: Filtered by 10.168.232.169
X-Policy: hopewellboro-nj.us
X-Primary: [email address]
X-Note-Sender: [email address]
X-Note-Envelope-Recip: FAILURE,DELAY, <[email address]>
X-Virus-Scan: V-
X-Note: SPF: IP: 54.240.48.105 DOM: bounce.requests.opramachine.com ADDR: [email address]
X-Note: SPF: Pass
X-Note: DKIM: Pass: requests.opramachine.com
X-Note: DMARC: opramachine.com p=none sp=none
X-Note: DMARC: Pass
X-Note-SnifferID: 0
X-GBUdb-Analysis: 0, 54.240.48.105, Ugly c=0.308711 p=-0.1 Source Normal
X-Signature-Violations: 0-0-0-5633-c
X-Note-419: 15.6279 ms. Fail:0 Chk:1438 of 1438 total
X-Note: VSCH-CT/SI: 0-1438/SG:1 5/21/2023 8:46:06 PM
X-Note: Spam Tests Failed:
X-Country-Path: United States of America->
X-Note-Sending-IP: 54.240.48.105
X-Note-Reverse-DNS: a48-105.smtp-out.amazonses.com
X-Note-Return-Path: [email address]
X-Note: User Rule Hits:
X-Note: Global Rule Hits: G316 G318 G319 G320 G337 G338 G339 G481 G482 G488 G679 G717 G902
X-Note: Encrypt Rule Hits:
X-Note: Mail Class: VALID
Return-Path:
[email address]
X-EOPAttributedMessage: 0
X-EOPTenantAttributedMessage: 8f8f2910-79e3-4efa-9f3f-b16d60105ca6:0
X-MS-PublicTrafficType: Email
X-MS-TrafficTypeDiagnostic: BN8NAM11FT037:EE_|MW5PR14MB5361:EE_
X-MS-Office365-Filtering-Correlation-Id: af90c109-d992-47d4-dd36-08db5a5e5bc2

References

Visible links
1. https://go.microsoft.com/fwlink/?LinkId=...
2. https://go.microsoft.com/fwlink/?LinkId=...
3. https://go.microsoft.com/fwlink/?LinkId=...