Envelope with shield band symbolizing trustworthy email delivery
Email deliverability is full of confident advice that’s half-true. This one-page cheat sheet separates common myths from what actually affects whether your message lands in Inbox, Spam, or nowhere.

Use it when you’re sending from work, a custom domain, or just trying to understand why “it sent” doesn’t mean “they got it.”

Quick note: “Deliverability” is about acceptance and placement (accepted vs bounced, inbox vs spam). “Open rate” is a separate (and increasingly unreliable) story.

Myth #1: “If it doesn’t bounce, it was delivered”

Reality: Many emails are accepted and then filtered to Spam, Quarantine, or a hidden “Other” tab. Some systems also accept and later silently suppress visibility.

What to do: Ask the recipient to check Spam/Promotions/Other, then search for your subject, your domain, and your “From” address. If you can, request the message headers from a received copy.

  • Bounce = the receiving server rejected it (you usually get a report).
  • Accepted = the receiving server took responsibility (not a promise of Inbox).
  • Placed = Inbox/Spam decision based on signals and policy.

Myth #2: “Adding more links makes it look spammy”

Reality: It’s not “number of links” in isolation. It’s link reputation, mismatch (display text vs actual URL), tracking redirect reputation, and whether your domain aligns with authentication.

Chain link metaphor for link reputation in emails
A short message with one suspicious tracking redirect can look worse than a longer email with clean, consistent links.

  • Use your own domain links where possible.
  • Avoid URL shorteners in professional mail.
  • Make sure the visible link text matches the destination domain.

Myth #3: “Gmail/Outlook are blocking me because of keywords”

Reality: Keywords can contribute, but most filtering is reputation + authentication + behavior. The same words can land fine from a good sender and fail from a risky one.

What matters more than buzzwords:

  • Domain and IP reputation (your sending history)
  • Authentication alignment (SPF/DKIM/DMARC)
  • Complaint rate (people marking you as spam)
  • Engagement patterns (replies, deletes, ignoring over time)

Myth #4: “SPF, DKIM, and DMARC are optional for small senders”

Reality: They’re not just for big companies. Without them, your mail can look spoofable, and many receivers now treat unauthenticated mail as suspicious by default.

Wax seal metaphor for SPF DKIM and DMARC authentication
Think of these as “proofs” that the domain shown in the From line is allowed to send that message.

  • SPF: which servers are allowed to send for your domain (helps with “is this server authorized?”).
  • DKIM: cryptographic signature (helps with “was it tampered with, and who signed it?”).
  • DMARC: policy + reporting (helps with “what should receivers do if SPF/DKIM don’t align?”).

Practical reality check: You can “pass SPF” and still fail DMARC if alignment doesn’t match the domain the user sees.

Myth #5: “Images cause spam filtering; plain text always wins”

Reality: Image-only emails are risky, but images themselves aren’t the enemy. The bigger issues are imbalance (one huge image, little text), missing alt text, sketchy linked domains, and poor authentication.

Safer pattern: a real text introduction + one supporting image + a clear, consistent call to action that matches your domain.

Myth #6: “If I’m in their contacts, I’ll always hit Inbox”

Reality: Contacts help, but they don’t override strong negative signals like failed authentication, sudden volume spikes, or a domain with a bad recent history.

What helps more than ‘being a contact’: consistent sending, low complaints, and replies (real conversation signals can matter for some providers).

Myth #7: “Forwarding and ‘Send mail as’ are harmless”

Reality: Forwarding can break SPF because the forwarder isn’t on your SPF record. Some forwarding setups preserve DKIM, some don’t. “Send as” can also create alignment confusion if configured incorrectly.

Envelope in relay tube showing forwarding can break delivery
This is why a message can deliver fine to one person but fail when auto-forwarded to another inbox.

  • If important mail is forwarded, prefer methods that preserve authentication (varies by provider).
  • For custom domains, ensure DKIM signing is enabled at the original sender.
  • When troubleshooting, test direct delivery vs forwarded delivery.

One-page checklist: what to check first (fast)

  • Recipient view: did it land in Spam/Promotions/Other? Can they search for it?
  • Bounce evidence: do you have a bounce code or rejection reason?
  • From domain consistency: does the visible From domain match the actual sending domain?
  • Authentication: SPF pass? DKIM pass? DMARC pass with alignment?
  • Links: are you linking to your own domain (not shorteners or mixed domains)?
  • Volume spike: did you suddenly send far more than usual?
  • List quality: are you emailing people who didn’t expect it (complaints/blocks)?
  • Forwarding: is the recipient using auto-forward rules that could break SPF?

Takeaway (keep this mental model)

Most “email disappeared” problems aren’t a single magic spam word. They’re a trust decision: who sent it (reputation), whether it’s provably authentic (SPF/DKIM/DMARC alignment), and how recipients react over time.

If you only fix one thing, make it authentication alignment—then review links and sending patterns.