Your message to luo@sutd.edu.sg couldn't be delivered.
luo wasn't found at sutd.edu.sg.
0100018df54760de-5a3. . . Office 365 luo
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: 2/29/2024 2:31:52 PM
Sender Address: 0100018df54760de-5a30cfda-074b-449f-aa17-c4507430ed6a-000000@amazonses.com
Recipient Address: luo@sutd.edu.sg
Subject: DRUID24: Deadline for submissions of papers and PDW proposals

Error Details
Error: 550 5.1.10 RESOLVER.ADR.RecipientNotFound; Recipient luo@sutd.edu.sg not found by SMTP address lookup
Message rejected by: TYUPR03MB7112.apcprd03.prod.outlook.com

Notification Details
Sent by: TYUPR03MB7112.apcprd03.prod.outlook.com

Message Hops
HOP TIME (UTC) FROM TO WITH RELAY TIME
1 2/29/2024
2:31:54 PM
a8-51.smtp-out.amazonses.com HK2PEPF00006FB2.mail.protection.outlook.com Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) 2 sec
2 2/29/2024
2:31:55 PM
HK2PEPF00006FB2.apcprd02.prod.outlook.com PS2PR06CA0002.outlook.office365.com Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) 1 sec
3 2/29/2024
2:31:56 PM
PS2PR06CA0002.apcprd06.prod.outlook.com TYUPR03MB7112.apcprd03.prod.outlook.com Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) 1 sec

Original Message Headers

Received: from PS2PR06CA0002.apcprd06.prod.outlook.com (2603:1096:300:56::14)
 by TYUPR03MB7112.apcprd03.prod.outlook.com (2603:1096:400:35f::10) with
 Microsoft SMTP Server (version=TLS1_2,
 cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.7316.39; Thu, 29 Feb
 2024 14:31:56 +0000
Received: from HK2PEPF00006FB2.apcprd02.prod.outlook.com
 (2603:1096:300:56:cafe::50) by PS2PR06CA0002.outlook.office365.com
 (2603:1096:300:56::14) with Microsoft SMTP Server (version=TLS1_2,
 cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.7339.29 via Frontend
 Transport; Thu, 29 Feb 2024 14:31:55 +0000
Authentication-Results: spf=pass (sender IP is 54.240.8.51)
 smtp.mailfrom=amazonses.com; dkim=pass (signature was verified)
 header.d=druid.dk;dmarc=bestguesspass action=none header.from=druid.dk;
Received-SPF: Pass (protection.outlook.com: domain of amazonses.com designates
 54.240.8.51 as permitted sender) receiver=protection.outlook.com;
 client-ip=54.240.8.51; helo=a8-51.smtp-out.amazonses.com; pr=C
Received: from a8-51.smtp-out.amazonses.com (54.240.8.51) by
 HK2PEPF00006FB2.mail.protection.outlook.com (10.167.8.8) with Microsoft SMTP
 Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id
 15.20.7292.25 via Frontend Transport; Thu, 29 Feb 2024 14:31:54 +0000
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/simple;
	s=3qzxzbyhaymt3i6nxxr5zjq5kjllp5wj; d=druid.dk; t=1709217112;
	h=Date:From:To:Message-ID:Subject:MIME-Version:Content-Type:Content-Transfer-Encoding;
	bh=8mEm4+xUD1WbPwwk8JhGxRhktAlyEJ56Cw+zqYKZmS8=;
	b=WZnF/c8KAzPHaNnXbK0jbSOBmwCtQeR1u5X5ItGN3bHGE8F8JrjdIQrfbWSNt19K
	MDkoXh++EHnS2kxZq+zQCG+GwEfzTdQraryu3Xe/+8gTAcZx9DR6SXynMkf1p7BbiIB
	AluFbUZtXhqEvrsYshbrrrD/6vUZWdkdicb3ltyI=
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/simple;
	s=224i4yxa5dv7c2xz3womw6peuasteono; d=amazonses.com; t=1709217112;
	h=Date:From:To:Message-ID:Subject:MIME-Version:Content-Type:Content-Transfer-Encoding:Feedback-ID;
	bh=8mEm4+xUD1WbPwwk8JhGxRhktAlyEJ56Cw+zqYKZmS8=;
	b=cVPux94jcHyj42DyKz0vp6gzgP5WlInDoLPQGy48s0p8b+LraJd124ZL7f8svb8g
	tHzo9IZjlWVf10ufehSRzQDO1xbtRgVSGCqvTicFvaDCLF1RAqnHPAS5av3OWIuWp5U
	4OP48YJcGwAjNM7nJrP1xjkcQPTSeE24c0SYOb5I=
Date: Thu, 29 Feb 2024 14:31:52 +0000
From: DRUID24 <druid@druid.dk>
To: Jianxi Luo <luo@sutd.edu.sg>
Message-ID: <0100018df54760de-5a30cfda-074b-449f-aa17-c4507430ed6a-000000@email.amazonses.com>
Subject: DRUID24: Deadline for submissions of papers and PDW proposals
MIME-Version: 1.0
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 7bit
Feedback-ID: 1.us-east-1.13mSgHqxbnUUx50/TZSkdjEk6laramo5BkOedBdTQl8=:AmazonSES
X-SES-Outgoing: 2024.02.29-54.240.8.51
Return-Path:
	0100018df54760de-5a30cfda-074b-449f-aa17-c4507430ed6a-000000@amazonses.com
X-EOPAttributedMessage: 0
X-EOPTenantAttributedMessage: 3476b776-e990-4f72-b950-62489831623d:0
X-MS-PublicTrafficType: Email
X-MS-TrafficTypeDiagnostic: HK2PEPF00006FB2:EE_|TYUPR03MB7112:EE_
X-MS-Office365-Filtering-Correlation-Id: e6d8bd29-8a0f-4804-e689-08dc39332dce