GMX, WEB.DE and mail.com share one set of rules, and DKIM is the heart of it: every message needs a DKIM signature aligned with the From domain — SPF alone is not enough. Since May 2026 they have been gradually starting to reject mail that fails DMARC when the sender’s domain publishes p=reject.
| Applies to | Mail to gmx.net, gmx.de, web.de and mail.com addresses |
| Bulk threshold | None; newsletters and promotions have extra rules |
| Authentication | DKIM required, aligned at least relaxed; SPF and DMARC recommended |
| DMARC p=reject | Rejected rather than filed as spam — rolling out since May 2026 |
| Limits | 20 recipients per transaction, 100 transactions per session |
Check your domain against GMX, WEB.DE and mail.com’s rules
Enter the domain in your From address. What its DNS shows is tested here; for the rest, send one message to our email test.
What every sender needs
- A DKIM signature on every message, aligned with the From domain at least in relaxed mode. “SPF alone is not sufficient.”
- A static IP address: dial-up and dynamic ranges are not accepted.
- Reverse DNS (PTR) pointing to a full host name that should belong to your own domain; generic names like 123-123-123-123-static.provider.tld usually lead to rejection, and the host name must point back to the IP.
- A HELO/EHLO name that is a valid, resolving host name.
- A sender domain with a valid MX record that itself has a valid A record; a null MX is rejected.
- Headers that follow RFC 5321 and 5322: Date, From and Message-ID present, no repeated single headers, one address in From, a plausible date.
- No listing on blocklists — Spamhaus is consulted for the IP, the sender domains and the links in the message.
What bulk senders also need
For newsletters and promotional mail, with no volume threshold, GMX and WEB.DE add:
- Consent from every recipient, ideally by double opt-in.
- The sender, and any service sending on its behalf, clearly identifiable.
- An easy way to unsubscribe in every email; RFC 8058 one-click is ideal and shows an unsubscribe button, otherwise a reply address that unsubscribes.
- No mail to invalid or inactive addresses, and no causes for spam complaints.
- The M3AAWG and CSA guidelines followed.
What happens to mail that does not comply
Replies use basic SMTP codes with no enhanced status code, and the last line carries a link to postmaster.gmx.net (or web.de, or mail.com) with a case code such as r0103 that explains the rejection — most case pages have their own contact form.
High volume without an aligned DKIM signature is deferred (451). Since May 2026 mail failing DMARC under a p=reject policy is being moved from the spam folder to outright rejection, gradually.
| The rejection | What it means |
|---|---|
451 … r0101, r0103 | No DKIM signature, or one not aligned with the From domain, on a high volume of mail: deferred. |
554 Reject due to sender domain’s DMARC policy (r2001) | The message failed DMARC and the From domain publishes p=reject. What to do → |
r0601, r0602, r0603 | The PTR record is wrong, missing, or does not point back to the IP. What to do → |
r0301 – r0303 | The sending IP is listed on Spamhaus. What to do → |
r0801 | The HELO name does not resolve, or is on an internal blocklist. |
r1401, r1402 | The sender domain has no MX with a valid A record, or publishes a null MX. |
GMX, WEB.DE and mail.com’s tools for senders
- Requirements and recommendations — the rules — identical at postmaster.web.de and postmaster.mail.com
- Error messages — how the rejections and their case links work
- Contact — include the exact error message and your IP, or the request is not processed
Recommended, not required
- SPF and a DMARC record.
- DKIM aligned strictly rather than relaxed.
- RFC 8058 one-click unsubscribe, double opt-in and membership of the Certified Senders Alliance.
- A host name for the sending server such as mail.yourdomain.tld.
Common mistakes
- Relying on SPF: GMX and WEB.DE require DKIM, aligned with the From domain.
- Signing only with your email service’s domain, which does not align with your From address.
- More than 20 recipients in one transaction, or 100 transactions in one session.
- Using the “blocklisting” form to get off a GMX block — it is for GMX users whose own mail is blocked elsewhere; use the contact form or the case page instead.
Setting up the records? The exact SPF include and DKIM records for each service are in our email setup guides, and what each part of a record does is in SPF, DKIM and DMARC explained.
Questions
Do GMX and WEB.DE require DMARC?
No — they recommend it. What they require is an aligned DKIM signature. They do enforce your own policy: since May 2026 they are rolling out rejection for mail that fails DMARC under p=reject.
Is there a GMX feedback loop?
None is mentioned on the GMX, WEB.DE or mail.com postmaster sites. They send DMARC aggregate reports to your rua address.
Sources
Checked against GMX, WEB.DE and mail.com’s own documentation on 25 September 2026:
- Requirements and Recommendations — postmaster.gmx.net
- Requirements and Recommendations — postmaster.web.de
- Error messages — postmaster.gmx.net
- FAQ — GMX Postmaster — postmaster.gmx.net
- 554 Reject due to sender domain’s DMARC policy — postmaster.web.de