A mailbox provider can accept a message and still put it in spam. In Mailgun’s State of Email Deliverability 2025 survey, only 12.3% of respondents correctly identified what delivery rate measures. If you need to know how to avoid emails going to spam, this guide gives you a practical way to identify the scope of the issue and fix likely causes without changing your whole email system at once.
To avoid spam placement, first determine whether the problem affects one recipient, one provider, or many recipients. Compare send, bounce, complaint, and engagement signals, then check authentication and sender reputation. Next, review consent, contact quality, sending patterns, and message relevance. Change one likely cause at a time and measure the result; no sender-side practice guarantees inbox placement.
First, find out whether your emails are actually going to spam
Start by mapping the problem. Ask affected users which mailbox provider they use, whether the message is in spam or missing entirely, and when they last received one successfully. A password reset missing for one Gmail user points to a different investigation than a campaign missing for customers across Gmail and Outlook.
Test with accounts at multiple providers. Send the same representative message—not only a plain test email—to accounts you control, and record whether it arrives in the inbox, spam, or nowhere visible. Repeat for each affected message type. A receipt, password reset, and promotional campaign may use different templates, sending paths, recipient groups, and expectations.
Check your sending system’s event data before rewriting copy. Compare accepted messages, bounces, rejections, complaints, unsubscribes, and engagement with your own previous results. Mailgun’s survey explains an important distinction: delivery rate measures messages accepted by receiving servers, including messages that may have landed in spam. Acceptance alone does not tell you where a message was placed.
Read the signals together
A bounce means a receiving server did not accept a message; it is not a spam-placement measure. If acceptance remains steady while complaints rise, engagement falls, or users report filtering, investigate placement and audience expectations. If only one recipient reports a problem while other accounts receive the same message, check for an individual filter, block, or contact-record issue before changing your sending setup.
Gmail Postmaster Tools provides dashboards for eligible Gmail traffic, including spam-rate and domain- and IP-reputation information. Google explains that dashboard data can be limited or unavailable when there is not enough eligible traffic, so an empty dashboard is not a clean bill of health. Its spam-rate data also does not reveal every message Gmail automatically routed to spam; it reflects messages users marked as spam. See Google’s Postmaster Tools dashboard documentation.
Do not begin by swapping words in a subject line. First identify the affected recipients, providers, and message streams. That gives you a baseline and helps separate a recipient-side preference from a sender-wide deliverability issue.
Why legitimate emails land in spam
Mailbox providers weigh multiple signals. A legitimate purpose—such as sending a receipt or account alert—does not override missing authentication, weak domain or sending IP reputation, recipient complaints, or a history of messages people ignore. Providers operate their own filtering systems, and the importance of each signal can vary by recipient and time.
Common causes include:
- Authentication problems: SPF or DKIM is missing, misconfigured, or fails to align with the domain in the visible From address.
- Reputation damage: Your sending domain or IP has a history of unwanted mail, complaints, or abrupt volume changes.
- Unwanted recipients: People did not knowingly subscribe, addresses are old or invalid, or the content no longer matches what they expect.
- Weak engagement: Recipients regularly ignore, delete, or report messages, which can be a sign that the mail is not wanted.
- Inconsistent sending: A long quiet period followed by a large burst differs from the stream’s previous pattern.
- Message mismatch: The sender name, subject, or content does not match the recipient’s expectation.
These causes can compound one another. An old newsletter list can generate complaints; complaints can weaken reputation; and weaker reputation can make subsequent messages more likely to be filtered. A template change cannot resolve a consent problem. Authentication establishes facts about the sending identity, not whether the recipient wants the message.
Google’s sender guidelines set requirements for mail sent to Gmail. For example, senders that send more than 5,000 messages per day to personal Gmail accounts have additional requirements, including SPF, DKIM, DMARC, alignment, and one-click unsubscribe for marketing and subscribed messages. Read the Gmail sender guidelines before building a high-volume Gmail stream; meeting requirements is a baseline, not a promise of inbox placement.
Authenticate your sending domain with SPF, DKIM, and DMARC
Use a domain you control in the visible From address, and configure its authentication records with your email service provider (ESP). Sending product mail as support@example.com gives recipients a recognizable identity tied to your organization. Using a free mailbox domain in your application’s From address can create authentication and identity problems because your service does not control that domain’s sending configuration.
Each mechanism has a separate role:
- SPF identifies which sending services are authorized to send for a domain. Your ESP specifies the configuration required for its sending setup.
- DKIM adds a cryptographic signature to a message. A receiving provider can use the public key published in DNS to check the signature and its relationship to the signing domain.
- DMARC lets a domain owner set a policy for messages that fail authentication checks and receive reports. It also checks alignment: the authenticated SPF or DKIM domain must relate appropriately to the domain recipients see in the From header.
For example, SPF can pass for a service’s sending domain while DMARC alignment fails because that domain does not align with the domain in the From address. DKIM can also pass cryptographically but fail alignment if it uses an unrelated signing domain. That is why checking only for an SPF pass is not enough.
Inspect an Authentication-Results header
After publishing the DNS records specified by your ESP, send a real message to a mailbox you control and inspect its full headers. Look for Authentication-Results and check the reported SPF, DKIM, and DMARC outcomes and the domains associated with each result. A simplified example might look like this:
Authentication-Results: mx.example.net;
spf=pass smtp.mailfrom=bounce.example.com;
dkim=pass header.d=example.com;
dmarc=pass header.from=example.com
This is an illustrative header, not a record to publish. The useful point is to compare smtp.mailfrom, header.d, and header.from: a passing mechanism only supports DMARC when the relevant domain aligns with the visible From domain. If a header reports dmarc=fail, compare the domains and sending route before editing DNS. Forwarding and other intermediate systems can also affect authentication results, so diagnose from the actual message path.
Volanea provides guided SPF, DKIM, and DMARC setup and checks domain authentication automatically. We send through Amazon SES, and domain verification is required before sending to real recipients. That verifies your sending identity; it does not, on its own, establish that a list is wanted or that messages will reach the inbox.
Build and protect sender reputation
Mailbox providers associate sending history with domains and, where applicable, IP addresses. There is no single reputation score shared by every provider. Gmail Postmaster Tools, for example, presents domain and IP reputation information for eligible traffic, while other providers may expose different diagnostics or none at all.
Choose an ESP that documents its sending model and provides event information you can use to investigate bounces and complaints. Check how the provider handles authentication and suppressions before moving important product mail. A successful API response or an ESP’s acceptance of a message is not an inbox-placement result; you still need recipient reports and provider-specific signals.
When you start a new domain or sending stream, increase volume gradually and consistently. Treat any ramp plan as an operational example, not a universal provider rule. For instance, a SaaS team expecting a small daily volume might first send only the messages triggered by active users, review bounces and complaints, and then add another expected message class after the first group is behaving normally. A service launching at a much larger volume needs a plan fitted to that volume and its provider guidance; one fixed schedule cannot responsibly cover both cases.
Avoid sudden, unexplained volume spikes. They make it harder for providers and your team to distinguish normal traffic from an audience or software problem. If a product launch, migration, or backfill will increase volume, identify the stream and expected recipients, inspect the contact source, and watch event trends as the change rolls out.
Account for shared sending IPs
IP reputation matters, but it is not always something an individual sender can tune directly. Volanea sends on shared Amazon SES infrastructure and does not offer dedicated IPs. That means you should not plan on isolating your Volanea traffic onto a dedicated IP or controlling an individual IP’s sending history. Put your effort into domain authentication, list quality, complaint handling, and consistent traffic, and review the provider-level information available to you.
Where your architecture allows, distinguish transactional and campaign traffic so you can monitor and manage the streams separately. For example, use a notification subdomain for account alerts and a different subdomain for newsletters. Separation improves operational clarity; it is not a way to erase an organization’s reputation or make an unwanted campaign safe to send.
Send only wanted email and manage contacts carefully
Permission and relevance are the foundation of sustainable sending. Make the sender and message type clear when collecting addresses. Someone who supplied an address to receive an invoice or reset a password has not necessarily agreed to receive a weekly newsletter. Store those purposes distinctly rather than treating every address as permission for every stream.
Double opt-in can help establish that the owner of an address requested a subscription, especially for public signup forms or audiences vulnerable to accidental entry. The confirmation step can reduce mistyped addresses and unwanted signups, at the cost of an extra step for subscribers. Keep the confirmation process and consent record appropriate to your product and audience.
Segment contacts by what they asked to receive and by recent behavior. A customer who uses a particular feature may expect an operational alert about it, but not an unrelated promotion. If a campaign receives weak engagement, resending it to the whole list is not a recovery plan. Narrow the audience to people who are likely to recognize and want the content.
Use a consistent contact-maintenance process:
- Suppress hard-bounced addresses instead of repeatedly retrying them.
- Honor unsubscribes and complaints promptly, and prevent those contacts from returning through another import or integration.
- Review inactive segments before mailing them; where appropriate, ask people to confirm interest rather than assuming an old signup still represents current consent.
- Inspect signup sources for typos, automated registrations, and unexpected bursts.
- Apply suppression rules consistently to campaigns and application-generated email.
Purchased lists are risky because recipients may not recognize your organization or remember giving permission. Stale lists create a similar expectation mismatch: a person who subscribed in the past may no longer want the mail. Both can generate complaints, invalid addresses, and low engagement that damage future sending.
Volanea includes a reputation guard that slows sending when a list may harm the sender domain. That guard is a protective measure, not a substitute for checking how contacts were acquired or what they consented to receive. Investigate the list source and message purpose rather than trying to bypass the slowdown with another batch or sending path.
Make every message easy to recognize and act on
Recipients should be able to identify the sender and understand why the message arrived. Use a familiar From name and a domain associated with your product. “Acme Billing” is easier to recognize for a customer expecting a receipt than an unfamiliar infrastructure name. Keep the identity consistent enough that users can connect their product activity with the mail that follows.
Write a subject line that accurately describes the message. A password reset should identify the action; a campaign should describe its content rather than disguising itself as a security alert. Personalization can help when it reflects real context, such as an account or requested update. Incorrect personalization can instead make a message look careless or suspicious.
Make the message readable in both HTML and plain text. Keep essential instructions available without images, use images to support rather than replace the message, and check that links lead to the expected domain. Unexpected attachments and confusing sender identities can undermine trust. Formatting and wording matter, but there is no universal list of forbidden words that diagnoses spam placement. Consent, reputation, and relevance come first.
Marketing messages need a visible unsubscribe option. Google’s requirements for bulk senders include one-click unsubscribe and a visible link in the message body for marketing and subscribed messages. Even when a stream does not fall under a particular bulk-sender requirement, an accessible unsubscribe path gives people who no longer want the mail an alternative to marking it as spam.
Review the From identity, segment, subject, links, and unsubscribe behavior together before a campaign. A message can be authenticated and well formatted yet still generate complaints if it reaches people who do not expect it. When that happens, improve the audience and purpose before spending time on minor copy changes.
A practical deliverability checklist for transactional email and Amazon SES
SaaS teams often send receipts, password resets, login codes, and event alerts from an application while campaigns follow a separate workflow. Treat each stream as a product surface with its own recipient expectations. Calling an email “transactional” does not exempt it from reputation filtering: repeated unwanted alerts, poorly handled bounces, or abrupt volume changes can still create problems.
For an application using Amazon SES, work through this sequence:
- Authenticate the From domain. Configure SPF and DKIM, publish DMARC, and inspect a received message for alignment.
- Check the sending mode. Confirm that production requests use live credentials and the intended sending configuration.
- Inspect bounce and complaint signals. Compare trends by provider, message type, and deployment. A sudden change after a release could point to a bad address source, a retry loop, or an application change.
- Suppress addresses that should not be retried. Ensure hard bounces and complaints do not continue through application retries or a second sending path. Treat temporary failures differently from permanent failures.
- Introduce new traffic deliberately. Start with expected messages for active users, observe results, and only then add new message classes or larger volumes.
- Test representative messages across providers. An API response confirms that a sending request was accepted; it does not confirm inbox placement.
A schematic request flow might look like this:
POST /v1/send
from: "Acme Accounts <accounts@example.com>"
to: "customer@example.net"
subject: "Your receipt is ready"
html: "<p>Your order receipt is attached to your account.</p>"
This illustrates the application’s sending decision, not a copy-paste API contract. The important implementation details are to use an authenticated domain, send only the message the user expects, and retain a message identifier or other correlation data so a support report can be traced to the request. Volanea documents a REST sending endpoint at POST /v1/send; our transactional email and campaigns platform also supports batch sends, contacts, templates, campaigns, segments, webhooks, and suppressions.
A webhook-driven suppression flow can keep application retries from re-sending to addresses that should stop receiving mail. Receive the provider’s event, associate it with the recipient and message, classify whether it represents a hard bounce or complaint, record the address in your suppression state, and consult that state before the next send. Avoid hard-coding event names or response fields until you have mapped the provider’s documented payload to your system; the key is to make suppression apply across every sending path.
Volanea also provides an SMTP relay for transactional sending. Its SMTP username is volanea, and the password is the project’s secret API key. If you use that route, keep the key in server-side configuration rather than client code, and apply the same bounce, complaint, and suppression handling as you would for API sends.
Test credentials need particular care during debugging: Volanea keys prefixed with sk_test_ render and log messages but never deliver them. A test message appearing in application logs is therefore not evidence that a real mailbox received it. Check which key the deployment uses before diagnosing a missing live email as a filtering problem.
Keep transactional content tied to the account event that triggered it. Adding cross-sells or newsletter material to receipts can make a utility message feel like marketing. Store campaign consent separately, and ensure a marketing unsubscribe does not accidentally disable messages needed for account security or service operation. If you use Volanea, its guide for AI-built apps covers configuring transactional sending through an agent-assisted development workflow.
How to avoid emails going to spam: a recovery sequence
If messages still land in spam, make controlled changes instead of editing several variables at once. Pause a campaign if it is generating complaints or users report a sudden filtering problem. Do not automatically stop security-critical transactional mail; investigate its recipients and route separately so a deliverability response does not create an account-access problem.
Follow this order:
- Map the scope. Record affected providers, message types, domains, and time period. Compare user reports with test accounts and send-event records.
- Separate rejection from placement. Review bounces and server responses for rejected mail. If the provider accepted a message, investigate spam placement and recipient-side filters separately.
- Inspect authentication and reputation. Check SPF, DKIM, DMARC alignment, domain reputation, IP-reputation information where available, and recent DNS or volume changes.
- Review recipients and responses. Look for complaints, hard bounces, unsubscribes, inactive segments, and unexpected signup sources. Suppress contacts that should not receive further mail.
- Make one targeted change. For example, remove a stale campaign segment or correct an authentication record. Record when you changed it and compare the same provider and stream afterward.
- Resume with a relevant audience. Restart with recipients most likely to expect the message, then watch the same indicators as volume grows. A successful test to one mailbox does not establish that the issue is fixed for all providers.
If only one Gmail recipient is affected while other accounts receive the same message, ask them to check Spam, filters, and blocked senders. They can mark a wanted message as “Not spam” and review any rule that moves or deletes mail. These recipient-side steps can help address an individual mailbox preference, but they do not fix a sender-wide authentication or reputation problem.
When a provider-specific issue persists, keep an incident record with the affected domain, approximate start time, message type, sample headers, response codes, and changes made. That is more useful to an ESP or mailbox provider than a general report that email is going to spam. Avoid sending repeated test blasts to large lists during investigation; they add noise and can compound the original problem.
FAQ
When should I switch email service providers?
Consider switching when you have isolated a provider limitation that affects a required workflow, such as missing event visibility or a sending method your application needs. First confirm that authentication, consent, list quality, and suppression handling are sound. Migrating an unwanted list or broken retry loop to another ESP carries the same underlying problem to a new sending path.
What happens if a test email appears in my logs but never arrives?
Check the credential and sending route before investigating spam. In Volanea, a key beginning with sk_test_ can render and log a message but never deliver it. Confirm that your live environment uses the project’s secret API key, that the sending domain is verified, and that the request went through the intended API or SMTP relay.
Does a business associate agreement solve email spam placement for healthcare mail?
No. A business associate agreement concerns contractual handling, not inbox placement. Volanea can provide a BAA on request at hello@volanea.com, but Volanea does not hold SOC 2 or ISO 27001 certification. Teams handling regulated information should assess their full legal and technical requirements separately from deliverability troubleshooting.
How can I tell whether to fix sender settings or a recipient’s Gmail account?
If several test accounts or users at the same provider report a problem, inspect sender authentication, complaints, and sending history first. If one recipient is affected while other accounts receive the same message, ask that person to check Spam, filters, and blocked senders, then mark the wanted message as “Not spam.” Compare scope before changing DNS or moving providers.
Start with the narrowest diagnosis you can support: one recipient, one provider, or one sending stream. Then correct the cause you can observe, keep transactional and campaign behavior accountable, and monitor what changes. If you want to test an integrated API for transactional mail, campaigns, and automations, start free with 1,000 emails a month.