Solanasis Docs

solanasis_cold_email_deliverability_playbook_2026

11 min read

Solanasis Cold Email Deliverability & Warmup Playbook (2026)

Purpose

This guide summarizes the key takeaways from our discussion about:

  • whether TrulyInbox is a reasonable low-cost warmup option,
  • how to set it up in the least-bad / safest practical way,
  • which free and low-cost postmaster-style tools matter most,
  • what to watch so cold outreach does not quietly damage the domain.

This is written so another AI can use it as a working playbook.

Executive summary

Core position

  • TrulyInbox appears to be a legitimate standalone warmup platform, not a Gmail browser extension. Its site and support docs show support for Google OAuth and SMTP/IMAP connection methods, plus provider-specific setup guides. (TrulyInbox home, Connection method guide)
  • The free plan is real: TrulyInbox currently advertises Free forever for 1 account with 10 warmup emails/day. Its paid Starter plan is currently 22/month annualized, and paid plans allow unlimited accounts with pricing based on total warmup email volume rather than per inbox. (TrulyInbox pricing)
  • This does NOT mean warmup is officially blessed by Google. Google’s sender guidance emphasizes SPF, DKIM, DMARC, low spam complaint rates, and gradual ramp-up, not automated warmup as a sanctioned shortcut. (Google sender guidelines, Postmaster dashboards)
  • Do not call TrulyInbox “low risk” without caveats. Better phrasing: it is a reasonable small helper for a low-volume outreach inbox, but it is not a safety guarantee.

Bottom-line recommendation for ds@solanasishq.com

  • For a single low-volume outreach inbox, the free TrulyInbox plan is acceptable to test.
  • Use it only after SPF, DKIM, and DMARC are in place.
  • Prefer Google OAuth over SMTP/IMAP if the mailbox is on Google Workspace.
  • Treat warmup as supplementary, not as the core deliverability strategy.
  • The real foundation is still: good list quality, relevant prospects, plain-text-ish emails, slow ramp-up, low complaint rates, and provider-side monitoring.

What was verified about TrulyInbox

Product/pricing facts

Verified from the current pricing page:

  • Free forever plan for 1 account
  • 10 warmup emails/day on free
  • Starter = $29/month if paid monthly
  • Starter annual equivalent = 264/year
  • Paid plans support Unlimited Accounts
  • TrulyInbox says it charges for warmup emails sent per day, not per connected mailbox

Source: TrulyInbox pricing

Setup / connection facts

Verified from TrulyInbox docs:

  • TrulyInbox supports Google OAuth and SMTP/IMAP style connections. (TrulyInbox home)
  • Their support docs explicitly say that if your email is hosted on Google Workspace or Microsoft 365, OAuth is recommended over SMTP for better security and easier maintenance. (SMTP single-account guide, Connection method guide)
  • Their “Getting Started” guide says before you start, the mailbox should be active and SPF, DKIM, and DMARC should already be configured correctly. (Getting Started)
  • If you use Gmail via SMTP/IMAP, TrulyInbox’s support flow says you need to:
    1. enable IMAP,
    2. enable 2-Step Verification,
    3. create an App Password. (Gmail SMTP/IMAP setup)
  • TrulyInbox also has a separate official guide for connecting via Google OAuth, where you select Google OAuth in TrulyInbox and complete Google sign-in / consent. (Google OAuth setup)

Important Google security nuance

Google’s own documentation says App Passwords aren’t recommended and that, where possible, you should use “Sign in with Google” instead. (Google app passwords guidance)

That makes the best practice here very clear:

  • Preferred: Google OAuth
  • Fallback only if needed: SMTP/IMAP + App Password

The key risk nuance: why this still might backfire

The correct, careful interpretation

It is fair to say:

  • TrulyInbox is architecturally different from a browser-extension style tool injected into Gmail.
  • That distinction probably reduces fragility compared with old extension-based approaches.

It is not fair to say:

  • this means Google approves of warmup,
  • or that warmup “won’t backfire usually.”

Google’s public sender docs do not endorse automated warmup. They tell senders to focus on authentication, complaint rate, and ramping volume responsibly. (Google sender guidelines, Sender requirements FAQ)

Why people are cautious

GMass publicly documented that it shut down its warmup system after Google told it to stop or risk losing Gmail API access. GMass also said Google considered warmup to violate its terms. That is GMass’s account of what happened, not the same thing as a fresh public Google policy page naming every warmup tool. But it is still an important signal that Google has historically cracked down on automated warmup behavior. (GMass warmup shutdown post)

Best framing

Use this framing instead:

TrulyInbox appears to be a legitimate standalone warmup service with Google OAuth and SMTP/IMAP connection options. It is materially different from the old browser-extension style setup. But that does not equal official provider approval. It should be treated as an optional assist for a low-volume inbox, not as a safety blanket.

Best-practice TrulyInbox setup for Solanasis

This section is the practical setup recommendation.

1) Prepare the mailbox correctly first

Before connecting anything:

  • Use a dedicated outreach mailbox such as ds@solanasishq.com
  • Confirm the inbox is active and usable
  • Confirm SPF, DKIM, and DMARC are set correctly
  • Confirm DNS is sane overall (MX, DKIM selector, SPF include chain, DMARC policy syntax)
  • Keep the domain itself clean and professional

Why: Google and Yahoo both emphasize authentication and complaint rate control as foundational deliverability requirements. (Google sender guidelines, Yahoo sender best practices)

2) Choose the connection method correctly

For a Google Workspace mailbox:

  • Use Google OAuth first
  • Only use SMTP/IMAP + App Password if OAuth is not workable for some reason

Why:

3) Use the free plan as a light assist, not as a crutch

For one outreach inbox, the free plan’s 10 warmup emails/day is enough to test the tool without creating a large synthetic footprint. (TrulyInbox pricing)

Recommended posture:

  • keep it conservative,
  • do not stack aggressive warmup + aggressive cold sending at the same time,
  • and do not assume the warmup network itself makes bad sending behavior safe.

4) Start real sending slowly anyway

Even if TrulyInbox is running, still ramp real outreach manually and conservatively.

Google explicitly advises senders to increase sending volume slowly over time. (Google sender guidelines)

Practical interpretation:

  • start with very small daily volumes,
  • prioritize highly relevant warm leads or second-degree contacts first,
  • and only scale when reply quality and complaint risk look healthy.

5) Keep outreach emails simple early on

Especially early in domain life:

  • mostly plain text
  • minimal links
  • minimal images
  • no attachments unless necessary
  • relevant personalization
  • no hypey spam language

This is not because a provider doc says “exactly this template.” It is because simple, relevant, low-friction mail tends to generate fewer negative signals and fewer filters.

6) Monitor continuously

Do not run warmup blind.

At minimum monitor:

  • Gmail reputation / spam rate via Google Postmaster Tools
  • Outlook reputation / complaints via SNDS + JMRP
  • Yahoo complaints via CFL
  • blacklist status
  • SPF/DKIM/DMARC health

My recommended free / low-cost postmaster stack

Free core stack — recommended first

Google Postmaster Tools — free

Use for:

  • spam rate
  • reputation
  • message authentication
  • delivery errors
  • Gmail-only visibility for mail sent to personal Gmail accounts

Google says Postmaster Tools dashboards expose spam rate, reputation, message authentication, and delivery errors. Google also says to keep spam rate below 0.10% and avoid ever reaching 0.30% or higher. (Postmaster setup, Google sender guidelines, Google sender FAQ)

Microsoft SNDS + JMRP — free

Use for:

  • Outlook / Hotmail / MSN IP reputation insight
  • complaint reports when users mark your mail as junk

Microsoft says SNDS gives detailed data about IPs and includes the Junk Email Reporting Program so you can receive reports when users junk your messages. (SNDS)

Yahoo Complaint Feedback Loop — free

Use for:

  • complaint visibility for Yahoo / AOL recipients

Yahoo says its CFL sends reports back to senders when users mark mail as spam, and that the DKIM domain used in the message must be enrolled. Yahoo also says to keep spam complaint rates below 0.3%. (Yahoo CFL FAQ, Yahoo sender best practices)

Google Admin Toolbox CheckMX — free

Use for:

  • SPF sanity checks
  • DKIM checks
  • DMARC checks
  • MX/DNS hygiene

This is one of the easiest quick checks for setup mistakes.

MXToolbox free

Use for:

  • blacklist checks
  • one basic monitor
  • quick DNS and mail health checks

ZeroBounce free account

Use for:

  • lightweight list verification
  • light deliverability testing
  • a cheap way to avoid obvious bad addresses

Best low-cost paid add-ons

GlockApps

Best if you want inbox placement testing before scaling sequences.

dmarcian

Best if you want stronger DMARC reporting / domain authentication governance.

The metrics that matter most

1) Spam complaint rate

This is one of the most important risk metrics.

2) Authentication health

Minimum expectations:

  • SPF
  • DKIM
  • DMARC

Google says all senders should authenticate mail, and bulk senders need stronger alignment. Yahoo also calls out SPF or DKIM at minimum and valid forward/reverse DNS. (Google sender guidelines, Yahoo sender best practices)

3) Real negative signals

Watch for:

  • spam complaints
  • hard bounces
  • sudden drops in replies
  • blacklisting
  • domain or IP reputation degradation

4) Delivery destination, not vanity metrics

Do not overweight opens.

Stronger signals are:

  • actual inbox placement,
  • actual replies,
  • complaint rates,
  • blocklist status,
  • and whether provider dashboards stay healthy.

Option A — recommended

  • 1 dedicated outreach inbox: ds@solanasishq.com
  • Google Workspace mailbox
  • SPF, DKIM, DMARC configured first
  • Google OAuth connection to TrulyInbox
  • TrulyInbox free plan initially
  • Google Postmaster Tools + Microsoft SNDS/JMRP + Yahoo CFL + CheckMX + MXToolbox free
  • manual / highly personalized low-volume cold outreach

Why this is the best current balance:

  • low cost,
  • lower operational complexity,
  • lower synthetic activity footprint,
  • still gives you real provider-side monitoring,
  • and does not overcommit to warmup mythology.

Option B — if scaling to multiple inboxes later

  • add more mailboxes only after the first domain/inbox behaves cleanly
  • keep each mailbox’s real send volume conservative
  • upgrade TrulyInbox only if you actually need more warmup volume
  • add GlockApps before materially increasing campaign volume

Weekly checklist

Every week

  1. Check Google Postmaster Tools for:

    • spam rate
    • reputation
    • authentication issues
    • delivery errors

  2. Check Microsoft SNDS / JMRP for:

    • complaint signals
    • unusual reputation issues

  3. Check Yahoo CFL / sender hub for complaint issues

  4. Run DNS / auth checks:

    • SPF
    • DKIM
    • DMARC
    • MX

  5. Check blacklist status

  6. Review campaign behavior:

    • hard bounces
    • unsubscribe / negative response patterns
    • spammy copy or misleading subject lines
    • overuse of links/images/attachments

  7. Keep ramp-up conservative

Red flags

Stop and reassess if you see:

  • rising spam complaints
  • sudden deliverability drop at Gmail or Outlook
  • blacklisting
  • lots of hard bounces
  • highly variable inbox placement
  • cold outreach volume increasing faster than reputation data supports
  • dependency on warmup while core copy / targeting / list quality remains weak

What another AI should NOT assume

Do not assume:

  • that a dedicated warmup tool is automatically “safe,”
  • that Google officially endorses warmup,
  • that warmup can compensate for bad targeting or weak authentication,
  • that more warmup volume is always better,
  • that low opens alone prove a deliverability issue,
  • or that one provider dashboard tells the whole story.

Preferred language / positioning

Safe wording to use

TrulyInbox appears to be a legitimate standalone warmup service and a reasonable low-cost helper for a small outreach inbox, especially when connected via Google OAuth. But it should be treated as a supplement to proper deliverability hygiene, not as a guarantee that cold outreach is safe or provider-approved.

Wording to avoid

  • “TrulyInbox is low risk.”
  • “This won’t backfire usually.”
  • “Dedicated services are safe because they run on their own servers.”
  • “Warmup solves deliverability.”

Final recommendation

For Solanasis right now:

  • Yes: test TrulyInbox on the free plan for ds@solanasishq.com
  • Yes: connect with Google OAuth if on Google Workspace
  • Yes: set up the free provider-side monitoring stack immediately
  • Yes: ramp real outreach slowly and keep it highly relevant
  • No: do not lean on warmup as the main deliverability strategy
  • No: do not describe it internally as “safe” or “won’t backfire”

The winning posture is not “trust the warmup tool.”

The winning posture is:

  • clean technical setup,
  • conservative sending,
  • relevant recipients,
  • strong copy,
  • low complaints,
  • and real postmaster monitoring.

Graph View