Employee Salary Records
Dear Lawnside 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.
Records requested:
I'm requesting the following records of any and all employees for the year of 2022
Each employee record should contain:
*Name
*Current job title
*Current Base salary
*Current Regular rate
*Longevity pay if applicable
*Stipends for licenses if applicable
*Hire date
*Pension ID
*Length of service
* Date of separation and the reason for such separation, and the amount and type of any pension received
*Cost of health and welfare for each employee and the % each employee contributes
*Current CBA if applicable
.....pursuant to N.J.S.A. 47:1A-10. N.J.S.A. 47:1A-10 23) Personnel and pension records, except specific information identified as follows: a. An individual’s name, title, position, salary, payroll record, length of service, date of separation and the reason for such separation, and the amount and type of any pension received, b. When required to be disclosed by another law, when disclosure is essential to the performance of official duties of a person duly authorized by this State or the United States, or when authorized by an individual in interest. c. Data contained in information which disclose conformity with specific experiential, educational or medical qualifications required for government employment or for receipt of a public pension, but not including any detailed medical or psychological information. ***The above information was taken from the Custodian's Handbook that the Government Records Council provides within the State of New Jersey.
Yours faithfully,
Marc Possoff
Your message to [email address] couldn't be delivered.
j.wilcox wasn't found at lawnside.net.
010001804d559471-a94. . . Office 365 j.wilcox
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 4/21/2022 6:14:55 PM
Date:
Sender [email address]
Address:
Recipient [email address]
Address:
Subject: OPRA request - Employee Salary Records
Error Details
Reported error: 550 5.1.10 RESOLVER.ADR.RecipientNotFound; Recipient [email address] not found
by SMTP address lookup
DSN generated by: CY4PR11MB1686.namprd11.prod.outlook.com
Message Hops
HOP TIME FROM TO WITH RELAY
(UTC) TIME
4/21/2022 Microsoft SMTP Server (version=TLS1_2,
1 6:14:57 a48-109.smtp-out.amazonses.com DM6NAM10FT037.mail.protection.outlook.com cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) 2 sec
PM
4/21/2022 Microsoft SMTP Server (version=TLS1_2,
2 6:14:57 DM6NAM10FT037.eop-nam10.prod.protection.outlook.com DS7P222CA0021.outlook.office365.com cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) *
PM
4/21/2022 Microsoft SMTP Server (version=TLS1_2,
3 6:14:57 DS7P222CA0021.NAMP222.PROD.OUTLOOK.COM CY4PR11MB1686.namprd11.prod.outlook.com cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) *
PM
Original Message Headers
Received: from DS7P222CA0021.NAMP222.PROD.OUTLOOK.COM (2603:10b6:8:2e::20) by
CY4PR11MB1686.namprd11.prod.outlook.com (2603:10b6:903:30::19) with Microsoft
SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id
15.20.5164.20; Thu, 21 Apr 2022 18:14:57 +0000
Received: from DM6NAM10FT037.eop-nam10.prod.protection.outlook.com
(2603:10b6:8:2e:cafe::81) by DS7P222CA0021.outlook.office365.com
(2603:10b6:8:2e::20) with Microsoft SMTP Server (version=TLS1_2,
cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.5186.15 via Frontend
Transport; Thu, 21 Apr 2022 18:14:57 +0000
Authentication-Results: spf=pass (sender IP is 54.240.48.109)
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.109 as permitted sender)
receiver=protection.outlook.com; client-ip=54.240.48.109;
helo=a48-109.smtp-out.amazonses.com;
Received: from a48-109.smtp-out.amazonses.com (54.240.48.109) by
DM6NAM10FT037.mail.protection.outlook.com (10.13.153.29) with Microsoft SMTP
Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id
15.20.5186.14 via Frontend Transport; Thu, 21 Apr 2022 18:14:57 +0000
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/simple;
s=drvjftetwukgvxxawhtk3luf3y2o3amm; d=requests.opramachine.com;
t=1650564896;
h=Date:From:To:Message-ID:Subject:Mime-Version:Content-Type:Content-Transfer-Encoding;
bh=yCB6xe9aEgZ2CQkg6LIiM6vDWHNjD5I62gV+xIub6mI=;
b=gr8KtaeAW208uqGAwG70BcSkzMuKFWq3aRtlq6r7iIuCjjwu2r76fFfmeykYMeo9
P81fvSLrTOmLadUFKrDCBJyNXBlL2pAOLbyhqVoxPQNclA0EGqd9qnZTjFSxqyzhyCU
y+DBRY8NJ7HgnNgR4UZmXII8TJnPg6/J31lZaTzg=
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/simple;
s=6gbrjpgwjskckoa6a5zn6fwqkn67xbtw; d=amazonses.com; t=1650564896;
h=Date:From:To:Message-ID:Subject:Mime-Version:Content-Type:Content-Transfer-Encoding:Feedback-ID;
bh=yCB6xe9aEgZ2CQkg6LIiM6vDWHNjD5I62gV+xIub6mI=;
b=Xu/eniWM8BcwFy5P7D7AfBhCqlBZVFGq/u9Dd0dG6GWZNOcaPGeNUq+70iUX/5IJ
qG3NPren5oyB7LCMg8zs23QtgJpR0EfOm8+gG2MVGd5VtkOY3KZvuPL1xrXI6JDTF++
l1+4hxSWECX5W0UbSfycb9wsh/xjshAYlrAfUNSk=
Date: Thu, 21 Apr 2022 18:14:55 +0000
From: Marc Possoff <[OPRA #31218 email]>
To: OPRA requests at Lawnside Borough <[email address]>
Message-ID: <[email address]>
Subject: OPRA request - Employee Salary Records
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: 2022.04.21-54.240.48.109
Return-Path:
[email address]
X-EOPAttributedMessage: 0
X-EOPTenantAttributedMessage: 2c43b1dc-83ca-40cd-b1e3-431ee3bcab2f:0
X-MS-PublicTrafficType: Email
X-MS-Office365-Filtering-Correlation-Id: 4b124a5e-9191-4ee0-16e2-08da23c2d77e
X-MS-TrafficTypeDiagnostic: CY4PR11MB1686:EE_
References
Visible links
1. https://go.microsoft.com/fwlink/?LinkId=...
2. https://go.microsoft.com/fwlink/?LinkId=...
3. https://go.microsoft.com/fwlink/?LinkId=...