Technical Deep-Dive & Remediation Playbook

The 4 Hidden Reasons Cloud VPS Mail Servers Get Spam-Filtered

Why Valid SPF & DMARC Syntax Isn't Enough on a Raw Cloud VPS

Many developers and companies run Postfix, Mailcow, or newsletter software on raw cloud servers (Hetzner AS24940, OVHcloud AS16276, Contabo, DigitalOcean, or IONOS). Even when SPF and DMARC syntax pass, major mailbox providers filter these messages due to four infrastructure signals:

  1. Subnet & ASN Reputation Escalation (UCEPROTECT Level 2 & Level 3): If other customers in your hosting provider's /24 IP block send spam, the entire subnet gets flagged on UCEPROTECT L2/L3 and S5H.
  2. Forward-Confirmed Reverse DNS (FCrDNS / PTR) Mismatch: If your MX/SMTP banner is mail.yourdomain.com but your VPS IP's Reverse DNS (PTR) is still static.123.45.clients.your-server.de (or a different hostname), strict receivers like GMX, Web.de, T-Online, and Outlook reject or spam-folder your mail.
  3. Unenforced DMARC (p=none) on Newsletter Subdomains: Sending bulk mail from a VPS IP while keeping DMARC on p=none signals low sender commitment to Gmail and Yahoo.
  4. Zero IP Warmup History: Freshly assigned cloud IPs have no positive engagement history with Gmail Postmaster Tools or Microsoft SNDS.

The Practical Fix for High Inbox Placement

Keep your incoming mail server on your VPS if you like, but relay outgoing transactional and newsletter traffic through a dedicated high-reputation SMTP relay (such as Postmark, Amazon SES, or Resend) and align your 2048-bit DKIM and p=quarantine DMARC records.

Free Interactive Generator

SPF & DMARC Record Fix-It Builder

Select every service that sends email from your domain to generate a clean, merged SPF record (within the 10-lookup limit) and a compliant DMARC policy.

1. Select Your Email Providers & Marketing Senders

Generated SPF TXT Record
Host / Name: @
Est. DNS Lookups: ~3 / 10
v=spf1 include:_spf.google.com ~all
Generated DMARC TXT Record
Host / Name: _dmarc
RFC 7489 Compliant
v=DMARC1; p=quarantine; pct=100; rua=mailto:dmarc@yourdomain.com; adkim=r; aspf=r;
Step-by-Step DNS Playbooks

Popular Email & DNS Provider Setup Guides

Copy-paste configurations for the most common domain registrars and email platforms.

Email Deliverability Knowledge Base

Frequently Asked Questions

Why does having two SPF records break email delivery?

RFC 7208 Section 3.2 explicitly states that a domain must not have multiple TXT records starting with v=spf1. If you add a second SPF record for Mailchimp or SendGrid instead of merging the include: tags into one record, receiving servers return SPF PermError and treat your authentication as failed.

How do I fix "SPF Too Many DNS Lookups" (>10 limit)?

Every include:, a, mx, ptr, and redirect= inside your SPF record (and nested inside your providers' SPF records) counts toward the strict 10-lookup ceiling. Remove unused senders, drop redundant a/mx tags, or move marketing/transactional emails onto a subdomain like mail.yourdomain.com.

Is DMARC p=none enough for Gmail and Yahoo?

v=DMARC1; p=none; satisfies the minimum entry requirement for bulk senders, but it offers zero protection against phishers spoofing your domain. Once you verify your legitimate email services pass SPF and DKIM, upgrade to p=quarantine or p=reject.

Why wasn't my DKIM key auto-detected?

Unlike SPF and DMARC (which live at fixed DNS locations), DKIM keys live at <selector>._domainkey.yourdomain.com. AmIInSpam.com automatically probes 16 common selectors (google, selector1, s1, k1, resend, etc.). If you use a custom selector, enter it in the DKIM Inspector box to verify it directly.