Your message to [Dirección de correo del organismo Ministerio De Tecnologías De La Información Y Las Comunicaciones] couldn't be delivered.
infor wasn't found at mintic.gov.co.
request-341-303f52db Office 365 infor
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: 6/9/2018 1:18:05 PM
Sender Address: [Dirección de correo de la solicitud #341]
Recipient [Dirección de correo del organismo Ministerio De Tecnologías De La Información Y Las Comunicaciones]
Address:
Subject: solicitud acceso a la información - Estadísticas del usa
de redes sociales por la población colombiana
Error Details
Reported error: 550 5.1.10 RESOLVER.ADR.RecipientNotFound; Recipient
[Dirección de correo del organismo Ministerio De Tecnologías De La Información Y Las Comunicaciones] not found by SMTP address lookup
DSN generated by: BN7PR05MB4195.namprd05.prod.outlook.com

Message Hops
HOP TIME FROM TO WITH RELAY
(UTC) TIME
6/9/2018 local (Exim 4.80) (envelope-from
1 1:18:05 foicolombia mastodon.ukcod.org.uk <[Dirección de correo de la solicitud #341]>) *
PM
6/9/2018 esmtps (TLS1.2:DHE_RSA_AES_128_CBC_SHA1:128) (Exim
2 1:18:06 mastodon.ukcod.org.uk bittern.ukcod.org.uk 4.89) (envelope-from 1 sec
PM <[Dirección de correo de la solicitud #341]>)
6/9/2018 Microsoft SMTP Server (version=TLS1_2,
3 1:18:07 bittern.ukcod.org.uk BY2NAM01FT059.mail.protection.outlook.com cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256) 1 sec
PM
6/9/2018 Microsoft SMTP Server (version=TLS1_2,
4 1:18:08 BY2NAM01FT059.eop-nam01.prod.protection.outlook.com SN4PR0501CA0156.outlook.office365.com cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) 1 sec
PM
6/9/2018 Microsoft SMTP Server (version=TLS1_2,
5 1:18:08 SN4PR0501CA0156.namprd05.prod.outlook.com BN7PR05MB4195.namprd05.prod.outlook.com cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) *
PM

Original Message Headers

Received: from SN4PR0501CA0156.namprd05.prod.outlook.com
(2603:10b6:803:2c::34) by BN7PR05MB4195.namprd05.prod.outlook.com
(2603:10b6:406:90::31) with Microsoft SMTP Server (version=TLS1_2,
cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.863.6; Sat, 9 Jun 2018
13:18:08 +0000
Received: from BY2NAM01FT059.eop-nam01.prod.protection.outlook.com
(2a01:111:f400:7e42::209) by SN4PR0501CA0156.outlook.office365.com
(2603:10b6:803:2c::34) with Microsoft SMTP Server (version=TLS1_2,
cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) id 15.20.797.5 via Frontend
Transport; Sat, 9 Jun 2018 13:18:08 +0000
Authentication-Results: spf=none (sender IP is 46.43.39.111)
smtp.mailfrom=queremosdatos.co; mintic.gov.co; dkim=none (message not signed)
header.d=none;mintic.gov.co; dmarc=none action=none
header.from=queremosdatos.co;
Received-SPF: None (protection.outlook.com: queremosdatos.co does not
designate permitted sender hosts)
Received: from bittern.ukcod.org.uk (46.43.39.111) by
BY2NAM01FT059.mail.protection.outlook.com (10.152.68.205) with Microsoft SMTP
Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256) id
15.20.841.10 via Frontend Transport; Sat, 9 Jun 2018 13:18:07 +0000
Received: from mastodon.ukcod.org.uk ([46.43.39.83]:53007)
by bittern.ukcod.org.uk with esmtps (TLS1.2:DHE_RSA_AES_128_CBC_SHA1:128)
(Exim 4.89)
(envelope-from <[Dirección de correo de la solicitud #341]>)
id 1fRdks-0007UZ-2H
for [Dirección de correo del organismo Ministerio De Tecnologías De La Información Y Las Comunicaciones]; Sat, 09 Jun 2018 14:18:06 +0100
Received: from foicolombia by mastodon.ukcod.org.uk with local (Exim 4.80)
(envelope-from <[Dirección de correo de la solicitud #341]>)
id 1fRdkr-0004sX-UX; Sat, 09 Jun 2018 14:18:05 +0100
Date: Sat, 9 Jun 2018 14:18:05 +0100
From: Susana Amado Medina <[Dirección de correo de la solicitud #341]>
To: =?UTF-8?B?U29saWNpdHVkZXMgZGUgaW5mb3JtYWNpw7NuIGEgTWluaXN0ZXJpbyBEZSBU?=
=?UTF-8?B?ZWNub2xvZ8OtYXMgRGUgTGEgSW5mb3JtYWNpw7NuIFkgTGFzIENvbXVuaWNh?=
=?UTF-8?B?Y2lvbmVz?= <[Dirección de correo del organismo Ministerio De Tecnologías De La Información Y Las Comunicaciones]>
Message-ID: <[correo electrónico]>
Subject: =?UTF-8?Q?solicitud_acceso_a_la_informaci=C3=B3n_-?=
=?UTF-8?Q?_Estad=C3=ADsticas_del_usa_de_redes_sociales_por_la?=
=?UTF-8?Q?_poblaci=C3=B3n_colombiana?=
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 #341]
X-EOPAttributedMessage: 0
X-EOPTenantAttributedMessage: 1a0673c6-24e1-476d-bb4d-ba6a91a3c588:0
X-Forefront-Antispam-Report: CIP:46.43.39.111;IPV:NLI;CTRY:GB;EFV:NLI;
X-Microsoft-Exchange-Diagnostics: 1;BY2NAM01FT059;1:Va/1OIsuk/SU+76/kncFDCMHMjcqX8m3mMyj1CDYwQUMLho+L0bsRioPOKQXFmCw2uj9EVwa4GxsppV88SPn8ngW4zG5sApAAC9dWNVM0OSTkc7C9TP2M231K2yp28M/
X-MS-PublicTrafficType: Email
X-Microsoft-Antispam:
UriScan:;BCL:0;PCL:0;RULEID:(7020095)(5600026)(4605076)(1401150)(1404068)(71702078);SRVR:BN7PR05MB4195;
X-Microsoft-Exchange-Diagnostics:
1;BN7PR05MB4195;3:rJFkqO8/2ePisemj7IZ6zv4yXuGD0IIUVtMZcclaiPDk9vS0qESOr+J2oA9uoYAlu3JsiDehNAcBZo8R7Z7Vq5+rGs4b1JauQrbEIgfKU+TqUljEALUmgQ/V04G3G/BsuyuRH/4ebDIrk72CUwl+oH4nVz7yC1yCaEExIVL5Pd/zuyrvZks0DHQ22112/P6hqIBiNKUmzOodpDT335cM45wh7wJx/pJiKQlLz8MAZT+VxOCGfdtF3tUYFmVXxsxyyff2GqTU1q6kS00cwFXX6rclgnOOEYHEv4L20P8khNDtvamWXjslfqmRWSB1dH1kzSBXKugzu7bWmX3YCKwhb/8pwMLeeNa6UbQxYsgJRK4=;25:qNIdlWW1vFYHeaa/Oe89hPcJ+ljTCvfsNegTGta8DKjy3Pz61p8cn+JH1yhIMaqAjB/SQVmGib6YyHUzjdj/03vrwyw1tsQLXPi7WjOCtFgomrxw+XyRwYTybMDI4NNxEuA4P8hLg56SvDBgenVwUtBZQh708qeI/o23hSsUraT0sPFPR33qf0f0yrySAyAsx2GOxqv+tAbtBFdrH5wHb9XlJANx5Hq/hfKqVu1aVdiIWQ3Iqvbgwxu+2dvjtyivj4rrFdAj06bVLr6eCDoRC+xCYvQa+9fkwxjsJ880NOpWvepfj1ii9rSZ7IqAC4Uw9y/LzDDLGRzOc0nKtEBzKw==
X-MS-TrafficTypeDiagnostic: BN7PR05MB4195:

References

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