Your message to kwon.seokbeom@mail.u-tokyo.ac.jp couldn't be delivered.
kwon.seokbeom wasn't found at mail.u-tokyo.ac.jp.
0100018b617d6dcf-559. . . Office 365 kwon.seokbeom
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: 10/24/2023 11:41:31 AM
Sender Address: 0100018b617d6dcf-559a7bdd-55c1-414b-bdf4-d32057896822-000000@amazonses.com
Recipient Address: kwon.seokbeom@mail.u-tokyo.ac.jp
Subject: FINAL CALL FOR PAPERS: DRUID Academy 2024, University of Southern Denmark, January 17-January 19, 2024

Error Details
Error: 550 5.1.10 RESOLVER.ADR.RecipientNotFound; Recipient kwon.seokbeom@mail.u-tokyo.ac.jp not found by SMTP address lookup
Message rejected by: OS3PR01MB10136.jpnprd01.prod.outlook.com

Notification Details
Sent by: OS3PR01MB10136.jpnprd01.prod.outlook.com

Message Hops
HOP TIME (UTC) FROM TO WITH RELAY TIME
1 10/24/2023
11:41:34 AM		 a8-195.smtp-out.amazonses.com TYCJPN01FT006.mail.protection.outlook.com Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) 3 sec
2 10/24/2023
11:41:35 AM		 TYCJPN01FT006.eop-JPN01.prod.protection.outlook.com TYCP301CA0051.outlook.office365.com Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) 1 sec
3 10/24/2023
11:41:35 AM		 TYCP301CA0051.JPNP301.PROD.OUTLOOK.COM OS3PR01MB10136.jpnprd01.prod.outlook.com Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) *

Original Message Headers

Received: from TYCP301CA0051.JPNP301.PROD.OUTLOOK.COM (2603:1096:400:384::16)
 by OS3PR01MB10136.jpnprd01.prod.outlook.com (2603:1096:604:1e5::11) with
 Microsoft SMTP Server (version=TLS1_2,
 cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.6907.35; Tue, 24 Oct
 2023 11:41:35 +0000
Received: from TYCJPN01FT006.eop-JPN01.prod.protection.outlook.com
 (2603:1096:400:384:cafe::8d) by TYCP301CA0051.outlook.office365.com
 (2603:1096:400:384::16) with Microsoft SMTP Server (version=TLS1_2,
 cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.6907.31 via Frontend
 Transport; Tue, 24 Oct 2023 11:41:35 +0000
Authentication-Results: spf=pass (sender IP is 54.240.8.195)
 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.195 as permitted sender) receiver=protection.outlook.com;
 client-ip=54.240.8.195; helo=a8-195.smtp-out.amazonses.com; pr=C
Received: from a8-195.smtp-out.amazonses.com (54.240.8.195) by
 TYCJPN01FT006.mail.protection.outlook.com (10.118.160.89) with Microsoft SMTP
 Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id
 15.20.6907.26 via Frontend Transport; Tue, 24 Oct 2023 11:41:34 +0000
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/simple;
	s=3qzxzbyhaymt3i6nxxr5zjq5kjllp5wj; d=druid.dk; t=1698147692;
	h=Date:From:To:Message-ID:Subject:MIME-Version:Content-Type:Content-Transfer-Encoding;
	bh=ChXcUMqbSZIHn/IBQozITbf4wdY2W8nymk/KFxvy5Ps=;
	b=Y8vo00uJ6hPuO793avtZfRCJO5DwJ/2l7CgPRvcUpyi4ObfiP57nbs4ZgfeCX8ya
	npDpl6ncDwoN8KynORpDieu/qzDqQMy4EtQU6wyndGO+nCXGh7VUBRj1rgvPZpGLyUR
	HOD/HCc4KcPge6xnBo5eMpCWCWmjZl1PrGpMRkmQ=
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/simple;
	s=224i4yxa5dv7c2xz3womw6peuasteono; d=amazonses.com; t=1698147692;
	h=Date:From:To:Message-ID:Subject:MIME-Version:Content-Type:Content-Transfer-Encoding:Feedback-ID;
	bh=ChXcUMqbSZIHn/IBQozITbf4wdY2W8nymk/KFxvy5Ps=;
	b=hzzF4dF2Y5qCXImHhyrGhpfsIGMoNyCoBtJEkEkWf+fkcH0bilPhoxwrw/le/K9a
	LYs6um2G3wKHgP2gzgTzFawdpG1QKCgxWKdYs1iamu0NHxeY8xiDDKka3QOCwLN9LxR
	8I9HEGdGan6GZSNd1wKwlXArEnfCp+xJZHc7GFks=
Date: Tue, 24 Oct 2023 11:41:31 +0000
From: DRUID Academy 2024 <druid@druid.dk>
To: Seokbeom Kwon <kwon.seokbeom@mail.u-tokyo.ac.jp>
Message-ID: <0100018b617d6dcf-559a7bdd-55c1-414b-bdf4-d32057896822-000000@email.amazonses.com>
Subject: FINAL CALL FOR PAPERS: DRUID Academy 2024, University of Southern
 Denmark, January 17-January 19, 2024
MIME-Version: 1.0
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Feedback-ID: 1.us-east-1.13mSgHqxbnUUx50/TZSkdjEk6laramo5BkOedBdTQl8=:AmazonSES
X-SES-Outgoing: 2023.10.24-54.240.8.195
Return-Path:
	0100018b617d6dcf-559a7bdd-55c1-414b-bdf4-d32057896822-000000@amazonses.com
X-EOPAttributedMessage: 0
X-EOPTenantAttributedMessage: f07baf4f-2b70-47d7-9a02-0875caf94c84:0
X-MS-PublicTrafficType: Email
X-MS-TrafficTypeDiagnostic: TYCJPN01FT006:EE_|OS3PR01MB10136:EE_
X-MS-Office365-Filtering-Correlation-Id: 546c5732-2f4e-4fd5-cd7f-08dbd4862cd4