Police Report request - 25PV08344

Rebecca Astroski 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.

The request is waiting for clarification. If you are Rebecca Astroski, please sign in to send a follow up message.

Rebecca Astroski
Unknown

Dear Salem City,

Please accept this electronic request for public records made under OPRA and the common law right of access. I am not required to fill out an official form or use a particular software platform to submit my request per NJSA 47:1A-6(f), which states that an email from a requestor including all of the information required on the adopted form shall suffice in place of a completed form as a valid government record request.

I HAVE NOT been convicted of any indictable offense under the laws of New Jersey, any other state, or the United States.

I WILL NOT use the requested government records for a commercial purpose.

I AM NOT seeking records in connection with a legal proceeding.

Records requested: I am requesting the police report under Salem Police #25PV08344. I am with Helmsman Management, the carrier for Uber which one of the vehicles was driving. We are trying to verify who the at fault party is and if they have insurance as no information was obtained at the scene by the drivers.

My preferred delivery method for response(s) to this request is by E-mail as attachments. Please confirm you have received this request.

Regards,
REBECCA ASTROSKI | SR CLAIMS SPECIALIST II
Helmsman Management Services
Uber Hms Core
PLANO, TX-0949
(P) (469) 997-4074 (F) (888)-325-8127

Link to this Report
Salem City

2 Attachments

  • Attachment

    attachment.delivery status

    0K Download

  • Attachment

    OPRA request Police Report request 25PV08344.txt

    2K View Download

Your message to [Salem City request email] couldn't be delivered.
cityclerk wasn't found at cityofsalemnj.gov.
01000198328945da-5b4. . . 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 7/22/2025 2:28:33 PM
Date:
Sender [email address]
Address:
Recipient [Salem City request email]
Address:
Subject: OPRA request - Police Report request - 25PV08344
Error Details
Error: 550 5.1.10 RESOLVER.ADR.RecipientNotFound; Recipient [Salem City request email]
not found by SMTP address lookup
Message rejected by: DS0PR09MB11446.namprd09.prod.outlook.com
Notification Details
Sent by: DS0PR09MB11446.namprd09.prod.outlook.com

Message Hops
HOP TIME FROM TO WITH RELAY
(UTC) TIME
7/22/2025 Microsoft SMTP Server (version=TLS1_3,
1 2:28:34 a8-30.smtp-out.amazonses.com DS1PEPF00017E08.mail.protection.outlook.com cipher=TLS_AES_256_GCM_SHA384) 1 sec
PM
7/22/2025 Microsoft SMTP Server (version=TLS1_3,
2 2:28:35 DS1PEPF00017E08.namprd09.prod.outlook.com CY5PR09CA0018.outlook.office365.com cipher=TLS_AES_256_GCM_SHA384) 1 sec
PM
7/22/2025 Microsoft SMTP Server (version=TLS1_2,
3 2:28:35 CY5PR09CA0018.namprd09.prod.outlook.com DS0PR09MB11446.namprd09.prod.outlook.com cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) *
PM

Original Message Headers

Received: from CY5PR09CA0018.namprd09.prod.outlook.com (2603:10b6:930:1::7) by
DS0PR09MB11446.namprd09.prod.outlook.com (2603:10b6:8:179::10) with Microsoft
SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id
15.20.8964.21; Tue, 22 Jul 2025 14:28:35 +0000
Received: from DS1PEPF00017E08.namprd09.prod.outlook.com
(2603:10b6:930:1:cafe::d) by CY5PR09CA0018.outlook.office365.com
(2603:10b6:930:1::7) with Microsoft SMTP Server (version=TLS1_3,
cipher=TLS_AES_256_GCM_SHA384) id 15.20.8964.21 via Frontend Transport; Tue,
22 Jul 2025 14:28:35 +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;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.8.30 as permitted sender)
receiver=protection.outlook.com; client-ip=54.240.8.30;
helo=a8-30.smtp-out.amazonses.com; pr=C
Received: from a8-30.smtp-out.amazonses.com (54.240.8.30) by
DS1PEPF00017E08.mail.protection.outlook.com (10.167.18.165) with Microsoft
SMTP Server (version=TLS1_3, cipher=TLS_AES_256_GCM_SHA384) id 15.20.8964.20
via Frontend Transport; Tue, 22 Jul 2025 14:28:34 +0000
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/simple;
s=drvjftetwukgvxxawhtk3luf3y2o3amm; d=requests.opramachine.com;
t=1753194514;
h=Date:From:To:Message-ID:Subject:Mime-Version:Content-Type:Content-Transfer-Encoding;
bh=gEceZNXnPFfSDjtdPot5vM/UmmjJUcM4V0QnSkX0PeE=;
b=cOALa8+e3UM1T3WCIVNBtfi9ySWi9BnJIy0RzqiK8l4da2r4FpxuOuSWYgLR/SYQ
wsifwQhXTZbUTQi1DoBhPdaYuBi77Y90vAZ5PUg+CO10m4BFpCjMud4JA00V5Zk2OOZ
omkc//K7NIQVqE67i8WnoPjEDuwEfYTxIyKnLCYA=
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/simple;
s=6gbrjpgwjskckoa6a5zn6fwqkn67xbtw; d=amazonses.com; t=1753194514;
h=Date:From:To:Message-ID:Subject:Mime-Version:Content-Type:Content-Transfer-Encoding:Feedback-ID;
bh=gEceZNXnPFfSDjtdPot5vM/UmmjJUcM4V0QnSkX0PeE=;
b=e7gnYw6SbotQiEzN5dy/ElU0M9GUnZEn9bXP1NGkT67GHWSRRlYz0vXKUh9GfYXT
osGF+1vRB0HAu20IMfPcXHuAg3ttiOyJTR+uAwBcC9r9SnES2aIa5TWOaiEJ1b1hy1g
CGuULTy+A/9OEF8g+pzg8Qz0iznhKat34gbAZFLM=
Date: Tue, 22 Jul 2025 14:28:33 +0000
From: Rebecca Astroski <[OPRA #78695 email]>
To: OPRA requests at Salem City <[Salem City request email]>
Message-ID: <[email address]>
Subject: OPRA request - Police Report request - 25PV08344
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.07.22-54.240.8.30
Return-Path:
[email address]
X-EOPAttributedMessage: 0
X-EOPTenantAttributedMessage: b54d12cd-398f-4e84-af8a-b626e9ac133d:0
X-MS-PublicTrafficType: Email
X-MS-TrafficTypeDiagnostic: DS1PEPF00017E08:EE_|DS0PR09MB11446:EE_
X-MS-Office365-Filtering-Correlation-Id: 2926dfa2-cf27-4e83-85dd-08ddc92c0a87

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