Outbound Wiki

Article

Email bounce categories - Dynamics 365 Customer Insights

learn.microsoft.com

Open at publisher

Quoted on this wiki

Every place a page here uses this source, in the order the words come in it.

  1. Triggering anti-spam, anti-virus, or anti-phishing software on the recipient side. We monitor cases related to not trusted domains and IP addresses on a daily basis and remove blocks if they appear, as well as analyze the email flow to avoid further issues. relaying-issues – This category represents errors from recipient servers that don't allow incoming email flow from the outside. This category also can mean that there's a misconfiguration of the DNS records on the recipient side, such as DNS records that point to a server that doesn't host email addresses for that domain. Relaying-issues errors can be transient. Recipients shouldn't immediately be excluded from the contact list. But, if the error results from the same contact multiple times, it is recommended to exclude the contact.

    In Blocklist monitoring

  2. Bounce category definitions The first two categories – invalid-mailbox and invalid-domain – are known as “hard bounces.” inactive-mailbox – This is closely related to the invalid-mailbox category. The inactive-mailbox category indicates that the recipient’s address is disabled, abandoned, or no longer exists on the recipient’s server. In most cases, inactive-mailbox addresses should be excluded from sending, as they rarely become active again.

    In Bounce types and SMTP codes

  3. The first two categories – invalid-mailbox and invalid-domain – are known as “hard bounces.” A hard bounce is an email that has been sent to an invalid mailbox or an invalid domain. This means that the recipient’s email address or the domain doesn't exist. The inactive-mailbox category indicates that the recipient’s address is disabled, abandoned, or no longer exists on the recipient’s server. full-mailbox – This category results from addresses that can't receive email messages due to lack of storage or limits on the number of emails received. In most cases, a full mailbox means that the recipient’s mailbox is abandoned or not being read regularly. This category isn't a hard bounce, but if the error appears for a contact on a regular basis, the contact isn't likely to receive future email messages.

    In Bounce types and SMTP codes

  4. To identify the cause of bounced campaign emails, Dynamics 365 Customer Insights - Journeys includes a bounce categorization feature. The bounce categorization feature groups typical bounce errors into bounce categories. Each category represents a type and reason for bounced emails. Here is the list of bounce categories we use: recipient-server-error Bounce category definitions

    In Bounce types and SMTP codes

  5. Multiple complaints from recipients. A spamtrap is an email address that is intentionally used to identify spammers. Triggering anti-spam, anti-virus, or anti-phishing software on the recipient side.

    In Email risk classification

  6. Bounce category definitions The first two categories – invalid-mailbox and invalid-domain – are known as “hard bounces.” inactive-mailbox – This is closely related to the invalid-mailbox category. The inactive-mailbox category indicates that the recipient’s address is disabled, abandoned, or no longer exists on the recipient’s server. In most cases, inactive-mailbox addresses should be excluded from sending, as they rarely become active again.

    In Hard-bounce suppression

  7. The first two categories – invalid-mailbox and invalid-domain – are known as “hard bounces.” A hard bounce is an email that has been sent to an invalid mailbox or an invalid domain. This means that the recipient’s email address or the domain doesn't exist. The inactive-mailbox category indicates that the recipient’s address is disabled, abandoned, or no longer exists on the recipient’s server. full-mailbox – This category results from addresses that can't receive email messages due to lack of storage or limits on the number of emails received. In most cases, a full mailbox means that the recipient’s mailbox is abandoned or not being read regularly. This category isn't a hard bounce, but if the error appears for a contact on a regular basis, the contact isn't likely to receive future email messages.

    In Hard-bounce suppression

  8. Multiple complaints from recipients. Senders that send emails to these addresses are automatically identified as spammers on the recipient server side. Triggering anti-spam, anti-virus, or anti-phishing software on the recipient side.

    In Inbox placement and spam filters

  9. inactive-mailbox – This is closely related to the invalid-mailbox category. The inactive-mailbox category indicates that the recipient’s address is disabled, abandoned, or no longer exists on the recipient’s server. In most cases, inactive-mailbox addresses should be excluded from sending, as they rarely become active again. This category results from addresses that can't receive email messages due to lack of storage or limits on the number of emails received. dmarc-issues – This category stands for errors closely related to a recipient's or sender's DMARC (Domain-based Message Authentication, Reporting, and Conformance) or other internal policies related to domain authentication such as SPF (Sender Policy Framework) record checks or DKIM (DomainKeys Identified Mail) signature checks. Such errors can result if the recipient's server doesn't allow emails from domains without a valid SPF record or DKIM signature. dmarc-issues errors can also result if there's mismatched sending domain alignment to the SPF record or DKIM signature in the email. Extensive dmarc-issues errors could mean that the sending domain is misconfigured or that the sending domain doesn't fill the requirements for acceptable email delivery. This category of issues usually requires additional investigation. If you run into this kind of issue, open a support ticket.

    In Mailbox and SMTP verification

  10. Multiple complaints from recipients. Senders that send emails to these addresses are automatically identified as spammers on the recipient server side. Triggering anti-spam, anti-virus, or anti-phishing software on the recipient side.

    In Sender reputation