Guides

# Warming Up Mailboxes

Warmup is the process of gradually increasing email volume from a new mailbox so that receiving servers build trust in it. Mission Inbox’s **Premium warm-up** powers mailbox warmup — a 14-day automated process you can start immediately after creating a mailbox.

## Why Warmup Matters

New mailboxes have no sending reputation

Receiving servers like Gmail and Outlook track sending history. A brand-new address sending large volumes on day one looks like spam. Warmup builds that history gradually.

Domain reputation is separate from IP reputation

Even on Mission Inbox's established shared infrastructure, your domain and mailbox reputation is unique to you and must be earned independently.

Early damage is hard to undo

A mailbox that gets flagged in its first week can take months to recover. 14 days of automated warmup is a small investment for reliable long-term delivery.

## How It Works

Mission Inbox uses **Premium warm-up**, running in Mission Inbox’s own **private warmup pool**. When you enable warmup on a mailbox, Mission Inbox registers it as a sender email in that pool, which starts sending and receiving low-volume emails between real mailboxes. These genuine interactions signal to receiving servers that the address is legitimate.

1

Enable warmup via the API.

2

Mission Inbox registers your mailbox with Premium warm-up.

The call returns once registration is done, with syncStatus synced.

3

Premium warm-up exchanges emails with other mailboxes daily.

warmedDays increments each active day.

4

After 14 warmed days, the mailbox is ready for full production sending.

## Step 1 — Enable Warmup

Warmup is available **immediately after creating a mailbox** — no additional setup required. Send `POST /api/warmup/mailboxes/:email` with `enabled: true`. Mission Inbox registers the mailbox with Premium warm-up automatically.

cURL

```bash
curl -X POST "https://api.v4.missioninbox.com/api/warmup/mailboxes/hello@yourdomain.com" \
  -H "X-Server-API-Key: miacme_4eC8vKmN2pQrStUwXyZaB6dEfGhIjLoPqRsT9uVwX1b" \
  -H "Content-Type: application/json" \
  -d '{
    "enabled": true
  }'
```

Response

```json
{
  "success": true,
  "message": "Warmup enabled successfully",
  "mailboxId": "hello@yourdomain.com",
  "enabled": true,
  "syncStatus": "synced",
  "lastSyncedAt": "2026-01-21T00:00:04.000Z",
  "stateChanged": true
}
```

The call waits for Premium warm-up, so a success returns `syncStatus: "synced"`. A failed registration returns an error, and the GET status endpoint then shows `error` with a `syncErrorMessage`. Enabling is refused with `409` while warmup is paused on the account.

## Step 2 — Monitor Progress

Poll `GET /api/warmup/mailboxes/:email` to track warmup progress. `warmedDays` increments once per day that the warmup network is actively running.

cURL

```bash
curl "https://api.v4.missioninbox.com/api/warmup/mailboxes/hello@yourdomain.com" \
  -H "X-Server-API-Key: miacme_4eC8vKmN2pQrStUwXyZaB6dEfGhIjLoPqRsT9uVwX1b"
```

Response

```json
{
  "success": true,
  "mailbox": {
    "email": "hello@yourdomain.com",
    "warmupStartDate": "2026-01-21T00:00:00.000Z",
    "warmedDays": 8,
    "totalWarmedDays": 8,
    "isWarmupActive": true
  },
  "emailBisonWarmup": {
    "senderEmailId": 25063,
    "syncStatus": "synced",
    "lastSyncedAt": "2026-02-20T08:00:00.000Z",
    "syncErrorMessage": null,
    "createdAt": "2026-01-21T00:00:00.000Z",
    "updatedAt": "2026-02-20T08:00:00.000Z"
  },
  "emailBisonWarmupStats": {
    "warmupEmailsSent": 312,
    "warmupRepliesReceived": 288,
    "warmupEmailsSavedFromSpam": 4,
    "warmupScore": 94,
    "warmupBouncesReceivedCount": 0,
    "warmupBouncesCausedCount": 0,
    "warmupDisabledForBouncingCount": 0,
    "startDate": "2026-02-11",
    "endDate": "2026-02-20"
  },
  "eventHistory": [
    {
      "id": "evt-abc",
      "action": "ENABLE",
      "status": "SUCCESS",
      "createdAt": "2026-01-21T00:00:00.000Z"
    }
  ]
}
```

| Field           | Meaning                                                                                                     |
| --------------- | ----------------------------------------------------------------------------------------------------------- |
| warmedDays      | Days warmed in the current active session.                                                                  |
| totalWarmedDays | Cumulative across all sessions — retained even if warmup was paused and re-enabled.                         |
| isWarmupActive  | false means warmup is currently disabled.                                                                   |
| syncStatus      | synced = registered with Premium warm-up · error = the last enable or disable failed (see syncErrorMessage) |

## Warmup Timeline

The full warmup cycle is **14 days**. Use `warmedDays` as a guide for how much production sending is safe at each stage.

| Warmed Days | Approx. daily volume | Recommendation                                 |
| ----------- | -------------------- | ---------------------------------------------- |
| 0 – 3       | 10 – 50 emails       | Don't send production email yet.               |
| 4 – 7       | 50 – 200 emails      | Suitable only for small, highly engaged lists. |
| 8 – 13      | 200 – 1 000 emails   | Good for opt-in transactional email.           |
| 14+         | 1 000+ emails        | Ready for full production sending.             |

These are guidelines, not hard limits. Safe sending volume also depends on your domain age, content quality, and how engaged your recipient list is.

## Tips

Don't disable warmup mid-cycle

Pausing resets momentum with receiving servers. Leave warmup running continuously for the full 14 days.

Production sending and warmup can run simultaneously

You can send real email while warmup is still active. Just keep production volume within the guidelines for your current warmedDays stage.

Check syncStatus if warmup looks stuck

If warmedDays stops increasing, check syncStatus on the status endpoint. error means the last enable or disable failed, and syncErrorMessage says why.

Warmup doesn't replace good sending practices

A warmed mailbox sending spammy or irrelevant content will still get flagged. Warmup builds infrastructure trust — you still need engaged recipients and clean lists.

[PreviousSMTP & IMAP Setup](https://doc.v4.missioninbox.com/sales/guides/smtp-imap.md)[NextWarming Up Domains](https://doc.v4.missioninbox.com/sales/guides/domain-warmup.md)
