This guide details the administrative procedures to transfer the management of a domain with the extension .de to another registrar than Infomaniak. 

Transfer a .de domain elsewhere

As long as the administrative contact listed in the WHOIS of the domain to be transferred does not include an address located in Germany, it will be impossible to request the transfer code. Refer to this other guide to modify the coordinates.

Otherwise, you can delete the domain name and in this case you must…

• … or contact Infomaniak support (by entering the email address listed in the WHOIS records) and request deletion
• … or wait for the domain to expire, after which it will be transferred to DENIC, whom you can contact to request its final deletion.

This guide concerns the Discussion List service, exclusively offered to Infomaniak users who activated it in the past and for whom a tool migration was performed in early 2025.

Introduction

• The discussion list service stands out from classic email or a newsletter service by offering unique features:
  • Allow users to subscribe to a “subscription” via a simple registration form for which the code is provided.
  • Allow one or more designated moderators to accept or reject subscriptions, send messages to subscribers, and moderate member responses before publication.
  • Allow users to contribute to the discussion by replying to a single address that automatically redistributes the email to the other members.
  • Offer an easy and GDPR-compliant unsubscribe option.
• Familiarize yourself with this other guide regarding the service limits.

Accessing the discussion list

The discussion list service, if activated in the past, is accessible within your Mail Service:

1. Click here to access the management of your Mail Service on the Infomaniak Manager (need help?).
2. Click directly on the domain name assigned to the relevant product.
3. Click on Discussion List in the left sidebar:
   

Creation and configuration of the discussion list

To create a new discussion list:

• Click on the Start button …
  
• … or on the button above your existing lists:
  

Otherwise:

1. Edit an existing list by clicking on its name:
   
2. Click on its Configuration tab:
   

The parameters necessary for the proper functioning of the system are as follows:

1. A discussion list revolves around an email address that should not yet exist in the Mail Service of the relevant domain (and that cannot be created or modified thereafter).
2. You can give a name to the list to identify it more easily if you have several or if the email address is not sufficiently explicit.
3. You can also add an additional description.
4. You must determine the email address(es) that will be moderators (= highest permission on the list).
5. You can set a language for your mailing list.
6. The setting of “who can subscribe to the list” is important:
   • It is possible to specify that the user will have to confirm their own registration (in addition to a moderator).
7. The setting of “who can write to the list” is just as important:
   • You can use the service as a one-way tool for information dissemination, for example, or as a multi-way tool for information exchange and discussion, including with non-members (with moderation)...

8. Click on Advanced Options.
   
   

9. It is possible to configure where responses should be sent…
   • … to the sender with the sender's email address visible
   • … to the list (everyone receives) with the sender's email address visible
   • … to the list as coming from the list's email address itself
10. Allows you to limit the size of emails sent via the discussion list (especially in case of attachment).
11. Allows you to customize a message that will be automatically sent to an email address upon subscription to the list.
12. Allows you to customize a message that will be automatically sent to an email address upon unsubscribing from the list.
13. Click on the button to save.

Subscription (according to settings in point 6 above)

• Subscribers can sign up by sending a message to the email address in the form list-name-join@list-domain.
• They can also be manually subscribed by the moderator via the interface and in this case, they receive a notification email whose content can be customized.
• If the subscription made by a subscriber must be validated by a moderator, the latter receives an email:
  • The moderator approves the request by clicking on the “mailto:” type link, which generates a new message that can be sent to the email address in the form nom-de-la-liste-request@domaine-de-la-liste with the subject accept adresse-mail-abonné and in the body of the message the line Approved: mot-de-passe-de-la-liste, optionally adding a line stop to prevent the execution of other scripts, for example in the case where there is a signature.
• If the subscription made by a subscriber must be validated by the subscriber himself, the latter receives an email to which he must respond (by clicking on the link to create a new reply email and pre-filled):
  
  • And in this case, the moderator receives the request at a second time, after validation by the subscriber, and he must respond to it to validate the subscription (the easiest is always to click on the link):
    

Unsubscription

• Subscribers can unsubscribe by sending a message to the email address in the form list-name-leave@list-domain.
• When unsubscribing, a confirmation request message is sent to the user.
  • The user approves the request (always by clicking on the “mailto:” type link which generates a new message that can be sent to the email address in the form nom-de-la-liste-request@domaine-de-la-liste with the subject specified in the confirmation email and an empty message body).

Sending / receiving messages

• Each subscriber can create a Mail signature and choose their name when sending an email.
• A footer is automatically added to each message sent via the mailing list:
  
• Also see the reply-to and from parameters in point 9 above.

Message Moderation

• To reject a message, the moderator must click on the link of type “mailto:” which generates a new message that can be sent to the email address in the form nom-de-la-liste-request@domaine-de-la-liste.
• When a moderator is also a member of the list, they do not receive the messages they send themselves, but they do receive those sent by other moderators.

Forms (subscription/unsubscription)

To allow a website visitor to subscribe to your list, you can generate a code to insert on your chosen site; example with Site Creator:

The Form tab allows you to specify the URL to which the user will be redirected after subscribing or unsubscribing:

• In case of an error while using the form, an error page may display the email address moderation-owner@domaine-de-la-liste allowing to contact the moderators.
• A user already subscribed to the list can sign up multiple times without any specific message being displayed.

Error management

The system indicates the number of errors encountered by an address and the date:

This guide explains how to create a new project with Public Cloud Infomaniak.

Prerequisites

• Have read and understood the Guide de démarrage.
• Have Public Cloud on your Manager Infomaniak.

Create a new project

To access Public Cloud:

1. Click here to access the management of your product on the Manager Infomaniak (need help?).
2. Click directly on the name assigned to the relevant product, on which a new project will be created
   
3. Click on the Create a project button:
   
4. Name your project.
5. An OpenStack identifier is automatically created (in the form PCU-XXXX).
6. It is possible to add a description (to specify who the identifier is intended for, for example).
7. Set a password (or send the procedure by email).
8. Click on Create to complete the project creation:
   

Resource level

The highest level of resources to which your organization has access is automatically assigned to the project. You can change it at any time once the project is created.

Also refer to this other guide if you are looking for information about actions on an existing project.

This guide explains how to solve a problem importing a .csv file into a MySQL table. The proposed alternative is to read the CSV file line by line using PHP and insert the data into the MySQL database.

"load data local infile" function disabled

The function LOAD DATA LOCAL INFILE allows you to import a CSV file into a MySQL table and is unfortunately now frequently used by hackers to gain access to certain sites hosted on machines that accept this function.

To combat malicious acts and continue to protect clients' data as much as possible, Infomaniak has disabled the LOAD DATA LOCAL INFILE function. This change does not affect users importing their CSV files (provided they do not check "CSV via LOAD DATA") via phpMyAdmin.

Here is an alternative to continue importing CSV formatted data into a MySQL table, a complete example (in French) of the code with proper error handling for opening the CSV file and inserting the data into the database.

This version uses mysqli to connect to the database and prepared statements to insert the data, thus offering better security and compatibility with recent versions of PHP and ease of implementation in your PHP script or simply in a new PHP file in your /web directory:

$NomDuFichier = "data.csv";
// Connexion à la base de données MySQL avec mysqli
$link = new mysqli("localhost", "username", "password", "database");
// Vérification de la connexion
if ($link->connect_error) {
   die("Échec de la connexion : " . $link->connect_error);
}
// Ouverture du fichier CSV en lecture
if (($handle = fopen($NomDuFichier, "r")) !== FALSE) {
   // Décomposition de chaque ligne du fichier CSV
   while (($data = fgetcsv($handle, 1000, ";")) !== FALSE) {
       // Préparation de la requête SQL
       $query = "INSERT INTO `test` VALUES (" . str_repeat('?,', count($data) - 1) . "?)";
       $stmt = $link->prepare($query);
       // Vérification de la préparation de la requête
       if ($stmt === FALSE) {
           die("Échec de la préparation de la requête : " . $link->error);
       }
       // Liaison des paramètres
       $types = str_repeat('s', count($data));  // Assume que toutes les colonnes sont de type string
       $stmt->bind_param($types, ...$data);
       // Exécution de la requête
       if (!$stmt->execute()) {
           die("Échec de l'exécution de la requête : " . $stmt->error);
       }
       // Fermeture de la déclaration
       $stmt->close();
   }
   // Fermeture du fichier CSV
   fclose($handle);
} else {
   echo "Erreur : impossible d'ouvrir le fichier.
";
   exit(1);
}
// Fermeture de la connexion à la base de données
$link->close();
?>

Getting help

Unfortunately, it is impossible to precisely indicate where these lines of code should be added in your script.

If the proposed alternative causes issues when you submit multiple CSV files to read and the procedure, for example, ends without returning a message despite the error handling points in the PHP file, it is possible that the tables and fields used are not properly indexed. In this case, also contact your webmaster.

Refer to the PHP documentation regarding fgetcsv.

This guide presents several examples of using Varnish on Cloud Server Infomaniak.

Varnish Configuration

After installation, configuring Varnish includes important rules for caching and purging. Be careful not to accidentally allow unwanted IP addresses.

Here is what a basic configuration file might look like with a few common cases and different actions/rules in one example:

vcl 4.0;
# Configuration du backend par défaut
backend default {
    .host = "127.0.0.80";  # Adresse IP du backend
    .port = "80";           # Port du backend
}
# Définition d'une liste de contrôle d'accès (ACL) pour les IPs autorisées à purger le cache
acl purge {
    "localhost";            # IP locale
    "1.2.3.4";              # IP de votre domicile
    "42.42.42.0"/24;        # Plage d'IP publique de votre entreprise
    ! "42.42.42.7";         # Exclusion d'une IP spécifique (ex : un collègue gênant)
}
# Traitement des requêtes à leur réception par Varnish
sub vcl_recv {
    # Autoriser les requêtes de purge
    if (req.method == "PURGE") {
        # Vérification si l'IP du client est autorisée à purger
        if (!client.ip ~ purge) {  # 'purge' fait référence à l'ACL définie plus haut
            # Retourne une page d'erreur si l'IP n'est pas autorisée
            return (synth(405, "Cette IP n'est pas autorisée à envoyer des requêtes PURGE."));
        }
        # Si l'IP est autorisée, purger le cache pour cette requête
        return (purge);
    }
    # Autoriser la purge de toutes les images via une requête PURGEALL
    if (req.method == "PURGEALL" && req.url == "/images") {
        if (!client.ip ~ purge) {
            return (synth(405, "Cette IP n'est pas autorisée à envoyer des requêtes PURGE."));
        }
        # Invalider tous les objets en cache correspondant à des images
        ban("req.url ~ \.(jpg|png|gif|svg)$");
        return (synth(200, "Images purgées."));
    }
    # Ne pas mettre en cache les pages avec une autorisation (header Authorization)
    if (req.http.Authorization) {
        # Passer la requête directement au backend sans la mettre en cache
        return (pass);
    }
}
# Traitement de la réponse du backend avant de la renvoyer au client
sub vcl_backend_response {
    # Mise en cache des images pour une durée de 1 jour
    if (beresp.http.content-type ~ "image") {
        set beresp.ttl = 1d;
    }
    # Si le backend indique que la réponse ne doit pas être mise en cache, respecter cette consigne
    if (beresp.http.uncacheable) {
        set beresp.uncacheable = true;
    }
}

Purge from the CLI interface

From there, the rules stated in the configuration above apply to all requests, so if the configured site is "domain.xyz", you can simply use the CLI tool "curl" and do the following:

# Envoyer une requête PURGE pour purger la page d'accueil de "domain.xyz"
$ curl -X PURGE https://domain.xyz/
# Réponse renvoyée par le serveur Varnish
<!DOCTYPE html>
<html>
<head>
    <title>200 Purged</title>
</head>
<body>
    <h1>Erreur 200 : Purge effectuée</h1>
    <p>La page a été purgée avec succès.</p>
    <h3>Guru Meditation:</h3>
    <p>XID: 2</p>
    <hr>
    <p>Serveur de cache Varnish</p>
</body>
</html>

And there, the homepage has been purged. Or to purge another URL, simply point the request to the latter:

# Envoyer une requête PURGE pour purger un fichier spécifique à "domain.xyz"
$ curl -X PURGE https://domain.xyz/some_path/some_file.html
# Réponse renvoyée par le serveur Varnish
<!DOCTYPE html>
<html>
<head>
    <title>200 Purged</title>
</head>
<body>
    <h1>Erreur 200 : Purge effectuée</h1>
    <p>Le fichier a été purgé avec succès.</p>
    <h3>Guru Meditation:</h3>
    <p>XID: 4</p>
    <hr>
    <p>Serveur de cache Varnish</p>
</body>
</html>

Or, as indicated in the VCL configuration, purge all images:

# Envoyer une requête PURGEALL pour purger toutes les images dans "domain.xyz"
$ curl -X PURGEALL https://domain.xyz/images
# Réponse renvoyée par le serveur Varnish
<!DOCTYPE html>
<html>
<head>
    <title>200 Purged images</title>
</head>
<body>
    <h1>Erreur 200 : Images purgées</h1>
    <p>Toutes les images ont été purgées avec succès.</p>
    <h3>Guru Meditation:</h3>
    <p>XID: 32770</p>
    <hr>
    <p>Serveur de cache Varnish</p>
</body>
</html>

Purge from a CMS

It is a bit more difficult to illustrate this case because there are many ways to manage caching from a backend. In the configuration example above, a control on the header "Uncacheable" is added, which disables caching. With this option, any CMS could simply set this header on the response to disable caching for this request, for example.

From any PHP code and with the configuration above, you can simply send an HTTP request and use this snippet to perform a PURGE of the cache:

<?php
if ($curl = curl_init("http://127.0.0.1/some_url")) {
    curl_setopt_array($curl, [
        CURLOPT_RETURNTRANSFER => true,
        CURLOPT_CUSTOMREQUEST => "PURGE",
        CURLOPT_HTTPHEADER => [
            "Host: {$_SERVER['HTTP_HOST']}"
        ]
    ]);
    curl_exec($curl);
    if (curl_getinfo($curl, CURLINFO_HTTP_CODE) == 200) {
        echo "Cache purged!";
    }
    curl_close($curl);
}
?>

Learn more

Useful links regarding the Varnish configuration language (VCL) to control request processing, routing, caching and several other aspects:

• VCL Tutorial
• VCL user guide
• VCL Reference

This guide shows how to export and save the contacts from the "Liste de discussion" tool into a CSV file (format .csv).

Export contacts into a file

The discussion list tool is accessible within your Mail Service:

1. Click here to access your Mail Service management on the Infomaniak Manager (need help?).
2. Click directly on the domain name assigned to the relevant product.
3. Click on Liste de discussion in the left sidebar.
4. Click on the name of your list.
5. Click on the Subscribers tab.
6. Click on Download the list in CSV format:
   

The CSV file will be downloaded to your computer's hard drive.

To import these contacts into the Newsletter tool:

1. Change the file extension from .txt to .csv if necessary.
2. Familiarize yourself with this other guide.

This guide explains why a website may be "broken" or stop displaying anything, following a password change at the level of a Web Hosting.

Broken link with the database

When your website, and more specifically a script (CMS, WordPress, Prestashop or any other application using MySQL databases), can no longer connect to the MySQL MariaDB or other database, an error message may display, such as:

• Erreur lors de la connexion à la base de données
• Database Error: Unable to connect to the database:Could not connect to MySQL
• Link to database cannot be established

Remember your last action…

In case an error occurs on your site, you should always examine the recent history. In this case, has there been…

1. … an action on your part regarding the configuration file of the script in question? Has it been altered, modified, or moved?
   
   Sometimes, the unintentional insertion of a space before or after a word can sever the connection between the web server and the database server. Go back and review your file modifications.
   If necessary, restore an older version of the files that you recently modified.
    
2. … an action regarding the database password in the Infomaniak Manager?
   
   If you change the password of your database via the Infomaniak Manager, then your script, which retrieves its information from the databases, will no longer display anything.Changing something in the Infomaniak Manager means you have to change it everywhere else. This change that you made in the Manager, you also need to report / reflect it in the configuration file of the script by connecting via FTP and going to modify the appropriate file, usually "wp-config.php", "configuration.php" or similar.
    
3. … a server move announced by Infomaniak?
   
   If this error follows a server move or another operation announced by email and related to the product in question, do not hesitate to contact Infomaniak support.

Thank you for entrusting the management of your domain names to Infomaniak.

This guide allows you to quickly use the essential functions of your new product.

Some important guides

Administrative

• Protect your personal information in the WHOIS
• Protect your domain against theft and loss
• Update the domain name details
• Who does a domain name belong to?
• Use the free services (mail and Web 10 Mo) linked to a domain managed by Infomaniak
• Transfer another domain to Infomaniak

Technical

• Edit the records (A, MX, Web, Mail, etc.) of a domain registered with Infomaniak to join, for example, a hosting service not managed by Infomaniak
• Change the DNS servers
• Redirect traffic
• Set up DynDNS

• Link a domain to another
• Unlink a domain, synonymous with a domain name

• Link a domain name to the Mail Service
• Add an additional domain to the Mail Service
• Unlink a domain linked to the Mail Service

• Link a domain name to Infomaniak Web Hosting
• Add an additional domain to a website
• Unlink a domain linked to the website

• Link a domain name to kSuite
• Add an additional domain to kSuite

• Link a domain name to the NAS Synology Infomaniak
• Link a domain name to Wix
• Link a domain name to Site Creator
• Link a domain name to the Newsletter
• Link an Infomaniak domain to an external service

Otherwise, find the topic you are looking for among the rest of the FAQs.

Click here to share a review or suggestion about an Infomaniak product.

This guide explains how to install and configure systemd on a Serveur Cloud and presents the main commands that can be used.

Prerequisites

• Follow the installation guide for systemd on Serveur Cloud.
• Consult the official documentation to learn about all the possibilities offered by systemd
• The "unit" files must be placed in: ~/.config/systemd/user/ (/home/clients/absolute-path-id/.config/systemd/user) (replacing absolute-path-id visible in your Manager) and the permissions must be set to 0644.
• The --user parameter must be specified in each command.

Main commands

Here is a non-exhaustive list of commands that can be used with systemd.

Force systemd to reload the unit files and take the changes into account:

systemctl --user daemon-reload

Activating a service:

systemctl --user enable --now SERVICENAME.service

Checking the status of a service:

systemctl --user status SERVICENAME.service

Configuration of Node as a service with systemd

It will be necessary to create a "Unit" file with the ".service" extension, which will need to be saved in the directory:

~/.config/systemd/user/

It is possible to reuse the example below by replacing the values starting with {}:

[Unit]
Description={Le nom du service} # Spécifier ici un nom du service. Celui-ci est obligatoire mais n'a pas d'impact sur le fonctionnement

[Service]
Restart=always
Environment=NODE_VERSION={la version souhaitée} # Spécifier ici la version de Node à utiliser. S'assurer qu'elle soit installée au préalable avec "nvm install {la version souhaitée}"
WorkingDirectory=%h/{repertoire du projet Node} # %h correspond à la racine de l'hébergement
ExecStart=/bin/bash -c "exec $HOME/.nvm/nvm-exec {commande de lancement du script node}" # Cette commande dépend du projet. Par exemple, "npm run start", "npm run serve" ou encore "node server.js" sont courants

[Install]
WantedBy=default.target

Additional actions with a Unit file

systemctl --user daemon-reload

Start the service (if it is already active, nothing happens):

systemctl --user start [Nom du Unit]

Stop the service (if it is not active, nothing happens):

systemctl --user stop [Nom du Unit]

Restart the service (if it is not running, it will be started):

systemctl --user restart [Nom du Unit]

Get information about the service; namely:

• "Active" which indicates whether the service is running and for how long
• "CGroup" shows the process group managed by the service, this allows you to see the active processes, with their arguments and their ID

Below "CGroup" are any logs (the standard output and error of the process):

systemctl --user status [Nom du Unit]

Enable automatic startup of the service at server boot; NB: this does not start the service:

systemctl --user enable [Nom du Unit]

Disable the automatic startup of the service at server boot; NB: this does not stop the service:

systemctl --user disable [Nom du Unit]

Configuration with user entries:

[Unit]
Description="nom service"

[Service]
Restart=always
Environment=NODE_VERSION=16.17
WorkingDirectory=%h/sites/"nom-repertoire-site"/
ExecStart=/bin/bash -c "exec $HOME/.nvm/nvm-exec npm run start"

[Install]
WantedBy=default.target

This guide helps you identify and correct most email errors encountered after sending an email to a recipient. Refer to this other guide if you are looking for information about errors obtained when configuring an email address in a software/email client.

Introduction

• Generally, a mail error message is the result of…
  • … an incorrect configuration of the domain name used with your email,
  • … an issue with your recipient's (mail provider).
• In any case, a delivery failure report (Mailer Daemon or Mail Delivery Subsystem) containing the explanation is sent to the sender.

Searching for and identifying the email error

When your message does not reach your recipient, an initial failure report (Temporary Delivery Failure Report) is sent and specifies that the server will attempt to resend your message several times.

A final delivery failure report (Final Delivery Failure Report or Undeliverable Mail) issued by the recipient's server is sent to the sender (via a passage through the Infomaniak mail server, hence the mention of Infomaniak at the beginning of most error messages you may receive) to inform them that the email could not be delivered even after several attempts.

The notification always contains the reason for the failure. Example below:

This is the mail system at host smtp-1-1234.mail.infomaniak.ch.
I'm sorry to have to inform you that your message could not be delivered to one or more recipients. It's attached below.
For further assistance, please send mail to postmaster.
If you do so, please include this problem report. You can delete your own text from the attached returned message.
The mail system anna.a@abc.xyz: host mxbw-abc-xyz.abc-ab12.abc.ch[123.456.789.00] said: 550 5.1.1
anna.a@abc.xyz recipient rejected, account administratively disabled (in reply to RCPT TO command) 

So here the address of your recipient is visibly suspended by their email provider (account administratively disabled).

Sometimes you need to look for the reason for the error message received among its attachments (often a raw text file). Example:

Reporting-MTA: dns; mxbw.abc.ch‍ [123.456.789.00]
Received-From-MTA: dns; smtp-1-1234.mail.infomaniak.ch [12.345.678.99]
Arrival-Date: Tue, 01 Aug 2023 15:49:22 +0200
Final-recipient: rfc822; anna.a@abc.xyz
Diagnostic-Code: smtp; 552 RCPT TO:anna.a@abc.xyz‍ Mailbox disk quota exceeded
Last-attempt-Date: Tue, 01 Aug 2023 15:49:22 +0200

Here the mailbox of your correspondent external to Infomaniak seems to be full (Mailbox disk quota exceeded).

Most common cases

SPF Failure

The SPF (Sender Policy Framework) record is not correctly configured:

Subject: Delivery Status Notification (Failure)
From: Mail Delivery System mailer-daemon@domain.xyz
To: Anna.A anna.a@abc.xyz
This is an automatically generated Delivery Status Notification.
Delivery to the following recipient failed due to SPF failure:
anna.a@abc.xyz
Technical details of SPF failure:
The sender's domain domain.xyz does not have a valid SPF record. Please contact your email administrator to correct the SPF configuration.

Solution: check the configuration of your domain name and especially the SPF record if your website is hosted with Wix or another provider.

User Unknown

The email address specified in the message is invalid or does not exist:

Subject: Delivery Status Notification (Failure)
From: Mail Delivery System mailer-daemon@domain.xyz
To: Anna.A anna.a@abc.xyz
This is an automatically generated Delivery Status Notification.
Delivery to the following recipient failed permanently:
anna.a@abc.xyz
Technical details of permanent failure:
The email address does not exist. Please check the recipient's email address and try again.

Solution: carefully check the recipient's email address and correct it if necessary; ensure that you are using a valid email address for the recipient.

Temporary Failure

Le serveur de messagerie du destinataire rencontre des problèmes temporaires ou est indisponible.

Solution: wait for some time, then try sending the message again later. If the problem persists, contact the recipient's technical support for help.

Blocked by SPAM Filter (or Content Rejected)

The recipient's mail server has blocked the message due to anti-spam filtering rules:

Subject: Delivery Status Notification (Failure)
From: Mail Delivery System mailer-daemon@domain.xyz
To: Anna.A anna.a@domain.xyz
This is an automatically generated Delivery Status Notification.
Delivery to the following recipient failed due to the message being rejected as spam:
anna.a@domain.xyz
Technical details of delivery failure:
The content of the message triggered the spam filters of the recipient's email server. Please review the message content and try again.

Solution: check if your message contains elements that may be considered spam (keywords, suspicious links, etc.). Contact the recipient to check if the message has been filtered into the junk mail folder.

Refer to this other guide regarding outgoing spam and this other guide regarding incoming spam.

Bad Reputation

The recipient's mail server has blocked the message due to anti-spam filtering rules:

gmail-smtp-in.l.google.com said: 550-5.7.1
Our system has detected that this message is likely suspicious due to the very low reputation of the sending domain.
To best protect our users from spam, the message has been blocked.
Please visit https://support.google.com/mail/answer/188131 for more information.

Solution: check the reputation of the domain, determine if one of your email addresses has been recently and involuntarily exploited for malicious purposes, for example.

Domain Not Found (or DNS Error)

Le nom de domaine du destinataire n'a pas pu être résolu ou n'existe pas.

Solution: check the spelling of the recipient's domain and correct it if necessary; ensure that the domain name and DNS are valid and active.

Mailbox Full

La boîte de réception du destinataire est pleine, empêchant la réception de nouveaux messages.

Solution: inform the recipient of the situation and ask them to free up space by deleting emails or archiving items.

This cannot happen with email addresses managed by Infomaniak since they have no storage size limit.

Part of their network is on our block list

If the error message (usually obtained after sending from an online tool, placed on the server where your website is hosted, for example a order confirmation from Prestashop or another online store that you manage) contains this:

host hotmail-com.olc.protection.outlook.com[104.47.30.97] said: 550 5.7.1
Unfortunately, messages from [89.123.456.789] weren't sent. Please contact your Internet service provider since part of their network is on our block list.

Solution: change the email sending method. The sending is unauthenticated and is sent from the server with a specific IP address that is apparently blocked by the recipient for some reason (Infomaniak does not intervene to request unblocking). Therefore, you need to configure the online tool to perform authenticated sendings.

Less frequent errors

Deferred - Delayed

The error message Deferred - Delayed - Warning: message still undelivered after 4 hours, Will keep trying until message is 3 days old means that the Infomaniak mail server tried to connect to your contact's mail server to send the message but was unable to do so for an undetermined reason. This error message specifies that the Infomaniak server will continue to attempt to send your message for the period specified in the error message. If, after this delay, the message has still not been delivered, you will receive a final error message informing you that your message could not be delivered and that your contact did not receive it.

Greylisting Delay

This error Greylisting Delay occurs when the recipient's mail server, like Infomaniak, uses a technique called "greylisting" that imposes a temporary delay on the first delivery attempt of a message from an unknown sender. The Mailer Daemon may possibly send an error report indicating that delivery has been delayed due to greylisting. The error may also mention banned sender. You should try resending your message a few minutes/hours later.

Malware message rejected

This error Malware message rejected occurs when the message contains an attachment, a link to a storage site like Dropbox, or dynamic content, including in the "forwarded" part of the message (in the case of a "forward" message, for example). You should try resending the message from the Web app Mail Infomaniak (online service mail.infomaniak.com) instead of a mail application, and remove any content that may cause this error.

Message Size Exceeded / File Too Large

These errors Message Size Exceeded / File Too Large occur when the size of the message (or attachments) exceeds the limit allowed by the recipient's mail server. The Mailer Daemon will return an error report indicating that delivery failed due to the message size being exceeded.

Rate Limit Exceeded

This error Rate Limit Exceeded occurs when the sender exceeds the allowed frequency or volume limit set by the recipient's mail server. Mail servers may impose these limits to prevent spam or system overload.

Sender denied: auth guards failed

Refer to this other guide if you encounter an error Sender denied: auth guards failed.

The message contains a Unicode character in a disallowed header

This error The message contains a unicode character in a disallowed header may appear if you have inserted a special character like a heart ♥ e.g. in the body of the email, the subject or especially in the full name; the risk of being rejected by providers is very high: it is best to keep the use of signs, characters and fonts as simple as possible.