Why your emails go to spam

Your email went to spam because the filters don't trust your sender yet. New domains and fresh mail servers start with zero reputation, so Gmail, Outlook, and Yahoo sort you with the scammers until you prove otherwise.

The fix isn't a trick. It's a two-lane system: keep sending through a service that's already trusted, and in the background warm up a mail server you own. You get email delivered this week, plus a setup that gets cheaper and more reliable as you grow. About ten minutes to read, and you'll know exactly what to do at the end.

Why the filters snub you

Email providers grade senders the way a bouncer grades IDs. They run three checks on every sender, and you need to pass all three:

• History. How long you've been sending, and whether people open your mail or report it. A brand-new domain has no history, and no history reads as suspicious.
• ID. Records called SPF, DKIM, and DMARC that prove the mail is really from you. Missing or broken, and the filters treat you like a stranger. At worst, like a phisher.
• Behavior. Bought lists, volume that spikes overnight, high bounce rates, spam complaints, no unsubscribe link. Each one is a strike against you.

One great email can't outrun a bad setup. You can write the best newsletter in your industry and it will still land in spam if the plumbing behind it is new or sloppy.

Why it's worth fixing

Email is the only channel you fully own. Social platforms change their rules whenever they feel like it, and your followers are rented. Your list is yours. But a list only pays if the mail reaches the inbox:

• Inbox = money. Mail in the spam folder is invisible. Every send is a lead, renewal, or referral that never happens.
• Reputation compounds. Send cleanly for months and providers trust you more, so every future send works better. Flag your domain in month one and you'll fight that scar for a year.
• Your domain is your name. People search you before they buy. When a customer wonders if you're legit and finds "their emails go to spam," that's a brand problem, not an IT problem.

The cheapest time to fix this is before it costs you. Starting clean beats rehabbing a burned domain.

SMTP and IMAP, explained simply

Two acronyms come up the moment you start talking about email servers. Here's what they mean.

SMTP is the mail carrier.

It's the protocol that moves outgoing mail from your computer or website to the recipient's provider. Think of it as the delivery truck: it picks up your message and hauls it across the internet to the right post office.

IMAP is your mailbox.

It's the protocol your email app uses to read mail that's arrived for you. When you check mail on your phone and your laptop shows the same read messages, that's IMAP syncing one mailbox to both devices.

What this means for you: run your own mail server and you're being your own delivery truck, and that truck has to earn trust with every post office it visits. Send through a service and you're borrowing their well-known trucks instead. Most businesses need both: IMAP for reading what comes in, and a trustworthy way to send what goes out. Everything below is about making the sending side trustworthy.

Lane 1: send through someone who's already trusted

Sign up with a reputable bulk sender (Amazon SES, Postmark, and Mailgun are the common ones) or your web host's mail API. Their servers already have reputation, so you borrow it while you build your own.

Two rules here:

• Put your name on the mail. Even through a service, you add SPF, DKIM, and DMARC records to your own domain. The mail should be stamped as yours, not just theirs.
• Send like a real person. Mail to people who actually asked. A weekly rhythm beats random blasts. Watch your bounce rate like a hawk.

This lane is your income today. It's not a workaround or a cheat. It's how you stay credible while the second lane warms up.

Lane 2: warm up a server you own

While Lane 1 carries your real mail, you build the asset that pays off later: your own SMTP server, warmed the right way.

Warming just means feeding a new server volume gradually so it looks like a normal sender instead of a spam cannon. You start with a trickle to your most engaged readers, then grow day by day over a few weeks.

Get the proof stack in place first: SPF, DKIM, and DMARC (start DMARC at p=none and tighten it as you earn trust), plus reverse DNS on the server's IP. Miss any piece and the ramp stalls.

Then watch three numbers every week:

• Bounce rate. Keep it in the low single digits. High bounces tell providers your list is dirty.
• Spam complaints. Keep them under 0.1%, one per thousand. Complaints are the fastest way to lose trust.
• Where mail lands. Send test messages to inboxes at Gmail, Outlook, and Yahoo, and check which tab they hit.

Send to your openers. The people who open and click are the ones building your reputation. The ones who never engage drag it down, so prune them as you go.

The warm-up plan, step by step

Here's the whole system as a checklist you can hand to anyone:

1. Pick your Lane 1 sender. Choose a reputable bulk sender or your host's mail API.
2. Authenticate your domain. Add SPF, DKIM, and DMARC records. Verify they resolve before sending anything.
3. Send to your engaged list weekly. Start with people who asked to hear from you, and keep volume steady.
4. Set up your own server. Provision your SMTP server and add reverse DNS pointing at it.
5. Reuse your records. Update SPF and DKIM so your own server is authorized to send for the same domain.
6. Start the ramp. Week one, send a few dozen messages to your most loyal readers. Increase volume gradually, week by week.
7. Watch the numbers. Every week, check bounces, complaints, and spam placement. Fix anything that slips before scaling further.
8. Shift real volume over. Once your server has clean history, move actual sends onto it a little at a time.
9. Keep Lane 1 for the big moments. Use the service for large campaigns and new lists, when you want the bigger sender's muscle.

What most people get wrong

They pick one lane, and usually the wrong one. A raw server looks cheap, so they plug it straight into their website, skip the warm-up, and blast their whole list on day one. That's how a domain earns a spam reputation in an afternoon.

They also buy lists. One rented list produces bounces and complaints that undo months of careful work, and the people on it never wanted your mail anyway.

And they treat deliverability as a one-time project instead of maintenance. The filters never stop watching, so the hygiene never stops either: keep unsubscribes instant, clean bounces monthly, re-engage or drop the cold readers, and never buy a list.

We can do it for you

If you're reading this and thinking "that's a lot of DNS records to babysit" — you're right, it is. And you shouldn't have to. That's exactly what Polliwog does: the whole loop, from the records to the ramp.

• Domain authentication — SPF, DKIM, and DMARC set up and verified before you send a thing
• Sender configuration — the right trusted service for your volume, wired to your site
• A warm-up plan with the numbers to watch — so your own server earns trust instead of burning it
• Monitoring — bounces, complaints, and spam placement, watched so you hear about trouble before it costs you

You run the business. We run the system that gets your mail out now and grows with you later.

Bottom line

Spam isn't a judgment on your writing. It's a judgment on your setup, and setup is fixable. Start with a sender that's already trusted, warm your own server on the side, and shift over as your reputation grows. Do that and in a few weeks your mail lands in the inbox instead of the tab nobody opens, and the setup scales with you.