National Center for Missing and Exploited Children Cyber-Tips and Arrest
Sean Nelson Boero made this OPRA request to Warren County Prosecutor's Office This request has been closed to new correspondence. Contact us if you think it should be reopened.
Dear Warren County Prosecutor's Office,
This is a request for public records made under OPRA and the common law right of access. I am not required to fill out an official form. Please acknowledge receipt of this message.
Records requested:
The Warren County Prosecutor’s Office is a member of the New Jersey State Police Internet Crimes Against Children (ICAC) Task Force and receives Cyber Tips from the National Center for Missing and Exploited Children for Cyber Tips that have been geo-located to Warren County, New Jersey.
I am respectfully requesting you review your records and determine the number of NCMEC Cyber Tips received by the Warren County Prosecutor’s Office during the time period commencing January 1, 2019 through December 31, 2019, and the number of arrests made by the Warren County Prosecutor’s Office as a result of those Cyber Tips received during 2019. As a member of the ICAC Task Force the Warren County Prosecutor’s Office is required to record the number of Search Warrants and Communication Data Warrants executed and the number of arrests made into the ICAC Data System on a monthly basis. Kindly query and report those records in accordance with the OPRA.
Yours faithfully,
Sean Nelson Boero
Your message to [Warren County Prosecutor's Office request email] couldn't be delivered.
mtallia wasn't found at co.warren.nj.us.
0100018bc386dabf-4f9. . . Office 365 mtallia
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 11/12/2023 12:34:36 PM
Date:
Sender [email address]
Address:
Recipient [Warren County Prosecutor's Office request email]
Address:
Subject: OPRA request - National Center for Missing and Exploited Children Cyber-Tips and Arrest
Error Details
Error: 550 5.1.10 RESOLVER.ADR.RecipientNotFound; Recipient [Warren County Prosecutor's Office request email] not
found by SMTP address lookup
Message rejected by: SA1PR09MB8907.namprd09.prod.outlook.com
Notification Details
Sent by: SA1PR09MB8907.namprd09.prod.outlook.com
Message Hops
HOP TIME (UTC) FROM TO WITH RELAY
TIME
11/12/2023 Microsoft SMTP Server (version=TLS1_2,
1 12:34:37 a48-107.smtp-out.amazonses.com BL0GCC02FT042.mail.protection.outlook.com cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) 1 sec
PM
11/12/2023 Microsoft SMTP Server (version=TLS1_2,
2 12:34:38 BL0GCC02FT042.eop-gcc02.prod.protection.outlook.com DM6PR09CA0017.outlook.office365.com cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) 1 sec
PM
11/12/2023 Microsoft SMTP Server (version=TLS1_2,
3 12:34:39 DM6PR09CA0017.namprd09.prod.outlook.com SA1PR09MB8907.namprd09.prod.outlook.com cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) 1 sec
PM
Original Message Headers
Received: from DM6PR09CA0017.namprd09.prod.outlook.com (2603:10b6:5:160::30)
by SA1PR09MB8907.namprd09.prod.outlook.com (2603:10b6:806:28d::9) with
Microsoft SMTP Server (version=TLS1_2,
cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.6977.28; Sun, 12 Nov
2023 12:34:39 +0000
Received: from BL0GCC02FT042.eop-gcc02.prod.protection.outlook.com
(2a01:111:f400:7d05::208) by DM6PR09CA0017.outlook.office365.com
(2603:10b6:5:160::30) with Microsoft SMTP Server (version=TLS1_2,
cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.6977.28 via Frontend
Transport; Sun, 12 Nov 2023 12:34:38 +0000
Authentication-Results: spf=pass (sender IP is 54.240.48.107)
smtp.mailfrom=bounce.requests.opramachine.com; dkim=pass (signature was
verified) header.d=requests.opramachine.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.107 as permitted sender)
receiver=protection.outlook.com; client-ip=54.240.48.107;
helo=a48-107.smtp-out.amazonses.com; pr=C
Received: from a48-107.smtp-out.amazonses.com (54.240.48.107) by
BL0GCC02FT042.mail.protection.outlook.com (10.97.10.95) with Microsoft SMTP
Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id
15.20.7002.14 via Frontend Transport; Sun, 12 Nov 2023 12:34:37 +0000
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/simple;
s=75ht6uujunbugea7bv75tq6udjzjx55y; d=requests.opramachine.com;
t=1699792477;
h=Date:From:To:Message-ID:Subject:Mime-Version:Content-Type:Content-Transfer-Encoding;
bh=4cC7tWrYlj+BFBaimr7mAxEqz2FKPGE384SOdyweCZ8=;
b=L3IavVpHb9Rwmyw/WyBshsCon9+CEuOh32oOaZvB5KVF1lrdhn6iVqGAtLHVIdrI
w7RJWvNIrFEpuX8u+ue6yVjyo/QAKTxOefEbaNhiW4UpprQJa13gDha4geVRW5iUWnN
J029HTHVmZ9zR2mmCqWEADOcweGLFRFaqEy1zRr0=
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/simple;
s=224i4yxa5dv7c2xz3womw6peuasteono; d=amazonses.com; t=1699792477;
h=Date:From:To:Message-ID:Subject:Mime-Version:Content-Type:Content-Transfer-Encoding:Feedback-ID;
bh=4cC7tWrYlj+BFBaimr7mAxEqz2FKPGE384SOdyweCZ8=;
b=dGlMvsAu1xdJGE91RNDWTzh+9YQGwtWaZ4sSvhLeabJRwHWIt0ffpwxkGgqSq3MN
DSTSH6l2lYhavWyumAYX8SyUwq4+1JKRzOc0EbvWssC3EaAWUBsFg2crP3WcUXRkEkV
+fspkUx4owUFh9XtWaHuyu01BtKDzYxon81z1XSY=
Date: Sun, 12 Nov 2023 12:34:36 +0000
From: Sean Nelson Boero <[OPRA #55213 email]>
To: "OPRA requests at Warren County Prosecutor's Office" <[Warren County Prosecutor's Office request email]>
Message-ID: <[email address]>
Subject: OPRA request - National Center for Missing and Exploited Children
Cyber-Tips and Arrest
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: 2023.11.12-54.240.48.107
Return-Path:
[email address]
X-EOPAttributedMessage: 0
X-EOPTenantAttributedMessage: ac89e516-b950-4fea-903b-820d793be497:0
X-MS-PublicTrafficType: Email
X-MS-TrafficTypeDiagnostic: BL0GCC02FT042:EE_|SA1PR09MB8907:EE_
X-MS-Office365-Filtering-Correlation-Id: ca183848-2bf4-468e-1f8e-08dbe37bbc17
References
Visible links
1. https://go.microsoft.com/fwlink/?LinkId=...
2. https://go.microsoft.com/fwlink/?LinkId=...
3. https://go.microsoft.com/fwlink/?LinkId=...
Dear Warren County Prosecutor's Office,
Very fast and efficient response from Warren County when a request was sent to them directly. Hopefully they fix/update the email associated with the OPRAMachine.
November 17, 2023
BRENTON S. WARNE
Chief of Detectives
MELISSA A. FEHR
Deputy Chief of Detectives
OFFICE OF THE PROSECUTOR
RE: Response to OPRA request for NCMEC Cyber Tips and Arrests for 2019 Calendar Year.
Mr. Boero:
In response to your above referenced OPRA/ Common Law request, the Warren County Prosecutor’s Office would like to inform you of the following:
ICAC Cyber Tips- 239
Arrests in 2019- 9
With this response, the Warren County Prosecutor’s Office considers you OPRA and Common Law request completed and closed.
Sincerely,
/s/ Brian R. Longenhagen
Brian R. Longenhagen Assistant Prosecutor
Yours faithfully,
Sean Nelson Boero
Your message to [Warren County Prosecutor's Office request email] couldn't be delivered.
mtallia wasn't found at co.warren.nj.us.
0100018bdf6d0c3c-207. . . Office 365 mtallia
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 11/17/2023 10:35:47 PM
Date:
Sender [email address]
Address:
Recipient [Warren County Prosecutor's Office request email]
Address:
Subject: Re: OPRA request - National Center for Missing and Exploited Children Cyber-Tips and Arrest
Error Details
Error: 550 5.1.10 RESOLVER.ADR.RecipientNotFound; Recipient [Warren County Prosecutor's Office request email] not
found by SMTP address lookup
Message rejected by: SJ0PR09MB9239.namprd09.prod.outlook.com
Notification Details
Sent by: SJ0PR09MB9239.namprd09.prod.outlook.com
Message Hops
HOP TIME (UTC) FROM TO WITH RELAY
TIME
11/17/2023 Microsoft SMTP Server (version=TLS1_2,
1 10:35:49 a48-100.smtp-out.amazonses.com BL0GCC02FT048.mail.protection.outlook.com cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) 2 sec
PM
11/17/2023 Microsoft SMTP Server (version=TLS1_2,
2 10:35:49 BL0GCC02FT048.eop-gcc02.prod.protection.outlook.com CYXPR09CA0005.outlook.office365.com cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) *
PM
11/17/2023 Microsoft SMTP Server (version=TLS1_2,
3 10:35:49 CYXPR09CA0005.namprd09.prod.outlook.com SJ0PR09MB9239.namprd09.prod.outlook.com cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) *
PM
Original Message Headers
Received: from CYXPR09CA0005.namprd09.prod.outlook.com (2603:10b6:930:d4::18)
by SJ0PR09MB9239.namprd09.prod.outlook.com (2603:10b6:a03:462::8) with
Microsoft SMTP Server (version=TLS1_2,
cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.7002.23; Fri, 17 Nov
2023 22:35:49 +0000
Received: from BL0GCC02FT048.eop-gcc02.prod.protection.outlook.com
(2a01:111:f400:7d05::204) by CYXPR09CA0005.outlook.office365.com
(2603:10b6:930:d4::18) with Microsoft SMTP Server (version=TLS1_2,
cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.7002.23 via Frontend
Transport; Fri, 17 Nov 2023 22:35:49 +0000
Authentication-Results: spf=pass (sender IP is 54.240.48.100)
smtp.mailfrom=bounce.requests.opramachine.com; dkim=pass (signature was
verified) header.d=requests.opramachine.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.100 as permitted sender)
receiver=protection.outlook.com; client-ip=54.240.48.100;
helo=a48-100.smtp-out.amazonses.com; pr=C
Received: from a48-100.smtp-out.amazonses.com (54.240.48.100) by
BL0GCC02FT048.mail.protection.outlook.com (10.97.10.86) with Microsoft SMTP
Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id
15.20.7025.12 via Frontend Transport; Fri, 17 Nov 2023 22:35:49 +0000
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/simple;
s=75ht6uujunbugea7bv75tq6udjzjx55y; d=requests.opramachine.com;
t=1700260547;
h=Date:From:To:Message-ID:Subject:Mime-Version:Content-Type:Content-Transfer-Encoding;
bh=MYLwyPyT0fnLI59EufrF4JynOsuNSXhBYCGCxUb6iJE=;
b=XsKhpRxS7SDChVRmPXfa7YMYC4iCWZgrOcDlstHgTBTjjXHqQaPw/AfaksketsTS
3rv+fmrAbN2wWovAs8EkpgDnEGnEo4EEhi6paDIw/vnVYAB0iDk82u/8zGXq3pzP91w
syIB4PpgXAvBnwa+Tuv5lWm14qynI4kqlDT1g5lk=
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/simple;
s=224i4yxa5dv7c2xz3womw6peuasteono; d=amazonses.com; t=1700260547;
h=Date:From:To:Message-ID:Subject:Mime-Version:Content-Type:Content-Transfer-Encoding:Feedback-ID;
bh=MYLwyPyT0fnLI59EufrF4JynOsuNSXhBYCGCxUb6iJE=;
b=fBohpt81jniLtPpkruj9Mz7RGMPMcBNR9qFSJ6vxfaK5m6YAFzmkWYXUH0Ldax/N
z2N06gDRYBYPLvisoHn5G+D20ADAXj7sjoTf79SMZbNWSN7MGD/5Rscafyh/zi8IpVk
MYtHY2BpHq0+17Lrkpxjc7HMnlzvXk5v5x2pmGXM=
Date: Fri, 17 Nov 2023 22:35:47 +0000
From: Sean Nelson Boero <[OPRA #55213 email]>
To: "OPRA requests at Warren County Prosecutor's Office" <[Warren County Prosecutor's Office request email]>
Message-ID: <[email address]>
Subject: Re: OPRA request - National Center for Missing and Exploited Children
Cyber-Tips and Arrest
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: 2023.11.17-54.240.48.100
Return-Path:
[email address]
X-EOPAttributedMessage: 0
X-EOPTenantAttributedMessage: ac89e516-b950-4fea-903b-820d793be497:0
X-MS-PublicTrafficType: Email
X-MS-TrafficTypeDiagnostic: BL0GCC02FT048:EE_|SJ0PR09MB9239:EE_
X-MS-Office365-Filtering-Correlation-Id: 04a33acf-f3b9-4ab8-bf01-08dbe7bd8c66
References
Visible links
1. https://go.microsoft.com/fwlink/?LinkId=...
2. https://go.microsoft.com/fwlink/?LinkId=...
3. https://go.microsoft.com/fwlink/?LinkId=...