HubSpot emails going to spam: identify the sending route first
Start with the HubSpot tool that sent the message. Marketing email and sales email sent through a connected inbox can use different networks and authentication. A change in marketing-domain settings may do nothing for an affected sales sequence.
- Why can email from HubSpot reach spam?
- The outcome depends on the actual sender, authentication, recipient expectations, message content and receiving controls. “Sent from HubSpot” identifies the interface, but not enough of the delivery path to diagnose the problem.
1. Identify the tool and sending network
HubSpot documents the distinction in its email sending overview (opens in a new tab). Verify which route the affected message actually used.
| Message type | Sending route | Start with |
|---|---|---|
| Marketing email, including automated marketing email | HubSpot’s email sending network. | Marketing-email results and the relevant sending-domain setup. |
| One-to-one or sequence email using a connected inbox | The connected mailbox provider’s network. | The connected account, provider logs and received message. |
2. Describe the actual failure
Record the HubSpot tool, sending account, visible From address, recipient, timestamp with time zone and message ID where available. Ask whether the message was not sent, rejected, accepted and then found in spam, or simply not answered. These require different next steps.
For marketing email, HubSpot explains that delivered records acceptance by the receiving provider. It does not report the final inbox folder. Use recipient evidence where possible and read our guide to delivered email missing from the inbox.
Keep a small set of comparable examples rather than collecting unrelated screenshots. Include the exact campaign or sequence version and recent changes. A report saying “HubSpot deliverability is bad” leaves both the responsible system and the observed symptom unclear.
3. For marketing email, verify the selected sending domain
Check that the sending identity in the email matches the intended configuration. Follow HubSpot’s current domain-authentication setup (opens in a new tab) and the records generated for your account. Review the status of DKIM, SPF and DMARC rather than copying another organisation’s DNS values.
An administrator should check existing records and other legitimate senders before applying changes. Where an SPF update is required, HubSpot instructs users to update the existing record rather than create a second one. A completed setup screen should then be checked against a message sent through that route.
Also distinguish verification of a From address from connecting an email sending domain. HubSpot describes these separately in its From-address verification guidance (opens in a new tab). Knowing that you can receive a verification email is not the same check as validating the authentication used on a sent message.
4. For connected-inbox email, investigate the mailbox route
Identify the mailbox provider and account connected to the salesperson’s HubSpot user. Compare a permitted direct send from that mailbox with a send through the affected HubSpot tool. Keep the test purpose clear and use agreed test recipients.
Record differences in the template, signature, links and received authentication. Ask the mailbox administrator to match the test to available sending logs and any restriction or error. A CRM connection that can authenticate to an account does not establish that every attempted send completes.
Use the Microsoft 365 investigation guide or Google Workspace investigation guide for the relevant provider. Keep recipient-side policy decisions separate from sender-side account problems.
5. Review recipient expectations and message changes
Authentication does not make every contact suitable for a marketing campaign. HubSpot’s opt-in consent guidance (opens in a new tab) sets requirements for marketing email. Check the source, permission and subscription context before treating a prospect list as a marketing audience.
Review what changed around the affected period: audience source, sender name, offer, links, attachments, tracking or frequency. A list that was valid at import can still contain people who do not expect the message. Do not answer a complaint pattern by merely changing the sending identity.
For an investigation, compare a specific hypothesis. If a tracked template appears to behave differently, agree a controlled comparison rather than removing every link, replacing the domain and changing the audience in one attempt. That would make the result difficult to interpret.
Give each team a question it can answer
| Owner | Question | Useful evidence |
|---|---|---|
| HubSpot administrator | Which tool, account and message version produced this email? | Campaign or sequence reference, recipient result and configuration history. |
| DNS or mail administrator | Did this actual route authenticate and complete its send? | Applicable configuration, received authentication and provider logs. |
| Marketing or sales owner | Why was the recipient included and what changed? | Audience source, relevant permission records, message and cadence history. |
| Receiving administrator, where available | What happened after the message arrived? | Observed folder or quarantine outcome and applicable filtering evidence. |
Verify the correction without overstating the result
Write down the proposed change, the person approving it and the observation that would support success. Repeat the relevant comparison after implementation, preserving the original message references.
A corrected DKIM result proves something different from a message reaching an agreed test inbox. Record both accurately and state the coverage. Neither one establishes future placement for the entire audience.
If the technical evidence is healthy but enquiries are being lost after replies arrive, investigate the handover instead. Our reply-handling guide covers routing, stopping sequences and assigning follow-up.
When the problem crosses HubSpot, IT and sales
Neotiqa can bring the evidence from these teams into one deliverability assessment, with a prioritised plan and clear ownership. If the problem is CRM routing or a broken hand-off, GTM engineering can address the workflow under a separate agreed scope.
Start the conversation with the tool you use, the observed symptom and the teams involved. We can agree a secure process for message evidence later. No passwords, contact exports or confidential email threads are needed in the initial enquiry.
Questions about HubSpot email delivery
Will authenticating our marketing domain fix sales sequence emails?
Not by itself. A sequence using a connected inbox sends through that mailbox provider. Verify the affected route before changing the configuration for a different one.
Why does HubSpot say delivered when the recipient found spam?
For marketing email, delivered reflects acceptance by the receiving provider. The recipient’s system can then place it outside the inbox. Received evidence is needed to investigate that outcome.
Does this mean we need to replace HubSpot?
The symptom alone does not establish that. Identify the sending route, configuration, audience and recipient decision first. An application change may not address the cause.
Connect the CRM evidence with the email evidence.
Tell us whether the issue affects marketing email, sequences or one-to-one messages. We can help define the investigation and the people needed to resolve it.