Help center

How can we help?

Answers to the questions we hear most. If you have an account and cannot find yours here, open a ticket and we’ll reply directly.

Getting started

Stand up domains, mailboxes and warming without guessing the order.

Domains

Register, bring your own, or claim aged inventory. Authentication is written for you.

Mailboxes

Provision senders, pull SMTP/IMAP credentials, and read replies in one inbox.

Pre-warmed inboxes

Leased inboxes on 90-day domains that already finished warming, with measured placement attached.

Pre-warmed Mailboxes by EmailPal

This article covers everything you need to know about EmailPal's pre-warmed mailboxes. Learn how they work, what measured placement means, how pricing and the 90-day term work, and how to start sending 15 cold emails a day from day one.

Pre-Warmed Domains and Accounts

Pre-warmed domains and accounts on EmailPal are leased mailboxes on 90-day-aged domains that already finished warming, with SPF, DKIM and DMARC in place and a measured inbox-placement rate attached. Ready to send 15 cold emails a day from day one.

What "pre-warmed" means

A plain-language definition of pre-warmed mailboxes and domains, and how EmailPal's version differs from an address that is merely aged, merely warmed, or a rented Google seat.

Pre-warmed vs fresh mailboxes

Fresh mailboxes are new domains and inboxes you provision and warm yourself. Pre-warmed mailboxes are already aged, authenticated and placement-tested. EmailPal sells both: register or BYO plus $0.60 warming, or lease pre-warmed inventory at $3/mo.

Pre-warmed vs email warmup

Email warmup builds reputation on a mailbox you already have. Pre-warmed mailboxes have already finished that ramp. EmailPal warmup is $0.60/mo; pre-warmed leases are $3/mo with warming included and 15 cold emails a day from day one.

How to claim pre-warmed inboxes

Step-by-step instructions for leasing pre-warmed inboxes from the EmailPal dashboard, the REST API and the MCP server.

Pre-warmed billing and the 90-day term

$3 per inbox per month, 90-day minimum, no double warming charge, and what releasing an inbox does to the invoice.

Warming

Real conversations with Gmail, Yahoo and AOL. Campaign-ready is a measured inbox rate, not a calendar date.

Email warming by EmailPal

How EmailPal warming works: $0.60 per inbox per month, real Gmail, Yahoo and AOL seed accounts, placement-graded graduation, spam rescue and weekend throttling. Campaign-ready is a measured inbox rate, not a calendar date.

What is email warmup and how it works

Email warmup explained: why new mailboxes get filtered, what a ramp is, how providers actually learn, and how EmailPal decides a mailbox is ready using measured inbox placement rather than a 14-day timer.

When is a mailbox ready to send?

An EmailPal mailbox is ready for cold email when warming reports campaign-ready placement — not after a fixed number of days. Pre-warmed leases skip that wait and can send 15 emails a day as soon as you claim them.

Enable, pause or resume warming

How to turn EmailPal warming on or off per mailbox, what pause does to the ramp, and how Slow-Ramp differs from paused.

Troubleshooting failed warmup

Warming fails when authentication is wrong, the mailbox cannot send or receive, placement stays in spam, or a bounce trips an automatic hold. This page is the EmailPal checklist — not a calendar wait.

Campaign-ready vs a number of days

EmailPal calls a mailbox campaign-ready from measured inbox placement, not from a 14-day timer. Typical times are still 14+ days (7 on aged domains). This is the metric behind "when can I send?"

Do warmup emails count toward sending limits?

Warmup messages are separate from your cold-email cap. EmailPal's 40/day plan limit and 15/day pre-warmed limit count campaign mail, not the warming conversations running in the background.

Warmup bounce and disabled warmup

If a warmup message bounces, EmailPal can disable warming on that mailbox so we stop hitting a broken address. Fix authentication, credentials or the mailbox itself, then resume.

Warm Gmail, Outlook or your own server

EmailPal warming is priced per inbox, not per host. Connect Google, Microsoft 365 or any SMTP/IMAP mailbox for $0.60/mo and the same seeds.

DNS and authentication

SPF, dual DKIM, DMARC p=reject and MX — written automatically and re-verified against public resolvers.

How to Set Up DNS Records (MX, SPF, DKIM, DMARC)

EmailPal writes MX, SPF, dual DKIM and DMARC p=reject for you, then re-verifies them on public resolvers. This page is the full setup guide: what each record does, what we publish, BYO copy-paste rules, and how to debug a red check.

SPF, DKIM, DMARC and MX

What EmailPal writes for SPF, dual DKIM, DMARC p=reject and MX, why we re-verify against public resolvers, and what to do when a check fails. This is the primer; the setup walkthrough is the Instantly-titled DNS article.

What is SPF?

SPF (Sender Policy Framework) is a DNS TXT record that lists which servers may send email for your domain. EmailPal publishes a hard-fail SPF that includes our sending hosts, then re-verifies it publicly.

What is DKIM?

DKIM (DomainKeys Identified Mail) is a cryptographic signature on each message. EmailPal publishes two keys per domain — RSA-2048 and Ed25519 — and signs outbound mail with them.

What is DMARC?

DMARC tells receivers what to do when SPF or DKIM fail, and whether the From domain aligns. EmailPal sets p=reject on sending domains so unauthenticated mail claiming to be you is not delivered.

DNS verification failed

What a failed SPF, DKIM, DMARC or MX check means, why we query public resolvers, and how to fix BYO domains.

DKIM not validating

DKIM fails when a selector TXT is missing, truncated, still propagating, or looking up against the wrong nameserver. EmailPal publishes rsa._domainkey and ed._domainkey and re-checks both on public resolvers.

Why DMARC is p=reject

EmailPal sets DMARC p=reject on sending domains so unauthenticated mail is refused. Why we do not offer p=none for hosted sending.

List verification

Catch-all detection by SMTP probing. Six verdicts, nothing ever delivered.

Deliverability

Sending limits, IP pools, domain reputation and what to do when a list or a mailbox misbehaves.

Cold email deliverability guide

The EmailPal deliverability checklist: authenticate the domain, warm or lease pre-warmed mailboxes, keep volume per inbox modest, verify the list, and treat placement as a measurement. This is the page for why cold email goes to spam and what to do about it.

Why emails go to spam

Cold email lands in spam when the domain is unknown or burned, authentication fails, the list bounces, volume per mailbox is too high, or the copy matches a spam fingerprint. Fix infrastructure first, then the list, then the send pattern.

Sending limits per mailbox

Default cold-email caps: 40 per day on plan mailboxes, 15 per day on pre-warmed leases, and why more volume means more inboxes not a higher cap. Warming traffic does not count.

Isolated IP pools

EmailPal runs four isolated IP pools so one customer's list does not define another customer's reputation. Dedicated IPs are $20/mo on Growth and Scale.

IP and domain blacklists

A listing on Spamhaus or a similar DNSBL can reject mail even when SPF and DKIM pass. Check the domain and the sending IP, request delisting only if the listing is real, and do not keep sending through a listed name.

What are sender bounces?

A sender bounce means the sending mailbox was rejected — quota exceeded, mailbox disabled, authentication failed — not that the recipient was invalid. Fix the sender before you resume volume.

How to check and improve your domain reputation

What domain reputation is, how EmailPal's authentication and warming affect it, and what to do if placement drops. Age is not reputation; measured conversations are.

Secondary sending domains for cold email

Send cold email from domains you own that are not your primary company website. EmailPal will register or host those secondary domains, authenticate them, and warm the mailboxes so a bounce storm does not take down acme.com.

Google and Yahoo sender requirements

Gmail and Yahoo require authenticated mail (SPF, DKIM, DMARC), one-click unsubscribe for bulk, and a low spam-rate. EmailPal writes SPF, dual DKIM and DMARC p=reject on hosted domains. You still owe a clean list and an unsubscribe story in the sequencer you connect.

API and MCP

The same operations as the dashboard, over REST and a Model Context Protocol server.

Billing

Plans, mailbox overage, warming, pre-warmed leases and how a month is billed.

Account

Support, passwords and the rules that keep the sending pools clean.