Police use of force reports, January - October, 2017

There was a delivery error or similar, which needs fixing by the OPRAmachine team. Can you help by finding updated contact details?

Dear Point Pleasant Borough,

This is a request for public records made under OPRA and the common law right of access. I certify under penalty of NJSA 2C:28-3 that I have not been convicted of an indictable offense. Please acknowledge receipt of this message. Please respond electronically to this address and not via postal mail.

Records requested:

1 . Please provide copies of all of your police department’s Use of Force Reports that were created from from January 1, 2017 to October 30th, 2017.

2. Please also provide your police department’s Police Use of Deadly Force Attorney General Deadly Notification Reports filed for the same time period (January 1, 2017 to October 30th, 2017).

Yours faithfully,

Gavin Rozzi

Point Pleasant Borough

2 Attachments

  • Attachment

    attachment.delivery status

    0K Download

  • Attachment

    Open Public Records Act request Police use of force reports January October 2017.txt

    1K View Download

Your message to [email address] couldn't be delivered.
BoroClerk wasn't found at ptboro.com.
0100015f6e2bb5d8-c04. . . Office 365 BoroClerk
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/30/2017 4:44:39 PM
Date:
Sender [email address]
Address:
Recipient [email address]
Address:
Subject: Open Public Records Act request - Police use of force reports, January - October, 2017
Error Details
Reported error: 550 5.1.10 RESOLVER.ADR.RecipientNotFound; Recipient [email address] not found
by SMTP address lookup
DSN generated by: MWHPR0401MB3691.namprd04.prod.outlook.com

Message Hops
HOP TIME (UTC) FROM TO WITH RELAY
TIME
1 10/30/2017 a8-71.smtp-out.amazonses.com SN1NAM01FT008.mail.protection.outlook.com Microsoft SMTP Server (version=TLS1_0, 5 sec
4:44:44 PM cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA_P384)
2 10/30/2017 SN1NAM01FT008.eop-nam01.prod.protection.outlook.com CY4PR04CA0078.outlook.office365.com Microsoft SMTP Server (version=TLS1_2, 1 sec
4:44:45 PM cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384)
3 10/30/2017 CY4PR04CA0078.namprd04.prod.outlook.com MWHPR0401MB3691.namprd04.prod.outlook.com Microsoft SMTP Server (version=TLS1_2, *
4:44:45 PM cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256)

Original Message Headers

Received: from CY4PR04CA0078.namprd04.prod.outlook.com (2603:10b6:910:4f::43)
by MWHPR0401MB3691.namprd04.prod.outlook.com (2603:10b6:301:79::29) with
Microsoft SMTP Server (version=TLS1_2,
cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256) id 15.20.178.6; Mon, 30
Oct 2017 16:44:45 +0000
Received: from SN1NAM01FT008.eop-nam01.prod.protection.outlook.com
(2a01:111:f400:7e40::205) by CY4PR04CA0078.outlook.office365.com
(2603:10b6:910:4f::43) with Microsoft SMTP Server (version=TLS1_2,
cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) id 15.20.178.6 via Frontend
Transport; Mon, 30 Oct 2017 16:44:45 +0000
Authentication-Results: spf=pass (sender IP is 54.240.8.71)
smtp.mailfrom=bounce.requests.opramachine.com; PtBoro.com; dkim=pass
(signature was verified) header.d=requests.opramachine.com;PtBoro.com;
dmarc=bestguesspass action=none header.from=requests.opramachine.com;
Received-SPF: Pass (protection.outlook.com: domain of
bounce.requests.opramachine.com designates 54.240.8.71 as permitted sender)
receiver=protection.outlook.com; client-ip=54.240.8.71;
helo=a8-71.smtp-out.amazonses.com;
Received: from a8-71.smtp-out.amazonses.com (54.240.8.71) by
SN1NAM01FT008.mail.protection.outlook.com (10.152.64.199) with Microsoft SMTP
Server (version=TLS1_0, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA_P384) id
15.20.178.5 via Frontend Transport; Mon, 30 Oct 2017 16:44:44 +0000
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/simple;
s=75ht6uujunbugea7bv75tq6udjzjx55y; d=requests.opramachine.com;
t=1509381879;
h=Date:From:To:Message-ID:Subject:Mime-Version:Content-Type:Content-Transfer-Encoding;
bh=EGUY9WGVMi9lLzc1uLSmHSqB1bEar8xgGrBw2DmyNco=;
b=FMCe3ZWoIS6sdP9mW5Y9rEjJYY5Pvl0931+jHOTfCx0T5vZPFk8HlHSx6aJwrQj7
eAF1Om7iSSbRFv5w5C+24fjqt8TXlzwDdnJ94ZCvNWLrnPD+ZZoB82wQcJFXmZmksEq
0alqb+4pDzImETxuHuO2tvI8k128fyQ1SBqEZH3k=
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/simple;
s=224i4yxa5dv7c2xz3womw6peuasteono; d=amazonses.com; t=1509381879;
h=Date:From:To:Message-ID:Subject:Mime-Version:Content-Type:Content-Transfer-Encoding:Feedback-ID;
bh=EGUY9WGVMi9lLzc1uLSmHSqB1bEar8xgGrBw2DmyNco=;
b=CUNwAjzeLT8M4dzCLcPyVqAR88M2c4vYkNaXkCF1P4a7qBi81zpITGsKfjUsQSN1
mz5j501QPXeCqKbriHkLWng4+XbMH4Ra6ExKwd/kjxw2iwBnbl5fP/4zTpcMR0mHA5h
elUbnOVRPRmXOuYVidwS0+7nnZyI6M6HnlS9nX1o=
Date: Mon, 30 Oct 2017 16:44:39 +0000
From: Gavin Rozzi <[OPRA #31 email]>
To: OPRA requests at Point Pleasant Borough <[email address]>
Message-ID: <[email address]>
Subject: Open Public Records Act request - Police use of force reports,
January - October, 2017
MIME-Version: 1.0
Content-Type: text/plain;
charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-SES-Outgoing: 2017.10.30-54.240.8.71
Feedback-ID: 1.us-east-1.Cy+CdIBOIzrBJluvD+AwZTYIIvgMdz3Pedsyi9/dX4g=:AmazonSES
Return-Path:
[email address]
X-EOPAttributedMessage: 0
X-EOPTenantAttributedMessage: 665243cd-c824-4007-ae8f-eebd7bb1caf7:0
X-Forefront-Antispam-Report: CIP:54.240.8.71;IPV:NLI;CTRY:US;EFV:NLI;
X-Microsoft-Exchange-Diagnostics: 1;SN1NAM01FT008;1:VQt5JW5UeEZPCtq/TlUhtmRA/QjrJevNTuuOB6i9t3Bd4J6y1oIfAmJ7IaDkwkRy2+cLeH3YCeSk7eVGgYBoMqcZLRj/oWzBLSG2WmTDtk1PzZudIYyM3S0NBLI31T94
X-MS-PublicTrafficType: Email
X-MS-Office365-Filtering-Correlation-Id: 8b1da6f9-e086-485f-3927-08d51fb586a4
X-DkimResult-Test: Passed
X-Microsoft-Antispam:
UriScan:;BCL:5;PCL:0;RULEID:(23075)(22001)(8251501002)(3001016)(4534020)(71702078);SRVR:MWHPR0401MB3691;
X-Microsoft-Exchange-Diagnostics:
1;MWHPR0401MB3691;3:JQB7NjfGl4d1ZM1xHe+x4QIy7RMKtxxZg74e86RUxQ5a2l6wddSAECQ63HSZMluDbk5jqdNDlm7t6msOzEmG/SnfxjMx40Y4O39NTqUJIcdCjOMiVC90g6am2T2yeoXSQG103PLesZ1EfFeUcBnrOk5HrqTB6CC+Y9z1QdmvYdO39AMf/Iiw922e3qrW3NMa38rNiAjihQNsMOBmAa6lVYCcRsFgEaKlralq9hMPnF6meQmzdOE+vBF225JQrucCMu1KSFDieqGkAGfj4+7n/DGQyK3MvCw6EsqcMqEWfZQ1Z2uAR2+OZFeF1+AdFDMFI0huc9/Ds/w0or4dy2r+gw==;25:xA1OHj0hCoS0EIlhhAaDxMkKAZTwPGaCwwSCinU9766WRmUyZ8HB27K+ELfxi7TE3Z697KpTjVcbylFLtgcsKZeaHATj951Tjvzs0EhfURsLQrEwrLVOpm0ndQ0ae5c+62DCy01kP3+TeC3TArcIXPypG1CxojGmhK0Qg8kt4kxadV3arVZXMqEWoiBJX5vbHhfj7ESTCNweIL4paCQS8gbktEOvpRC32ODczcyiDRDUykTXT0Tc9HZvELvAANuNjEHXTuvJ7H7gUdveXAbr/tcHkMd8Q+U6y3K1VENXBFDSueiA4nR/ydF5sEn9c7/a44KgE4FQuag3XA/M1ZwY6Q==
X-MS-TrafficTypeDiagnostic: MWHPR0401MB3691:

References

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