Loading

Marketing Cloud Next - Addressing Email Deliverability Issues with Marketing Cloud Next

发布日期: May 27, 2026
描述

Email deliverability is an assessment of your sending practices and reputation, and it is the key factor that determines if inbox service providers deliver your email to recipient inboxes. Neglecting email sending best practices will result in email deliverability issues. Review the following major areas to ensure you are adhering to best practices when sending email via Marketing Cloud Next.

1) Email Authentication

Set up email authentication methods for your domain (SPF, DKIM, and DMARC) or validate that they are configured properly. 

  • Please reference this knowledge article for additional information on authenticated emails for Marketing Cloud Next. At a high level, Marketing Cloud Next takes care of SPF/DKIM once your domain is authenticated, but you will need to configure their own DMARC record separately (Marketing Cloud Next provides a suggested DMARC record, but work with your IT team to determine the appropriate DMARC record for your organization).

  • Failure to configure one or more of these would lead to deliverability issues. You can review email headers from a Marketing Cloud Next email to confirm all authentication methods pass (see instructions for retrieving email headers for various inbox providers). Alternatively, 3rd-party tools such as aboutmy.email or mail-tester.com can be used for analysis.

2) List Hygiene & Audience Quality

A healthy database contains a growing list of engaged recipients. When your database is clean, you can focus on marketing to the most qualified recipients.

  • Ensure subscribers have opted-in and are engaging regularly. 

  • Consider removing subscribers that have been inactive for over a year.

  • When importing email addresses into Marketing Cloud Next from a different platform, consider only importing email addresses that have never hard bounced/unsubscribed and have had meaningful interactions with your email in the past year. 

    • Sending emails to previously hard bounced email addresses will only harm your domain’s reputation and increase the likelihood of being blocked by inbox service providers (ISPs). Switching marketing platforms will not make these previously bounced email addresses deliverable. 

    • Sending to previously unsubscribed email addresses could increase the potential for spam complaints. 

  • Set reminders to conduct a regular hygiene check-up to protect your sending reputation.

  • Do not use email addresses from a purchased list. 

  • Consider using a confirmed opt-in process for net new recipients/email addresses. 

  • Reminder that harming your sending reputation will eventually impact even your most highly engaged/qualified recipients and potentially prevent you from landing email into their inboxes.

3) Sending Volume

To build a strong sender reputation and maintain reliable email delivery, gradually increase the volume and frequency of your email sends and avoid spikes in email volume. 

 

If you’re using a brand new domain or recently started using Marketing Cloud, your domain is not immediately recognized by inbox service providers (ISPs) and starts with a reputation of zero/unknown. ISPs are increasingly prioritizing domain reputation in addition to IP reputation. 

 

Warm up your domain by sending a small number of emails first to your most engaged subscribers. You can use the domain warming schedule outlined in this knowledge article. 

4) Content & Formatting Issues

  • Include a prominent unsubscribe link that makes opting out easy. Avoid hiding unsubscribe functions behind a login.

  • Mail testing tools (such as mail-tester.com) can give content optimization hints.

  • Include a physical contact address to comply with the CAN-SPAM law where applicable.

解决方案

Below are common bounce codes/reasons and potential resolution steps for Marketing Cloud Next. For other bounce codes not listed here, typically many third party resources can be used to look-up bounce codes and potential resolution steps. If you are looking for overall information on how Marketing Cloud Next handles email bounces, check out the linked knowledge article (Marketing Cloud Next - Email Bounce Management). 

4.4.7 (delivery time expired)

Validate Impact

  • This bounce is generated by Salesforce’s servers after Marketing Cloud Next has exhausted all retries for an email that received a soft bounce from receiving servers.

  • Seeing a large spike in the 4.4.7 (delivery time expired) bounce sometimes indicates that there was a recent spike in daily sending volume and receiving ISPs are sending back deferrals as a warning sign that you’ve sent too much email within a short period of time. 

  • You can validate your sending pattern a number of ways in Marketing Cloud Next. If you see any large email spikes that correspond to the time period where you’ve seen a large spike in the 4.4.7 (delivery time expired) bounces, that indicates that you’ve seent

    • Marketing Performance Dashboard - Deliverability Dashboard

      • Go to the Email Sends widget and use the dropdown to Open the metric.

      • This will display cumulative email sends over time. You can look for single day jumps that are larger than your typical daily average sending volume. 

    • Total Email Activities (OOTB report)

      • Turn off Detail Rows. 

      • This will display Sum of is Sent which represents daily email send volume over time. 

    • Query Editor using the below query to group SENT emails by calendar date and looking back the past 30 days. 

    • SELECT CAST("ssot__EngagementDateTm__c" AS DATE),count(*) FROM "ssot__EmailEngagement__dlm" where "ssot__DataSourceId__c" like 'MessagingEvents%' AND "ssot__EmailRecipientSendStatus__c"='SENT' AND ssot__EngagementDateTm__c >= CURRENT_TIMESTAMP - INTERVAL '30' DAY GROUP BY CAST("ssot__EngagementDateTm__c" AS DATE) order by CAST("ssot__EngagementDateTm__c" AS DATE) ASC LIMIT 100

  • You may also see other deferral bounces logged in your Email Engagement DMO and showing in your common bounce reasons in your Marketing Performance dashboard. Below is a sample, non-exhaustive list:

    • 4.7.650 The mail server [###.###.###.#] has been temporarily rate limited due to IP reputation.

    • 4.7.0 [TSS04] Messages from  [###.###.###.#] temporarily deferred due to unexpected volume or user complaints.

Resolution Steps

  • Start by reducing your daily send volume back down to the last known daily volume that did not result in a spike in bounces. 

  • Once that lower daily volume of email no longer triggers 4.4.7 (delivery time expired) bounces, continue to ramp up sending volume by following the guidelines in Marketing Cloud Next Domain Warming knowledge article.

5.7.1 Unfortunately, messages from [###.###.###.#] weren't sent

Validation

  • This is a common hard bounce code from Microsoft email servers.

  • This type of bounce is a symptom of not following email sending best practices, and is not the cause of deliverability issues. Microsoft evaluates senders based on more than just the sending IP. If the underlying sending behavior is not changed, the bounces are likely to happen again even if Microsoft chooses to unblock the IP address

Resolution Steps

  • Verify your emails are being authenticated properly (see Email Authentication section above).

  • Verify your sending volume hasn’t spiked recently (see List Hygiene & Audience Quality section above).

  • Verify your list hygiene to ensure you aren’t sending to stale recipients (see List Hygiene & Audience Quality section above).

  • If this persists, open a support case with Marketing Cloud Next support. 

Out of Storage

Validation 

You may see bounces like the following:

  • 5.2.2 <<email_address>>: user is over quota

  • 4.2.2 The recipient's inbox is out of storage space. 

  • 5.2.2 The recipient's inbox is out of storage space and inactive. 

Resolution/Next Steps

Start by analyzing your list/database hygiene as described above (see List Hygiene & Audience Quality section above). A full mailbox is usually from infrequent use, a temporary change in email checking habits, or an address change. Mailbox full errors are a warning sign. Having a large number of these can indicate that your database needs cleanup to remove older addresses. 

Unknown Domain/User

Validation 

You may see bounces like the following:

  • 5.1.1 The email account that you tried to reach does not exist. Please try double-checking the recipient's email address for typos.

Resolution/Next Steps

Start by analyzing your list/database hygiene as described above (see List Hygiene & Audience Quality section above). Industry statistics indicate that up to 33% of email addresses become invalid over 12 months. Receiving the User Unknown error indicates that the address is no longer active or has never been an active email address. Because of the high turnover rate of email addresses, sending to recipients regularly decreases the possibility of a sudden spike on a specific campaign. If mailing to an old list, we recommend sending a random 10% test to avoid a sudden increase in bounces. This error could also be the result of poor data capture methods. If so, we recommend requiring subscribers to enter their email address twice

其他资源

Note: some of these resources may reference other Marketing Cloud products (such as Marketing Cloud Engagement or Marketing Cloud Account Engagement). The content is relevant because email deliverability best practices are applicable to any email platforms. 

知识文章编号

005225012

 
正在加载
Salesforce Help | Article