Deliverability warmup
WarmupTool — cross-account SMTP warmup with clear roles, safer pairing, and honest monitoring.
Connect mailboxes, separate senders from passive or active receivers, and run controlled cycles. Built for teams who want predictable volume, not random spam loops.
By continuing you agree to our Terms and Privacy Policy.
What WarmupTool does
- Lets you connect mailboxes you control (SMTP/IMAP credentials or Google OAuth for Gmail) and store configuration in your account.
- Runs controlled outbound warmup mail between your connected mailboxes, with roles such as sender, passive receiver, and active IMAP receiver.
- Shows a dashboard and email activity log so you can monitor sends, replies, and errors.
- Optionally drafts short message text via a third-party AI API when you configure an API key; otherwise the app uses built-in templates.
Google Sign-In & why we request Gmail access
If you connect Gmail with Google, you will see OAuth scopes similar to the following. We only use them to operate the features described above for mailboxes you connect.
- Gmail (
https://mail.google.com/) — send and receive mail through Gmail for warmup and optional replies, consistent with how desktop mail clients use Gmail IMAP/SMTP. - Email address (
userinfo.email) — identify which Google account you connected. - Offline access — store a refresh token server-side so the app can obtain short-lived access tokens when mail jobs run. You can revoke access anytime in your Google Account security settings.
Privacy policy (public, no login required)
The same Privacy Policy URL you configure on the OAuth consent screen should match this link. It explains what we collect (account data, mailbox settings, optional OAuth tokens, warmup message records), how we use it, retention, security, and your rights.
Public homepage URL (for reviewers)
https://warmup.digital/
Google verification often expects a domain you can verify in Google Search Console. A Vercel preview hostname may be treated as shared infrastructure. If Google asks for verified ownership of the homepage, add a custom domain in your DNS and hosting (for example point app.yourdomain.com to this deployment), verify that property in Search Console, set NEXT_PUBLIC_GOOGLE_SITE_VERIFICATION from the HTML tag method, then use that HTTPS URL as the OAuth application home page and privacy policy host.
SMTP & IMAP aware
Sender-only mailboxes can skip IMAP. Active receivers validate IMAP so replies and inbox actions stay possible.
Safer pairing
Prefers cross-provider targets when your pool allows it, so Gmail does not only talk to Gmail.
Runs on your schedule
Trigger cycles from the dashboard or wire a daily cron. States like cooldown help you back off when reputation dips.