Your message to [email address] couldn't be delivered.

wazirmasy wasn't found at prospectpark.net.

0100016cf3b9c8ea-315. . . Office 365 wazirmasy 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: 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? 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 Fix email delivery issues for error code 5.1.10 in Office 365.

Original Message Details

Created Date: 9/2/2019 8:45:34 PM Sender Address: [email address] Recipient Address: [email address] Subject: OPRA request - Invoices paid to Subway between 11/2016 to 9/2019

Error Details

Reported error: 550 5.1.10 RESOLVER.ADR.RecipientNotFound; Recipient [email address] not found by SMTP address lookup DSN generated by: SN6PR0901MB2462.namprd09.prod.outlook.com

Original Message Headers

Received: from BN6PR09CA0074.namprd09.prod.outlook.com (2603:10b6:404:dc::12)
 by SN6PR0901MB2462.namprd09.prod.outlook.com (2603:10b6:805:a::24) with
 Microsoft SMTP Server (version=TLS1_2,
 cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2220.21; Mon, 2 Sep
 2019 20:45:36 +0000
Received: from BL0GCC02FT007.eop-gcc02.prod.protection.outlook.com
 (2a01:111:f400:7d05::206) by BN6PR09CA0074.outlook.office365.com
 (2603:10b6:404:dc::12) with Microsoft SMTP Server (version=TLS1_2,
 cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) id 15.20.2220.19 via Frontend
 Transport; Mon, 2 Sep 2019 20:45:36 +0000
Authentication-Results: spf=pass (sender IP is 54.240.8.87)
 smtp.mailfrom=bounce.requests.opramachine.com; prospectpark.net; dkim=pass
 (signature was verified) header.d=requests.opramachine.com;prospectpark.net;
 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.87 as permitted sender)
 receiver=protection.outlook.com; client-ip=54.240.8.87;
 helo=a8-87.smtp-out.amazonses.com;
Received: from a8-87.smtp-out.amazonses.com (54.240.8.87) by
 BL0GCC02FT007.mail.protection.outlook.com (10.97.10.173) with Microsoft SMTP
 Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) id
 15.20.2052.18 via Frontend Transport; Mon, 2 Sep 2019 20:45:35 +0000
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/simple;
	s=drvjftetwukgvxxawhtk3luf3y2o3amm; d=requests.opramachine.com;
	t=1567457135;
	h=Date:From:To:Message-ID:Subject:Mime-Version:Content-Type:Content-Transfer-Encoding;
	bh=ev0bjTQMZ3qoSwZJ/sStoCt3Q6vsyXqtNU4BhYKi2cU=;
	b=TDIDnn9l7ixrBgnNBUnyCiYC6ZVdwXaZy26e/sa8Xy6yILL/vvUVhcRMpX9XO+XA
	UX9MLqxWvezEb6Mez0eJxah8jdaDhcW0P6dNPXYvC/4DA5V7Vd+dL4Cq+KJ36wS+KWT
	8EFuVHrVfIIvzQGHMibBeaIWW1NgMgBfNUT2wkms=
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/simple;
	s=6gbrjpgwjskckoa6a5zn6fwqkn67xbtw; d=amazonses.com; t=1567457135;
	h=Date:From:To:Message-ID:Subject:Mime-Version:Content-Type:Content-Transfer-Encoding:Feedback-ID;
	bh=ev0bjTQMZ3qoSwZJ/sStoCt3Q6vsyXqtNU4BhYKi2cU=;
	b=hsOGF/kuykGfk6//bC1YHwSW/I2+Pn4CZqGVOUUkzN4gkL4i/oG6D8jAyAvb+3uZ
	tVfXX7jrFQiYWdj2XfxieSnCu1zzaq1f4WLDCv2upx+C9uPYzVppkov/nomRSeJ8qSA
	VPy9PPZzsj9krtDySvnJx5+m8ZckMtqWRzV274ko=
Date: Mon, 2 Sep 2019 20:45:34 +0000
From: "Dr. Anderson" <[OPRA #7075 email]>
To: OPRA requests at Prospect Park Borough <[email address]>
Message-ID: <[email address]>
Subject: OPRA request - Invoices paid to Subway between 11/2016 to 9/2019
MIME-Version: 1.0
Content-Type: text/plain;
 charset=UTF-8
Content-Transfer-Encoding: 7bit
X-SES-Outgoing: 2019.09.02-54.240.8.87
Feedback-ID: 1.us-east-1.Cy+CdIBOIzrBJluvD+AwZTYIIvgMdz3Pedsyi9/dX4g=:AmazonSES
Return-Path:
	[email address]
X-EOPAttributedMessage: 0
X-EOPTenantAttributedMessage: f1c42e30-61cb-4a50-b284-00ea90e09323:0
X-Forefront-Antispam-Report: CIP:54.240.8.87;IPV:NLI;CTRY:US;EFV:NLI;
X-MS-PublicTrafficType: Email
X-MS-Office365-Filtering-Correlation-Id: 5dbfaac2-74a7-4627-83e2-08d72fe68187
X-Microsoft-Antispam:
	BCL:5;PCL:0;RULEID:(2390118)(7020095)(4652040)(5600166)(711020)(4605104)(4709080)(8001031)(1402095)(71702078);SRVR:SN6PR0901MB2462;
X-MS-TrafficTypeDiagnostic: SN6PR0901MB2462:
X-MS-Exchange-PUrlCount: 3