# WHMCS Email Deliverability Fix

> WHMCS invoices and ticket replies in the inbox: mail provider, SPF, DKIM, DMARC and reverse DNS set up and tested.

WHMCS emails going to spam? We switch WHMCS from PHP Mail to a proper provider, publish SPF, DKIM and DMARC, set reverse DNS, and prove delivery with Gmail, Outlook and Yahoo tests.

- **Price:** Starting at $199
- **Billing:** One-time, fixed scope
- **Category:** WHMCS
- **Quote turnaround:** Fixed-price quote within 24 hours
- **Start a project:** https://whmcspilot.com/start-project
- **Details:** https://whmcspilot.com/services/whmcs-email-deliverability
- **Last updated:** 2026-11-05

## Overview

The WHMCS email deliverability fix gets invoices, password resets, welcome emails and ticket replies out of spam folders and into inboxes, by setting up how WHMCS sends and the DNS records behind your sending domain. One sending domain starts at $199. This service is about delivery only: changing what the messages say or how they look is [WHMCS email templates](/services/whmcs-email-templates), and newsletters or promotions are [WHMCS email marketing](/services/whmcs-email-marketing). If you want to try first, the guide to [WHMCS emails not sending](/blog/whmcs-emails-not-sending) walks through the checks in order; below is what we do when you pass the job to us.

## Our first hour

- **Where mail leaves from.** PHP Mail, SMTP through your own server's Exim or Postfix, Google Workspace, Microsoft 365, or a transactional provider.
- **Every address WHMCS sends as.** The client-mail address from the General tab, the System Emails From Email setting for admin notices, and the address each support department uses. Installs often send from three domains without anyone noticing.
- **What receivers actually see.** Test messages to Gmail, Outlook.com and Yahoo, with the Authentication-Results headers read for SPF, DKIM and DMARC alignment.
- **Reputation.** The sending IP and domain checked against Spamhaus and other major blocklists, and Google Postmaster Tools or Microsoft SNDS data where you have it.
- **Look-alikes.** A stopped cron, a disabled template or a hook cancelling mail can look like a delivery problem. If that is the real cause, we tell you in the first hour and point you to the right fix, such as [cron fixing](/services/whmcs-cron-fixing).

## What we set up

### The sending path

PHP Mail is replaced with SMTP or one of WHMCS's built-in mail providers, configured at Configuration &gt; System Settings &gt; General Settings &gt; Mail under Configure Mail Provider. For most hosts that means a transactional service such as Amazon SES, Postmark, Mailgun or SendGrid, or WHMCS's Google or Microsoft provider with OAuth for smaller volumes. We complete the provider's domain verification so its DKIM signature uses your domain rather than its own, which is what DMARC alignment needs. WHMCS will not save a mail provider until Test Configuration succeeds, so the switch is confirmed before anything else changes.

### DNS records

- **SPF.** One record that names every service sending as your domain, kept under the limit of 10 DNS lookups.
- **DKIM.** Selector records from your provider or cPanel, with 2048-bit keys where the provider supports them.
- **DMARC.** A record starting at p=none with a reporting address, and a dated plan for moving to quarantine and then reject once the reports are clean.
- **Reverse DNS.** For mail sent from the WHMCS server itself, a PTR entry on the sending IP, matched by a forward record for the hostname it names, if your host allows it.

### Separating mail streams

When the same domain carries invoices, marketing and server notifications, a burst of complaints about a newsletter can hurt invoice delivery. Where it fits, we move billing mail and bulk mail to separate subdomains or provider streams so one cannot drag the other down. Google and Yahoo apply stricter rules to senders that pass 5,000 messages a day to their users, and a busy invoicing day can cross that line.

## What you receive

1. A table of every DNS record added or changed, with its value, so you can recreate it anywhere.
2. Test results from Gmail, Outlook.com and Yahoo showing SPF, DKIM and DMARC passing.
3. The provider account set up in your name, with the login handed over.
4. A note on reading the first weeks of DMARC reports and when to tighten the policy.

## What we need from you

- DNS access at Cloudflare, your registrar or the cPanel Zone Editor
- A WHMCS admin login
- Access to your mail provider, or permission to create an account for you
- A list of everything else that sends as your domain, such as Google Workspace, a helpdesk or a marketing tool

## Pricing

ScopePriceOne sending domain: mail provider, SPF, DKIM, DMARC, reverse DNS where possible, and testsFrom $199Additional brands or sending domains on the same WHMCSFixed quoteBlocklist delisting and reputation recovery after a spam incident$65/hourTransactional provider feesPaid by you to the provider

Version matters in one place: Google mailboxes connected by password under 8.x must be linked again through OAuth on 9.x.

## Not included

- A promise of inbox placement, which no one can honestly give, since receivers make the final call
- Mail servers that host your customers' mailboxes on the servers you sell from
- Rewriting template content or building campaigns

For reminders that should not rely on email alone, the [Multi-Channel Notifications module](/modules/whmcs-notifications) delivers WHMCS alerts over SMS, WhatsApp and Telegram as well. Forward us one invoice email that landed in spam, with its full headers, and we can usually name the cause before the call ends.

## What's included

- Audit of every From address WHMCS uses, including support departments
- Header checks of test mail to Gmail, Outlook.com and Yahoo
- Blocklist and reputation check for the sending IP and domain
- PHP Mail replaced with SMTP or a built-in WHMCS mail provider
- Transactional provider set up with your domain verified for aligned DKIM
- Single SPF record kept under the 10-lookup limit
- DKIM selectors published and DMARC started at p=none with reporting
- Reverse DNS set where WHMCS sends from its own server
- Billing and bulk mail separated where they share a domain
- Table of every DNS record and test results handed over

## Business outcomes

- Invoices and reminders reach customers, so fewer payments are missed
- Password resets and welcome emails arrive when customers are waiting for them
- A newsletter complaint no longer puts invoice delivery at risk
- You can see in DMARC reports who is sending as your domain
- Every record is documented, so a DNS or provider move does not undo the work

## Frequently asked questions

### Why do WHMCS emails go to spam?

Most often because WHMCS sends through PHP Mail from a server with no SPF, DKIM or DMARC for the From domain. Gmail and Yahoo now reject or filter that mail far more often.

### How much does the deliverability fix cost?

From $199 for one sending domain, covering the mail provider, DNS records and tests. Provider fees, if any, are paid to the provider directly.

### Which mail provider should WHMCS use?

For most hosts, a transactional service such as Amazon SES, Postmark, Mailgun or SendGrid. WHMCS has built-in providers for Mailgun, SendGrid and SparkPost, and SES and Postmark connect over SMTP.

### Is this the same as your email templates service?

No. Deliverability is about whether messages arrive. Email templates is about their content and design, and email marketing covers campaigns.

### Can you guarantee inbox placement?

No one can, because Gmail, Microsoft and Yahoo make the final decision. What we can do is meet every published sender requirement and show you the passing results.

### When is the final 50% due?

On delivery, once the test results show SPF, DKIM and DMARC passing. You can pay through Stripe, PayPal or NOWPayments.
