We don't know whether the most recent response to this request contains information or not – if you are Pamelina Manna please sign in and let everyone know.

Request for Bodycam footage(FOIA)

Pamelina Manna made this OPRA request to Salem City Automatic anti-spam measures are in place for this older request. Please let us know if a further response is expected or if you are having trouble responding.

We're waiting for Pamelina Manna to read a recent response and update the status.

Pamelina Manna
Unknown

Dear Salem City,

Under the authority granted by the New Jersey Open Public Records Act (N.J.S.A. 47:1A-1 et seq.), I am formally requesting the release of the below-mentioned body-worn camera and dashcam footage pertaining to the specific incident outlined below:

Incident Case Number: 202205123
Officer Name & Badge Number:
1. Sgt Pelura = bodycam + dashcam (patrol unit)
2. Ofc Melton = bodycam + dashcam (patrol unit )
3. Ofc Klein, Robert = bodycam + dashcam (patrol unit)

This request encompasses unedited footage from the above-mentioned officer's body-worn cameras and patrol vehicle dashcams involved in the referenced incident.

In compliance with the New Jersey OPRA, I expect a response to this request within seven business days as stipulated by state law. Failure to meet this deadline will result in my seeking judicial relief to enforce compliance under the statute.

Please inform me of any fees associated with the processing of this request prior to proceeding. The timely and unimpeded access to these records is essential for maintaining public transparency and upholding New Jersey's statutory requirements.

Should there be any need for clarification or further details regarding this request, please contact me directly without delay.

I appreciate your prompt attention to this matter and look forward to your cooperation.

Sincerely,
Pamelina Manna

Link to this Report
Salem City

2 Attachments

  • Attachment

    attachment.delivery status

    0K Download

  • Attachment

    OPRA request Request for Bodycam footage FOIA.txt

    2K View Download

Your message to [Salem City request email] couldn't be delivered.
cityclerk wasn't found at cityofsalemnj.gov.
010001951ef2bb0f-077. . . Office 365 cityclerk
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 2/19/2025 4:02:58 PM
Date:
Sender [email address]
Address:
Recipient [Salem City request email]
Address:
Subject: OPRA request - Request for Bodycam footage(FOIA)
Error Details
Error: 550 5.1.10 RESOLVER.ADR.RecipientNotFound; Recipient [Salem City request email]
not found by SMTP address lookup
Message rejected by: SA1PR09MB11132.namprd09.prod.outlook.com
Notification Details
Sent by: SA1PR09MB11132.namprd09.prod.outlook.com

Message Hops
HOP TIME FROM TO WITH RELAY
(UTC) TIME
2/19/2025 Microsoft SMTP Server (version=TLS1_3,
1 4:02:59 a48-108.smtp-out.amazonses.com BL02EPF0001B418.mail.protection.outlook.com cipher=TLS_AES_256_GCM_SHA384) 1 sec
PM
2/19/2025 Microsoft SMTP Server (version=TLS1_3,
2 4:02:59 BL02EPF0001B418.namprd09.prod.outlook.com CY5PR09CA0006.outlook.office365.com cipher=TLS_AES_256_GCM_SHA384) *
PM
2/19/2025 Microsoft SMTP Server (version=TLS1_2,
3 4:03:00 CY5PR09CA0006.namprd09.prod.outlook.com SA1PR09MB11132.namprd09.prod.outlook.com cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) 1 sec
PM

Original Message Headers

Received: from CY5PR09CA0006.namprd09.prod.outlook.com (2603:10b6:930:1::31)
by SA1PR09MB11132.namprd09.prod.outlook.com (2603:10b6:806:369::21) with
Microsoft SMTP Server (version=TLS1_2,
cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.8466.15; Wed, 19 Feb
2025 16:03:00 +0000
Received: from BL02EPF0001B418.namprd09.prod.outlook.com
(2603:10b6:930:1:cafe::87) by CY5PR09CA0006.outlook.office365.com
(2603:10b6:930:1::31) with Microsoft SMTP Server (version=TLS1_3,
cipher=TLS_AES_256_GCM_SHA384) id 15.20.8466.16 via Frontend Transport; Wed,
19 Feb 2025 16:02: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;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.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
BL02EPF0001B418.mail.protection.outlook.com (10.167.242.199) with Microsoft
SMTP Server (version=TLS1_3, cipher=TLS_AES_256_GCM_SHA384) id 15.20.8466.11
via Frontend Transport; Wed, 19 Feb 2025 16:02:59 +0000
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/simple;
s=drvjftetwukgvxxawhtk3luf3y2o3amm; d=requests.opramachine.com;
t=1739980979;
h=Date:From:To:Message-ID:Subject:Mime-Version:Content-Type:Content-Transfer-Encoding;
bh=/c+7L524V5HGOYIsphvc9/8e25IencSwX7gOxC2Qma4=;
b=cAtk+KOm5YcvNuEkMlV77UU47/hNlngAVwuOnnTobFM2yT1QmVOBBzxAawYja+po
j1WjEs6KA7t83Vb8qY2tqoRbWRq4KR0xdFrAD+/hd7+6V5vposWOSd/c2vm/1nHwQzZ
lk5KvXHD5YcZJi3wAsz7J7x7kHN8ALi6qHz8tCn8=
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/simple;
s=ug7nbtf4gccmlpwj322ax3p6ow6yfsug; d=amazonses.com; t=1739980979;
h=Date:From:To:Message-ID:Subject:Mime-Version:Content-Type:Content-Transfer-Encoding:Feedback-ID;
bh=/c+7L524V5HGOYIsphvc9/8e25IencSwX7gOxC2Qma4=;
b=keBbU1P1x7cDpXl5HhmPHxwcdCtBcYFclVY6dS3UXGc8rETbuOT5jidhmIfW/h2j
wky9sB6bUvqknI94iWmfSDJtV1bkQge/TP65ZMUMrzyuzOrLZjqF7oudhmx2L0k+ZyF
e3ShribKckCWwlYCVPFAI1N8cSuZJhB25XuCTz8Y=
Date: Wed, 19 Feb 2025 16:02:58 +0000
From: Pamelina Manna <[OPRA #72331 email]>
To: OPRA requests at Salem City <[Salem City request email]>
Message-ID: <[email address]>
Subject: OPRA request - Request for Bodycam footage(FOIA)
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: 2025.02.19-54.240.48.108
Return-Path:
[email address]
X-EOPAttributedMessage: 0
X-EOPTenantAttributedMessage: b54d12cd-398f-4e84-af8a-b626e9ac133d:0
X-MS-PublicTrafficType: Email
X-MS-TrafficTypeDiagnostic: BL02EPF0001B418:EE_|SA1PR09MB11132:EE_
X-MS-Office365-Filtering-Correlation-Id: 8923bda4-440c-41ad-ef55-08dd50fee1ba

References

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

Link to this Report
We don't know whether the most recent response to this request contains information or not – if you are Pamelina Manna please sign in and let everyone know.