Cloud Server for Email
cloudserverforemail.com · infrastructure@cloudserverforemail.com · +372 602 3545
EU-Based Infrastructure
Operating Since 2015
Operating Since 2015
Cold Email Infrastructure Setup Checklist
B2B Cold Outreach — Infrastructure Requirements
Version 2026-04 · Cloud Server for Email
Cold email infrastructure MUST be completely isolated from marketing infrastructure. Shared IPs contaminate warm IP reputation.
Domain Setup
- Dedicated sending subdomain for cold email (NOT primary business domain)
- Domain is 30+ days old before first cold send
- Domain has website or redirect (not a parked domain)
- SPF configured for cold sending IPs only
- DKIM: 2048-bit key, unique selector separate from marketing
- DMARC: p=none minimum with rua reporting
- PTR/rDNS configured for all cold sending IPs
IP Infrastructure
- Dedicated IPs: never used for marketing, never shared with warm IPs
- 1 IP per 200–500 cold emails/day (conservative)
- IP warming: start 10–20 emails/day, grow slowly over 4–6 weeks
- Separate PowerMTA virtual MTA pool for cold IPs
Daily Volume Limits by Week
| Week | Max/Domain/Day | Max/IP/Day |
|---|---|---|
| 1–2 | 20–50 | 10–20 |
| 3–4 | 50–100 | 25–50 |
| 5–8 | 100–200 | 50–100 |
| Production | 200–500 | 100–250 |
Compliance Checklist
- Every email includes: company name, physical address, unsubscribe mechanism
- Unsubscribe honored within 10 business days (CAN-SPAM)
- B2B only — EU consumer cold email requires consent
- Recipient role relevant to your product/service
- No purchased consumer lists; no scraped lists
- Canadian recipients: CASL implied consent applies (verify relationship)
List Quality
- All addresses validated before sending (email verification service)
- Individual professional emails only (no info@, sales@, noreply@)
- List freshness: verify lists older than 6 months before use
- Remove non-responders after 3 touches
Monitor Google Postmaster Tools daily for the cold domain. Spam rate >0.05% requires immediate volume reduction.