OPRA Request - Laundromats in Cresskill

Lance B Sexton made this OPRA request to Cresskill Borough This request has been closed to new correspondence. Contact us if you think it should be reopened.

The request was partially successful.

Lance B Sexton
Unknown

Dear Cresskill Borough,

Under the Open Public Records Act (OPRA), I am requesting access to records held by the Cresskill Licensing and Inspections Department regarding all laundromats operating within the Borough of Cresskill.

Specifically, I would like to request a list of all licensed laundromats in Cresskill, including their addresses and contact information, as well as any records of inspections conducted on these premises over the last five years.

I would prefer to receive this information electronically if possible, and if there are any fees associated with fulfilling this request, please let me know.

If you require any additional information or have any questions, please do not hesitate to contact me. I can be reached at my email

Thank you for your attention to this matter.

(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.)

Sincerely,
Lance Sexton

Link to this Report
Cresskill Borough

2 Attachments

  • Attachment

    attachment.delivery status

    0K Download

  • Attachment

    OPRA request OPRA Request Laundromats in Cresskill.txt

    2K View Download

Your message to [Cresskill Borough request email] couldn't be delivered.
bnasuto wasn't found at cresskillboro.org.
01000187ec6ec558-081. . . Office 365 bnasuto
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 5/5/2023 3:01:35 PM
Date:
Sender [email address]
Address:
Recipient [Cresskill Borough request email]
Address:
Subject: OPRA request - OPRA Request - Laundromats in Cresskill
Error Details
Error: 550 5.1.10 RESOLVER.ADR.RecipientNotFound; Recipient [Cresskill Borough request email]
not found by SMTP address lookup
Message rejected by: BLAPR22MB2115.namprd22.prod.outlook.com
Notification Details
Sent by: BLAPR22MB2115.namprd22.prod.outlook.com

Message Hops
HOP TIME FROM TO WITH RELAY
(UTC) TIME
5/5/2023 Microsoft SMTP Server (version=TLS1_2,
1 3:01:36 a8-79.smtp-out.amazonses.com MW2NAM04FT043.mail.protection.outlook.com cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) 1 sec
PM
5/5/2023 Microsoft SMTP Server (version=TLS1_2,
2 3:01:38 MW2NAM04FT043.eop-NAM04.prod.protection.outlook.com MW4PR03CA0136.outlook.office365.com cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) 2 sec
PM
5/5/2023 Microsoft SMTP Server (version=TLS1_2,
3 3:01:38 MW4PR03CA0136.namprd03.prod.outlook.com BLAPR22MB2115.namprd22.prod.outlook.com cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) *
PM

Original Message Headers

Received: from MW4PR03CA0136.namprd03.prod.outlook.com (2603:10b6:303:8c::21)
by BLAPR22MB2115.namprd22.prod.outlook.com (2603:10b6:208:27e::16) with
Microsoft SMTP Server (version=TLS1_2,
cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.6387.11; Fri, 5 May
2023 15:01:38 +0000
Received: from MW2NAM04FT043.eop-NAM04.prod.protection.outlook.com
(2603:10b6:303:8c:cafe::26) by MW4PR03CA0136.outlook.office365.com
(2603:10b6:303:8c::21) with Microsoft SMTP Server (version=TLS1_2,
cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.6363.27 via Frontend
Transport; Fri, 5 May 2023 15:01:38 +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
MW2NAM04FT043.mail.protection.outlook.com (10.13.31.121) with Microsoft SMTP
Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id
15.20.6387.12 via Frontend Transport; Fri, 5 May 2023 15:01:36 +0000
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/simple;
s=cofuhmhcsf5ualrhpbcimprdgtodlfak; d=requests.opramachine.com;
t=1683298895;
h=Date:From:To:Message-ID:Subject:Mime-Version:Content-Type:Content-Transfer-Encoding;
bh=WNBXF+AQvYaN3Pt6vSSdMRsgaSQ2SLvL3L2LRw7xhCM=;
b=CD1GZAVSfW4h7pkdQ2o5kYhl4KzlWs6PrnrxxKbLU0BUGgj5qhHWYlj6clilUUVN
jsAGN8n5M+p4SONKyaOmYZLYqnUuiZ5OFKCJ/Aal4ZCVjwGh5qlK8rzSCLGKW7fqixg
EtYTWC9dJ/gUatPsg5PWjCUDguZxRR9ZZztXvYWc=
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/simple;
s=224i4yxa5dv7c2xz3womw6peuasteono; d=amazonses.com; t=1683298895;
h=Date:From:To:Message-ID:Subject:Mime-Version:Content-Type:Content-Transfer-Encoding:Feedback-ID;
bh=WNBXF+AQvYaN3Pt6vSSdMRsgaSQ2SLvL3L2LRw7xhCM=;
b=b3ddfaq08YrCp0NHU5HU5tNtQdSiY2NMgyB50DGMsDT+ju4EsPnwO+kHO+S0zK/T
Gbo55RpjCgsgau+lMp+vy9W9kGqsPYNB59s7yqGj8Tk8zkKNxVLGdXNb/RiSr+az7cQ
43xBLZ934UjDmZmZJBkKQWTrJQmW+1LNmxZOfCwY=
Date: Fri, 5 May 2023 15:01:35 +0000
From: Lance B Sexton <[OPRA #42302 email]>
To: OPRA requests at Cresskill Borough <[Cresskill Borough request email]>
Message-ID: <[email address]>
Subject: OPRA request - OPRA Request - Laundromats in Cresskill
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: 2023.05.05-54.240.8.79
Return-Path:
[email address]
X-EOPAttributedMessage: 0
X-EOPTenantAttributedMessage: 82dad6cc-2f61-4522-89b2-4f5a56289de7:0
X-MS-PublicTrafficType: Email
X-MS-TrafficTypeDiagnostic: MW2NAM04FT043:EE_|BLAPR22MB2115:EE_
X-MS-Office365-Filtering-Correlation-Id: 0f423eeb-dd31-41aa-033f-08db4d799fd0

References

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

Link to this Report