Email Infrastructure Provider: The Complete Guide for Cold Email

An email infrastructure provider supplies the mailboxes, domains, IPs, and authentication systems that let you send email at scale. For cold email, this means Google Workspace or Microsoft 365 accounts configured for outbound prospecting, with dedicated sending IPs, automated DNS (SPF/DKIM/DMARC), and administrative access so you own your infrastructure outright.

What is an email infrastructure provider?

An email infrastructure provider handles the technical foundation of sending email: mailboxes, sending servers, IP addresses, domain authentication, and the systems that make messages reach inboxes. The term covers different things depending on the use case.

Transactional email infrastructure

Services like AWS SES, SendGrid, Postmark, and Mailgun provide APIs and SMTP relays for application-generated email, such as password resets, receipts, and notifications. These are built for high volume, low touch, and developer integration.

Marketing email infrastructure

Platforms like Mailchimp, Klaviyo, and HubSpot combine sending infrastructure with campaign tools, list management, and analytics. Infrastructure is bundled into the marketing platform.

Cold email infrastructure

Specialized providers supply mailboxes specifically for outbound prospecting. The key differences are genuine Google Workspace or Microsoft 365 accounts (not shared SMTP), dedicated sending IPs, proper DNS authentication, and full administrative ownership. This is what Inboxlogy provides.

The rest of this guide covers cold email infrastructure: what to look for, how to evaluate providers, and how to avoid common traps.

Why does cold email infrastructure matter?

Cold email deliverability is 80% infrastructure, 20% copy. You can write the perfect message, but if it sends from a poorly authenticated domain on a flagged IP, it lands in spam. The infrastructure layer determines:

• Inbox placement: Google and Microsoft filter based on domain reputation, IP reputation, and authentication signals. Proper infrastructure gets you to Primary; bad infrastructure gets you to spam or blocks entirely.
• Sending capacity: How many emails you can safely send per day per mailbox without triggering rate limits or spam flags.
• Sustainability: Whether your sending reputation holds up over weeks and months of continuous outreach, or degrades as complaints accumulate.
• Recovery options: When something goes wrong, whether you can isolate the problem, swap infrastructure, and keep campaigns running.

Teams that treat infrastructure as an afterthought burn through domains and waste campaigns on low deliverability, and eventually hit a wall that no copy optimization can fix. Teams that build proper infrastructure from the start scale smoothly.

What features should an email infrastructure provider have?

Twelve questions separate real cold email infrastructure from disposable accounts.

1. Mailbox type

Is it genuine Google Workspace or Microsoft 365? Some providers use Azure/Entra inboxes (a different product with different deliverability), private SMTP servers (a red flag for cold email), or recycled and aged accounts (inconsistent quality). For cold email to business addresses, genuine Google Workspace and Microsoft 365 have the best deliverability because recipients already trust them.

2. Ownership and admin access

Do you get full admin access to the tenant? Can you add users, modify domains, change passwords, and move billing directly to Google or Microsoft if you leave? If you're renting access to someone else's tenant, you have no control and no exit path.

3. Dedicated sending IPs

Are you on dedicated US and EU IPs, or shared pools? On shared IPs, your reputation is affected by other senders' behavior. When someone else on that IP spams, your deliverability drops. Dedicated IPs give you control.

4. DNS automation

Is SPF, DKIM, DMARC, and MX configured automatically? Manual DNS setup is error-prone at scale, and a single typo breaks authentication. Good providers automate this completely.

5. API access

Can you provision and manage mailboxes programmatically? For agencies and teams scaling across clients, API access is essential. Manual ordering and setup doesn't scale.

6. Tool compatibility

Does it connect to your sending tools via OAuth, app password, or IMAP? Most cold email tools (Instantly, Smartlead, ReachInbox, Woodpecker) work with any standard mailbox, but verify before you buy.

7. Warmup integration

Where does warmup run? Good infrastructure providers hand off to your sending tool for warmup, where you control it. Inboxlogy does not run warmup; warmup runs in whatever sending tool you connect the mailboxes to.

8. Pricing transparency

Per-mailbox pricing? Volume tiers? Setup fees? Annual commitments? Hidden costs? Good providers publish clear per-mailbox rates with no surprises.

9. Minimum orders

Can you buy a single mailbox, or are you forced into packages? 10-mailbox minimums are common but unnecessary; they exist to increase order size, not because there's a technical reason.

10. Domain handling

Can you bring your own domains? Are domains included or separate? What TLDs are supported? Good providers work with any registrar and any TLD.

11. Support and SLAs

What's the response time? Is there human support? What happens when something breaks on a Friday afternoon?

12. Exit terms

What happens when you leave? Can you take your mailboxes with you? If the answer is "no," you're renting infrastructure, not owning it.

What compliance requirements apply to cold email infrastructure?

Mailbox providers have tightened requirements significantly since 2024. Failing to meet these gets your mail filtered or rejected.

Google and Yahoo (February 2024)

• SPF or DKIM must pass on every message. In practice, configure both.
• DMARC published on the sending domain (at least p=none).
• Valid PTR records on sending IPs (handled by Google/Microsoft for their mailboxes).
• Spam complaint rate under 0.3% as measured in Google Postmaster Tools. Google recommends staying under 0.1%; treat that as your ceiling.
• One-click unsubscribe for bulk senders (5,000+ messages/day to a single provider). Most cold email doesn't hit this volume to a single provider, but the same signals still affect filtering.

Microsoft (May 2025)

• Similar authentication requirements: SPF, DKIM, DMARC.
• Microsoft's consumer domains (outlook.com, hotmail.com, live.com) now enforce stricter filtering.
• Corporate Microsoft 365 tenants run Exchange Online Protection with tenant-specific rules. Your deliverability depends partly on each recipient company's configuration.

A proper email infrastructure provider configures all authentication automatically and provides infrastructure that meets these requirements out of the box.

How do you evaluate email infrastructure providers?

Use this checklist when comparing providers.

Verification questions

• Ask for a demo account. Log into a mailbox. Check the admin panel. Verify you have full control.
• Check IP ranges. Ask what IPs you'll be sending from. Look them up in blacklist databases. Verify they're dedicated, not shared.
• Test authentication. Send a test email to a personal Gmail account. Open the message, click "Show original," and verify SPF, DKIM, and DMARC all show PASS.
• Ask about exit. "If I leave in 6 months, do I keep my mailboxes?" If the answer involves transferring or losing anything, you don't own the infrastructure.
• Verify partner status. Ask them to show Google Partner or Microsoft Partner credentials on a live call. Legitimate partners can show this instantly.

Red flags

• Can't explain what type of mailboxes they provide (Google vs Microsoft vs SMTP).
• Pricing too low to be real ($0.50/mailbox usually means shared infrastructure or recycled accounts).
• No admin access to the mailbox tenant.
• Forced annual contracts or large upfront payments.
• No API or automation options.
• Reviews mentioning deliverability issues or account suspensions.

How do you migrate to a new email infrastructure provider?

Switching providers without losing deliverability requires planning.

What transfers

• Domains: You own these. Update DNS to point to the new provider's authentication records.
• Domain reputation: Partially transfers with the domain. If a domain is already burned, moving it doesn't fix it.

What doesn't transfer

• Mailbox warmup: New mailboxes on a new provider need fresh warmup, even if the domain is aged.
• IP reputation: You'll be on new IPs with the new provider.
• Sending history: Campaign data stays with your sending tool, but mailbox-level reputation resets.

Migration process

1. Provision new mailboxes with the new provider on your existing domains (or new secondary domains).
2. Update DNS authentication records (SPF, DKIM, DMARC) to include the new provider.
3. Start warmup on new mailboxes (3-4 weeks for Google, 4-6 weeks for Microsoft).
4. Gradually shift sending volume from old to new infrastructure.
5. Once new infrastructure is stable, retire old mailboxes.

Plan migrations during low-volume periods. Don't cut over everything at once.

How do agencies scale cold email infrastructure?

Agencies running campaigns across multiple clients have specific infrastructure needs.

Client isolation

Each client should have separate domains and mailboxes. One client's reputation issue shouldn't affect another's campaigns. This means separate workspaces, not shared tenants.

Volume requirements

• Small client (500 sends/day): ~20 mailboxes across 7-10 domains
• Medium client (2,000 sends/day): ~80 mailboxes across 25-30 domains
• Large client (5,000 sends/day): ~200 mailboxes across 70-80 domains

API provisioning

At agency scale, manual ordering doesn't work. You need API access to provision, configure, and manage mailboxes programmatically. Inboxlogy provides a full API for this use case.

Monitoring

Track warmup scores, bounce rates, and deliverability metrics per client. Catch problems before they spread. Rotate out underperforming domains before they burn completely.

Frequently asked questions

What's the difference between an email infrastructure provider and an ESP?

An ESP (Email Service Provider) typically combines infrastructure with campaign tools, think Mailchimp or HubSpot. An email infrastructure provider focuses on the underlying mailboxes, IPs, and authentication, leaving campaign management to specialized tools like Instantly or Smartlead. For cold email, you usually want separate infrastructure (owned mailboxes) plus a dedicated cold email tool.

Can I use AWS SES or SendGrid for cold email?

Technically yes, but they're not designed for it and will likely suspend you. AWS SES and SendGrid are built for transactional email (password resets, receipts) from applications. Their terms of service typically prohibit cold outreach, and their abuse detection will flag prospecting patterns. Use them for what they're built for, and use dedicated cold email infrastructure for outbound.

How much should cold email infrastructure cost?

Genuine Google Workspace or Microsoft 365 mailboxes from a specialized provider typically run $2.50-$4.00 per mailbox per month at volume. Direct from Google or Microsoft costs $6-$12 per seat. Sub-$1 options usually mean Azure inboxes, private SMTP, or shared infrastructure, which are different products with different deliverability. Domains cost $8-$15/year each, separate from mailboxes.

What's the difference between Google Workspace and Microsoft 365 for cold email?

Both work well. Google Workspace tends to have slightly better deliverability to Gmail recipients (Google-to-Google trust), better warmup pool coverage, and smoother OAuth integration with most cold email tools. Microsoft 365 has advantages when targeting enterprise companies on Microsoft 365 (Microsoft-to-Microsoft trust). Most teams run 70-80% Google and 20-30% Microsoft for diversification.

Do I need dedicated IPs for cold email?

Strongly recommended. On shared IPs, your sender reputation is affected by other users' behavior. If someone else on that IP sends spam, your deliverability suffers. Dedicated IPs give you full control over your reputation. The main providers (Google Workspace, Microsoft 365) use shared pools by default, but specialized infrastructure providers like Inboxlogy can provision on dedicated US and EU IPs.

How long does it take to set up cold email infrastructure?

With a good provider, ordering and provisioning takes about 10 minutes. DNS propagation takes up to 48 hours, usually faster. Warmup takes 3-4 weeks for Google, 4-6 weeks for Microsoft. Plan on about a month from order to first campaign if starting from scratch.

What happens if my infrastructure provider shuts down?

This depends entirely on ownership structure. If you have full ownership and admin access to your mailboxes (as Inboxlogy provides), your mailboxes keep functioning; you just need to manage them directly or connect a different management service. If the provider retained control of your accounts, you may lose access entirely when they shut down. Ownership is insurance against provider risk.

How do I verify a provider is legitimate?

Ask them to show their Google Partner or Microsoft Partner portal on a live call. Genuine partners can show this instantly. Also test a mailbox yourself: send an email to your personal Gmail, click "Show original," and verify SPF, DKIM, and DMARC all pass. Check the IP reputation in blacklist lookup tools. Ask about exit terms; if you can't take your mailboxes when you leave, you don't really own them.