One morning, the IONOS webmail refuses to display the inbox, or an email sent from Outlook no longer goes out without explanation. This type of blockage affects both Mail Basic accounts and Mail Business offers, and the cause is almost never unique. Precisely identifying the origin of the malfunction before changing anything remains the most reliable approach to restore operational email service.
Test from another network to isolate the IONOS email outage
The first action to take requires no technical skills. Simply connect to the IONOS webmail (mail.ionos.fr) from another device or another network (mobile hotspot, a colleague’s network).
If the webmail works normally elsewhere, the problem is local: browser, cache, blocking extension, corporate proxy, or firewall. If the malfunction persists regardless of the network, the cause lies on the server side or account configuration side.
This simple test helps avoid touching DNS settings or IMAP parameters when the problem comes from a corrupted browser cache. Before any manipulation, it is useful to know how to resolve an IONOS email issue by process of elimination rather than modifying several parameters simultaneously.
Clearing the browser cache and temporarily disabling extensions (especially ad blockers and built-in antivirus in the browser) resolves a significant portion of cases where the webmail displays a blank page or a connection error.

Blocked sending and receiving: check IMAP and SMTP server settings
When the webmail works but an email client (Outlook, Thunderbird, Apple Mail) refuses to send or receive, the problem almost always comes from the configuration of the incoming and outgoing servers.
IONOS server settings for email clients
The parameters expected by IONOS for a standard email account are precise. A single incorrect value is enough to block the flow in one direction or the other.
- Incoming IMAP server: imap.ionos.fr, port 993, SSL/TLS encryption. The POP3 protocol uses pop.ionos.fr on port 995 with the same type of encryption.
- Outgoing SMTP server: smtp.ionos.fr, port 587, STARTTLS encryption. SMTP authentication must be enabled, otherwise sending fails without an explicit error message on some clients.
- Identifier: the full email address (not just the part before the at sign). The password is the one defined in the IONOS client area, not that of the client account itself.
On Apple Mail, field reports indicate that the client may continue to display “connecting” indefinitely if the SMTP port is set to 465 instead of 587. The error message does not mention the port, making diagnosis less obvious.
The webmail as a diagnostic tool
When Outlook or Thunderbird are malfunctioning, the IONOS webmail may continue to function normally. If this is the case, the email service itself is not down. The problem is limited to the local configuration of the email client or a network conflict on the workstation.
This check avoids opening a ticket with IONOS support for an incident that does not fall under their infrastructure.
Email filters and storage quota: the invisible causes
A message can disappear without any error being displayed, neither for the sender nor for the recipient. Two mechanisms explain this silent behavior.
Active filtering rules in the webmail
The IONOS webmail allows the creation of automatic sorting rules. A poorly configured rule can redirect, archive, or delete incoming emails without notification. The check is done in the webmail settings, under the “Filters” or “Email Rules” tab depending on the version of the interface.
Sorting rules can delete emails without a visible error. They must be reviewed one by one, especially those that contain generic conditions (filtering by subject containing a common word, filtering by sender with a whole domain).
Full mailbox
A full mailbox blocks reception without warning on the sender’s side in some cases. The sender may receive a non-delivery message (bounce), but this is not always the case. The used space quota can be checked in the IONOS client area or directly in the webmail.
Deleting large attachments and emptying the trash immediately frees up space. The trash and spam folder count towards the total quota, a detail often overlooked.

DNS zone and MX records: when the domain no longer points to IONOS servers
For users who have a domain name associated with their IONOS email, a widespread reception problem (no emails arrive, regardless of the sender) often points to the DNS records, and more specifically the MX records.
MX records tell servers around the world which mail server to route emails destined for a domain. If these records have been modified (website migration, change of host, unintentional manipulation in the DNS zone), emails go elsewhere or are no longer delivered at all.
The check is done in the IONOS client area, under the “Domains” section, then “DNS” or “DNS Zone”. The MX records must point to the IONOS mail servers. Any DNS modification may take several hours to propagate, which explains why a problem that appeared after a configuration change does not resolve instantly.
An online tool like MX Lookup allows you to check in seconds which servers the MX records of a domain point to, without needing to access the client area.
IONOS server incident: how to check before acting
Before modifying parameters, there remains a reflex to adopt: check if IONOS is experiencing an ongoing incident. Sites like statut-services.fr aggregate user reports and allow you to quickly spot an outage affecting mail servers or webmail.
If an incident is confirmed, no user-side manipulation will resolve the problem. The only option is to wait for resolution by the IONOS technical teams. Modifying DNS settings or SMTP parameters during a server outage risks adding a second problem to the first.
IONOS email malfunctions rarely have a single spectacular cause. A browser cache, an incorrect SMTP port, a forgotten filtering rule, or a misplaced MX record are enough to block the entire email flow. Proceeding by elimination, starting with the network test and ending with the DNS zone, remains the most time-efficient and error-free method.



