Your message to vytaute.dlugoborskyte@ktu.edu couldn't be delivered.
vytaute.dlugoborskyte wasn't found at ktu.edu.
010001853511204e-26f. . . Office 365 vytaute.dlugoborskyt. . .
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: 12/21/2022 2:23:13 PM
Sender Address: 010001853511204e-26f3ef36-3237-4e30-961b-ba32c1a981a5-000000@amazonses.com
Recipient Address: vytaute.dlugoborskyte@ktu.edu
Subject: SECOND CALL FOR PAPERS: DRUID23,NOVA School of Business and Economics, June [STARTDAY]-[ENDDAY], 2023

Error Details
Reported error: 550 5.1.10 RESOLVER.ADR.RecipientNotFound; Recipient vytaute.dlugoborskyte@ktu.edu not found by SMTP address lookup
DSN generated by: AS2PR02MB8792.eurprd02.prod.outlook.com

Message Hops
HOP TIME (UTC) FROM TO WITH RELAY TIME
1 12/21/2022
2:23:15 PM		 a8-59.smtp-out.amazonses.com VE1EUR01FT017.mail.protection.outlook.com Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) 2 sec
2 12/21/2022
2:23:16 PM		 VE1EUR01FT017.eop-EUR01.prod.protection.outlook.com FR3P281CA0075.outlook.office365.com Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) 1 sec
3 12/21/2022
2:23:16 PM		 FR3P281CA0075.DEUP281.PROD.OUTLOOK.COM AS2PR02MB8792.eurprd02.prod.outlook.com Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) *

Original Message Headers

Received: from FR3P281CA0075.DEUP281.PROD.OUTLOOK.COM (2603:10a6:d10:1f::23)
 by AS2PR02MB8792.eurprd02.prod.outlook.com (2603:10a6:20b:553::14) with
 Microsoft SMTP Server (version=TLS1_2,
 cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.5924.16; Wed, 21 Dec
 2022 14:23:16 +0000
Received: from VE1EUR01FT017.eop-EUR01.prod.protection.outlook.com
 (2603:10a6:d10:1f:cafe::9c) by FR3P281CA0075.outlook.office365.com
 (2603:10a6:d10:1f::23) with Microsoft SMTP Server (version=TLS1_2,
 cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.5944.10 via Frontend
 Transport; Wed, 21 Dec 2022 14:23:16 +0000
Authentication-Results: spf=pass (sender IP is 54.240.8.59)
 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.59 as permitted sender) receiver=protection.outlook.com;
 client-ip=54.240.8.59; helo=a8-59.smtp-out.amazonses.com; pr=C
Received: from a8-59.smtp-out.amazonses.com (54.240.8.59) by
 VE1EUR01FT017.mail.protection.outlook.com (10.152.2.226) with Microsoft SMTP
 Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id
 15.20.5944.10 via Frontend Transport; Wed, 21 Dec 2022 14:23:15 +0000
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/simple;
	s=zc5f2us2jbwdrx3rxw5cs2ibbe3pi5ly; d=druid.dk; t=1671632593;
	h=Date:From:To:Message-ID:Subject:MIME-Version:Content-Type:Content-Transfer-Encoding;
	bh=XGRT6eJ5VwJdXKUNdtO0AgjcTtm8tOVEqPrwODIPVNo=;
	b=MiOvrcbkiWqeUa7T7srIpPxYF97LpGR3FhgbLtneyqMHVDag8lD1SATWn2sPLBQa
	r1fkZ4PvPxRHF/HVqFIgDXgVhYtaUd9dy8ZlxmWJWAfWxA37Q4638nYDOpjSceaGsYW
	JoFOzMpit4uPI1/KNBPMKp7E8k27Ash/rVVzlGbY=
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/simple;
	s=6gbrjpgwjskckoa6a5zn6fwqkn67xbtw; d=amazonses.com; t=1671632593;
	h=Date:From:To:Message-ID:Subject:MIME-Version:Content-Type:Content-Transfer-Encoding:Feedback-ID;
	bh=XGRT6eJ5VwJdXKUNdtO0AgjcTtm8tOVEqPrwODIPVNo=;
	b=Ac/o1FvzwVxzR0UbNUXHtx/ToF748gt9zlY/uL6bgh73aDdjuB3I1Sy1Pvg+NpQk
	Rt5Z5qFdv3CEByf9DEYWJyJqDZ59VGeJ8JYaOmSBUTZbsPFK4tXMPNZwQu+F7YawLya
	l4KpnQJlnXj+ugavvBPCQz44ipJX7Qd2ffPXyLxw=
Date: Wed, 21 Dec 2022 14:23:13 +0000
From: DRUID23 <druid@druid.dk>
To: Vytaute Dlugoborskyte <vytaute.dlugoborskyte@ktu.edu>
Message-ID: <010001853511204e-26f3ef36-3237-4e30-961b-ba32c1a981a5-000000@email.amazonses.com>
Subject: SECOND CALL FOR PAPERS: DRUID23,NOVA School of Business and
 Economics,  June [STARTDAY]-[ENDDAY], 2023
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: 2022.12.21-54.240.8.59
Return-Path:
	010001853511204e-26f3ef36-3237-4e30-961b-ba32c1a981a5-000000@amazonses.com
X-EOPAttributedMessage: 0
X-EOPTenantAttributedMessage: 3415f2f7-f5a8-4092-b52a-003aaf844853:0
X-MS-PublicTrafficType: Email
X-MS-TrafficTypeDiagnostic: VE1EUR01FT017:EE_|AS2PR02MB8792:EE_
X-MS-Office365-Filtering-Correlation-Id: 64c09cdf-400d-4067-5339-08dae35ee662