Bulk email server setup checklist

 “Just send an email.” It looks like a one-liner: await sendEmail(to, subject, body); But in production, that line explodes into a full subsystem. Here’s what you actually end up building 👇 1. Reliability - never send inline Sending directly inside a request works… until latency spikes or the provider times out. You decouple it using a queue (Kafka, SQS, or RabbitMQ) -> a background worker processes sends. Each message gets a unique message_id for idempotency, retries use exponential backoff, and you persist status = pending/sent/failed. 2. Deliverability - “sent” != “delivered” Your API logs “200 OK,” but user didn't get it. You need webhooks from SES/SendGrid to capture delivered, bounced, or spam events. Those callbacks update your DB, mark bad addresses inactive, and feed a delivery analytics dashboard so you actually know what happened. 3 Spam filters & domain reputation You can write the best emails, and still end up in spam if you skip the basics: Set up SPF, DKIM, and DMARC. Warm up new domains gradually (start with low send volume). Use a dedicated sending domain (e.g., mailer.myapp.com) and separate IPs for transactional vs marketing. Without this, your whole app’s communication pipeline can get blacklisted overnight. 4 Personalization at scale You’re not just sending static HTML. Each email has dynamic placeholders ({{user.name}}, {{order.id}}), localized text, and sometimes attachments. You pre-render templates (Liquid/MJML), cache HTML in Redis, and bulk fetch user data to avoid DB thrash. At high volume, even template rendering becomes a performance bottleneck. 5 Observability & throttling At scale, email providers rate-limit you. You’ll need token-bucket throttling, multiple provider fallbacks, and metrics (Prometheus/Grafana) for latency and bounce trends. When one region hits its SES quota, your system should automatically failover to another provider without losing events. That “forgot password” email that lands in 2 seconds? It’s backed by queues, workers, webhooks, templates, cryptographic signatures, and deliverability tuning.

Google is deleting your cold emails before they even hit inbox. This happened to us recently!! We had: - Clean list. - Warmed domain. - SPF, DKIM, DMARC — all ✅ - Great copy. But stil… Zero replies. We thought something was off. It was: our infrastructure. Gmail doesn’t just scan your words. It scans how you send, from where, and what patterns you follow. If any of it looks off, your emails are erased before they reach anyone. What fixed it for us: 1. We set-up our own Infra: We set up our own SMTP server Postfix on a VPS. Hooked it to a dedicated IP. No shared infra. No third-party fingerprints. → Clean sender identity. Now Gmail treats us as a standalone sender not a bulk app user. 2. We fully configured DNS (beyond the basics) Most people set SPF, DKIM, and DMARC and think they’re done. Wrong. You also need: - PTR records (reverse DNS) - FCrDNS (forward-confirmed reverse DNS) These are what Gmail uses to verify that your IP = your domain. 3. We slowed everything down Started sending 5–10 plain-text emails/day. Just real messages, written manually. Replies boosted sender reputation. Then we scaled up slowly over 45 days. Volume only grew when reply rates held steady. 4. We re-learned how to write No fancy formatting. No AI-sounding “quick questions.” No calendar links. Instead we used: - all small caps email - made mistakes on emails Gmail flags anything that looks templated or mass-produced. 5. We implemented greylisting + rate-limiting Most people don’t know what this is. We configured our server to: Accept retry attempts from legit mail servers The bursts that look like spam behavior Gmail tracks this. It’s their way of filtering real senders from spam bots. If your infra can’t retry or slows down under load that’s a good thing. 6. We started live monitoring everything We now use internal dashboards to monitor: - Spam feedback loops (Spamcop, AOL, etc.) - IP reputation health - Open/reply/soft bounce signals - Domain temperature Auto-rotation of sending IPs One red flag… The system pauses, reroutes, and resets warm-up if needed. Most founders optimize copy. Smart founders fix infrastructure. Google’s AI doesn’t care how clever your hook is. It cares how trustworthy your server looks from the outside. I’m still learning and implementing things day by day —— Send this to your SDR

Before copy, before offers, before personalization… your emails need to land in the inbox If you're doing [X] - sending emails straight from a fresh domain without setup Switch to warming and proper infrastructure first, because inbox providers will flag you immediately. 1. Disable Tracking Links Tracking pixels and link tracking often trigger spam filters. They add extra redirects → suspicious behavior They signal “mass outreach tool” What works: Use plain links or no links at all in the first email. Focus on getting a reply, not a click. 2. Use Multiple Mailboxes per Domain One inbox blasting emails = high risk. Spread volume across 2–3 inboxes per domain Example: john@ mike@ Why it matters: Lower activity per inbox = more natural sending pattern. 3. Mix Google and Outlook Accounts Email providers watch patterns. If all your emails come from one ecosystem, it’s easier to detect. Better approach: 50% Google Workspace 50% Outlook This creates diversity and reduces risk signals. 4. Warm Up Your Domains (Minimum 2 Weeks) New domains have zero trust. If you're doing [X] sending emails immediately after setup - switch to warming first, because cold domains get flagged fast. Simple process: Start with 5–10 emails/day Gradually increase Use real conversations or warm-up tools Goal: build history that looks human. 5. Use Separate Domains for Outreach Never send cold emails from your main domain. Why: Protect your brand domain reputation Avoid affecting your core business emails Example: Main: yourcompany.com Outreach: yourcompany.co / getyourcompany.com 6. Set Up SPF, DKIM, and DMARC Properly Skip this and your emails won’t be trusted. These are your authentication signals: SPF → confirms sender DKIM → verifies message integrity DMARC → tells servers how to handle failures No setup = low deliverability, even with great copy 7. Keep Volume Low (Max ~20 Emails/Day per Inbox) More volume doesn’t mean more results. Among outbound campaigns, accounts sending lower daily volume tend to last longer and perform better. What works: 10–20 emails per inbox per day Scale by adding inboxes, not volume That's it!

There are too many outbound email guides full of fluff. But not enough simple step-by-step checklists. So, I built one for you to follow: 🔸 Buy new domains from trusted providers like Google, Outlook, GoDaddy or Maildoso. 🔸 Create multiple inboxes - two per domain. 🔸 Set up SPF, DKIM, and DMARC for email deliverability. 🔸 Warm up your inboxes with a tool like Woodpecker.co (warm-up powered by Mailivery - Land in the Inbox). 🔸 Define your ICP. 🔸 Build a prospect list with Lead Finder in Woodpecker, or tools like Linkedin Sales Navigator Premium, Persana AI or Clay. 🔸 Validate and enrich your contact list. 🔸 Build a strategic sequence in Woodpecker.co. You don’t need fluffy guides - you need actionable steps. Try these 👆

I've sent 100,000+ emails for freight forwarders, and here's what we've learned: your cold emails aren't getting ignored because of a bad message. They're not even reaching the inbox. (let me explain) Deliverability isn't luck. It's infrastructure. And most freight forwarders skip straight to writing emails without building the foundation to actually deliver them. Here are the 8 non-negotiables we follow: 1. Never use your main domain. One spam complaint tanks your entire company's email reputation. 2. Distribute volume across 10+ secondary domains. Set up 20+ mailboxes to keep sending controlled. 3. Authenticate everything. SPF, DKIM, and DMARC aren't optional. Without them, you're flagged by default. 4. Warm up for 2 weeks minimum. Use warm-up tools to build trust gradually. Ramp too fast and you trigger filters. 5. Cap at 50 emails per day per domain. High volume too early = instant red flag. 6. Use Spintax for natural variation. Even subtle changes to messages help avoid repetition triggers. 7. Handle tracking links carefully. Disable them or use a custom tracking domain. Generic links get flagged. 8. Remember, targeting and messaging still matter. Perfect setup means nothing if your list is off or your message is weak. People still have a "Report Spam" button. The reality? Perfect deliverability infrastructure won't save you from bad targeting or weak messaging. But without it, even your best emails have no chance. And If you are still using your own domain and inbox for cold emailing, we need to talk ASAP.

B2B companies spend MILLIONS every year on Cold Email Infra tools. But you don’t need to spend an arm and a leg to get your setup right. We broke it down by budget and maturity so you can build the email infrastructure that scales without wasting a dollar. Your email infra determines: → whether you land in inbox or spam, → how fast you can scale, → and how predictable your sending is. We broke it down by budget & maturity so you can pick the stack that fits you 👇 💰 The $500 Email Infra Stack For founders or new GTM teams testing cold email and messaging. Simple, fast, and keeps your domain reputation clean. 💡 Goal: Test your messaging fast without burning your sender reputation. - Inbox provider: Gmail or Outlook (free domain aliases) - Sending platform: Instantly.ai or Smartlead (1–3 inboxes) - Warm-up / deliverability: Instantly or Smartlead - Verification: ZeroBounce or Bouncer - Domain setup: Namecheap, Inc + Cloudflare - Health monitoring: Free tools (GlockApps free tier, Instantly reports) ⚙️ The $1K Email Infra Stack For growing teams doing consistent outbound and testing multichannel setups. 💡 Goal: Stable deliverability + visibility over what’s actually landing. - Inbox provider: Mailforge - Cold Email Infrastructure 📈 or Zapmail.ai - Sending platform: lemlist or Mailforge built-in - Warm-up / AI monitoring: Mailforge Warm + Clay Signals - Verification: NeverBounce by ZoomInfo + ZeroBounce (bulk clean) - Health & deliverability: MailReach or Mailsuite - Automation: n8n for automated health checks 🚀 The $5K Email Infra Stack For GTM teams sending 100K+ emails/mo, managing multiple brands, or agencies running multi-client setups. 💡 Goal: Predictable deliverability at volume, monitored, automated, and CRM-connected. - Inbox provider: Mailreef, Mailscale, or Inframail (dedicated IPs & servers) - Sending platform: lemlist, Salesforge 🔥, Salesloft, Outreach - Reputation AI: Mailscale’s active recovery + Mailreach premium - Monitoring: Folderly Inc. or Warmbox enterprise - Verification: ZeroBounce + MillionVerifier - Automation: Clay + n8n + HubSpot CRM sync We mapped all three stacks into the visual below. If you want the exact stack we use at SalesCaptain, with our recommended infra providers, comment INFRA below and I’ll send it (i'm terrible at gatekeeping 😂 ) #gtm #coldemail #salesops #emaildeliverability