Check Mailbox Health and Warmup Status

How do you check mailbox health and warmup?

Connect the HotHawk MCP server to Claude and ask which mailboxes are healthy, warming or need attention. Claude reads back the connection status and warmup progress for every inbox, so you can see which ones are ready to carry volume and reconnect any that have dropped, all from the chat.

Start your 7 day free trial Connect the MCP server

No credit card required.

Before you start

You need a HotHawk account and the HotHawk MCP server connected to Claude. It takes a couple of minutes and no code. Full setup is on the MCP server page.

Step by step

1

You ask Claude
Which of my mailboxes are healthy, and which need attention?

Claude calls mcp__hothawk__mailboxes_list

workspaceId current workspace

Claude pulls every mailbox with its connection status and sending state, then sorts them for you: the ones running clean, and the ones that have dropped or need a look.
2

You ask Claude
Show me how warmup is going across the pool.

Claude calls mcp__hothawk__warmups_tags_list

workspaceId current workspace

It reads back where each mailbox sits in warmup: still ramping, settled, or being held back, so you can see which inboxes are ready to carry real volume.
3

You ask Claude
[email protected] dropped. Reconnect it.

Claude calls mcp__hothawk__reconnect_mailbox

mailboxId [email protected]

Claude re-authenticates the account and confirms when it is back sending. Warmup picks up where it left off rather than starting from scratch.

Reputation is the thing you are protecting

Deliverability is not luck. It is the sending reputation your mailboxes have built up, and it is fragile. Push a fresh inbox too hard, let a dropped connection sit for a week, or scale a campaign onto accounts that are still finding their feet, and you spend the reputation you were meant to be banking. A quick health check before you turn up the volume is the cheapest insurance there is.

The trouble is that checking properly means opening each mailbox in turn: is it connected, is it sending, how far through warmup is it. Do that across thirty inboxes and it stops being a check and starts being an afternoon. Asking Claude collapses it into one question, and you get the whole pool sorted into fine, warming and needs-a-look.

What the check actually reads

Two tools do the work. mailboxes_list returns every mailbox with its connection and sending status, so a dropped account or one that has hit its limit stands out. warmups_tags_list reads back where each inbox sits in warmup: still ramping, settled, or being held back. Together they answer the only question that matters before you scale, which is whether an inbox is ready for the load you are about to put on it.

Warmup here runs on real Google and Microsoft inboxes, not bots and not a raw SMTP relay. Warmed mailboxes send genuine messages to each other, so the reputation the score reflects is one a mailbox provider would actually recognise. That is why the number is worth reading rather than glancing at.

Fix it in the same breath

A health check is only useful if you can act on it, and you can, without leaving the chat. If a mailbox has dropped, ask Claude to reconnect it and warmup picks up where it left off instead of resetting. If a batch is still ramping, you know to hold heavier campaigns off it for now. If the pool is running clean, you know you have the headroom to scale.

From here the next moves are a sentence each: attach the healthy mailboxes to a campaign so rotation spreads the sending, or connect more inboxes to widen the pool before a bigger push. The check tells you where you stand. The chat lets you do something about it on the spot.

The HotHawk tools behind this

Every action here is a real endpoint. Claude reaches it over the MCP server, and you can hit the same endpoints directly from the REST API if you would rather build it into your own stack.

mcp__hothawk__mailboxes_list List every mailbox with its connection and sending status
mcp__hothawk__warmups_tags_list Read back how warmup is progressing per mailbox
mcp__hothawk__reconnect_mailbox Re-authenticate a mailbox that has dropped

MCP server setup Read the API docs

Frequently asked

What does a healthy mailbox look like in HotHawk?

Connected, sending inside its limits, and past the early stage of warmup so it can carry real volume. Claude reads all three back in one go, so you get the picture without opening each mailbox in the app.

How does HotHawk warm a mailbox?

On real Google and Microsoft inboxes, not bots or a raw SMTP relay. Warmed mailboxes exchange genuine messages with each other, so the reputation being built is real. That is the whole reason a warmup score is worth checking before you scale.

Why check warmup before I turn up the volume?

Because a mailbox that is still ramping will not hold the same daily load as a settled one. Push too hard too soon and you risk the reputation you are trying to build. Checking first tells you which inboxes are ready to do the heavy lifting.

Are the deliverability protections still on when I check from a chat?

Yes, and checking changes nothing. Warmup keeps running on real inboxes, sending rotates across your mailboxes, and open and link tracking stay off. Claude is reading the numbers, not touching the machinery.

Do I need to write code?

No. You add HotHawk as a connector in Claude once, then a health check is one plain question. The same list endpoints are in the REST API if you want to pull the data into a dashboard of your own.

Keep going

Connect a mailbox from Claude Add a sending mailbox over IMAP and SMTP in a sentence Rotate sends across your mailboxes Attach a pool so no one account sends too much AI cold email software The whole picture: what AI runs on inside HotHawk AI cold email Run your cold email infrastructure from a chat

How to check mailbox health and warmup