Outgrowing ImprovMX: Moving From Email Forwarding to Real Hosted Mailboxes

The email came in at 2am. A client asking for the contract revision. I saw it on my phone, tapped reply, and watched Gmail compose a response from my personal address instead of the business domain I'd set up "Send as" for months ago.

Google had silently unlinked the alias. Again.

ImprovMX forwarding works. I'll say that upfront. For around $9/month you get unlimited aliases, forwarding to any personal inbox, and a setup that takes five minutes. I ran three client domains on it for over a year. But the cracks show when you actually need to send from the domain — not fake-send through Gmail's alias feature, but actually send from an inbox that exists and stores mail. The "Send as" workaround is fine until it isn't. And it always stops being fine at the worst possible moment.

We're the JustEmails team — JustEmails is built by Velocity Digital Labs, the same team behind ClickzProtect and JustAnalytics. This runbook is what we give freelancers and agencies when they've outgrown forwarding and want real mailboxes without Google Workspace's per-user tax.

What You'll Have at the End

A fully hosted mailbox setup: real inboxes you can log into from any IMAP client, native sending with proper SPF/DKIM/DMARC, and (optionally) your old forwarded mail imported. Your domain's email becomes a real thing, not a redirect trick.

Prerequisites

Before you start, you'll need:

• Access to your ImprovMX account (or whatever forwarder you're using)
• DNS access to your domain (Cloudflare, Namecheap, wherever your nameservers live)
• A JustEmails account — start the 7-day free trial if you haven't
• Any mail client that supports IMAP (Apple Mail, Thunderbird, Outlook, your phone's built-in app)
• 45-60 minutes of hands-on time

One thing worth mentioning: if you have years of forwarded mail sitting in your personal Gmail, you can import it into your new mailbox. But the forwarded mail is already in Gmail — this migration is about new mail and native sending, not necessarily moving history. We'll cover the import option, but it's optional.

(I skipped it for one domain. The Gmail archive is fine where it is.)

Native sending is the point of this move, so know the sending ceiling going in. The per-account cap is 20/day for the first week, 200/day in the second, and 500/day from day 15 on, with mailbox sends and API sends counted against the same number. Warm-up is measured from domain verification rather than signup, so each domain you verify starts at the bottom of a ramp of its own no matter how long you've had the account.

Step 1: Inventory Your Current Forwarding Setup

Log into ImprovMX and write down every alias you have configured. You'll be recreating these as either real mailboxes or internal forwards.

Typical setup we see:

• hello@yourdomain.com → personal Gmail (you want this as a real mailbox)
• support@yourdomain.com → personal Gmail (maybe real, maybe forward internally)
• *@yourdomain.com catch-all → personal Gmail (recreate as catch-all in JustEmails)

Decide which addresses need real mailboxes (an inbox you log into) and which can stay as forwards (just piped to another address). Most people want 1-3 real mailboxes and the rest as catch-all forwarding.

Don't touch ImprovMX yet. Leave it running until step 5.

Step 2: Create Mailboxes in JustEmails

Log into JustEmails. Add your domain — the dashboard walks you through domain verification with a TXT record. Once verified, create a mailbox for each address you want as a real inbox.

JustEmails has unlimited mailboxes on the $49/year plan, so there's no cost pressure here. If you're unsure whether an address needs a real inbox, make it one. You can always delete it later.

For each mailbox, you'll get IMAP/SMTP credentials:

• Incoming (IMAP): mail.justemails.app, port 993, SSL/TLS
• Outgoing (SMTP): mail.justemails.app, port 587, STARTTLS

Write these down. You'll need them when you set up your mail client.

If you want internal forwarding for some addresses (support@ goes to hello@, for example), set that up now in the alias/forwarding section. You can also configure a catch-all that forwards anything not matching a real mailbox to your personal email — mimicking what ImprovMX does, but on JustEmails' infrastructure.

Step 3: Lower Your DNS TTL

Before you touch MX records, drop the TTL on your existing records. If your MX TTL is 24 hours (86400 seconds), some mail servers will cache the old ImprovMX MX for a full day after you change it. That's mail disappearing into a system you're trying to turn off.

In Cloudflare:

1. Go to DNS → Records
2. Find your MX records (they point to ImprovMX right now)
3. Edit each one and set TTL to 300 (5 minutes)
4. Do the same for any TXT records you'll be changing (SPF)

Wait at least 1-2 hours. Ideally overnight. The old TTL needs to expire before the new short TTL takes effect. Yes, this is boring. DNS is always boring. It's also how you avoid losing mail — and explaining to a client why their invoice disappeared into the void.

Step 4: Update DNS Records

This is the cutover. Deep breath — it's simpler than it looks.

Replace MX Records

Delete the ImprovMX MX records. They look something like:

mx1.improvmx.com (priority 10)
mx2.improvmx.com (priority 20)

Add the JustEmails MX record from your dashboard. You're deleting two rows and adding one:

mail1.justemails.app (priority 10)

That asymmetry is deliberate, not an omission — JustEmails accepts inbound mail on a single host, so there's no priority-20 sibling to add. Leaving ImprovMX's second row behind, or duplicating ours under a made-up mail2 name, both cost you delivery attempts against a host that isn't there. Check your JustEmails domain settings for the exact value before you save.

Add or Update SPF

If you had an SPF record for ImprovMX, it might look like:

v=spf1 include:spf.improvmx.com ~all

Change it to:

v=spf1 a:mail1.justemails.app ~all

ImprovMX used an include:; ours is an a: mechanism, which authorises the IP that mail1.justemails.app resolves to without a second DNS lookup. Swapping improvmx for justemails inside the old include: won't work — that name has no TXT record behind it, so the record would parse cleanly and authorise nothing.

If you're also sending from other services (Mailchimp, your app's transactional email), keep their includes on the same line:

v=spf1 a:mail1.justemails.app include:servers.mcsv.net ~all

One SPF record only. Creating a second one breaks everything. I've seen this mistake more times than I'd like to admit. (I've made it myself. Twice.) If you're running paid ads to domains where email matters, proper SPF also prevents click fraud bots from spoofing your domain — something ClickzProtect customers often discover when investigating suspicious traffic patterns.

Add DKIM Records

Here's the big difference from forwarding. ImprovMX didn't need to sign mail because you were sending via Gmail. Now you're sending from JustEmails' servers, and they need to sign with your domain's keys.

JustEmails generates DKIM keys automatically. Add the CNAME records from your dashboard:

je1._domainkey.yourdomain.com → je1.dkim.justemails.app
je2._domainkey.yourdomain.com → je2.dkim.justemails.app

This is the step people skip when they're in a hurry. Don't skip it. Without DKIM, mail you send from your new mailbox will get spam-foldered — or worse, rejected outright by domains with strict DMARC policies.

Set Up DMARC

If you didn't have DMARC before (common with forwarding setups), add one now:

_dmarc.yourdomain.com.  IN  TXT  "v=DMARC1; p=quarantine; rua=mailto:dmarc@yourdomain.com; adkim=r; aspf=r"

Start at p=quarantine not p=reject. You want to catch misconfiguration as spam-foldered mail, not rejected mail, during the first week. Our guide on ramping DMARC from p=none to p=reject safely covers the full progression. If you're tracking email deliverability metrics alongside your ad campaigns, JustAnalytics can help you correlate sender reputation changes with conversion data.

Step 5: Verify and Test

Check DNS propagation with MXToolbox:

https://mxtoolbox.com/SuperTool.aspx?action=mx:yourdomain.com

You should see the single JustEmails MX host, with no ImprovMX rows left. Check SPF and DKIM too — MXToolbox surfaces problems in plain English.

Send a test email from an external account (your personal Gmail, a friend's Outlook) to one of your new mailboxes. Verify it arrives. Then send a test from your new mailbox to an external account. Verify it arrives and check the headers — you should see dkim=pass with your domain.

If both directions work, your cutover is done.

Step 6: Disable ImprovMX Forwarding

Now — and only now — log into ImprovMX and disable or delete your forwarding rules. If you leave them active, ImprovMX will try to receive mail it can't receive (because MX points elsewhere), which doesn't break anything but clutters their logs and your dashboard.

Keep your ImprovMX account for a week in case you need to check something. Then cancel.

Step 7 (Optional): Import Saved Mail

If you have years of forwarded mail in your personal Gmail and want it in your new mailbox, imapsync is the tool. On Ubuntu/Debian:

sudo apt install imapsync

Then run:

imapsync \
  --host1 imap.gmail.com --port1 993 --ssl1 \
  --user1 "yourpersonal@gmail.com" --password1 "google-app-password" \
  --host2 mail.justemails.app --port2 993 --ssl2 \
  --user2 "hello@yourdomain.com" --password2 "justemails-password" \
  --gmail1 --automap --f1f2 "yourdomain.com=INBOX"

The --f1f2 flag maps Gmail labels containing your domain to the INBOX folder — handy if you filtered forwarded mail into a label.

This is optional. Plenty of people leave the archive in Gmail and start fresh. There's no wrong answer here. Honestly, migrating years of email history is usually not worth the hassle unless you're legally required to have it in one place.

Common Errors and Fixes

"Send as" in Gmail stops working

Gmail's "Send as" feature relies on SMTP credentials from your email provider. Update the SMTP settings in Gmail → Settings → Accounts and Import → Send mail as → Edit info. Use your JustEmails SMTP credentials (mail.justemails.app, port 587, STARTTLS). If you're moving to a real mailbox though, consider sending directly from a proper mail client instead of through Gmail.

DKIM fails in MXToolbox

The CNAME records need 15-60 minutes to propagate. If they're still missing after an hour, double-check the record names — the underscore in _domainkey trips people up. It's je1._domainkey.yourdomain.com, not je1.domainkey.yourdomain.com.

Mail still arriving at old forwarder

DNS propagation isn't complete, or the sending server cached your old MX. Wait longer. Run imapsync or check your old Gmail for any stragglers the next day. This resolves itself within 24-48 hours if your TTL was lowered properly.

Can't connect with IMAP client

Verify you're using the full email address as the username, not just the part before the @. Security should be SSL/TLS for IMAP (port 993) and STARTTLS for SMTP (port 587). Some older clients have trouble with modern TLS — try a different client if you're stuck on an ancient Outlook version.

Next Steps

Once you're running on real mailboxes, a few things become possible that weren't before:

Team access. Add team members at $2/member/month with their own logins. Useful if you have a VA or assistant who needs to check support@ without logging into your personal Gmail. Learn more about team workflows in our shared inbox collaboration guide.

Transactional email. JustEmails includes 1,000 transactional API emails/month. If you're sending password resets or notifications from your app, you can route them through the same domain — no separate SendGrid/Postmark account needed for low volume.

Better deliverability. Your mail now has proper authentication from a dedicated mail server, not forwarding hops that make every email look slightly suspicious. Combined with proper DMARC enforcement, you'll see better inbox placement over time. Will it fix all your deliverability problems? No. But it removes one of the dumbest reasons for mail to land in spam.

For the DNS basics that come before any of this, our custom domain email setup guide covers the fundamentals. If you're comparing hosted options before committing, JustEmails vs Google Workspace breaks down the cost math. For agencies managing client domains, our multi-domain email management guide explains how to scale this setup across dozens of domains.

Questions? support@justemails.app. We answer email. (Obviously.)

Frequently Asked Questions

Why switch from ImprovMX forwarding to real mailboxes?

Forwarding works until you need to reply natively (not through Gmail's "Send as"), access an inbox from multiple devices, or collaborate with a team on a shared address. Real mailboxes also let you store mail in the inbox itself rather than your personal Gmail, which matters for client work, compliance, and not mixing personal and business mail.

Will I lose forwarded emails during the migration?

Not if you keep ImprovMX forwarding active during the cutover window. Leave the forwarding rules in place until you've confirmed new mail is arriving at your hosted mailbox, then disable them. Any mail that hit your personal Gmail via forwarding before the switch stays there — you can import it later with IMAP sync if needed.

Do I need to configure DKIM if I was just forwarding before?

Yes. Forwarding doesn't require you to sign outbound mail because you were sending from your personal Gmail account, not your custom domain. Once you're sending natively from your domain, DKIM signing is how receiving servers verify you're actually authorized to send. Without it, your mail goes to spam or gets rejected at domains with strict DMARC policies.

Can I keep some aliases forwarding while others are real mailboxes?

You can't mix MX providers on the same domain — MX records apply to the whole domain. But you can create catch-all forwarding inside JustEmails itself. Set up real mailboxes for the addresses you want full inboxes on, then create catch-all forwarding for everything else that pipes to your personal email. You get the same behavior as ImprovMX for overflow addresses.

---

Try JustEmails

Unlimited custom domain email hosting for $49/year flat — unlimited domains, unlimited mailboxes, 10 GB storage, full IMAP/SMTP. Built for agencies, freelancers, and anyone managing email across more than one domain.

Start your 7-day free trial → · How it compares