SPF, DKIM and DMARC all pass. It still goes to spam.
Authentication is the entry ticket, not the seat. Passing all three records proves you are allowed to send as your domain — it says nothing about whether the receiver's reputation system wants your mail. This page is the order to check things in when the records are right and the inbox is still empty.
What each record actually does.
Worth thirty seconds, because most "it is all set up correctly" conversations are really about the gap between the second and third lines.
- SPF says which servers may send mail for a domain. It is checked against the envelope sender and the connecting IP, not against what the recipient sees in the From: line.
- DKIM attaches a signature to the message, made with a key published in DNS. It survives forwarding better than SPF, which is why large senders lean on it.
- DMARC asks two things: did SPF or DKIM pass, and does the domain that passed align with the From: domain the recipient sees. Pass without alignment still fails DMARC.
That last clause is the one that catches people. You can have a perfect SPF record and a valid DKIM key and still fail DMARC, because the record passing belongs to a different domain than the one in the header. Google states the requirement plainly for bulk senders: the From: domain must align with either the SPF or the DKIM domain.
Seven reasons, most likely first.
Each one is checkable from a terminal or a DNS lookup. None of them requires changing your records to something exotic.
1 · Alignment, not passing
Check the From: domain against the domains that actually authenticated. A form sending as noreply@yourdomain.com while signing with a shared provider's key fails alignment, even though both checks "pass". Fix it by signing with a key on your own domain, which is what per-domain selectors are for.
2 · Reverse DNS
The sending IP must appear in the PTR record's hostname, and that hostname must resolve forward to the same IP. Google is explicit: the IP must match the hostname in the PTR record. On a VPS you inherit whatever the provider set, and it is usually a generic ip-203-0-113-10.provider.net that no receiver is going to like. Set the PTR to your mail hostname — and check IPv6 separately, because an IPv6 address with no matching PTR is its own rejection (550-5.7.1).
3 · The neighbours
A shared IP's reputation belongs to everyone on it. If another customer on that address has been reported, your perfectly authenticated mail suffers for it. Check the address against the major blocklists, and check its reputation rather than guessing: Google's guidance for shared hosting is to watch the shared IP's reputation, not just the domain's.
4 · Complaints, not content
The number that moves reputation fastest is the proportion of recipients who press "report spam". Google's stated target is below 0.10%, with 0.30% as the line never to reach. A newsletter with a slightly wrong address list will do more damage in an hour than a decade of perfect DNS. Remove non-openers, confirm opt-ins, and never import a purchased list.
5 · Volume shape
Reputation is also built from sending history, and a sudden spike from an IP with no history reads as an attack. Ramp: start with the engaged recipients, increase over days, avoid bursts. If you see Gmail's 4.7.28 quota error, the documented response is to stop sending for at least ten minutes, then resume over a single connection and build up.
6 · One-click unsubscribe
Over 5,000 messages a day to Gmail, marketing and subscribed mail must carry one-click unsubscribe: the List-Unsubscribe and List-Unsubscribe-Post: List-Unsubscribe=One-Click headers. A link in the body is not enough. Missing it is a compliance gap with the mailbox provider, not a cosmetic one.
7 · Key length and key hygiene
Gmail requires a 1024-bit key minimum and recommends 2048. One key shared across every domain on a server also means one compromised or complaining domain takes the others with it, so per-domain selectors are worth the extra records.
The five-minute version.
What good looks like, and the specific thing people get wrong on each line.
| Thing | Where it lives | What good looks like | The usual mistake |
|---|---|---|---|
| PTR | Your VPS provider, not your DNS zone | Resolves to your mail hostname; that name resolves forward to the same IP | Left on the provider's generic name; IPv6 never set at all |
| SPF | TXT record on the sending domain | Lists every sender that sends as the domain, ends in a hard fail or a soft fail you have chosen deliberately | A third-party sender added later and never added to SPF |
| DKIM | TXT record at selector._domainkey | 1024-bit minimum, 2048 preferred, one selector per sending domain | Valid but on a different domain than the From: header |
| DMARC | TXT record at _dmarc | Start at p=none with reporting, move to quarantine then reject as your reports show only senders you recognise | Jumping to reject while a third-party sender is still unauthenticated |
| Unsubscribe | Message headers | List-Unsubscribe plus the one-click POST header, above 5,000 a day | Only a visible link in the body |
| Postmaster Tools | Google's dashboard, verified by DNS | Domain verified, spam rate visible and under 0.10% | Never verified, so nobody can see the complaint rate at all |
The thresholds, key length, alignment rule and error codes above are from Google's Email sender guidelines, read 9 November 2026. Other mailbox providers have their own reputation systems and their own thresholds; this page uses Gmail's because they publish numbers.
Where the panel does the work.
Most deliverability problems on a shared server come from one customer's site, not from the mail stack. Those are the ones a panel can actually prevent.
- Site mail is signed as the site's own domain. PHP mail from a customer's site is DKIM-signed with a key for the From: domain — but only for domains the account owns — so it can align and pass DMARC at Gmail and Outlook instead of looking like a shared server sending as a domain it does not own.
- IPv4 first, IPv6 as fallback. Outbound delivery tries the receiving server's IPv4 address first, so a VPS's generic IPv6 reverse DNS does not get the message rejected for a PTR problem that was never yours to fix.
- Default SPF includes the server's IPv6 address, and records still on the panel default are updated automatically.
- A cap per account on PHP mail, per hour, so one compromised form cannot turn a shared IP into a spam source in an afternoon.
- Mail guard switches PHP mail off and holds the queue for an account whose site floods past its cap, and tells the owner and the admin why.
- A form-abuse notice for bots using a site's contact form to mail other people — usually a missing CAPTCHA — with the form's path.
- Deliverability scoring, a blacklist monitor and a queue browser, so the answer to "is it us or them" is visible rather than a guess.
None of that guarantees an inbox. What it removes is the largest single cause on shared hosting: an unauthenticated, unthrottled script sending as someone else's domain.
Is it the form, or the mail server?
They fail differently, and knowing which one you have saves an afternoon of changing DNS that was never wrong.
- Test from a real mailbox first. Send from webmail to Gmail and to Outlook, then send through the website's form. If the mailbox arrives and the form does not, the problem is the sending path, not your records.
- Form mail is usually PHP's
mail(). It carries no authentication of its own and is the classic source of a server's bad reputation. Sending the form through the account's own mailbox over SMTP gives it a real identity and a real signature. - Look at the headers. In the received message, check which domain passed and whether it matches the From: header. That single check separates an alignment problem from a reputation problem.
What no panel can promise.
Stated plainly, because the alternative is a page that reads like a guarantee.
The three that come up.
Short answers.
If everything passes, why does Gmail still filter it?
Because filtering is a separate decision from authentication. Gmail will say a message is authenticated and still classify it as spam on reputation, complaint history or content. Authentication removes the "we cannot tell who sent this" penalty; it does not add a positive score.
Do I need a dedicated IP?
Only if you send enough volume to build a reputation of your own. A dedicated IP with no sending history starts cold and can be worse than a shared IP with a long, quiet history. Below a few thousand messages a month the shared address is usually the better trade.
Does moving to this panel fix deliverability?
No, and any vendor saying so is selling. What changes is that PHP mail is capped per account, signed as the site's own domain, and reported when it misbehaves — which removes the most common cause rather than all of them.