to have building subcode close out on their end to obtain a Certificate of Approval. From 1/30/24-3/19/24 we have been trying to reach out.
Dear Newark City,
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:
Building subcode to hand paperwork in to supervisor to close out project for 274 Pomana Ave. We have been trying to obtain a Certificate of Approval and have tried contacting since 1/30/24-3/19/24.
Yours faithfully,
Matthew Bizzarro
Permit Coordinator, NJ
Bright Planet Solar
300 Horizon Center Blvd. Unit 304
Trenton, NJ 08691
Phone: (609) 249- 4732
Fax: (609) 249- 4733
Your message to [Newark City request email] couldn't be delivered.
The group OPRA only accepts messages from people in its organization or on its allowed senders list,
and your email address isn't on the list.
0100018e56e62045-e1a. . . Office 365 OPRA
Sender Action Required
Sender not allowed
How to Fix It
It appears you aren't in the same organization as the group (or a sub-group) you're sending to or your
email address isn't on the group's allowed senders list. Ask the owner of the group to grant you
permission to send to it, and then try again. If the group belongs to a different organization than
yours, contact the organization's customer service department for assistance. If the group is in your
organization and you don't know who the group owner is, you can find it by doing the following in
either Outlook on the web or Outlook:
• Open your Sent folder and select the original message.
• If you're using Outlook on the web, select the group name located on the To or CC line. If you're
using Outlook, double-click the group name located on the To or CC line.
• In Outlook on the web, from the pop-up dialog box, choose Owner. In Outlook, choose Contact. The
owner's name is listed under Owner.
The owner of the group may have intentionally chosen to restrict who can send messages to it, and they
may not want to adjust the existing restriction. In this case, you'll have to contact the group
members by some other means, such as sending an email message to their individual email addresses or
contacting them by phone.
Was this helpful? [1]Send feedback to Microsoft.
══════════════════════════════════════════════════════════════════════════════════════════════════════
More Info for Email Admins
Status code: 550 5.7.133
This error occurs when the distribution group, security group, or Microsoft 365 group is configured to
accept messages only from authenticated senders (senders in the same organization or those added to
the group's allowed senders list).
To fix the issue, the recipient's email admin or the group owner must add the sender's email address
to the group's allowed senders list or change the group's delivery management setting to accept
messages from senders inside and outside of the organization.
Usually this issue can only be fixed by the recipient's email admin or the group owner.
For more information and steps to fix this error, see [2]Fix email delivery issues for error code
5.7.133 in Office 365.
Original Message Details
Created 3/19/2024 1:28:25 PM
Date:
Sender [email address]
Address:
Recipient [Newark City request email]
Address:
Subject: OPRA request - to have building subcode close out on their end to obtain a Certificate of
Approval. From 1/30/24-3/19/24 we have been trying to reach out.
Error Details
Error: 550 5.7.133 RESOLVER.RST.SenderNotAuthenticatedForGroup; authentication required;
Delivery restriction check failed because the sender was not authenticated when
sending to this group
Message rejected by: SA1PR04MB8240.namprd04.prod.outlook.com
Notification Details
Sent by: SA1PR04MB8240.namprd04.prod.outlook.com
Message Hops
HOP TIME FROM TO WITH RELAY
(UTC) TIME
3/19/2024 Microsoft SMTP Server (version=TLS1_2,
1 1:28:26 a48-100.smtp-out.amazonses.com CH3PEPF0000000E.mail.protection.outlook.com cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) 1 sec
PM
3/19/2024 Microsoft SMTP Server (version=TLS1_2,
2 1:28:26 CH3PEPF0000000E.namprd04.prod.outlook.com CH2PR07CA0058.outlook.office365.com cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) *
PM
3/19/2024 Microsoft SMTP Server (version=TLS1_2,
3 1:28:27 CH2PR07CA0058.namprd07.prod.outlook.com SA1PR04MB8240.namprd04.prod.outlook.com cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) 1 sec
PM
Original Message Headers
Received: from CH2PR07CA0058.namprd07.prod.outlook.com (2603:10b6:610:5b::32)
by SA1PR04MB8240.namprd04.prod.outlook.com (2603:10b6:806:1e7::15) with
Microsoft SMTP Server (version=TLS1_2,
cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.7386.30; Tue, 19 Mar
2024 13:28:27 +0000
Received: from CH3PEPF0000000E.namprd04.prod.outlook.com
(2603:10b6:610:5b:cafe::b8) by CH2PR07CA0058.outlook.office365.com
(2603:10b6:610:5b::32) with Microsoft SMTP Server (version=TLS1_2,
cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.7386.19 via Frontend
Transport; Tue, 19 Mar 2024 13:28:26 +0000
Authentication-Results: spf=pass (sender IP is 54.240.48.100)
smtp.mailfrom=bounce.requests.opramachine.com; dkim=pass (signature was
verified) header.d=requests.opramachine.com;dkim=pass (signature was
verified) header.d=amazonses.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.100 as permitted sender)
receiver=protection.outlook.com; client-ip=54.240.48.100;
helo=a48-100.smtp-out.amazonses.com; pr=C
Received: from a48-100.smtp-out.amazonses.com (54.240.48.100) by
CH3PEPF0000000E.mail.protection.outlook.com (10.167.244.42) with Microsoft
SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id
15.20.7409.10 via Frontend Transport; Tue, 19 Mar 2024 13:28:26 +0000
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/simple;
s=75ht6uujunbugea7bv75tq6udjzjx55y; d=requests.opramachine.com;
t=1710854906;
h=Date:From:To:Message-ID:Subject:Mime-Version:Content-Type:Content-Transfer-Encoding;
bh=XmGcSpJ9cXQWi5QF92TwFRBp1qRouE/zan1hjnQx7fw=;
b=onsH0z7PfZVY+SJgn/U0wdZAQG2Ch8cHrrS4uFWZolXHBCWnAT/ZSXB5D5krYqwJ
ZWebRstrTUTL/CStaVhit+d6dwropgD38PYnz+dqyrzmmjgEMpnEABGTwExr/sCm20l
DnGJ2RkW+HjEvzpo20fssLNtQ4cAevlP1t1iwkbg=
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/simple;
s=ug7nbtf4gccmlpwj322ax3p6ow6yfsug; d=amazonses.com; t=1710854906;
h=Date:From:To:Message-ID:Subject:Mime-Version:Content-Type:Content-Transfer-Encoding:Feedback-ID;
bh=XmGcSpJ9cXQWi5QF92TwFRBp1qRouE/zan1hjnQx7fw=;
b=Rrh60LbYDcTsXvd/FxXTri47XONAXOF228bpDtsMNBfEraa++PsTmY87Wx8nYLd8
8ugNQqgnyugWUvUr1xIHdes2SQ8FOdCU0HkT5luiU8faGsNacLCC+qGGHXBMsgADrbd
y5j4P3VgJVzjdASwNEg59M5zs2UzFy6nTstPyj4s=
Date: Tue, 19 Mar 2024 13:28:25 +0000
From: matthew bizzarro <[OPRA #59672 email]>
To: OPRA requests at Newark City <[Newark City request email]>
Message-ID: <[email address]>
Subject: OPRA request - to have building subcode close out on their end to
obtain a Certificate of Approval. From 1/30/24-3/19/24 we have been trying to
reach out.
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: 2024.03.19-54.240.48.100
Return-Path:
[email address]
X-EOPAttributedMessage: 0
X-EOPTenantAttributedMessage: 24883a20-af7b-4ead-9b4c-900a20da8933:0
X-MS-PublicTrafficType: Email
X-MS-TrafficTypeDiagnostic: CH3PEPF0000000E:EE_|SA1PR04MB8240:EE_
X-MS-Office365-Filtering-Correlation-Id: 07381089-b059-43f0-7c9a-08dc4818758d
References
Visible links
1. https://go.microsoft.com/fwlink/?LinkId=...
2. https://go.microsoft.com/fwlink/p/?LinkI...