A German customer opens a ticket. Your mail never arrived. You check the bounce and see web.de, gmx.net, or mail.com.
Those brands look separate. You are often dealing with one filter family under different logos.
GMX deliverability problems show up a lot for teams with EU lists. The mailboxes look simple. The filtering is not. Treat each brand as its own ISP and you will waste a week filing the wrong form and reading the wrong docs.
TL;DR: one filter family, three logos
- Shared stack. Web.de, GMX, and Mail.com look separate. Filtering and postmaster expectations largely line up under the wider 1&1 / IONOS family.
- Read the bounce link. Their bounce text often points at a postmaster error page. That page beats guessing.
- Reputation drivers still win. Spam reports, content fingerprinting, blacklist hits, and spamtraps are the usual blockers.
- CSA can help. The Certified Senders Alliance whitelist is how they describe lower spam probability for participating senders.
- Unblock per brand. Use the contact form that matches the domain you hit, and bring details.
What to watch out for: purchased lists and email append. This family notices bad acquisition fast.
For the broader spam picture, start with why emails go to spam. For how predictability trains placement, see predicting inbox placement.
Why GMX deliverability looks brand-specific
1&1 runs a large email footprint out of Germany, with heavy EU volume and a real US presence too. The consumer domains people hit most often include gmx.net, web.de, mail.com, and email.com, plus related domains under the same roof.
Each brand ships its own postmaster site:
Treat them as one sending problem with branded doors. Fix reputation for one of these domains and ignore the others, and you often still have the same underlying issue.
If you also send into German business mailboxes, keep Mail.de deliverability nearby. Different stack, same region, same operator habits.
Always open the bounce link
Their postmaster docs include a catalog of error messages. Start there when mail is delayed or rejected.
Bounces here tend to fall into a few buckets:
- Policy issues tied to spam signals or sender reputation
- Blacklist problems
- Authentication failures
- Other operational issues
The bounce itself often includes a URL into that documentation. Follow it. Do not stop at the SMTP code in your ESP UI.
Operators skip this step constantly. They paste "550 blocked" into Slack and start debating IP warmups. Meanwhile the bounce already explained whether you are looking at policy, a blacklist, or broken auth.
If authentication is the callout, fix SPF, DKIM, and DMARC before you file an unblock request. If the page points at reputation, cleaning the list beats arguing with postmaster.
What usually gets you blocked
This family stops spam with the same signals other ISPs watch. The drivers that show up again and again:
Spam reports. Recipients hitting junk train the system against you. EU consumer inboxes are not shy about that button.
Content fingerprinting. Spammy patterns get matched across campaigns. Recycled affiliate templates and shady link patterns travel poorly here.
Blacklistings. A listing on a major DNSBL can show up in the bounce path. Check the error page before you assume it is "just GMX being strict."
Spamtrap hits. Old, scraped, or purchased addresses are how traps end up on your list. One bad acquisition channel can poison a whole mail stream.
None of that is unique to GMX. It just bites harder when a big slice of your EU audience sits on these domains. Clean consent and steady volume still matter. Purchased lists and email append are especially bad ideas here.
If you need a compliance checklist for European sending habits, keep MAGY compliance bookmarked next to this guide.
CSA and the whitelist
GMX documents participation in the Certified Senders Alliance. Their framing is blunt. CSA whitelist participation is meant to lower spam probability and keep mail out of the spam folder for qualifying senders.
It will not cover for ugly complaint rates or a messy list. CSA is a structured path for senders who already meet the alliance bar.
Use it when you already send clean mail at volume into DE/AT/CH-heavy lists and want the formal channel. Skip the cargo-cult version where someone buys a badge and keeps blasting cold lists.
How to ask for an unblock
Each brand has its own contact form:
Use the form that matches the domain in the bounce, even if you suspect the backend is shared. Wrong queue means a longer wait.
Bring detail. Sending IP or IPs. From domain. Approximate volume. Example Message-IDs or full bounce samples. What you already fixed. What changed right before the block.
Response quality varies. Some operators get quick replies. Others hear nothing. The request goes better when you already fixed the obvious reputation drivers and can prove it.
Do not open a ticket that just says "please whitelist us." Open one that shows you read the bounce page and cleaned the cause.
Takeaways
Treat Web.de, GMX, and Mail.com as one deliverability problem with three postmaster doors. Read the bounce link first. Fix reports, traps, blacklists, and auth before you ask for an unblock. Consider CSA if you already run a clean EU stream. File the form that matches the domain you hit.
In Bento, keep EU marketing and transactional traffic on predictable Authors and domains so one bad campaign does not train the whole brand into junk. If a GMX-family bounce lands, open the linked postmaster page before you change anything else.
Questions? Ask in Discord.
