Warm Up iCloud Email: Settings, DNS and 14-Day Ramp

Warm up iCloud Mail for at least 14 days, starting at 3 emails per day and adding 2 per day until the mailbox reaches the 30/day cap. If you send campaigns before authentication, connection and spam signals are stable, receiving providers can treat the mailbox as risky. This guide gives the exact settings, DNS checks, ramp and fixes.

BobWork Email Warm-up supports iCloud Mail through IMAP and SMTP with an Apple app-specific password. You can use the free warm-up tool for up to 10 mailboxes with no card, then check SPF, DKIM and DMARC before adding real outbound. If this is your first mailbox, read what to expect during first-time warm-up before you connect it.

What does iCloud Mail need?

Treat iCloud Mail as two separate checks.

First, the mailbox must allow a third-party app to send and read warm-up mail. For iCloud Mail, that means IMAP, SMTP and an Apple app-specific password. Your normal Apple ID password is not the right credential.

Second, receiving providers judge the mail you send. They look at authentication, sending consistency, recipient engagement, spam placement, bounces and complaint signals. iCloud does not publish a warm-up score, so you need to watch these signals directly.

For an @icloud.com, @me.com or @mac.com address, Apple controls the sending domain. You do not add SPF, DKIM or DMARC records for those domains.

For a custom domain hosted on iCloud Mail, you must add the DNS records Apple gives you. Do not copy old DNS values from a blog. Use Apple’s current custom-domain setup screens.

Warm-up builds a normal sending pattern before campaigns. It does not fix bad targeting, purchased lists or misleading copy. If real recipients ignore, delete or report the mail, warm-up will not hide that.

For broader volume planning, use the email warm-up schedule guide or generate a plan with the warm-up schedule generator.

How do you connect iCloud?

Use the iCloud Mail preset in BobWork. It uses IMAP for receiving, SMTP for sending and an Apple app-specific password for authentication.

Apple documents both app-specific passwords and mail server settings for third-party clients. Use those pages if Apple changes the account flow.

Create the app password

Sign in to your Apple account and create an app-specific password for the warm-up connection. Name it something clear, such as BobWork warm-up.

Copy the generated password immediately. It is not the same as your Apple ID password. If you lose it, revoke it and create a new one.

Add the mailbox

Open BobWork Email Warm-up and add a mailbox. Choose the iCloud Mail preset.

Enter the full iCloud email address as the username. Paste the app-specific password into the password field. The preset supplies the IMAP and SMTP hosts, ports and security modes.

Save the mailbox and let the connection test run. A good setup must pass both receiving and sending. IMAP proves the warm-up engine can find its own messages. SMTP proves it can send from the mailbox.

Choose the pool mode

BobWork uses a shared warm-up network by default. Your active mailbox exchanges warm-up messages with other active mailboxes on the service, across accounts. One mailbox is enough to start.

If you prefer isolation, switch to a private pool in the dashboard under Mailbox pool → Pool mode. In private mode, only your own mailboxes write to each other. A private pool needs at least two mailboxes.

The free pool handles the recurring work automatically: short plain-text office notes, some replies, spam rescue for its own warm-up mail and archive after 24 hours. Only mail carrying the engine’s own hidden header is touched. Real mail is never read, moved or answered.

Which DNS records matter?

DNS depends on the domain in your From address.

If you send from an Apple-owned address such as name@icloud.com, Apple manages authentication for that domain. Your job is to connect with the correct app-specific password and keep volume conservative.

If you send from a custom domain on iCloud Mail, add the records Apple shows for that domain. Apple documents custom email domains for iCloud Mail.

SPF authorises the sending source. DKIM signs messages with your domain. DMARC tells receivers how to evaluate SPF and DKIM alignment. For cold outreach from a custom domain, all three should be present before you raise volume.

Do not create multiple SPF TXT records at the root. That often breaks SPF evaluation. Merge providers into a single SPF record, then remove the duplicate.

Do not move DMARC straight to a strict policy until you have checked every legitimate sender. A strict policy can reject real mail if another service is not authenticated correctly.

If your iCloud custom domain is new, use the SPF, DKIM and DMARC checklist for cold email before you send campaigns.

How do you warm up iCloud email?

The default BobWork ramp starts at 3 warm-up emails per day, adds 2 per day and caps at 30 per day. Weekends run at 30% volume. Sends are spread across 09:00–18:00 in the mailbox’s own time zone, with randomness.

The table shows the weekday target. If a day falls on a weekend, expect about 30% of that number.

BobWork measures spam rate as the share of a sender’s warm-up mail that receiving mailboxes found in Spam over the last 7 days. It does not use third-party seed lists.

A mailbox is ready for outbound when it has warmed for 14+ days, has a 7-day spam rate of 3% or lower and has received at least 30 warm-up emails. If one of those is missing, wait.

For a new domain, use 3–4 weeks instead of stopping at day 14. New domains have less history, and DNS plus engagement signals need more time to settle. The guide on warming up a new domain gives a slower plan.

How do you fix iCloud blocks?

Most iCloud connection problems come from credentials, port settings or account security. Fix those before you assume the mailbox is blocked.

If SMTP passes but mail lands in spam, do not keep raising volume. Check DNS, reduce real outbound and let warm-up continue. For a custom domain, verify that SPF, DKIM and DMARC all pass.

If the mailbox shows a blocked or permission-failed health status, reconnect it. A revoked app-specific password will break access. Changing Apple account security settings can also break the connection.

If you use an iCloud custom domain, avoid routing the same domain through several senders without a plan. Every sender must be covered by SPF where needed. Every sender should sign with DKIM where supported. DMARC should align with the From domain.

For broader spam placement causes, use the guide on why emails go to spam. It covers list quality, copy, links, attachments and mailbox history.

Do this now

Use this checklist before you send any cold campaign from iCloud Mail.

Do not skip DNS checks for a custom domain. They take a few minutes and prevent hours of false diagnosis later.

Do not start with links, images and attachments in your first campaigns. Plain text is easier to evaluate. Add complexity after the mailbox has a stable sending pattern.

Do not treat warm-up as permission to send to poor lists. If the list is stale, scraped or irrelevant, real recipient behaviour will still hurt you.

When is iCloud ready?

A warmed iCloud mailbox should meet three conditions at the same time: enough time, enough received warm-up mail and low spam placement.

In BobWork, the ready gate is 14+ days warming, 7-day spam rate at or below 3% and at least 30 warm-up emails received. Use that as the minimum for an existing mailbox. For a new domain, wait closer to 3–4 weeks.

When you start real outbound, stay conservative. A typical cold outreach range is 30–50 emails per mailbox per day. If you need more volume, add mailboxes instead of forcing one iCloud account to carry the campaign.

Keep warm-up active while campaigns run. A background level of 10–15 warm-up emails per day is enough for many mailboxes. If replies fall, bounces rise or spam placement gets worse, pause and fix the cause before increasing volume.

You can set up iCloud Mail in BobWork Email Warm-up with the iCloud Mail preset, an Apple app-specific password and the ramp above. Use the shared warm-up network by default, or switch to a private pool per account if you prefer. Then verify DNS and wait for the ready signals before sending campaigns.

Frequently asked questions