Emails from Outlook bounce back from all yahoo and sky emails with error message

Anonymous

error message "Your message wasn't delivered. Despite repeated attempts to deliver your message, a connection to the remote server was closed abruptly.

Contact the recipient by some other means (by phone, for example) and ask them to tell their email admin that it appears that your email system is unable to connecto their email system. Give them the error details shown below. It's likely that the recipient's email admin is the only one who can fix this problem.

For Email Admins
This often indicates the recipient's firewall SMTP fixup setting or other firewall settings are preventing the SMTP protocol negotiation from succeeding.

For more information and tips to fix this issue see this article: https://go.microsoft.com/fwlink/?LinkId=389361.

For Yahoo: returned '550 5.4.318 Message expired, connection reset (SuspiciousRemoteServerError)(450 4.4.318 Connection was closed abruptly (SuspiciousRemoteServerError))'
3/8/2024 8:44:42 PM - Server at mx-eu.mail.am0.yahoodns.net (188.125.72.73) returned '450 4.4.318 Connection was closed abruptly (SuspiciousRemoteServerError)'

For sky: returned '550 5.4.300 Message expired -> 421 4.4.2 Connection dropped due to SocketError'
3/8/2024 8:39:33 PM - Server at 188.125.72.73 (188.125.72.73) returned '421 4.4.2 Connection dropped due to SocketError'

I cannot ask all my contacts that have yahoo or sky accounts to change their firewall settings. There seems to be a problem with Microsoft!

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

60 answers

Anonymous

2024-03-11T19:19:38+00:00

I don't know if this will help but last month I had a problem with AOL and Yahoo emails bouncing and it had to do with new email authentication requirements implemented by them in 2024. I found that my own email program (Godaddy) had TWO SPFs in the DNS file, and once I removed the erroneous one, it went through just fine. You might need to look into DMARC and DKIM... The following link might be helpful: https://senders.yahooinc.com/best-practices/#authenticate
Was this answer helpful?

0 comments No comments
Anonymous

2024-03-11T20:32:22+00:00

This did solve my issue, thank you so much! Also for anyone else, when you go to turn this ON it will give you the records to add to your DNS.
Was this answer helpful?

0 comments No comments
Anonymous

2024-03-11T21:58:19+00:00

DMARC record and SPF simply wasn't enough...had clients who had this in place and they started getting rejections last week. DKIM is now needed to send to ATT/Yahoo/Sbcglobal addresses...their guidelines should be updated: https://senders.yahooinc.com/best-practices/
Was this answer helpful?

3 people found this answer helpful.

0 comments No comments
Anonymous

2024-03-12T00:57:17+00:00

Thank you for this information however it would be super helpful if the links that your posted actually explained where to access all these settings within the Admin Center.

This is really pointless information that doesn't help the average person much.

Are you able to explain or provide clear information on this please.
Was this answer helpful?

1 person found this answer helpful.

0 comments No comments

Anonymous

I am experiencing this exact issue with at least one client who has a yahoo.com email address. I am using Microsoft Outlook email via GoDaddy. Please advise of the resolution to this issue asap.

Message headers from the notification email:

3/10/2024 12:40:48 AM - Server at BY5PR12MB4145.namprd12.prod.outlook.com returned '550 5.4.318 Message expired, connection reset (SuspiciousRemoteServerError)(450 4.4.318 Connection was closed abruptly (SuspiciousRemoteServerError))'3/10/2024 12:30:45 AM - Server at 67.195.204.77 (67.195.204.77) returned '450 4.4.318 Connection was closed abruptly (SuspiciousRemoteServerError)'

Original message headers:

Received: from CYXPR12MB9337.namprd12.prod.outlook.com (2603:10b6:930:d8::20)
 by BY5PR12MB4145.namprd12.prod.outlook.com (2603:10b6:a03:212::11) with
 Microsoft SMTP Server (version=TLS1_2,
 cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.7362.33; Sat, 9 Mar
 2024 21:21:10 +0000
Received: from SJ0PR12MB5663.namprd12.prod.outlook.com (2603:10b6:a03:42a::18)
 by CYXPR12MB9337.namprd12.prod.outlook.com (2603:10b6:930:d8::20) with
 Microsoft SMTP Server (version=TLS1_2,
 cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.7362.26; Sat, 9 Mar
 2024 11:39:13 +0000

b=odvgbriKJfvr8VyaP31MQ9rnujGhyjuim0Oys/h0pqBIIdluR+JOOj9fCLgIiyjIMjQ4DUpGu1k3/3ZRrg4NVtO/k4etU1lALWHZd+sCgcnufmM1gVd1p5pLxjg/zGP8UxsNsRrMNWALzU31QgimjjRtT6CKtOFVie7XW3/376twwloAwHQrUHLy3kLm7jT+xp1cL0iyj6wp9V/lIcVs0vrCNsJRVNU/ibwbaoF3Fm9Xo22GXAQU/GfZ9t4TQzjRD7QstYtYIFS+UXIVvdlbeQE9+6VcDnqunS/Xd8jHMggYV9onDqSP/IYfLlAeGjkmINYRStdHwBWD1K0U6Kpdag==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com;
 s=arcselector9901;
 h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-AntiSpam-MessageData-ChunkCount:X-MS-Exchange-AntiSpam-MessageData-0:X-MS-Exchange-AntiSpam-MessageData-1;
 bh=ChRACqoeKcAxCHZmVj3euLGeYsqSOPBTXmitHX+NJdE=;
 b=d7Pb+k6nsM9NSqMlYSropFba4uieAHv/v4SvkN3ztnTYpSUFhA8zUbTZjNGr77fGhzlYY3NQiAtm5ufEGQz2A/jeZY2TRnDDrMzPREMUNfp07erzYr9a3yEU0CAhJon5VKC1R8CMpfM9RrTlJJG+pX/JWAc814FOVyPvLXepIT34LzPDAX4XPAP6vh9sER+lq7DpdvD5bQ9oYzOtxq7H++SpQx+0ssy8hpGu/iMWJ6Fxe1VPD2nVirAT7P+TejhRhkQDog6VGbvZ0+v404Ki8sTPp5EA8Ndrc0STWyI/prbMkj/fgzURr0euKDniVg+hWzDQdk2Az/bhTwbetVEi+A==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass
 smtp.mailfrom=<REDACTED>; dmarc=pass action=none
 header.from=<REDACTED>.com; dkim=pass
 header.d=<REDACTED>; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=NETORG444643.onmicrosoft.com; s=selector2-NETORG444643-onmicrosoft-com;
 h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck;
 bh=ChRACqoeKcAxCHZmVj3euLGeYsqSOPBTXmitHX+NJdE=;

-----------

0 comments