Email Warm Up Terms: 25 Plain-English Definitions

Email warm-up has 25 terms you need before scaling a mailbox: reputation, authentication, placement, volume, pools and rescue signals. If you ignore the vocabulary, you can raise volume when the right move is to pause. This glossary defines each term, then gives the numbers and checks that matter.

If you want setup steps instead of definitions, start with the free warm-up tool or the email warm-up schedule guide. This page is for reading dashboards, talking to providers, and spotting weak advice before it damages a domain.

What numbers matter first?

Warm-up terms make more sense when you attach them to working thresholds. These are practical ranges, not guarantees. Provider limits change, and inbox placement is never guaranteed.

Google and Yahoo publish sender requirements for authentication, complaints and mailing behaviour. Use primary sources when you manage volume: Google’s email sender guidelines and Yahoo’s sender requirements.

Do not start troubleshooting by raising volume. Check DNS first, placement second, volume third, then complaints and bounces.

Which email warm up terms matter?

1. Email warm-up: The gradual process of sending, receiving, opening and replying to ordinary emails before larger outreach. It helps a mailbox develop normal activity history.

Warm-up cannot fix bad targeting, spammy copy or broken DNS by itself. A good process uses plain text, low volume, replies and steady timing. It should not send links, images or sales pitches through a warm-up network.

2. Sender reputation: The trust attached to a sender identity. It may include the mailbox, domain, IP, complaint history, bounce patterns, sending consistency and recipient engagement.

Sender reputation is not one public score. Gmail, Yahoo, Microsoft and business filters each judge mail differently. Treat it as a set of signals.

3. Domain reputation: The trust attached to your sending domain, such as example.com. It can affect every mailbox on that domain.

A domain with poor history can hurt new mailboxes. A healthy mailbox can also suffer if the domain sends sudden high-volume campaigns or receives many complaints.

4. IP reputation: The trust attached to the server IP that sends the email. It matters most when you send through platforms such as Amazon SES, SendGrid or Mailgun.

Shared IPs can carry mixed history. Dedicated IPs need their own ramp. If you use Gmail, Workspace, Zoho, Yahoo or iCloud, the mailbox provider handles most IP infrastructure.

5. Inbox placement: Where your email lands after delivery. Useful folder labels include Inbox, Primary, Updates, Promotions, Spam, Junk and quarantine.

Delivery only means the receiving server accepted the message. Inbox placement tells you whether the recipient is likely to see it.

6. Spam placement: The share of accepted email that lands in Spam or Junk. Warm-up tools often track this by sending to mailboxes they can inspect.

BobWork measures spam landings directly in receiving mailboxes. It does not use third-party seed lists for that metric.

7. Complaint rate: The share of recipients who mark your mail as spam. This is one of the clearest negative signals.

For Gmail, keep the spam complaint rate under 0.1% and never at or above 0.3%. If complaints rise, reduce volume and fix targeting before changing warm-up settings.

8. Bounce rate: The share of emails rejected or returned as undeliverable. Hard bounces usually mean the address does not exist. Soft bounces are temporary failures, such as throttling or full mailboxes.

High bounce patterns make senders look careless. Verify addresses before campaigns and remove hard bounces quickly.

9. Engagement signals: Recipient actions that suggest wanted mail. Positive signals include replies, opens, moving from Spam to Inbox and continued thread activity.

Do not treat opens as perfect data. Image blocking and privacy features can distort them. Replies and low complaints are stronger signals.

How does authentication fit?

10. SPF: Sender Policy Framework is a DNS TXT record that lists which servers may send mail for a domain. Receivers use it to check whether the sending server is authorised.

SPF is defined in RFC 7208. In practice, your SPF record often includes providers such as Google, Zoho, SendGrid, Mailgun or Amazon SES.

11. DKIM: DomainKeys Identified Mail adds a cryptographic signature to email. The public key sits in DNS. The receiving server checks whether the message was signed and unchanged.

DKIM depends on selectors. Common selectors include google, zmail, default, selector1, selector2, k1, s1, mail, dkim, lark, feishu and zoho.

12. DMARC: Domain-based Message Authentication, Reporting and Conformance tells receivers what to do when SPF and DKIM checks fail alignment. Common policies are none, quarantine and reject.

DMARC is defined in RFC 7489. A p=none policy monitors. Quarantine and reject are stricter. Move to them only after checking legitimate senders.

13. DMARC alignment: The visible From domain must align with the domain authenticated by SPF or DKIM. At least one aligned method must pass for DMARC to pass.

This is where many senders get confused. Passing SPF for a provider domain does not always protect your visible From domain. Alignment connects authentication to what the recipient sees.

14. DNS propagation: The time DNS changes take to become visible across resolvers. Some changes appear quickly. Others take longer because of TTL and caching.

After changing SPF, DKIM or DMARC, verify the record from more than one checker. BobWork checks SPF, DKIM and DMARC daily per domain. You can also use a manual SPF, DKIM and DMARC checklist.

15. Custom tracking domain: A branded domain or subdomain used for click and open tracking links. It keeps tracking infrastructure closer to your sender identity.

Use it carefully. Heavy link tracking can still hurt cold email. For first outreach, plain text and fewer links are usually safer.

Which volume terms control risk?

16. Ramp-up schedule: A planned increase in daily email volume. The goal is to avoid sudden spikes from a new or quiet mailbox.

A ramp is not just more email every day. It should include replies, normal timing and days with lower activity. Weekend volume is often lower than weekday volume.

17. Sending cap: The maximum number of warm-up or campaign emails a mailbox may send each day. Caps prevent accidental overuse.

In BobWork, warm-up starts at 3 emails per day, rises by 2 per day, and caps at 30 per day by default. The cap is editable per mailbox, up to 100.

18. Throttling: A provider or receiving system slows or limits delivery. It can happen after volume spikes, repeated errors, suspicious patterns or policy limits.

Throttling is not always visible as a clean bounce. You may see delayed mail, temporary errors or reduced placement. Check the provider’s current limits instead of guessing.

19. Sending window: The hours when emails are sent. Normal business-hour sending looks more natural than constant 24-hour sending.

BobWork spreads sends across 09:00–18:00 in the mailbox’s own time zone. It decides every 15 minutes with randomness, and weekends run at 30% volume.

20. Cold email volume: The number of prospecting emails sent from a mailbox each day. Warm-up volume and campaign volume should be planned together.

For cold outreach, a typical safe range is 30–50 real emails per day per mailbox. If you need more volume, add mailboxes and domains rather than forcing one sender harder. See how many cold emails per day is safe for a fuller plan.

How do pools and seeds differ?

21. Warm-up network: A group of mailboxes that exchange warm-up emails. The network creates sending, receiving and reply activity between participating inboxes.

A network should control the content. If users can write arbitrary warm-up emails, they can push links, spam or risky wording through other inboxes. Learn more in the email warm-up network guide.

22. Shared pool: A warm-up pool where mailboxes from different accounts exchange warm-up emails. This gives one mailbox enough peers to start without owning many inboxes.

BobWork uses a shared warm-up network by default. The free pool does this step automatically with short office-style messages, no links, no images and plain text.

23. Private pool: A warm-up pool where only your own mailboxes write to each other. It gives more control over who receives your warm-up mail.

Private pools need at least two mailboxes. In BobWork, any account can switch to a private pool from Mailbox pool → Pool mode. For the trade-offs, read private pools vs public networks.

24. Seed list: A fixed set of test inboxes used to measure placement. You send to the list, then check whether mail lands in Inbox, Promotions, Spam or another folder.

Seed lists are diagnostic tools. They do not create normal reply history by themselves. Use them to test placement, not as a replacement for real mailbox activity.

25. Spam rescue: The process of finding warm-up mail in Spam, moving it to Inbox, marking it read, and treating it as wanted mail.

Spam rescue must be narrow. BobWork only touches mail carrying its own hidden engine header, or a known subject for Zoho API senders. Real mail is never read, moved or answered.

A healthy warm-up system should show authentication status, warm-up volume, spam placement, mailbox errors and readiness. It should also stop or warn you when logins fail.

BobWork uses a 0–100 health score. Healthy is 85 or higher. Watch is 60–84. At risk is below 60. Blocked means login or permission failed.

The readiness gate is stricter than a calendar date. A mailbox is ready for outbound after 14 or more days warming, a 7-day spam rate of 10% or less, and at least 30 warm-up emails received.

For first-time setup expectations, use what to expect during email warm-up. For new domains, use the new domain warm-up plan.

What should you check now?

Use this checklist before you send the next campaign. It turns the glossary into an operating routine.

Do not skip DNS checks. Many reputation problems are authentication problems. A missing DKIM record or misaligned DMARC policy can make every other fix look ineffective.

The practical order is simple: authenticate the domain, warm the mailbox, monitor placement, then add campaign volume slowly. If a metric turns red, reduce pressure before you change copy, tools or providers.

BobWork Email Warm-up is free for up to 10 mailboxes per account, with no card and no time limit. It supports Gmail and Google Workspace, Zoho Mail, Lark Mail, Yahoo Mail, iCloud Mail, Amazon SES, SendGrid, Mailgun and any IMAP+SMTP mailbox. Outlook and Microsoft 365 are not supported yet.

Google users may see an unverified-app notice because BobWork has not completed the CASA audit. If you prefer, use IMAP with an app password where your provider supports it.

Start with one mailbox in the shared warm-up network, or switch to a private pool per account if you prefer. Then use the terms above to read the dashboard correctly before sending real outreach.

Frequently asked questions