OPRA Request - 70 Evergreen
Dear Cresskill Borough,
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.
Requesting OPRA for a list of all open & closed permits on the referenced property. Please include a copy of the survey if available.
Property address: 70 Evergreen Ave, Cresskill, NJ 07626
Lot: 01030
Block: 00062
Thanks,
Vanessa
Your message to [Cresskill Borough request email] couldn't be delivered.
bnasuto wasn't found at cresskillboro.org.
0100017e5987f5ac-2e6. . . Office 365 bnasuto
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 1/14/2022 4:59:49 PM
Date:
Sender [email address]
Address:
Recipient [Cresskill Borough request email]
Address:
Subject: OPRA request - OPRA Request - 70 Evergreen
Error Details
Reported error: 550 5.1.10 RESOLVER.ADR.RecipientNotFound; Recipient [Cresskill Borough request email] not
found by SMTP address lookup
DSN generated by: PH0PR22MB2696.namprd22.prod.outlook.com
Message Hops
HOP TIME FROM TO WITH RELAY
(UTC) TIME
1/14/2022 Microsoft SMTP Server (version=TLS1_2,
1 4:59:50 a48-107.smtp-out.amazonses.com DM6NAM04FT041.mail.protection.outlook.com cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) 1 sec
PM
1/14/2022 Microsoft SMTP Server (version=TLS1_2,
2 4:59:50 DM6NAM04FT041.eop-NAM04.prod.protection.outlook.com DS7PR03CA0075.outlook.office365.com cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) *
PM
1/14/2022 Microsoft SMTP Server (version=TLS1_2,
3 4:59:50 DS7PR03CA0075.namprd03.prod.outlook.com PH0PR22MB2696.namprd22.prod.outlook.com cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) *
PM
Original Message Headers
Received: from DS7PR03CA0075.namprd03.prod.outlook.com (2603:10b6:5:3bb::20)
by PH0PR22MB2696.namprd22.prod.outlook.com (2603:10b6:510:55::12) with
Microsoft SMTP Server (version=TLS1_2,
cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.4888.10; Fri, 14 Jan
2022 16:59:50 +0000
Received: from DM6NAM04FT041.eop-NAM04.prod.protection.outlook.com
(2603:10b6:5:3bb:cafe::9b) by DS7PR03CA0075.outlook.office365.com
(2603:10b6:5:3bb::20) with Microsoft SMTP Server (version=TLS1_2,
cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.4888.9 via Frontend
Transport; Fri, 14 Jan 2022 16:59:50 +0000
Authentication-Results: spf=pass (sender IP is 54.240.48.107)
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: Pass (protection.outlook.com: domain of
bounce.requests.opramachine.com designates 54.240.48.107 as permitted sender)
receiver=protection.outlook.com; client-ip=54.240.48.107;
helo=a48-107.smtp-out.amazonses.com;
Received: from a48-107.smtp-out.amazonses.com (54.240.48.107) by
DM6NAM04FT041.mail.protection.outlook.com (10.13.159.52) with Microsoft SMTP
Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id
15.20.4888.9 via Frontend Transport; Fri, 14 Jan 2022 16:59:50 +0000
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/simple;
s=drvjftetwukgvxxawhtk3luf3y2o3amm; d=requests.opramachine.com;
t=1642179589;
h=Date:From:To:Message-ID:Subject:Mime-Version:Content-Type:Content-Transfer-Encoding;
bh=O9au67fisJ1j+D6BNrYpAlPi0UPBB9N4o8Sfjj5t9ZA=;
b=C4+VjsN70K7J5kk4BWgtRfKfrL6YE5S3bGXjTQcTaSYYX9uYYy4d+20XcywkKSTS
UfglZPG5s9ydtuSSEKnOUm6F17CV5Kpi27zQlB7pALmBcFShBnjNlIJYPQDtjQ3tVex
fu36Hy9UJlDouk9oJkPTlXwufHfe+PCHjeNgUGqc=
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/simple;
s=ug7nbtf4gccmlpwj322ax3p6ow6yfsug; d=amazonses.com; t=1642179589;
h=Date:From:To:Message-ID:Subject:Mime-Version:Content-Type:Content-Transfer-Encoding:Feedback-ID;
bh=O9au67fisJ1j+D6BNrYpAlPi0UPBB9N4o8Sfjj5t9ZA=;
b=Yn3cpKM8InasSLkdvxT4XtipvCTS31YPx5Zhea35IWeGV0W2qNPg9HVWLnvgkxtv
hYc//OjLY+cOrD9jFNvQl5G+mohePQgibEhfnZwlnwxlgSQwRStlTYWwHzgdg3PHnLy
i9XBYxzkVOzQx1iR6r9SA/BFsMDpiViopZj08sB4=
Date: Fri, 14 Jan 2022 16:59:49 +0000
From: Vanessa Hall <[OPRA #28798 email]>
To: OPRA requests at Cresskill Borough <[Cresskill Borough request email]>
Message-ID: <[email address]>
Subject: OPRA request - OPRA Request - 70 Evergreen
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.01.14-54.240.48.107
Return-Path:
[email address]
X-EOPAttributedMessage: 0
X-EOPTenantAttributedMessage: 82dad6cc-2f61-4522-89b2-4f5a56289de7:0
X-MS-PublicTrafficType: Email
X-MS-Office365-Filtering-Correlation-Id: ea86c6a6-629c-4ea1-11aa-08d9d77f4745
X-MS-TrafficTypeDiagnostic: PH0PR22MB2696: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=...
Dear Cresskill Borough,
Please pass this on to the person who conducts Open Public Records Act reviews.
I am writing to request an internal review of Cresskill Borough's handling of my OPRA request 'OPRA Request - 70 Evergreen'.
This says it was undelivered. Is there an updated contact this can go to?
A full history of my OPRA request and all correspondence is available on the Internet at this address: https://opramachine.com/request/opra_req...
Yours faithfully,
Vanessa Hall
Your message to [Cresskill Borough request email] couldn't be delivered.
bnasuto wasn't found at cresskillboro.org.
0100017e7e635b7c-cf8. . . Office 365 bnasuto
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 1/21/2022 8:45:47 PM
Date:
Sender [email address]
Address:
Recipient [Cresskill Borough request email]
Address:
Subject: Internal review of OPRA request - OPRA Request - 70 Evergreen
Error Details
Reported error: 550 5.1.10 RESOLVER.ADR.RecipientNotFound; Recipient [Cresskill Borough request email] not
found by SMTP address lookup
DSN generated by: DM5PR2201MB1180.namprd22.prod.outlook.com
Message Hops
HOP TIME FROM TO WITH RELAY
(UTC) TIME
1/21/2022 Microsoft SMTP Server (version=TLS1_2,
1 8:45:48 a8-30.smtp-out.amazonses.com MW2NAM04FT013.mail.protection.outlook.com cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) 1 sec
PM
1/21/2022 Microsoft SMTP Server (version=TLS1_2,
2 8:45:48 MW2NAM04FT013.eop-NAM04.prod.protection.outlook.com MWHPR22CA0040.outlook.office365.com cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) *
PM
1/21/2022 Microsoft SMTP Server (version=TLS1_2,
3 8:45:48 MWHPR22CA0040.namprd22.prod.outlook.com DM5PR2201MB1180.namprd22.prod.outlook.com cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) *
PM
Original Message Headers
Received: from MWHPR22CA0040.namprd22.prod.outlook.com (2603:10b6:300:69::26)
by DM5PR2201MB1180.namprd22.prod.outlook.com (2603:10b6:4:35::21) with
Microsoft SMTP Server (version=TLS1_2,
cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.4909.10; Fri, 21 Jan
2022 20:45:48 +0000
Received: from MW2NAM04FT013.eop-NAM04.prod.protection.outlook.com
(2603:10b6:300:69:cafe::a1) by MWHPR22CA0040.outlook.office365.com
(2603:10b6:300:69::26) with Microsoft SMTP Server (version=TLS1_2,
cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.4909.12 via Frontend
Transport; Fri, 21 Jan 2022 20:45:48 +0000
Authentication-Results: spf=pass (sender IP is 54.240.8.30)
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: Pass (protection.outlook.com: domain of
bounce.requests.opramachine.com designates 54.240.8.30 as permitted sender)
receiver=protection.outlook.com; client-ip=54.240.8.30;
helo=a8-30.smtp-out.amazonses.com;
Received: from a8-30.smtp-out.amazonses.com (54.240.8.30) by
MW2NAM04FT013.mail.protection.outlook.com (10.13.30.89) with Microsoft SMTP
Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id
15.20.4909.7 via Frontend Transport; Fri, 21 Jan 2022 20:45:48 +0000
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/simple;
s=drvjftetwukgvxxawhtk3luf3y2o3amm; d=requests.opramachine.com;
t=1642797948;
h=Date:From:To:Message-ID:Subject:Mime-Version:Content-Type:Content-Transfer-Encoding;
bh=iaXrKilwVJ/Soj9Q3lk7JO+wqN3EuJmmBgVW+Buh5Jc=;
b=CkH92/8HkjDYSaAEWoRhbaovPINqRSY15TXZ0zjSGGWcq360WaRCGvJVyb4jPaia
v/gJUNH/UEHTVF2dZvxYDEgKoyXpL9TcNwjQuYzoyA7i03loGgLxhQLGtQNUluYp9YY
TOlDEoX9YkjEDCU5Oa2F3ewLp6AtGC+a7OzdiWiU=
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/simple;
s=ug7nbtf4gccmlpwj322ax3p6ow6yfsug; d=amazonses.com; t=1642797948;
h=Date:From:To:Message-ID:Subject:Mime-Version:Content-Type:Content-Transfer-Encoding:Feedback-ID;
bh=iaXrKilwVJ/Soj9Q3lk7JO+wqN3EuJmmBgVW+Buh5Jc=;
b=VFzn1eZShVwLsqTUkIaI1ei2ralyIY7KWyIRYaJQ22BNdzl0MRRnq/G2qtFarCZx
4tOwXJLK0QwU7yGNAdFY3qr2dM4SNC2nBQJ5htc2Qedu6i0AtAGFD5euZLx3279wPSm
UGKYJ/3vLqveyW3GJnKuVeJhJ4OdxqeEUJAllgjw=
Date: Fri, 21 Jan 2022 20:45:47 +0000
From: Vanessa Hall <[OPRA #28798 email]>
To: OPRA requests at Cresskill Borough <[Cresskill Borough request email]>
Message-ID: <[email address]>
Subject: Internal review of OPRA request - OPRA Request - 70 Evergreen
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.01.21-54.240.8.30
Return-Path:
[email address]
X-EOPAttributedMessage: 0
X-EOPTenantAttributedMessage: 82dad6cc-2f61-4522-89b2-4f5a56289de7:0
X-MS-PublicTrafficType: Email
X-MS-Office365-Filtering-Correlation-Id: d48befbc-a502-4c17-f3dc-08d9dd1f015e
X-MS-TrafficTypeDiagnostic: DM5PR2201MB1180: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=...