Business Email Not Working
Higher-risk issue — be cautious and consider professional help sooner.
Email at your own domain ([email protected]) won't send, won't receive, or won't connect in your mail app — and every bounced message is a customer wondering why you didn't answer.
Common signs of this issue
- You can't send, can't receive, or both — or mail arrives only sometimes.
- Your mail app keeps demanding the password or shows connection errors.
- People who write to you get bounce-backs — often you learn this from a phone call: "your email bounced."
- It stopped after moving hosts, changing email providers, renewing/transferring the domain, or a password change.
- The website broke at the same time — a clue the shared foundation (domain/DNS) is the problem.
Safe checks you can do yourself
None of these require sharing passwords with anyone.
- Run the four-way test to localize the break: send to yourself from your own address, to your address from a personal account (Gmail), out to a personal account, and note exactly which legs fail. "Can't receive" and "can't send" have different causes and different urgency — receiving failures mean customer mail is bouncing right now.
- Log into your provider's webmail in a browser. This single check splits the world: webmail works but your app doesn't → the mailbox is fine and only the app's settings are wrong (annoying, not urgent). Webmail also fails → the mailbox, account, or domain is the problem (urgent).
- Read any bounce-back message carefully — bounces state their reason: "mailbox full" (clear the quota), "address not found" / "domain not found" (DNS or domain problem), "rejected as spam" (authentication problem — see the spam guide). The bounce text is diagnosis handed to you.
- Check quotas: your individual mailbox AND the hosting account's overall disk. Full is a silent killer — mail simply bounces until space is cleared, and host-based mailboxes fill faster than people expect.
- Check the domain itself: a whois lookup for expiry (an expired domain kills email and website together), and note any recent DNS changes, host migrations, or transfers — email's MX records are the most commonly damaged item in every one of those events.
- If the app is the problem (webmail works): get the exact settings — server names, ports, SSL, username format — from your provider's setup page rather than guessing, delete the account from the app, and re-add it fresh. Half-edited settings cause more grief than clean re-adds.
What this usually means
Email problems sort into three layers, outermost first: the domain/DNS layer (expired domain, or MX records pointing at the wrong provider — kills everything, often after a migration), the mailbox layer (full quota, suspended account, changed password — kills one address), and the app layer (wrong server settings — kills one device while webmail hums along). The four-way test plus the webmail check tells you which layer you're in.
The layer determines urgency. App-layer problems inconvenience you only — mail is safely arriving at the server. Mailbox and DNS-layer failures mean senders are getting bounces: customers concluding you're ignoring them or out of business. That's the version to treat as a same-day emergency.
There's a hidden mercy in how mail works: during shorter outages, sending servers retry for hours (often up to a couple of days) before giving up. Fix the problem quickly and much of the mail from the outage window still arrives late rather than never — one more argument against letting it sit.
What not to do
- Don't change DNS or MX records by guessing — wrong values take mail down for everyone, and each change adds propagation hours in both directions. Copy exact values from your mail provider's documentation or have it done carefully.
- Don't delete and recreate your mailbox to 'start fresh' — deletion typically destroys the stored mail in it, and rarely fixes the actual cause.
- Don't keep retrying a rejected password until the server locks the account — one deliberate reset beats five guesses.
- Don't run your business from a personal Gmail 'temporarily' without setting up forwarding thoughtfully — ad-hoc workarounds have a way of becoming permanent and confusing customers.
- Don't hand your email password to an unverified helper — email is the recovery key to every other account you own; treat its credentials as the most sensitive you have.
When to get help
Email is business-critical, DNS mistakes multiply outage time, and the mailbox is the skeleton key to your other accounts — three reasons this is worth careful hands rather than experimentation. A capable helper can usually locate the layer from the outside (DNS lookups and bounce messages) before touching anything private, then fix records or settings in one pass. If receiving is down, say so first — that's the finding that upgrades the job to urgent.
Could your hosting be the problem?
If your host is slow, unreliable, or hard to deal with, moving to a better one can clear up issues like this for good. One we genuinely recommend is Instant Access Internet Services — a smaller, compassionate company with 30 years in the business, known for being one of the fastest, with great management and low pricing. (Just a recommendation — no affiliate link, no kickback.)
Not sure what to do next?
Answer a few short questions and we'll point you to the safest next step — DIY, a freelancer, or a direct review. No passwords required.
Is this a business website? If this issue may be costing you leads, sales, or trust, you may want a direct review instead of trial and error.
Frequently asked questions
Why did email stop after I moved my website to a new host?
The move reset or repointed your domain's DNS, and the MX records that route mail no longer point at your actual mail provider. It's the single most common migration casualty. Restoring correct MX records fixes it — and until then, senders get bounces.
Webmail works but Outlook/Apple Mail doesn't — what's wrong?
The mailbox is healthy; the app's settings (server names, ports, SSL, password) aren't. Get the exact values from your provider's setup page, remove the account from the app, and add it fresh — cleaner than editing in place.
People say their email to me bounced. How bad is this?
Treat it as urgent — bounces mean customer mail is being refused now. The bounce text they received states the reason (full mailbox, DNS, spam rejection). Ask someone to forward you a bounce; it's your best diagnostic.
Is mail lost during an outage?
Often not, if you fix it fast: sending servers retry for hours (commonly up to a day or two) before giving up. Mail from a brief outage mostly arrives late. Multi-day outages do lose mail permanently — the reason speed matters.
Should my email even be on my web host?
Host-based email works but is the fragile setup — it dies with hosting problems and migrations, exactly as you may be experiencing. Dedicated providers (Google Workspace, Microsoft 365) separate email's fate from your website's; see the set-up-business-email guide.
Why does my sent mail land in recipients' spam?
That's a different disease than 'not working' — your domain's authentication records (SPF/DKIM/DMARC) don't vouch for how you send. The going-to-spam and SPF/DKIM guides cover the fix.