Your message to JBOWES@ECCAREMGT.ORG couldn't be delivered.

JBOWES wasn't found at eccaremgt.org.

topf Office 365 JBOWES 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: 3/19/2024 2:07:35 PM Sender Address: topf@zapf.in Recipient Address: JBOWES@ECCAREMGT.ORG Subject: [ZaPF-Lists] Bitte bestätige deine E-Mail-Adresse

Error Details

Error: 550 5.1.10 RESOLVER.ADR.RecipientNotFound; Recipient JBOWES@ECCAREMGT.ORG not found by SMTP address lookup Message rejected by: BL3PR01MB6931.prod.exchangelabs.com

Notification Details

Sent by: BL3PR01MB6931.prod.exchangelabs.com

Original Message Headers

Received: from CH2PR05CA0029.namprd05.prod.outlook.com (2603:10b6:610::42) by
 BL3PR01MB6931.prod.exchangelabs.com (2603:10b6:208:356::9) with Microsoft
 SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id
 15.20.7386.29; Tue, 19 Mar 2024 14:07:47 +0000
Received: from CH2PEPF0000014A.namprd02.prod.outlook.com
 (2603:10b6:610:0:cafe::12) by CH2PR05CA0029.outlook.office365.com
 (2603:10b6:610::42) with Microsoft SMTP Server (version=TLS1_2,
 cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.7409.11 via Frontend
 Transport; Tue, 19 Mar 2024 14:07:47 +0000
Authentication-Results: spf=fail (sender IP is 148.163.129.48)
 smtp.mailfrom=zapf.in; dkim=none (message not signed)
 header.d=none;dmarc=temperror action=none header.from=zapf.in;
Received-SPF: Fail (protection.outlook.com: domain of zapf.in does not
 designate 148.163.129.48 as permitted sender)
 receiver=protection.outlook.com; client-ip=148.163.129.48;
 helo=dispatch1-us1.ppe-hosted.com;
Received: from dispatch1-us1.ppe-hosted.com (148.163.129.48) by
 CH2PEPF0000014A.mail.protection.outlook.com (10.167.244.107) with Microsoft
 SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id
 15.20.7409.10 via Frontend Transport; Tue, 19 Mar 2024 14:07:45 +0000
Authentication-Results-Original: ppe-hosted.com; spf=pass
 smtp.mailfrom=zapf.in; dmarc=none header.from=zapf.in header.policy=none; 
X-Virus-Scanned: Proofpoint Essentials engine
Received: from mail.zapf.in (hetzner.zapf.in [94.130.65.175])
	(using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
	(No client certificate requested)
	by mx1-us1.ppe-hosted.com (PPE Hosted ESMTP Server) with ESMTPS id 16471C0009F
	for <JBOWES@ECCAREMGT.ORG>; Tue, 19 Mar 2024 14:07:42 +0000 (UTC)
Received: from localhost (localhost [IPv6:::1])
	by mail.zapf.in (Postfix) with ESMTPS id ADA15E042C
	for <JBOWES@ECCAREMGT.ORG>; Tue, 19 Mar 2024 15:07:35 +0100 (CET)
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: base64
Subject: =?utf-8?q?=5BZaPF-Lists=5D_Bitte_best=C3=A4tige_deine_E-Mail-Adresse?=
From: topf@zapf.in
To: JBOWES@ECCAREMGT.ORG
Date: Tue, 19 Mar 2024 14:07:35 -0000
Message-ID: <171085725569.278.950749880234820476@localhost>
X-MDID: 1710857263-gYYj5qAMe3RV
X-MDID-I: us5;ut7;1710857263;gYYj5qAMe3RV;<topf@zapf.in>;179438640a889d21a7561ca7db951677
Return-Path: topf@zapf.in
X-EOPAttributedMessage: 0
X-EOPTenantAttributedMessage: bd124aad-6f8f-4e2f-b0f4-4d126e529160:0
X-MS-PublicTrafficType: Email
X-MS-TrafficTypeDiagnostic: CH2PEPF0000014A:EE_|BL3PR01MB6931:EE_
X-MS-Office365-Filtering-Correlation-Id: c9772c64-c5b8-4b98-bc8b-08dc481df3dd