Salesforce emails going to spam or not arriving: find the sending route
An email written in Salesforce may leave through Salesforce, a connected Microsoft 365 or Gmail account, or an email relay. Start with the feature and account used for one affected message. The right investigation depends on that route, not just the Salesforce screen where someone clicked Send.
- Why are Salesforce emails going to spam?
- Possible causes include authentication on the actual sending route, message and link characteristics, sending behaviour and the recipient’s filtering policies. A missing message may instead have failed before it left the application. Identify the route, match the message to its sending record and establish whether it was never sent, rejected or received in spam before changing settings.
1. Establish what happened to one message
| Observed outcome | Useful first check | Owner to involve |
|---|---|---|
| The user sees a sending error or the automation did not run | Keep the exact error and identify the action, user and record involved. Check application access, verification and automation execution. | Salesforce administrator or the owner of the automation |
| A bounce or non-delivery report is available | Retain the complete error, time and recipient. Identify the system that rejected the attempt. | The administrator of the sending route |
| The recipient finds the original message in junk or quarantine | Obtain its received headers and the filtering verdict where available through an agreed process. | The recipient’s administrator, with the sender’s administrator |
| Salesforce records activity but the recipient cannot find the email | Confirm the destination address and actual sending event. An activity record alone does not establish inbox placement. | The Salesforce owner and mail administrator together |
2. Identify which service actually sent it
Salesforce describes these options in its Send Email Through Salesforce guidance (opens in a new tab). Verify the affected feature and user configuration rather than assuming that the whole organisation uses one route.
| Route or message type | Where to start | Important distinction |
|---|---|---|
| Email sent through Salesforce’s infrastructure | Salesforce sending configuration and email logs, followed by received headers or the bounce. | The visible company address does not mean Microsoft 365 or Google sent it. |
| Individual email using Send through Gmail or Office 365 | The connected account and that provider’s delivery evidence. | Salesforce email logs do not provide delivery details for messages sent through these external services. |
| Automated email, such as workflow or trigger email | The specific automation and its sending route, including Salesforce logs where applicable. | Connecting a user’s Gmail or Microsoft 365 account does not move every automated message onto that account. |
| Salesforce Email Relay | Salesforce’s handoff and the relay server’s acceptance, routing and delivery records. | A successful relay handoff is only one stage of delivery. |
This guide concerns email from the Salesforce CRM routes above. Marketing Cloud, Account Engagement and third-party sales tools can have their own sending infrastructure and controls. Name the product and feature when asking for help so that its administrator can follow the appropriate configuration.
3. Build an evidence record both teams can use
Identify the sending action
- Salesforce product and feature, affected user and the action or automation that sent it
- Visible From address, connected account or relay where applicable, and the actual destination
- Sending timestamp and time zone, message identifier where available, and the exact error or observed outcome
Match the message across systems
- Application sending event and the appropriate Salesforce, Microsoft, Google or relay log
- Original received headers for a junked example, obtained with the recipient’s agreement
- One comparable successful example and a note of changes to connections, domains, templates or routing
Match records using the time, sender, recipient and identifiers that each system provides. Keep a record of which log was searched and its coverage. An empty search in the wrong provider is not evidence that the message was never sent. Our annotated email-header walkthrough explains how to connect the received evidence to a sending service.
Collect Salesforce logs promptly. Its email-log limits (opens in a new tab) allow requests for the preceding 30 days, with no more than seven days in one request. These investigation logs are not an audit record. Connected-provider sends need the provider’s logs instead.
4. When Salesforce is the sender, check access and authentication
Have the Salesforce administrator check whether the affected feature is permitted to send and whether the required sender and domain verification is complete. Salesforce’s sending-verification requirements (opens in a new tab) distinguish user or address verification from domain verification, with domain-level verification exceptions for particular routes such as connected Gmail and Office 365.
For applicable Salesforce-origin mail, domain verification can use an active DKIM key or a verified Authorized Email Domains entry. Verifying an organisation-wide address does not independently verify its domain. These checks establish permission to use a sender identity, not where the recipient will place a message.
For mail using your domain through Salesforce, review its supported DKIM configuration (opens in a new tab). Creating a key, publishing the generated DNS records and activating the key are separate steps. The authorised administrators should use your organisation’s actual values and inspect a message from the affected route after an approved change.
Check the signing domain, visible From domain and reported authentication results together. Do not copy an SPF string from another organisation, add a second SPF record or assume that every Salesforce product uses the same setup. An authentication change must preserve the other legitimate services sending for the domain.
If authentication passes, continue with the actual outcome and recipient evidence. Passing SPF, DKIM or DMARC does not guarantee inbox placement. The deliverability audit checklist sets out the wider evidence to collect.
5. When a connected mailbox sends it, use that provider’s evidence
Confirm which account is connected to the affected Salesforce user and whether its connection is still authorised. Then ask the mail administrator for the provider’s record of the exact send. Salesforce’s documentation directs administrators to Gmail or Office 365 logs for messages sent through those services.
Compare an agreed test sent directly from the mailbox with one sent through the affected Salesforce feature. Keep the recipient and purpose comparable, and record differences in template, signature, attachments and tracking. A successful direct message narrows the question but does not prove that the application connection or its content is correct.
For a Microsoft route, use our Microsoft 365 spam investigation. If the message instead returns 550 5.1.8, follow the restricted-sender guide. For Google-hosted sending, see the Google Workspace delivery guide. Changing Salesforce’s own DKIM setup will not repair an unrelated restriction on a connected mailbox.
6. When Email Relay is enabled, trace both sides of the handoff
Ask the Salesforce and mail administrators to confirm the relay destination, matching sender-domain rules and supported connection requirements. Correlate Salesforce’s attempt with the relay’s receipt or rejection, then follow the message onward. A failure before relay acceptance belongs at a different point from junk placement after delivery.
Check support for the proposed route before altering connectors. Salesforce’s Office 365 relay guidance (opens in a new tab) states that direct relay from Salesforce through Exchange Online to external recipients is not supported. This is distinct from the user-level Send through Office 365 feature.
Do not treat an open relay, broad filtering bypass or disabling authentication as a troubleshooting shortcut. Work with the administrators to identify a supported route and verify it with controlled messages. Retain the original error so that a routing limitation is not mistaken for a domain-reputation problem.
Illustrative example: a personal reply arrives but an automated follow-up does not
A fictional software team connects a salesperson’s Microsoft 365 account to Salesforce. The salesperson’s individual reply arrives, but an automated follow-up appears to go missing. The team initially asks IT to change the mailbox’s spam settings.
First confirm the route of each message. If the reply used Microsoft 365 and the automation used Salesforce infrastructure, the successful reply did not test the automated route. Look for the automation’s event and Salesforce sending record, then establish whether that attempt failed, was rejected or reached the recipient.
If the recipient supplies the original automated message from junk, compare its authentication and filtering evidence with a successful message from the same automated route. Only then decide whether a configuration, content or receiving-side correction is justified. These are hypothetical branches, not results from a client engagement.
The useful handover
- Two message types, each with its actual route
- An observed outcome for each affected example
- The logs or received evidence supporting it
- A named owner and a test for the next change
When should Salesforce and email specialists work together?
Bring the teams together when the issue repeatedly crosses application settings, mailbox administration and recipient filtering, or when each provider can confirm only its own part of the journey. One bounced address or an automation that never ran may be resolved directly by the responsible administrator.
Neotiqa’s email deliverability assessment maps the sending routes, compares message evidence and provides findings with a technical handover. The initial assessment is read-only. Any implementation is scoped separately with the relevant system owners. For account ownership, stop conditions or reply-routing work, explore GTM engineering.
This coordination is particularly relevant to B2B SaaS sales teams and treasury and payments software vendors using several sales systems. We can also work alongside IT services providers and MSPs. The scope follows the actual tools and messages involved.
Questions about Salesforce email delivery
Why does Outlook email arrive when Salesforce email goes to spam?
The messages may use different sending infrastructure, identities, templates or links. Identify the Salesforce feature and actual sending route first, then compare suitable examples. A successful Outlook message does not test every Salesforce route.
Does connecting Microsoft 365 make every Salesforce email use Microsoft?
No. Individual email can use a connected account while automated messages such as workflow or trigger email still use Salesforce infrastructure. Confirm the behaviour of the affected feature instead of assuming one route for the organisation.
Why is a Salesforce message missing from Salesforce email logs?
Messages sent through connected Gmail or Office 365 use those providers’ delivery logs. Also check the time range, time zone, user, feature and whether the sending action occurred. A missing log entry alone is not an explanation of the failure.
Will configuring DKIM guarantee Salesforce emails reach the inbox?
No. DKIM is one part of authenticating a sending identity. The recipient can still filter a message based on other signals or policies. Verify the actual message’s authentication and its observed delivery outcome.
What should we include in an initial enquiry?
Tell us the Salesforce product and feature, mailbox provider or relay, observed symptom and when it began. Keep credentials, customer records and original message samples out of the public form. We agree the evidence needed and how it will be shared when scoping the work.
Connect your Salesforce and email evidence.
Tell us which Salesforce messages are affected and how your team sends them. We can discuss a focused investigation with your CRM and IT owners.