Forum Discussion
Your message wasn't delivered because the recipient's email provider rejected it
Same thing happens here since tonight when I sent hotmail from Outlook 365.
Same issue started a few hours ago for me. The below is what I have received from every email I send via the Mail app on Windows 10. Using same mail app but sending from gmail and organisation account I have no issues. I have also attempted to send emails to a variety of domains.
Email from browser and iPhone work fine. Have uninstalled and reinstalled app, along with removed outlook account and added back again. No success.
*Note: have used asterisks to protect recipient email, email was typed correctly in original attempt*
Your message wasn't delivered because the recipient's email provider rejected it.
Diagnostic information for administrators:
Generating server: BN7NAM10HT095.mail.protection.outlook.com
****kins@gmail.com
Remote Server returned '550 5.7.520 Message blocked because it contains content identified as spam. AS(4567)'
Original message headers:
Received: from BN7NAM10FT021.eop-nam10.prod.protection.outlook.com (2a01:111:e400:7e8f::36) by BN7NAM10HT095.eop-nam10.prod.protection.outlook.com (2a01:111:e400:7e8f::440) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2686.25; Wed, 5 Feb 2020 12:11:19 +0000Received: from MN2PR06MB6736.namprd06.prod.outlook.com (10.13.156.58) by BN7NAM10FT021.mail.protection.outlook.com (10.13.157.29) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2686.25 via Frontend Transport; Wed, 5 Feb 2020 12:11:19 +0000X-IncomingTopHeaderMarker: OriginalChecksum:E373BE5D7BC4659545DD2140729D47AC62BFF186EE4CB140507460522D6477E4;UpperCasedChecksum:B8299216575BC0331BE4BD3398746A07F97C9AD8A53649403793369EABD79C92;SizeAsReceived:6682;Count:43Received: from MN2PR06MB6736.namprd06.prod.outlook.com ([fe80::19d3:642b:a959:79f7]) by MN2PR06MB6736.namprd06.prod.outlook.com ([fe80::19d3:642b:a959:79f7%5]) with mapi id 15.20.2686.031; Wed, 5 Feb 2020 12:11:19 +0000Content-Type: application/ms-tnef; name="winmail.dat"Content-Transfer-Encoding: binaryFrom: Kane Vellin <kane.vellin@outlook.com>To: "caeminmurphyatkins@gmail.com" <caeminmurphyatkins@gmail.com>Subject: test.....Thread-Topic: test.....Thread-Index: AQHV3B1YgULN/rz4/USgyB3NQcigpw==X-MS-Exchange-MessageSentRepresentingType: 1Date: Wed, 5 Feb 2020 12:11:18 +0000Message-ID: <MN2PR06MB673621009C12AC60D50F360FE7020@MN2PR06MB6736.namprd06.prod.outlook.com>Accept-Language: en-AU, en-USContent-Language: en-USX-MS-Has-Attach:X-MS-TNEF-Correlator: <MN2PR06MB673621009C12AC60D50F360FE7020@MN2PR06MB6736.namprd06.prod.outlook.com>MIME-Version: 1.0X-TMN: [+cqdbnoi2KOUb0RMLbgIUgRllJGx/F2d]X-MS-PublicTrafficType: EmailX-IncomingHeaderCount: 43Return-Path: kane.vellin@outlook.comX-EOPAttributedMessage: 0X-MS-Office365-Filtering-Correlation-Id: d65d66d7-720e-43b6-ef01-08d7aa3481e5X-MS-TrafficTypeDiagnostic: BN7NAM10HT095:
Every message that I have been sending out for the past hour has been returned with that error.
After finally getting through to someone on Microsoft support live chat, they've advised that they're aware of the issue and are in the process of resolving it:
Thank you for letting us know about this problem Alistair. Actually an ongoing issue at the moment and our Reasearch Engineers are up on fixing this issue. This may take around a maximum of 24 to be fixed. If this issue has already been fixed, you might be notified via email. Okay? 🙂 I deeply apologize about the inconvenience with regards to this problem. Please bear with us.
