Your message to [email address] couldn't be delivered.
s.bohinski wasn't found at helmettaboro.com.
010001854fc9e8cc-038. . . Office 365 s.bohinski
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 12/26/2022 6:55:10 PM
Date:
Sender [email address]
Address:
Recipient [email address]
Address:
Subject: OPRA request - 2023 Municipal Meetings Schedules
Error Details
Reported error: 550 5.1.10 RESOLVER.ADR.RecipientNotFound; Recipient [email address] not
found by SMTP address lookup
DSN generated by: BY3PR17MB5220.namprd17.prod.outlook.com

Message Hops
HOP TIME (UTC) FROM TO WITH RELAY
TIME
1 12/26/2022 a8-79.smtp-out.amazonses.com CO1NAM11FT050.mail.protection.outlook.com Microsoft SMTP Server (version=TLS1_2, 2 sec
6:55:12 PM cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384)
2 12/26/2022 CO1NAM11FT050.eop-nam11.prod.protection.outlook.com MW4PR04CA0357.outlook.office365.com Microsoft SMTP Server (version=TLS1_2, *
6:55:12 PM cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384)
3 12/26/2022 MW4PR04CA0357.namprd04.prod.outlook.com BY3PR17MB5220.namprd17.prod.outlook.com Microsoft SMTP Server (version=TLS1_2, *
6:55:12 PM cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384)

Original Message Headers

Received: from MW4PR04CA0357.namprd04.prod.outlook.com (2603:10b6:303:8a::32)
by BY3PR17MB5220.namprd17.prod.outlook.com (2603:10b6:a03:3c1::9) with
Microsoft SMTP Server (version=TLS1_2,
cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.5944.12; Mon, 26 Dec
2022 18:55:12 +0000
Received: from CO1NAM11FT050.eop-nam11.prod.protection.outlook.com
(2603:10b6:303:8a:cafe::1f) by MW4PR04CA0357.outlook.office365.com
(2603:10b6:303:8a::32) with Microsoft SMTP Server (version=TLS1_2,
cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.5944.16 via Frontend
Transport; Mon, 26 Dec 2022 18:55:12 +0000
Authentication-Results: spf=pass (sender IP is 54.240.8.79)
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.8.79 as permitted sender)
receiver=protection.outlook.com; client-ip=54.240.8.79;
helo=a8-79.smtp-out.amazonses.com; pr=C
Received: from a8-79.smtp-out.amazonses.com (54.240.8.79) by
CO1NAM11FT050.mail.protection.outlook.com (10.13.174.79) with Microsoft SMTP
Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id
15.20.5944.17 via Frontend Transport; Mon, 26 Dec 2022 18:55:12 +0000
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/simple;
s=cofuhmhcsf5ualrhpbcimprdgtodlfak; d=requests.opramachine.com;
t=1672080910;
h=Date:From:To:Message-ID:Subject:Mime-Version:Content-Type:Content-Transfer-Encoding;
bh=QPd2pY7/SijLarCt/97JqvKmOSx2vpAIIzbUgzJm82w=;
b=emxsdnCdNiea28oAjrqhsAEkG8xDOaeD/flw/tVaKewmdcMO98YnOw1DGdHrtlL0
WiVQq1eyQstE7oUZh00BVelY8ZnpaZy1Eb0bBDm/7PhPnhNfT4iL+ki+0jurNmFQ/aw
SG/WEr5awy9OTZnfuEbM6qTFM4JyVgMoAQhbcp10=
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/simple;
s=6gbrjpgwjskckoa6a5zn6fwqkn67xbtw; d=amazonses.com; t=1672080910;
h=Date:From:To:Message-ID:Subject:Mime-Version:Content-Type:Content-Transfer-Encoding:Feedback-ID;
bh=QPd2pY7/SijLarCt/97JqvKmOSx2vpAIIzbUgzJm82w=;
b=JEQmvJlyeE33XcJpNhYcpohCX7ayVqESBAB3PM8vBnsPfRNMirFr8EXNpqo1amFy
hlCgENeXaSFJocT6iflSq/Msdqa+7kvUcmR97MJCa6fMadvE6CcsRQkQk5fHBRCetZz
8dmfUvjeMIxcx7IGCRA4eJ9flJZVQS5RFycbrW1E=
Date: Mon, 26 Dec 2022 18:55:10 +0000
From: Charlie Kratovil <[OPRA #37976 email]>
To: OPRA requests at Helmetta Borough <[email address]>
Message-ID: <[email address]>
Subject: OPRA request - 2023 Municipal Meetings Schedules
MIME-Version: 1.0
Content-Type: text/plain;
charset=UTF-8
Content-Transfer-Encoding: 7bit
Feedback-ID: 1.us-east-1.Cy+CdIBOIzrBJluvD+AwZTYIIvgMdz3Pedsyi9/dX4g=:AmazonSES
X-SES-Outgoing: 2022.12.26-54.240.8.79
Return-Path:
[email address]
X-EOPAttributedMessage: 0
X-EOPTenantAttributedMessage: 68d3e33b-0dcc-454e-8158-4e66f8e3bf54:0
X-MS-PublicTrafficType: Email
X-MS-TrafficTypeDiagnostic: CO1NAM11FT050:EE_|BY3PR17MB5220:EE_
X-MS-Office365-Filtering-Correlation-Id: bcc1fc1e-79ae-428c-77f7-08dae772b7f8

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 Mr. Kratovil,

The Borough of Helmetta received your Open Public Records Act (OPRA) request on January 9, 2023. As such, the seven (7) business day deadline to respond to your request is January 18, 2023. This response to your request is being provided to you on the 3rd business day after the custodian's receipt of said request.

The following records are being provided in their entirety and are responsive to your request.

1. Borough of Helmetta Mayor and Council Meeting dates of 2023 in person, 1 page
2. Borough of Helmetta Planning Board Meeting dates of 2023 in person, 1 page

These records are being transmitted to you via email as attachments.

Melissa Hallerman, CMR
Acting Municipal Clerk
Borough of Helmetta
Phone: 732-521-4946, ext: 100
Email: [email address]

show quoted sections