554 Nemesis ESMTP IP Address Is Block Listed: Causes and Fix

SMTP error code 554: causes, retry logic, and the sender-side fix. Nemesis ESMTP IP Address Is Block Listed: Causes and Fix.
SMTPedia editorial team
Email infrastructure & deliverability editor
3 min read Updated Aug 27, 2026 29 views
Code554
Bounce typeHard bounce
RetryableNo (until delisted)
Action neededContact Ionos postmaster
Typical error message
554 (mxgmx116) Nemesis ESMTP Service refused; IP address is block listed

What does 554 Nemesis ESMTP IP address is block listed mean?

Nemesis is the proprietary mail server software developed by 1&1 Ionos (United Internet AG) and used to handle inbound mail for GMX, WEB.DE, mail.com, and 1&1 hosted domains. When Nemesis returns this rejection, your sending IP is on the Nemesis-internal block list. The list is populated by a combination of public DNSBLs (Spamhaus, Abusix), Ionos sensor data, and abuse reports from German and European users. The hostname prefix in parentheses (such as mxgmx116, mxeueus002) identifies which Nemesis MX instance returned the rejection but is not relevant to the fix.

Is this a soft or hard bounce?

⚠️
Hard bounce affecting all GMX, WEB.DE, mail.com recipients

Nemesis serves a significant share of German consumer email. A Nemesis block effectively cuts off delivery to the German consumer market until Ionos removes the listing.

Common causes

📣
Spam complaints from Ionos users

Marks-as-spam from GMX, WEB.DE, or mail.com users feed directly into the Nemesis block list.

Public DNSBL inheritance

Nemesis queries Spamhaus and Abusix. Listings on those zones often propagate into the internal block list.

🪹
Spam trap hits

Ionos maintains spam trap addresses across its consumer mailbox population. Hitting traps results in immediate listing.

🔗
Authentication or HELO issues

Missing or misaligned SPF, DKIM, DMARC, or a HELO that does not match PTR feeds the negative score.

How to fix it

1
Verify public DNSBL status first

Look up your IP at Spamhaus, Abusix, and Barracuda. Clearing public listings often resolves the Nemesis block automatically within 24 to 48 hours.

2
Fix authentication thoroughly

Verify SPF, DKIM, and DMARC all pass with strict alignment. Nemesis is strict about authentication for German consumer mail.

3
Contact Ionos postmaster

Submit a delisting request through postmaster.web.de (which also handles GMX and mail.com). Provide your IP, sending domain, evidence of legitimate use, and a description of remediation taken.

4
Audit and clean list before resuming

Use email verification to remove invalid addresses. Add Nemesis to your blocklist monitoring if your tooling supports it.

Provider-specific notes

Recipient domainOperator notes
GMX.de, GMX.net, GMX.comAll routed through Nemesis. Same block list, same removal path through Ionos postmaster.
WEB.DE, freenet.deSame Nemesis infrastructure. WEB.DE is the largest German consumer mail provider.
mail.com, 1and1.com, ionos.comMail.com is the global consumer brand. 1and1.com/ionos.com cover hosted business domains.
Pre-bounce verification

Prevent the bounces that hurt your sender IP

Nemesis blocks are often triggered by bounce-driven reputation decay. SMTPing catches invalid addresses before you send, keeping your reputation healthy across Ionos infrastructure. 25 free checks daily, no card required.

Try SMTPing free →

About the Author

Alaa - SMTPedia author

Alaa · LinkedIn

Email infrastructure specialist with 8+ years of hands-on experience in SMTP, deliverability, and email verification. I’ve configured and troubleshot mail systems across Postfix, Exchange, and cloud relays, managed IP reputation and warmup campaigns, and built verification pipelines processing millions of addresses. My work spans DNS authentication (SPF, DKIM, DMARC, BIMI), bounce handling, blocklist monitoring, and compliance frameworks including CAN-SPAM and GDPR. I write every article on SMTPedia to give email professionals, developers, and marketers the accurate, RFC-grounded reference they need.


About SMTPedia

SMTPedia is an independent email industry reference covering SMTP, IMAP, POP3, email deliverability, marketing platforms, DNS authentication, and email verification. Every article is researched from official provider documentation, IETF RFCs, and industry best practices. Settings and configurations are verified quarterly.

We are cited as a source by ChatGPT, Microsoft Copilot, and thousands of email professionals worldwide. Learn more about our editorial process.