Your message to [Dirección de correo del organismo Ministerio De Defensa Nacional] couldn't be delivered.
usuarios wasn't found at mindefensa.gov.co.
request-2779-aede9d5. . . Office 365 usuarios
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: [1]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? [2]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 [3]Fix
email delivery issues for error code 5.1.10 in Office 365.
Original Message Details
Created Date: 5/8/2025 12:30:53 AM
Sender Address: [Dirección de correo de la solicitud #2779]
Recipient Address: [Dirección de correo del organismo Ministerio De Defensa Nacional]
Subject: solicitud acceso a la información - Solicitud
certificado Cetil
Error Details
Error: 550 5.1.10 RESOLVER.ADR.RecipientNotFound; Recipient
[Dirección de correo del organismo Ministerio De Defensa Nacional] not found by SMTP address
lookup
Message rejected SA1PR13MB6145.namprd13.prod.outlook.com
by:
Notification Details
Sent by: SA1PR13MB6145.namprd13.prod.outlook.com

Message Hops
HOP TIME FROM TO WITH RELAY
(UTC) TIME
5/8/2025 local (Exim 4.94.2) (envelope-from
1 12:30:53 foicolombia mstr001hexa.srv.mysociety.org <[Dirección de correo de la solicitud #2779]>) *
AM
5/8/2025 esmtps (TLS1.3) tls
2 12:30:54 mstr001hexa.srv.mysociety.org mslb001sova.srv.mysociety.org TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 1 sec
AM 4.94.2) (envelope-from
<[Dirección de correo de la solicitud #2779]>)
5/8/2025 Microsoft SMTP Server (version=TLS1_3,
3 12:30:55 mslb001sova.srv.mysociety.org SN1PEPF0002529D.mail.protection.outlook.com cipher=TLS_AES_256_GCM_SHA384) 1 sec
AM
5/8/2025 Microsoft SMTP Server (version=TLS1_3,
4 12:30:57 SN1PEPF0002529D.namprd05.prod.outlook.com SA1P222CA0139.outlook.office365.com cipher=TLS_AES_256_GCM_SHA384) 2 sec
AM
5/8/2025 Microsoft SMTP Server (version=TLS1_2,
5 12:30:57 SA1P222CA0139.NAMP222.PROD.OUTLOOK.COM SA1PR13MB6145.namprd13.prod.outlook.com cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) *
AM

Original Message Headers

Received: from SA1P222CA0139.NAMP222.PROD.OUTLOOK.COM (2603:10b6:806:3c2::25)
by SA1PR13MB6145.namprd13.prod.outlook.com (2603:10b6:806:339::16) with
Microsoft SMTP Server (version=TLS1_2,
cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.8699.26; Thu, 8 May
2025 00:30:57 +0000
Received: from SN1PEPF0002529D.namprd05.prod.outlook.com
(2603:10b6:806:3c2:cafe::b9) by SA1P222CA0139.outlook.office365.com
(2603:10b6:806:3c2::25) with Microsoft SMTP Server (version=TLS1_3,
cipher=TLS_AES_256_GCM_SHA384) id 15.20.8699.33 via Frontend Transport; Thu,
8 May 2025 00:30:57 +0000
Authentication-Results: spf=pass (sender IP is 2a00:1098:80:3b::3:1)
smtp.mailfrom=queremosdatos.co; dkim=none (message not signed)
header.d=none;dmarc=bestguesspass action=none header.from=queremosdatos.co;
Received-SPF: Pass (protection.outlook.com: domain of queremosdatos.co
designates 2a00:1098:80:3b::3:1 as permitted sender)
receiver=protection.outlook.com; client-ip=2a00:1098:80:3b::3:1;
helo=mslb001sova.srv.mysociety.org; pr=C
Received: from mslb001sova.srv.mysociety.org (2a00:1098:80:3b::3:1) by
SN1PEPF0002529D.mail.protection.outlook.com (2603:10b6:82c:400:0:1004:0:4)
with Microsoft SMTP Server (version=TLS1_3, cipher=TLS_AES_256_GCM_SHA384) id
15.20.8722.18 via Frontend Transport; Thu, 8 May 2025 00:30:55 +0000
Received: from mstr001hexa.srv.mysociety.org ([2a00:1098:82:dd::c:1]:47600)
by mslb001sova.srv.mysociety.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
(Exim 4.94.2)
(envelope-from <[Dirección de correo de la solicitud #2779]>)
id 1uCpA6-003iSV-6z
for [Dirección de correo del organismo Ministerio De Defensa Nacional]; Thu, 08 May 2025 00:30:54 +0000
Received: from foicolombia by mstr001hexa.srv.mysociety.org with local (Exim 4.94.2)
(envelope-from <[Dirección de correo de la solicitud #2779]>)
id 1uCpA5-00GsDN-RE
for [Dirección de correo del organismo Ministerio De Defensa Nacional]; Thu, 08 May 2025 00:30:53 +0000
Date: Thu, 08 May 2025 00:30:53 +0000
From: Dager Johan Pino Melenje <[Dirección de correo de la solicitud #2779]>
To: =?UTF-8?B?U29saWNpdHVkZXMgZGUgaW5mb3JtYWNpw7NuIGEgTWluaXN0ZXJpbyBEZSBE?= =?UTF-8?B?ZWZlbnNhIE5hY2lvbmFs?= <[Dirección de correo del organismo Ministerio De Defensa Nacional]>
Message-ID: <[correo electrónico]>
Subject: =?UTF-8?Q?solicitud_acceso_a_la_informaci=C3=B3n_-_Solicitud?=
=?UTF-8?Q?_certificado_Cetil?=
MIME-Version: 1.0
Content-Type: text/plain;
charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Return-Path: [Dirección de correo de la solicitud #2779]
X-EOPAttributedMessage: 0
X-EOPTenantAttributedMessage: 7aab4bdf-7e74-4242-a817-1c24236899e7:0
X-MS-PublicTrafficType: Email
X-MS-TrafficTypeDiagnostic: SN1PEPF0002529D:EE_|SA1PR13MB6145:EE_
X-MS-Office365-Filtering-Correlation-Id: fcce2d90-bc96-4854-f778-08dd8dc798ca

References

Visible links
1. https://go.microsoft.com/fwlink/?LinkId=...
2. https://go.microsoft.com/fwlink/?LinkId=...
3. https://go.microsoft.com/fwlink/?LinkId=...