Emails go to spam due to sender reputation, user complaints, and sending patterns—not just technical setup. Focus on audience consent, list quality, and consistent behavior.
Brandset Team11 min de leituraYour SPF record can be correct, your template can look professional, and your emails can still go to spam.
Emails go to spam when mailbox providers see enough signals that make the sender, message, or sending pattern look unwanted, unsafe, or inconsistent. Authentication matters, but it is only one part of that assessment.
That is where a lot of email deliverability advice goes wrong. It treats inbox placement as a technical checklist: configure SPF, add DKIM, publish DMARC, remove a few suspicious words from the subject line, and expect the inbox to cooperate.
Those steps help. They cannot rescue a list that never wanted the email, a domain with a poor sending history, or campaigns that generate complaints every time they go out.
Gmail, Yahoo Mail, Outlook.com, iCloud Mail, and other mailbox providers are trying to keep unwanted and fraudulent email away from their users.
They cannot see the meeting where your team approved the campaign. They do not know that your business is legitimate because you have a nice website. They evaluate the information available to them.
That can include:
whether the message is properly authenticated;
the reputation associated with the sending domain and infrastructure;
user-reported spam complaints;
bounce and delivery patterns;
sudden changes in sending volume;
message formatting and technical compliance;
whether unsubscribe requirements are being followed;
patterns associated with unwanted or abusive mail.
There is no single public “deliverability score” shared across Gmail, Yahoo, and Outlook.
Each provider has its own systems, thresholds, reputation models, and filtering decisions.
So when an email lands in spam, searching for one universal reason can send you in the wrong direction.
Look for the pattern.
SPF, DKIM, and DMARC matter because impersonation is one of email’s oldest problems.
A receiving provider needs a way to determine whether a server claiming to send email for yourcompany.com is actually authorized to do so.
Sender Policy Framework, or SPF, identifies the systems permitted to send email for your domain.
DomainKeys Identified Mail, or DKIM, adds a cryptographic signature to outgoing messages. Receiving systems can verify that signature against information published in your DNS.
Domain-based Message Authentication, Reporting and Conformance, or DMARC, works with SPF and DKIM and adds domain-alignment and policy controls.
These standards establish identity and authorization.
They do not tell Gmail that your newsletter is interesting.
A perfectly authenticated sender can still generate complaints, send to people who never opted in, reactivate an old database too aggressively, or publish campaigns recipients consistently consider irrelevant.
Authentication gives your email a legitimate identity.
Your sending behavior builds the history attached to that identity.
Authentication has moved from an infrastructure detail to a basic part of running an email program.
Gmail requires all senders to personal Gmail accounts to use SPF or DKIM, maintain valid forward and reverse DNS, use TLS, follow standard message formatting, and keep user-reported spam rates below 0.3%. (Google Help)
Senders that reach roughly 5,000 messages to personal Gmail accounts within a 24-hour period are treated as bulk senders. They face additional requirements, including SPF and DKIM, DMARC, domain alignment, and one-click unsubscribe for applicable marketing and subscribed messages. Once Google classifies a domain as a bulk sender, that classification does not expire. (Google Help)
Yahoo requires all senders to use at least SPF or DKIM and keep spam complaint rates below 0.3%. Bulk senders face additional requirements including both SPF and DKIM, DMARC, domain alignment, and easy unsubscribe. (Senders)
Microsoft also requires SPF, DKIM, and DMARC for domains sending more than 5,000 messages per day to Outlook.com consumer addresses, including Hotmail and Live accounts. Enforcement began in May 2025. (TECHCOMMUNITY.MICROSOFT.COM)
For a small business sending far less than 5,000 messages per day, those bulk thresholds may feel distant.
Configure authentication anyway.
It is easier to establish the technical foundation while your program is small than to discover authentication problems when your list has grown and revenue depends on email.
If someone reports an email as spam, the meaning is hard to misunderstand.
They did not simply skip the campaign. They actively told their mailbox provider that they did not want it.
Google tells senders to keep the user-reported spam rate shown in Postmaster Tools below 0.1% and prevent it from reaching 0.3% or higher. For bulk senders, Google says rates above 0.1% already have a negative impact on inbox delivery, with greater impact at 0.3% and above. (Google Help)
Yahoo also requires complaint rates below 0.3%. (Senders)
Those numbers are guardrails.
If your complaint rate starts rising, do not celebrate because it remains technically below a threshold. Investigate what changed.
Maybe an old segment was reactivated.
Maybe signup expectations were unclear.
Maybe campaign frequency increased.
Maybe a promotional message reached people who signed up for something different.
Maybe unsubscribing is harder than it should be.
A complaint metric tells you that recipients are rejecting the relationship. The fix often starts upstream from the campaign itself.
Large lists make people reluctant to delete anything.
A database may contain 20,000 contacts, so removing 5,000 feels like throwing away an asset.
That assumes every address has equal value.
Consider two subscribers.
One joined two weeks ago after downloading your pricing guide. The other entered your database four years ago through a giveaway and has received dozens of campaigns since.
They occupy one row each in the CRM.
They do not represent the same relationship.
Continuing to send indefinitely to people who no longer recognize or care about the sender can increase the chance of negative recipient behavior. Old addresses can also become invalid, creating additional list-quality problems.
Avoid replacing that mistake with another rigid rule.
There is no universal point at which every contact should be removed after 90 days, six months, or a year.
A weekly newsletter and a seasonal accounting firm naturally create different engagement patterns.
Review inactivity relative to your normal cadence, the reason someone subscribed, and the signals you actually have.
One of the weakest pieces of deliverability advice is the claim that every unopened email directly lowers some hidden “domain credit score.”
Mailbox providers do not publish a universal domain credit score.
Open data is also unreliable enough that it should not carry that kind of weight.
Apple’s Mail Privacy Protection, for example, can privately load remote email content before the recipient actively reads the message. That affects the accuracy of tracking pixels commonly used to record opens. (Apple Support)
Someone can also read an email without triggering the tracking mechanism your platform expects.
So an individual non-open does not tell you very much.
A broader pattern can.
If the same audience receives campaign after campaign without clicks, replies, purchases, bookings, visits, or other meaningful activity, you should ask whether those contacts still belong in the active audience.
The decision comes from context, not one pixel.
Imagine a business sends 300 emails a month for most of the year.
Then Black Friday arrives and it suddenly sends 25,000.
The business may have a legitimate reason for the campaign. Mailbox systems still see a dramatic change in behavior.
Google explicitly advises senders to increase volume gradually, avoid sudden spikes, and maintain consistent sending patterns. (Google Help)
This becomes especially relevant for:
new sending domains;
businesses restarting email after a long pause;
companies migrating to a new sending setup;
senders suddenly activating much larger portions of an existing list.
Permission-based email does not need fake warm-up activity.
Start with the audience most likely to recognize the sender. Expand progressively as the domain establishes a normal sending history.
There is no universal schedule.
A business with 400 subscribers has a different risk profile from one preparing to send 40,000 emails.
Another persistent myth says your email went to spam because you used words such as free, sale, limited time, or guaranteed.
Modern filtering systems evaluate far more than individual vocabulary.
Google’s sender guidance focuses on authentication, DNS, TLS, spam rates, message formatting, sender identity, unsubscribe behavior, and responsible sending practices. It does not publish a blacklist where one marketing word automatically determines spam placement. (Google Help)
That does not give deceptive copy a free pass.
A subject line saying Your account has been suspended when the email contains a discount offer creates a trust problem regardless of which individual words appear in it.
Write subject lines that accurately describe the message.
Use a sender identity subscribers recognize.
Keep links understandable.
Make the email functional even when images do not load.
Give people an obvious way to unsubscribe.
Trustworthy presentation is a better standard than trying to replace every word that appeared on a “spam trigger words” list from 2014.
A useful way to diagnose deliverability is to separate the technical and audience sides.
Technical identity | Audience and sending behavior |
|---|---|
SPF configured correctly | Contacts have a valid reason to expect the email |
DKIM signatures working | Campaigns match signup expectations |
DMARC configured appropriately | Complaints remain low |
Valid DNS and sending configuration | Invalid addresses are removed |
Consistent sender identity | Volume changes are gradual |
Functional unsubscribe mechanisms | Inactive audiences are reviewed |
Healthy sending infrastructure | Messages have a clear reason to be sent |
If the left side fails, providers may struggle to verify who you are.
If the right side fails, authentication cannot make recipients want the message.
That distinction saves a lot of wasted troubleshooting.
Sender reputation develops over time, but the symptoms can appear abruptly.
A business sends for months without an obvious problem. Then a campaign underperforms and everyone assumes Gmail changed an algorithm overnight.
Sometimes filtering changes do happen.
Often something closer to home changed first.
The business may have imported an older segment. Sending volume may have increased. Complaint rates may have climbed gradually. A DNS change may have broken authentication. An old domain may have returned after months without regular sending.
When deliverability changes, compare recent campaigns with the period before the problem.
Ask:
Did the audience change?
Look at list source, segment size, age, and consent.
Did the sending pattern change?
Compare volume, cadence, domain, infrastructure, and frequency.
Did authentication change?
Check SPF, DKIM, DMARC, DNS, and provider feedback.
Did complaints or bounces change?
These are often more useful diagnostic signals than open rate alone.
Did the message type change?
A highly promotional campaign may produce different recipient behavior from a newsletter the audience normally receives.
Find the first meaningful change before changing everything else.
A useful checklist starts with the factors closest to the actual relationship.
Authenticate the sending domain correctly. Check SPF, DKIM, DMARC, DNS, sender identity, and unsubscribe functionality.
Every active segment should have a defensible reason for receiving the campaign.
Purchased and scraped lists fail this test immediately.
If a campaign is going to the wrong people, redesigning the template will not fix the problem.
Review inactive contacts, invalid addresses, list source, and segmentation first.
New and inactive domains should establish sending history gradually through real campaigns.
Do not manufacture reputation with fake opens or artificial conversations.
Investigate why someone would choose the spam button instead of simply ignoring or unsubscribing.
An unsubscribe costs you one subscriber.
Making the exit difficult can cost you a spam complaint.
A newsletter, launch email, nurture message, and re-engagement campaign should not all be measured by the same number.
A sender can do everything right with its audience and still struggle if the delivery infrastructure is poorly managed.
A platform can maintain healthy infrastructure and still fail to protect a customer who sends unwanted email to a bad list.
Both sides matter.
Brandset manages and protects the infrastructure used to send email, monitors abuse, and guides customers through sending-domain authentication and responsible sending practices.
The sender controls who enters the audience, what those people agreed to receive, which campaigns reach them, how frequently they are contacted, and when an old contact should stop receiving email.
Brandset does not create fake opens, simulated conversations, or artificial warm-up activity to manufacture sender reputation. Your domain develops its history through real campaigns sent to real people.
Before troubleshooting your next deliverability problem, open the audience for the campaign and ask one question:
Why does each group on this list reasonably expect this email?
If that answer is weak, start there.
Brandset Team25 min de leituraLearn how to plan, segment, write, design, and measure effective email campaigns for small businesses, focusing on strategy, relevance, deliverability, and post-send analysis.
Brandset Team11 min de leituraLearn how to clean your email list effectively by separating inactive, bounced, and unsubscribed contacts, using multiple engagement signals, and avoiding loss of good subscribers.
