Emails keep bouncing back

Question

Hello,

Certain email accounts keep bouncing back to us. Some are going through, and some are not. We receive this message every time:

Delivery has failed to these recipients or groups:

CONTACT ******@yahoo.com
Your message couldn't be delivered. Despite repeated attempts to contact the recipient's email system it didn't respond.

Contact the recipient by some other means (by phone, for example) and ask them to tell their email admin that it appears that their email system isn't accepting connection requests from your 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 more information and tips to fix this issue see this article: https://go.microsoft.com/fwlink/?LinkId=389361.

Diagnostic information for administrators:

Generating server: CH3PR10MB7283.namprd10.prod.outlook.com
Total retry attempts: 4

******@yahoo.com
Remote server returned '550 5.4.300 Message expired -> 451 This mail has been deferred because the sender is sending too much mail for its authentication status. Please set up DKIM aligned to the From: domain. See https://senders.yahooinc.com/smtp-error-codes#authentication-failures for more information.'

Original message headers:

Received: from DS7PR10MB5039.namprd10.prod.outlook.com (2603:10b6:5:3a6::16)
 by CH3PR10MB7283.namprd10.prod.outlook.com (2603:10b6:610:12f::17) with
 Microsoft SMTP Server (version=TLS1_2,
 cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.7409.46; Tue, 2 Apr
 2024 16:34:38 +0000
Authentication-Results: dkim=none (message not signed)
 header.d=none;dmarc=none action=none header.from=projectdancestudio.com;
Received: from BL3PR10MB6017.namprd10.prod.outlook.com (2603:10b6:208:3b0::16)
 by DS7PR10MB5039.namprd10.prod.outlook.com (2603:10b6:5:3a6::16) with
 Microsoft SMTP Server (version=TLS1_2,
 cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.7409.46; Tue, 2 Apr
 2024 05:24:55 +0000
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none;
 b=fDESW3AvXagCEKCSYwmzzqBhqlCpEnlZj+WyvWD6e7QQSHiROR+63YFYVsr2jKRldcHhU93/FJgDdqBOohkwpP+D/yM5B6e2BZVe5Is0T+LzTCzX0zqGgv9JTi6w/R5OVtot6euL6RvMO37mOFGE7H5meCzbs0SEI6efT1Agc5VFCtMF4V+dM1OLA3GSPW2/8X5B84wOf9BQK6tUk8vsPCkJKNVmW5i5AFBwnzRgsvc4xvCdEyqlUjNxI3v1YPaHbMNsUdQe8osN0XwsKaG0B70//BAAmbgKEWWAcWR7z4vHi7+8vmct7AWJxGQM7vMuVkU1QyXvhCgk1BrpwFDHvA==
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=oH70LNZogUqTpaD+FqHKD22ZYt0oGej1fHKqty5mncE=;
 b=fdxZn1AfC+TcUhvZ3j75cwNUuIZzalhWZygigB/UjCOJ7Rarcx52EDrvjg4nxiYCVDy2sFDHkossKDLovsmkH2i1Mz28Dan8xpsV4elS05bQbkCuKrrbITGfOtT+q69TPaWRnWacNejGCQkIgXiKLDVmRpjHAl68mXTgyMblxEZrhzkedw4Qz33Tg9CuM7FiAaKczWgiS+z/pwwTLTnOH3aLzdDDG6OkERckGAi2s8v5gG5AwP1plYPR1OIlD5FUZvIehVWkFgxHaZZkgoxmJQNnXVhkBHocxY5DprEb/G+CVH7wtb4SBc8Wl+RNpz5x4zR9cUl7/xdGhh1XZjyDmA==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass
 smtp.mailfrom=projectdancestudio.com; dmarc=pass action=none
 header.from=projectdancestudio.com; dkim=pass
 header.d=projectdancestudio.com; arc=none
Received: from BL0PR10MB3441.namprd10.prod.outlook.com (2603:10b6:208:7f::11)
 by BL3PR10MB6017.namprd10.prod.outlook.com (2603:10b6:208:3b0::16) with
 Microsoft SMTP Server (version=TLS1_2,
 cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.7409.46; Mon, 1 Apr
 2024 18:16:56 +0000
Received: from BL0PR10MB3441.namprd10.prod.outlook.com
 ([fe80::2682:bbf2:c070:8e9b]) by BL0PR10MB3441.namprd10.prod.outlook.com
 ([fe80::2682:bbf2:c070:8e9b%5]) with mapi id 15.20.7409.042; Mon, 1 Apr 2024
 18:16:53 +0000

Answer 1

Read this:

https://techcommunity.microsoft.com/t5/exchange-team-blog/authenticate-outbound-email-to-improve-deliverability/ba-p/3947623

Unfortunately many don't understand the problem and choose to wait for a fix that no one can fix except themselves. If you have an IT personnel, forward the above link to them.

Answer 2

Dear Project Dance,

Good day! Thank you for posting to Microsoft Community. We are happy to help you.

Based on your description, I understand that you are experiencing issues with not able send emails to yahoo accounts.

This is a known issue as you said that customer support told you that they reported the issue, it was formerly a service incident but has been fixed. However, for users who are still experiencing issue sending to yahoo and AOL, this is what Yahoo/AOL gave as fix, refer to Authenticate Outbound Email to Improve Deliverability - Microsoft Community Hub.:

Google and Yahoo have announced that starting in February 2024 they will be implementing stricter measures about how emails are sent. As such, you will need to take action to ensure you don’t lose the ability to send emails to anyone with a Google or Yahoo email address.

• What does this mean for you?
  If you don’t take the steps (outlined below) to authenticate your email domain before early February, your business will lose the ability to send emails (including those via MyCRM) to anyone with a Gmail and/or Yahoo account. This means your client emails will be impacted.
• What do I need to do?

1. Tell your IT expert about these new rules from Google and Yahoo (the details are in step 2).
2. Change some of the settings for your email (your IT expert will ensure that your DNS configuration for your domain(s) includes the following
   [replace yourdomain.com with your domain name]
   1. Email Authentication:
      CNAME mte1._domainkey.yourdomain.com dkim1.mandrillapp.com
      CNAME mte2._domainkey.yourdomain.com dkim2.mandrillapp.com
3. DMARC Record:

If you have an existing record for _dmarc.yourdomain.com leave it as is.
If there is no _dmarc.yourdomain.com record, add the following record: 
TXT.  _dmarc.yourdomain.com  v=DMARC1; p=none  

1. SPF Record:

If there is already a TXT for the root domain (e.g. yourdomain.com) that contains the v=spf1 value, simply add the “include:sendgrid.net  include:spf.mandrillapp.com” values to the existing record. For example:
 
Existing record:
"v=spf1 mx include:_spf.google.com include:example.com ip4:xxx.xxx.xxx.xxx ~all"
 
Update to:
"v=spf1 mx include:_spf.google.cominclude:example.com include:sendgrid.net  include:spf.mandrillapp.com  ip4:xxx.xxx.xxx.xxx ~all"
 
(please note the "include:sendgrid.net include:spf.mandrillapp.com " in bold is an insertion into your existing SPF record)
 
If there is no existing record:
Add the following record to your DNS.
TXT       yourdomain.com v=spf1 include:sendgrid.netinclude:spf.mandrillapp.com ~all 
  I hope this fixes your issue. Please let me know if you need further assistance from my end. I will try my best to assist you.