A bounce message is also called a Non-Delivery Report/Receipt (NDR). It's an automated message from the recipient's email server with details about the specific problem with the email delivery. Complete details about the bounce type and server response are available in the Recipients tab of sent marketing emails.
When contacts hard bounce on a marketing email, HubSpot drops them as recipients of future marketing emails. This protects your email sending reputation by preventing future bounces. If any valid contacts bounce on marketing emails, there's likely a security filter blocking the incoming message.
To resolve the problem:
For emails sent through a connected inbox, bounce details are available in the email engagement on the contact timeline. A bounce for a one-to-one sales email sent from HubSpot CRM will display less information than a marketing email because it's sent through a connected inbox. You'll receive a bounceback email with the full bounce response in your own inbox.
Please note:
You can view why a contact hard bounced in the Recipients tab of one of your sent emails.
Content: something in the email body or subject triggered spam filters. To solve the problem, ask the contact to whitelist your sending IP addresses, then unbounce the contact in HubSpot. Learn more about spam trigger words.
Spam: something in the body, subject, or From address of the email that is classified as spam by the recipient's email server. To solve the problem, ask the contact to whitelist your sending IP addresses, then unbounce the contact in HubSpot.
Policy: the email did not pass one of the security policies of the recipient's server, but it is not explicit about which one. This includes DMARC; DKIM, and SPF authentication failures. To solve the problem, ask the contact to whitelist your sending IP addresses, then unbounce the contact in HubSpot.
Other: the response from the recipient's email server wasn't specific enough to categorize the bounce. To solve the problem, ask the contact to whitelist your sending IP addresses, then unbounce the contact in HubSpot.
Temporary technical issue with the recipient's email: the recipient's server may be overloaded, timing out, or undergoing some configuration changes that prevented it from accepting the message. Create a clone of the original email and send it to the affected contacts at a later date. For a one-to-one sales email, try sending your message again at a later date.
Rejected by recipient's email security filter: there's a temporary problem with the recipient's server or HubSpot's sending IP addresses. To solve the problem, ask the contact to whitelist your sending IP addresses. Then create a clone of the original email and send it to the affected contacts at a later date. For a one-to-one sales email, try sending your message again at a later date.
Your IT team has not authorized HubSpot to send emails on your behalf: your IT team set up a custom DMARC policy that needs to be updated to include HubSpot. Reach out to your IT team to send them documentation about using a DMARC policy with HubSpot.
Temporary technical issue: there may have been a temporary technical problem with the recipient's email server or HubSpot's email server. Create a clone of the original email and send it to the affected contacts at a later date. For a one-to-one sales email, try sending your message again at a later date.