Current Table of Organization & Roster List as of 10-6-2025
ASK NJ Media made this OPRA request to Asbury Park 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.
Dear Asbury Park 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:
Please send your response in PDF form.
1. Table of Organization for the Asbury Park Police Department.
2. Full roster list of all Asbury Park police officers' names, ranks, corresponding badge numbers, and length of time with the department.
Please include a Record Index with your response.
*A record index that identifies each record requested and the specific legal basis for a denial of access (including redactions) to each record.
My preferred delivery method for response(s) to this request is by E-mail as attachments. Please confirm you have received this request. If you are not the custodian of records, please forward my request to that person and provide their email address to me for future reference.
Yours faithfully,
ASK NJ Media
Your message to [Asbury Park City request email] couldn't be delivered.
lisa.esposito wasn't found at cityofasburypark.com.
01000199b65ebb58-a9e. . . Office 365 lisa.esposito
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 10/5/2025 9:54:45 PM
Date:
Sender [email address]
Address:
Recipient [Asbury Park City request email]
Address:
Subject: OPRA request - Current Table of Organization & Roster List as of 10-6-2025
Error Details
Error: 550 5.1.10 RESOLVER.ADR.RecipientNotFound; Recipient
[Asbury Park City request email] not found by SMTP address lookup
Message rejected by: SJ0PR09MB10387.namprd09.prod.outlook.com
Notification Details
Sent by: SJ0PR09MB10387.namprd09.prod.outlook.com
Message Hops
HOP TIME FROM TO WITH RELAY
(UTC) TIME
10/5/2025
1 9:54:49 a48-108.smtp-out.amazonses.com USSF63.UpStreamSecurity.Net ESMTPS 4 sec
PM
10/5/2025
2 9:54:58 USSF63.UpStreamSecurity.Net USSF63.UpStreamSecurity.Net ESMTP 9 sec
PM
10/5/2025
3 9:55:03 localhost USSF63.UpStreamSecurity.Net ESMTP 5 sec
PM
10/5/2025 Microsoft SMTP Server (version=TLS1_3,
4 9:55:03 USSF63.UpStreamSecurity.Net DS1PEPF00017E09.mail.protection.outlook.com cipher=TLS_AES_256_GCM_SHA384) *
PM
10/5/2025 Microsoft SMTP Server (version=TLS1_3,
5 9:55:04 DS1PEPF00017E09.namprd09.prod.outlook.com BL0PR0901CA0024.outlook.office365.com cipher=TLS_AES_256_GCM_SHA384) 1 sec
PM
10/5/2025 Microsoft SMTP Server (version=TLS1_2,
6 9:55:05 BL0PR0901CA0024.namprd09.prod.outlook.com SJ0PR09MB10387.namprd09.prod.outlook.com cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) 1 sec
PM
Original Message Headers
Received: from BL0PR0901CA0024.namprd09.prod.outlook.com
(2603:10b6:208:1c0::34) by SJ0PR09MB10387.namprd09.prod.outlook.com
(2603:10b6:a03:460::16) with Microsoft SMTP Server (version=TLS1_2,
cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.9182.20; Sun, 5 Oct
2025 21:55:05 +0000
Received: from DS1PEPF00017E09.namprd09.prod.outlook.com
(2603:10b6:208:1c0:cafe::9a) by BL0PR0901CA0024.outlook.office365.com
(2603:10b6:208:1c0::34) with Microsoft SMTP Server (version=TLS1_3,
cipher=TLS_AES_256_GCM_SHA384) id 15.20.9182.20 via Frontend Transport; Sun,
5 Oct 2025 21:55:04 +0000
Authentication-Results: spf=softfail (sender IP is 38.99.86.63)
smtp.mailfrom=bounce.requests.opramachine.com; dkim=fail (body hash did not
verify) header.d=requests.opramachine.com;dkim=fail (body hash did not
verify) header.d=amazonses.com;dmarc=fail action=none
header.from=requests.opramachine.com;
Received-SPF: SoftFail (protection.outlook.com: domain of transitioning
bounce.requests.opramachine.com discourages use of 38.99.86.63 as permitted
sender)
Received: from USSF63.UpStreamSecurity.Net (38.99.86.63) by
DS1PEPF00017E09.mail.protection.outlook.com (10.167.18.166) with Microsoft
SMTP Server (version=TLS1_3, cipher=TLS_AES_256_GCM_SHA384) id 15.20.9203.9
via Frontend Transport; Sun, 5 Oct 2025 21:55:03 +0000
Received: from localhost (localhost [127.0.0.1])
by USSF63.UpStreamSecurity.Net (Postfix) with ESMTP id 5ED71707C002
for <[Asbury Park City request email]>; Sun, 05 Oct 2025 21:55:03 +0000 (UTC)
X-Quarantine-ID: <ON78ysoMJC7v>
X-Virus-Scanned: by SpamTitan at UpStreamSecurity.net
X-Spam-Flag: NO
X-Spam-Score: -0.268
X-Spam-Level:
X-Spam-Status: No, score=-0.268 tagged_above=-999 required=5
tests=[BAYES_00=-0.1, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1,
DMARC_PASS=-0.1, KAM_ASCII_DIVIDERS=0.8, RCVD_IN_DNSWL_BLOCKED=0.001,
RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01,
RCVD_IN_VALIDITY_CERTIFIED_BLOCKED=0.001,
RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, RCVD_IN_VALIDITY_SAFE_BLOCKED=0.001,
SPF_HELO_NONE=0.001, SPF_PASS=-0.001, ST_RCVD_IN_HOSTKARMA_W=-0.8,
TXREP=0.048] autolearn=ham autolearn_force=no
Received: from USSF63.UpStreamSecurity.Net (localhost [127.0.0.1])
by USSF63.UpStreamSecurity.Net (Postfix) with ESMTP id 9FA5B707C009
for <[Asbury Park City request email]>; Sun, 05 Oct 2025 21:54:58 +0000 (UTC)
Authentication-Results-Original: USSF63.UpStreamSecurity.Net; dkim=pass
(1024-bit rsa key sha256) header.d=amazonses.com
header.i=@amazonses.com header.b=sks3Oesz header.a=rsa-sha256
header.s=6gbrjpgwjskckoa6a5zn6fwqkn67xbtw x-bits=1024;
dkim=pass (1024-bit rsa key sha256)
header.d=requests.opramachine.com
header.i=@requests.opramachine.com header.b=aa3lLrbr
header.a=rsa-sha256 header.s=cofuhmhcsf5ualrhpbcimprdgtodlfak
x-bits=1024; dmarc=pass policy.published-domain-policy=none
policy.applied-disposition=none policy.evaluated-disposition=none
policy.policy-from=p header.from=requests.opramachine.com;
spf=pass smtp.mailfrom=
[email address]
smtp.helo=a48-108.smtp-out.amazonses.com
Received-SPF: pass
(bounce.requests.opramachine.com: Sender is authorized to use '[email address]' in 'mfrom' identity (mechanism 'include:amazonses.com' matched))
receiver=USSF63.UpStreamSecurity.Net;
identity=mailfrom;
envelope-from="[email address]";
helo=a48-108.smtp-out.amazonses.com;
client-ip=54.240.48.108
Received: from a48-108.smtp-out.amazonses.com (a48-108.smtp-out.amazonses.com [54.240.48.108])
by USSF63.UpStreamSecurity.Net (Postfix) with ESMTPS id 3DA36707C005
for <[Asbury Park City request email]>; Sun, 05 Oct 2025 21:54:49 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/simple;
s=cofuhmhcsf5ualrhpbcimprdgtodlfak; d=requests.opramachine.com;
t=1759701285;
h=Date:From:To:Message-ID:Subject:Mime-Version:Content-Type:Content-Transfer-Encoding;
bh=tlOrKHRca0RQzmnWfMzWJQqT+fTx4XcvoL6HQlINE9Q=;
b=aa3lLrbrlpfmWX0UYu3h44PARtiz7hBfb2mcpy6aS2cvoIDCdUNMzp967U/SrBXv
bYyfaU1FdFQNp2XtvdmP1hpexJULZa8QE4J+lam5wqnXH/rxnH5Hst72JKWmMIpkO5b
8iNIcwG8JP2JWNqNrnrJdjITkGLIOk9S/Le6Vyj4=
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/simple;
s=6gbrjpgwjskckoa6a5zn6fwqkn67xbtw; d=amazonses.com; t=1759701285;
h=Date:From:To:Message-ID:Subject:Mime-Version:Content-Type:Content-Transfer-Encoding:Feedback-ID;
bh=tlOrKHRca0RQzmnWfMzWJQqT+fTx4XcvoL6HQlINE9Q=;
b=sks3Oeszsw/jvaifNGRiT09SV2nmNDPvJWBr5iHj3z8GXfykeU+oZhITgW7291SM
C+wOMel27hvGOwgQGP0+9BYNlJpfjWM7fw0QXGjYrTIOwpTXQrNp9TYYRJwUYVETIXG
1oRQpDfmBe538zWlFAEJVycvOaluWmx8qU0Aqg2A=
Date: Sun, 5 Oct 2025 21:54:45 +0000
From: ASK NJ Media <[OPRA #81744 email]>
To: OPRA requests at Asbury Park City <[Asbury Park City request email]>
Message-ID: <[email address]>
Subject: OPRA request - Current Table of Organization & Roster List as of
10-6-2025
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.10.05-54.240.48.108
Return-Path:
[email address]
X-EOPAttributedMessage: 0
X-EOPTenantAttributedMessage: 21546314-5f74-4f5b-a96b-1d2c8f4189da:0
X-MS-PublicTrafficType: Email
X-MS-TrafficTypeDiagnostic: DS1PEPF00017E09:EE_|SJ0PR09MB10387:EE_
X-MS-Office365-Filtering-Correlation-Id: 742aeb33-a512-4a85-960a-08de0459d70b
References
Visible links
1. https://go.microsoft.com/fwlink/?LinkId=...
2. https://go.microsoft.com/fwlink/?LinkId=...
3. https://go.microsoft.com/fwlink/?LinkId=...