Newark Police Accident Report
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:
NJ Crash Investigation Report. CC# 24003157.
Accident occurred on 1/21/24 near 1034 McCarter Hwy.
Party involved: Lasha Kudukhovi.
PD unit - 912T.
Yours faithfully,
Alex Barakh
Barakh Law firm, LLC
P. 2012249904
F. 2012249906
[email address]
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.
0100018daea5c704-6ad. . . 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 2/15/2024 9:21:56 PM
Date:
Sender [email address]
Address:
Recipient [Newark City request email]
Address:
Subject: OPRA request - Newark Police Accident Report
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: BY5PR04MB7108.namprd04.prod.outlook.com
Notification Details
Sent by: BY5PR04MB7108.namprd04.prod.outlook.com
Message Hops
HOP TIME FROM TO WITH RELAY
(UTC) TIME
2/15/2024 Microsoft SMTP Server (version=TLS1_2,
1 9:21:58 a48-108.smtp-out.amazonses.com MWH0EPF000971E6.mail.protection.outlook.com cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) 2 sec
PM
2/15/2024 Microsoft SMTP Server (version=TLS1_2,
2 9:21:59 MWH0EPF000971E6.namprd02.prod.outlook.com SJ0PR03CA0344.outlook.office365.com cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) 1 sec
PM
2/15/2024 Microsoft SMTP Server (version=TLS1_2,
3 9:21:59 SJ0PR03CA0344.namprd03.prod.outlook.com BY5PR04MB7108.namprd04.prod.outlook.com cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) *
PM
Original Message Headers
Received: from SJ0PR03CA0344.namprd03.prod.outlook.com (2603:10b6:a03:39c::19)
by BY5PR04MB7108.namprd04.prod.outlook.com (2603:10b6:a03:227::24) with
Microsoft SMTP Server (version=TLS1_2,
cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.7292.27; Thu, 15 Feb
2024 21:21:59 +0000
Received: from MWH0EPF000971E6.namprd02.prod.outlook.com
(2603:10b6:a03:39c:cafe::12) by SJ0PR03CA0344.outlook.office365.com
(2603:10b6:a03:39c::19) with Microsoft SMTP Server (version=TLS1_2,
cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.7292.26 via Frontend
Transport; Thu, 15 Feb 2024 21:21:59 +0000
Authentication-Results: spf=pass (sender IP is 54.240.48.108)
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.108 as permitted sender)
receiver=protection.outlook.com; client-ip=54.240.48.108;
helo=a48-108.smtp-out.amazonses.com; pr=C
Received: from a48-108.smtp-out.amazonses.com (54.240.48.108) by
MWH0EPF000971E6.mail.protection.outlook.com (10.167.243.74) with Microsoft
SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id
15.20.7292.25 via Frontend Transport; Thu, 15 Feb 2024 21:21:58 +0000
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/simple;
s=75ht6uujunbugea7bv75tq6udjzjx55y; d=requests.opramachine.com;
t=1708032116;
h=Date:From:To:Message-ID:Subject:Mime-Version:Content-Type:Content-Transfer-Encoding;
bh=ClK5/eFI9zRuDk4EX7LndDf7BvoWzr/ZoZE8lIvpJl4=;
b=CRN1YLsDAnEcbTMbRyZma6GUerbfSDsdEpfAnyJQUMZr6wfKglx349PZfEY07QFH
RQ3/gopsWWaZpNuN1uIbsqJV5AomHiDqNsUFUyuwxn8JXJHmswbJgEnHXQYyiN1irGj
DvikCyoZIscYPzBYNQD4CZkYTpoxvfUTvgY9GvX0=
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/simple;
s=224i4yxa5dv7c2xz3womw6peuasteono; d=amazonses.com; t=1708032116;
h=Date:From:To:Message-ID:Subject:Mime-Version:Content-Type:Content-Transfer-Encoding:Feedback-ID;
bh=ClK5/eFI9zRuDk4EX7LndDf7BvoWzr/ZoZE8lIvpJl4=;
b=BdDJ66ylW3XxzOsNAj7HZqYy23KBuRWCMeoV7xRfu9yy3+XAsviNWQhkp7lzNfWR
rcmmZ8gp5qSviQkBOTqY7W9HnhIEbukLxbla8r8kEtUZxPup9iHPTC+XPcoYO7Tr0fd
fnA0pXyoC4Zm+pE5uZTL68MBpNh8uc8GUGVjtujY=
Date: Thu, 15 Feb 2024 21:21:56 +0000
From: Alex Barakh <[OPRA #58449 email]>
To: OPRA requests at Newark City <[Newark City request email]>
Message-ID: <[email address]>
Subject: OPRA request - Newark Police Accident Report
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.02.15-54.240.48.108
Return-Path:
[email address]
X-EOPAttributedMessage: 0
X-EOPTenantAttributedMessage: 24883a20-af7b-4ead-9b4c-900a20da8933:0
X-MS-PublicTrafficType: Email
X-MS-TrafficTypeDiagnostic: MWH0EPF000971E6:EE_|BY5PR04MB7108:EE_
X-MS-Office365-Filtering-Correlation-Id: e22e6e35-243d-4dfe-ae51-08dc2e6c24d3
References
Visible links
1. https://go.microsoft.com/fwlink/?LinkId=...
2. https://go.microsoft.com/fwlink/p/?LinkI...