BWC Footage
Dear Cranbury Township Police Department,
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:
Body worn camera footage of all traffic stops performed on 7-4-25
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.
The maximum authorized cost is $0.
Yours faithfully,
Tony Michael
Your message to [Cranbury Township Police Department request email] couldn't be delivered.
lgrogan wasn't found at cranbury-nj.com.
010001995414bc03-277. . . Office 365 lgrogan
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 9/16/2025 7:51:09 PM
Date:
Sender [email address]
Address:
Recipient [Cranbury Township Police Department request email]
Address:
Subject: OPRA request - BWC Footage
Error Details
Error: 550 5.1.10 RESOLVER.ADR.RecipientNotFound; Recipient [Cranbury Township Police Department request email] not
found by SMTP address lookup
Message rejected by: MWHPR13MB7105.namprd13.prod.outlook.com
Notification Details
Sent by: MWHPR13MB7105.namprd13.prod.outlook.com
Message Hops
HOP TIME FROM TO WITH RELAY
(UTC) TIME
9/16/2025
1 7:51:09 a48-105.smtp-out.amazonses.com mx-inbound12-173.us-east-2a.ess.aws.cudaops.com *
PM
9/16/2025 Microsoft SMTP Server (version=TLS1_2,
2 7:51:11 outbound-ip152a.ess.barracuda.com CH1PEPF0000AD77.mail.protection.outlook.com cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) 2 sec
PM
9/16/2025 Microsoft SMTP Server (version=TLS1_3,
3 7:51:11 CH1PEPF0000AD77.namprd04.prod.outlook.com CH2PR08CA0029.outlook.office365.com cipher=TLS_AES_256_GCM_SHA384) *
PM
9/16/2025 Microsoft SMTP Server (version=TLS1_2,
4 7:51:11 CH2PR08CA0029.namprd08.prod.outlook.com MWHPR13MB7105.namprd13.prod.outlook.com cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) *
PM
Original Message Headers
Received: from CH2PR08CA0029.namprd08.prod.outlook.com (2603:10b6:610:5a::39)
by MWHPR13MB7105.namprd13.prod.outlook.com (2603:10b6:303:287::17) with
Microsoft SMTP Server (version=TLS1_2,
cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.9115.22; Tue, 16 Sep
2025 19:51:11 +0000
Received: from CH1PEPF0000AD77.namprd04.prod.outlook.com
(2603:10b6:610:5a:cafe::50) by CH2PR08CA0029.outlook.office365.com
(2603:10b6:610:5a::39) with Microsoft SMTP Server (version=TLS1_3,
cipher=TLS_AES_256_GCM_SHA384) id 15.20.9137.13 via Frontend Transport; Tue,
16 Sep 2025 19:51:11 +0000
Authentication-Results: spf=softfail (sender IP is 209.222.82.21)
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 209.222.82.21 as permitted
sender)
Received: from outbound-ip152a.ess.barracuda.com (209.222.82.21) by
CH1PEPF0000AD77.mail.protection.outlook.com (10.167.244.55) with Microsoft
SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id
15.20.9137.12 via Frontend Transport; Tue, 16 Sep 2025 19:51:11 +0000
Received: from a48-105.smtp-out.amazonses.com (a48-105.smtp-out.amazonses.com [54.240.48.105]) by mx-inbound12-173.us-east-2a.ess.aws.cudaops.com (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Tue, 16 Sep 2025 19:51:09 +0000
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/simple;
s=drvjftetwukgvxxawhtk3luf3y2o3amm; d=requests.opramachine.com;
t=1758052269;
h=Date:From:To:Message-ID:Subject:Mime-Version:Content-Type:Content-Transfer-Encoding;
bh=KWF/SxxDc8gsUzsnAeV9HsQrTNzoGF9OIiP08O0jraY=;
b=aArP9JagQYBFpW0poEHHNowfkXypclDBZIBhZKAJ6BK8fpTQojl08L1elZV5Xg2C
4865jhzCLGQTMnblfsMpCDREMbXcRrE020KrqEtnEZXIaDV0KxuKneNIdS5onK20Vpw
tWwVj6YFkERIokJPTeoYblVOY13OnaN+twyV71VI=
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/simple;
s=6gbrjpgwjskckoa6a5zn6fwqkn67xbtw; d=amazonses.com; t=1758052269;
h=Date:From:To:Message-ID:Subject:Mime-Version:Content-Type:Content-Transfer-Encoding:Feedback-ID;
bh=KWF/SxxDc8gsUzsnAeV9HsQrTNzoGF9OIiP08O0jraY=;
b=iq7r7+YmZgqqDos/eHdzuJ7Ht3DxTC1mDuIVRcvKTk1mKhOXJVm5PYrWRXSb15W6
teC/KxE0plWl8D5+6FOZ2ueCt1ECDP3sZ6nxncNn9QIyjjNz/QBMdf3Ilx40tceziXw
xN4SZV2j5zcNv0BwMHIFZyPerRN2VMWW4PInkYUQ=
Date: Tue, 16 Sep 2025 19:51:09 +0000
From: Tony Michael <[OPRA #80932 email]>
To: OPRA requests at Cranbury Township Police Department <[Cranbury Township Police Department request email]>
Message-ID: <[email address]>
Subject: OPRA request - BWC Footage
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.09.16-54.240.48.105
X-BESS-ID: 1758052269-103245-7899-2429-1
X-BESS-VER: 2019.1_20250904.2304
X-BESS-Apparent-Source-IP: 54.240.48.105
X-BESS-Parts: H4sIAAAAAAACA4uuVkqtKFGyUioBkjpK+cVKVkYmhiZAVgZQ0CjRLNnEPCU5Jc
nE0MLSzMwoxcLU0CzJIsk0MSnF3MxEqTYWAHXDrW9BAAAA
X-BESS-Spam-Status: SCORE=0.00 using account:ESS199828 scores of QUARANTINE_LEVEL=0.0 KILL_LEVEL=5.0 tests=
Received-SPF: pass (mx-inbound12-173.us-east-2a.ess.aws.cudaops.com: domain of [email address] designates 54.240.48.105 as permitted sender)
X-BESS-Spam-Score: 0.00
Authentication-Results-Original: mx-inbound12-173.us-east-2a.ess.aws.cudaops.com; spf=pass (sender IP is
54.240.48.105)
smtp.mailfrom=[email address];
dkim=fail header.d=requests.opramachine.com; dmarc=none
header.from=[OPRA #80932 email]
X-BESS-Spam-Report: Code version 3.2, rules version 3.2.2.267538 [from cloudscan22-
127.us-east-2b.ess.aws.cudaops.com]
Rule breakdown below
pts rule name description
---- ---------------------- --------------------------------
X-BESS-BRTS-Status: 1
X-BESS-Info: H4sIAAAAAAACA6tWSslMUbIyNjY1s7TUUUrJU7JSSi5KzEsqLarUzcvSS87PVao
FAGW3OaUlAAAA
Return-Path:
[email address]
X-EOPAttributedMessage: 0
X-EOPTenantAttributedMessage: 77bdd8b0-bec6-4382-9fda-e2950fa8fbe1:0
X-MS-PublicTrafficType: Email
X-MS-TrafficTypeDiagnostic: CH1PEPF0000AD77:EE_|MWHPR13MB7105:EE_
X-MS-Office365-Filtering-Correlation-Id: 374018df-4399-4538-fa34-08ddf55a6315
References
Visible links
1. https://go.microsoft.com/fwlink/?LinkId=...
2. https://go.microsoft.com/fwlink/?LinkId=...
3. https://go.microsoft.com/fwlink/?LinkId=...