This guide presents the DNS Diagnostic tool, which allows you to verify the relationships between…

• DOMAIN NAME at Infomaniak
  
  and
  
• MAIL SERVICE with Infomaniak

… are correct, so that Mail traffic is directed to the right place.

Introduction

• To verify, the tool checks the MX records, SPF, etc.
• This allows you to detect and correct certain Mail issues, particularly if they are related to DNS (technical information that essentially determines where certain Mail traffic should be directed) by taking action at the domain level.
• Automatic correction is only possible when the domain name is present in the same Organization as the product to which it must be linked.
  • If this is not the case, then the correction must be done manually.

Troubleshooting DNS issues

To access the DNS diagnostics for your domain name:

1. Click here to access the Mail Service management in your Infomaniak Manager (❓: help).
2. Click on the name of the Mail Service in question:
   
3. Click on Domain Management in the left-hand menu:
4. Click on DNS Diagnostics in the left-hand menu.
5. Click the button if necessary to refresh the information, which should then be displayed in green.
6. If DNS issues are detected, a red display in the table indicates this:
   
   1. Correct each error individually by clicking the button to the right of the item in question…
   2. … or correct all errors at once using the button above the table.

Refer to this other guide regarding the same automatic verification process, but for Web Hosting.

And if necessary, consult the security diagnostic related to email.

This guide explains how to modify specific entries, records of type A & AAAA (❓: help), MX (❓: help), TXT (❓: help), etc. in advanced (expert) mode within the DNS zone of a domain registered with Infomaniak.

Prerequisites

• You must have a domain name with Infomaniak or at least a DNS zone.
• Understand:
  • how a domain and a DNS zone work (❓: help) before modifying the latter,
  • that the DNS zone presented here is valid and used only if the name servers are those of Infomaniak (❓: help),
  • that any DNS addition/modification may take up to 48 hours to propagate (❓: help).

Modify an existing record

To configure the services associated with the domain and enable the correct resolution of domain names to the corresponding resources (such as external websites, third-party email servers, etc.):

1. Click here to access the domain management section in your Infomaniak Manager (❓: help).
2. Click on the name of the domain in question.
3. Click on DNS Zone in the left-hand menu.
4. Click on Advanced view:
   
5. Edit the desired information.
   • The syntax is accepted in BIND format (❓: help).
6. Save your changes:
   

Restore a DNS zone

Thanks to Expert mode, you can use versioning to find a previous version of your domain name's DNS zone and restore it to its state at a specific point in time:

1. Once in the Advanced View tab (see above), click on Current Version to display the menu containing previous dates.
2. Click on the desired date to view the changes.
3. Click the blue Save button on the right to revert to the selected version:
   
4. Click on the second drop-down menu if necessary to access the configuration restoration for delegated subdomains.

DNS Diagnostics

A tool available in your Manager (❓: help) allows you to easily correct certain problematic records.

This guide explains how to obtain the EPP code for your domain name at Squarespace (formerly Google Domains) so that you can transfer it to Infomaniak and set up this Dynamic DNS (DDNS) service free of charge.

Introduction

• Between 2023 and 2024, all domains registered with Google Domains were transferred to Squarespace, which no longer offers DDNS (Dynamic DNS).
• The terms "EPP", "AuthCode", "AuthInfo", "transfer code", and "authorization code" all refer to alphanumeric sequences specific to the domain, the main purpose of which is to verify the owner's authorization before a transfer between Registrars.
• Consult the main guide for the rest of the transfer procedure.
• ⚠️ This involves transferring a domain name that you own with a different provider than Infomaniak, so that the future management of this domain is handled by Infomaniak; therefore, this is not an internal transfer from one account holder to another, and the code you need to obtain is not a code for an internal transfer to your current provider.

Transfer your domain name to Infomaniak

To obtain the authorization code from your current provider:

1. Click here to log in to the management interface for your products at your current Registrar.
2. Refer to the complete procedure provided by Squarespace to obtain the code and keep it in a safe place.
3. Once you have obtained the authorization code, consult the main Infomaniak guide regarding the rest of the domain name transfer procedure.
4. Once the domain has been transferred to Infomaniak, consult this Infomaniak guide to recreate the Dynamic DNS you had with Google, if necessary.

This guide explains how to configure a dynamic DNS record (Dynamic DNS, DDNS) for a domain name whose DNS zone is managed by Infomaniak. This free alternative to Dyn and DynHost is very useful if you want to access devices connected to the Internet with a dynamic IP address from outside your network (e.g., a NAS, a surveillance camera, an Internet/home automation router/box, etc.).

Prerequisites

• The DNS zone for the domain name must be managed with Infomaniak.
  • If necessary, transfer your domains to Infomaniak. (❓: help).
• Your device or application must support dynamic DNS records.

Specific guides

The following guides explain how to link a domain name with:

• … a Synology NAS
• … a Qnap NAS
• … Zyxel / Sunrise Internet Box / TP-Link solutions
• … a UniFI device
• … Swisscom Internet Box
• … Fritzbox
• … Home Assistant
• … Jeedom
• … Linux via ddclient
• … potentially everything via the API

Add a Dynamic DNS

To create a dynamic DNS for your domain:

1. Click here to access the domain management section in your Infomaniak Manager (❓: help).
2. Click on the name of the domain in question.
3. Click on Dynamic DNS in the left-hand menu.
4. Click on the blue Add a Dynamic DNS button.
5. Enter the required information:
   
   1. Choose the desired subdomain or leave the Dynamic DNS Name field blank to use the main domain.
   2. Enter an IP address; this will then be dynamically updated by your device/app.
   3. Define an ID / password pair (uppercase, lowercase + numbers, no special characters); the latter must be entered in the configuration of your device/app.

This guide details the entire procedure for transferring a domain name from your current provider to Infomaniak.

Introduction

• Validity and registration date: ensure that the domain was created or transferred at least 60 days ago and that the email addresses associated with the owner's profile are valid.
• Expiration: during a transfer, no already paid period is lost; the domain's expiration date will be automatically extended by one year.
• DNS Backup: If you plan to keep some services (Web, Mail, etc.) with another provider after the transfer, note your current DNS records (A, MX, TXT, CNAME) beforehand.
• External vs. Internal Transfer: This involves having Infomaniak manage your domain instead of your current registrar (this is not a transfer of ownership between two accounts with the same provider).
• Terminology: The terms EPP, AuthCode, AuthInfo, "transfer code", and "authorization code" all refer to the same alphanumeric key used to validate the transfer of a domain between registrars.

1. Obtain the authorization code (AuthCode)

Log in to your current provider's customer account to retrieve the authorization code. Also, remember to disable transfer protection if it is enabled.

2. Start the transfer with Infomaniak

Go to the Infomaniak domain transfer page, find your domain name, and then click the button to start the process.

3. Configure the options and DNS management

Enter the details of the account holder. At this stage, configure the toggle switch for DNS management:

Leave the switch activated if…

• All your services (hosting, emails) are already with Infomaniak (or if you are already using the DNS servers ns11.infomaniak.com and ns12.infomaniak.com).
• No product or service is linked to this domain name.

Disable the button if…

• Some services (website, email) remain hosted elsewhere than with Infomaniak. In this case, be sure to keep your current DNS settings and verify beforehand that your DNS zone is still available with your previous registrar.

Note: If you are unsure about your current DNS settings, perform a search on the Infomaniak WHOIS service.

4. Enter the authorization code

Paste the AuthCode / EPP code retrieved in step 1 into the field provided, validate the code, and then click Next.

5. Adjust the order and confirm

This final step allows you to adjust your renewal preferences and pay any applicable transfer fees (depending on the extension).

Accept the terms and conditions, then click Next to complete the order.

6. Monitor the transfer from the Manager

Access your Infomaniak Manager to monitor the progress of the transfer. If any issues or blockages occur, an automated email will provide instructions on how to proceed.

Batch Transfer

To transfer multiple domains simultaneously:

1. Use the Infomaniak batch transfer assistant.
2. Enter the list of domains and their respective authorization codes, or import a file in .csv or .xlsx format (2 columns, up to 300 lines).

DNS propagation and delays

• Transfer duration:
  • Variable depending on the extension's registry (e.g., up to 8 days for a .FR domain, as defined by Afnic) and the responsiveness of your previous registrar in releasing the domain.
    • Consult the details per extension on Infomaniak's pricing table.
• DNS propagation:
  • Any DNS zone modifications require a propagation time of up to 24 hours.
• During the transfer:
  • The DNS zone cannot be modified while the transfer procedure is in progress.

This guide is for you if you receive the The web host does not exist error when visiting a website address on an Infomaniak Web Hosting service.

Introduction

• This type of error most often occurs because your domain name is not correctly linked to your website (your domain name probably points to the wrong IP address or is incorrectly configured).
  • Example: a domain abc.xyz that is incorrectly configured and points to an IPv4 address for a Starter hosting plan, and to an IPv6 address for a shared hosting plan…

Troubleshooting Domain - Website Linking Issues

To get your website back online:

• Check the DNS zone of your domain name, especially its A records.
• Correct them if necessary by indicating the IP address of your hosting.
  • Any DNS addition/modification may take up to 48 hours to propagate (❓: help).

To do this, the easiest way is to use the DNS Diagnostic tool (❓: help) to automatically correct the settings, by grouping the products (❓: help) into the same Organization if necessary.

This guide is for users who own a domain name on the Infomaniak infrastructure and are experiencing a DMARC issue when using certain Google tools such as Meet or Calendar.

Troubleshooting a DMARC error

To ensure compatibility between your domain name configuration (which has a DMARC policy (❓: help) of type reject) and the use of certain Google services, it is necessary to add the corresponding SPF record:

• Before: v=spf1 include:spf.infomaniak.ch -all
• After: v=spf1 include:spf.infomaniak.ch include:_spf.google.com -all

To edit the SPF record currently configured in the DNS zone of your domain name:

1. Click here to access the domain management section in your Infomaniak Manager (❓: help).
2. Click on the name of the domain in question.
3. Click on DNS Zone in the left-hand menu.
4. Click on the action menu ⋮ located to the right of the TXT record containing the relevant SPF value.
5. Click on Edit:
   
6. Edit the field by adding include:_spf.google.com on the same line after the existing include Infomaniak, and before the final -all.
7. Click on the Save button:
   

Please refer to this Google documentation if you need information on configuring Google's SPF.

This guide explains how to easily set up a redirection for your domain name managed with Infomaniak.

Introduction

• A web redirection allows you to redirect a domain name or subdomain to the internet address of your choice.
• This procedure is only valid if the domain's DNS records are managed by Infomaniak (❓: help) and if Custom Brand is not activated.
  • Any DNS addition/modification may take up to 48 hours to propagate (❓: help).
• If necessary, create a redirection for your domain with and without the www (domain.xyz and www.domain.xyz).

Redirect a domain to the URL of your choice

To do this:

1. Click here to access the domain management section in your Infomaniak Manager (❓: help).
2. Click on the name of the domain in question.
3. Click on Web Redirections in the left-hand menu.
4. Click on the Add a redirection button:
   
5. Enter the destination address (under To).
6. Choose between a 301 or 302 redirect.
7. The advanced options allow you to specify a redirect in the form of an iframe (invisible, but not recommended).
8. Click the button to Confirm:
   

This guide explains how to connect a domain name managed with Infomaniak to an external service.

Specific guides

Click on the link corresponding to the external service you wish to connect to your domain name registered with Infomaniak:

• Wix
• Shopify
• Google Sites
• dynamic devices such as a NAS, an Internet box, or a smart home hub, etc.

Guide for any other external service

To connect your domain name to any other external service such as Odoo, Microsoft 365, or Squarespace, follow the procedures below:

1. Click here to access the domain management section in your Infomaniak Manager (❓: help).
2. Click on the name of the domain in question.
3. Click on Connect a service in the left-hand menu.
4. Click the blue Connect button on the tile corresponding to your external service and follow the procedure:
   

If the external service you want to connect is not in the list, you will need to manually change some of the technical information for your domain name:

• Refer to this other guide to modify all DNS records if that is what you were asked to do…
• … or this other guide if you only need to modify specific DNS records (for example, the MX record if you need to link your domain to an external email service).

This guide explains how to link a domain name managed by Infomaniak to a Wix hosting plan.

Introduction

• A website created on Wix cannot be exported so that its content can be hosted on third-party servers, such as those of Infomaniak.
• It is therefore recommended to create the website directly with Infomaniak using Site Creator or WordPress.

Connect your Wix site to your domain name with Infomaniak

Prerequisites

• Obtain the two DNS servers provided by Wix, in the format ns0.wixdns.net and ns1.wixdns.net, for example (❓: help).

To connect a website hosted on Wix with a domain name hosted on Infomaniak:

1. Click here to access the domain management section in your Infomaniak Manager (❓: help).
2. Click on the name of the domain in question.
3. Click on Connect a service in the left-hand menu.
4. Click on the blue Connect button on the WIX tile:
   
5. Enter the 2 Wix DNS servers (see the prerequisite above).
6. Click the Next button:
   

Your domain name will point to Wix servers within a few hours, and all web and email traffic will now be routed to Wix.

This guide explains how to redirect a domain name directly to another, or how to automatically send visitors to your website to another page address (internal or external URL).

Introduction

• To redirect traffic, you will need to take action…
  • … either on the domain name itself (it must be hosted by Infomaniak and its DNS must also be Infomaniak's),
  • … or on the code present in your pages (e.g., .htaccess page, homepage, etc.) if you have a website.

Acting on the domain name

Via Web Redirection Tool

The tool available in the Manager allows you to easily manage your domain name (or subdomain) and redirect it to the internet address of your choice.

via DNS modifications or A record updates

Change the DNS of the domain name or modify its A/AAAA records to redirect web traffic to another provider.

Modify the page code…

… by inserting HTML code

Insert this line of code between the <head> and </head> tags of your homepage (usually named index.html):

<meta http-equiv="refresh" content="5;url=INSERT-HERE-NEW-URL">

Replace 5 with the desired wait time in seconds (0 for immediate execution).

The Google search engine indicates that it is preferable to use a 301 redirect on the server-side (see below). The W3C also advises against using it.

… via PHP code to be inserted

If the website page has a .php extension, insert this function call at the very top of the file:

header("refresh: 5; url=INSERT-HERE-NEW-PAGE-URL");
```
… via the .htaccess file

… via fichier .htaccess

To redirect all traffic to your site (regardless of the page being accessed) to another address, insert the following into the .htaccess file at the root of your site:

RewriteEngine On
RewriteRule ^(.*)$ INSERT-HERE-NEW-URL/$1 [R=301]

To target the page that should be redirected:

Redirect permanent /old_page.html insert destination URL here

Redirectpermanent, Redirect permanent, and Redirect 301 are equivalent commands.

The following is another example of redirecting a sub-section to the homepage (this directive has the advantage of working with "deep links" unlike a permanent redirect):

RewriteEngine on
RewriteRule "old/path/url" "/" [L]

Refer to this other guide for more information.

This guide will help you if you receive error emails that mention SPF when sending emails to gmail, microsoft, or similar addresses.

Are all your services with Infomaniak?

The Global Security tool informs you of any configuration inconsistencies regarding your Infomaniak Mail Service.

Are some of your services located elsewhere?

To resolve an email sending issue when your email is managed by Infomaniak and your website is hosted with another provider (such as Wix, for example), and in this situation, the DNS zone for your domain name is managed elsewhere, please refer to this other guide.

This guide helps you troubleshoot configuration errors if you are experiencing difficulties linking your domain name to Site Creator.

Common issues and solutions

Identify the current status of your domain to apply the appropriate solution:

This guide will help you quickly use the essential functions of your new Cloud Server.

Install an application

• Create a WordPress website
• Install a web application (ownCloud, Joomla, Typo3, Drupal, phpBB, Simple Machines Forum, Magento, Prestashop, …)
• Install applications/technologies on Cloud Server (Fast Installer)

Configure the server

• Manage your MySQL databases
• Manage MySQL limits
• Manage your FTP accounts/users
• Manage and publish files on your hosting via FTP
• Modify resources and configuration

Manage websites and domains

If your domain name is not managed by Infomaniak or your hosting is not managed in the same user account as your domain name, please refer to this other guide to configure the DNS or records to link the domain name to your hosting. Also:

• Migrate a shared web hosting to a Cloud Server
• Add a website or subdomain to your hosting (multisite)
• Preview your website even if your domain name does not yet point to Infomaniak's servers

Thank you for choosing to customize your account with Custom Brand!

Introduction

• Available as an option with any Infomaniak plan or already included with kSuite Enterprise, discover this customization tool to make your web addresses unique, add a logo, or add an image slideshow to your Infomaniak organization login page.
• The Web Redirection tool will no longer be usable on your domain after Custom Brand is activated on it.

Custom Brand Customization Guides

Prerequisites

• Own a domain name with Infomaniak (transfer it if necessary).
  • Its extension must be among those supported by Custom Brand.
  • Note that this also works with a subdomain.
• Configure the domain to use Infomaniak's DNS servers.

Next, to use Custom Brand:

• Getting started with Custom Brand: customize URLs & the interface
• Troubleshooting:
  • Check the associated domain
  • Block the associated domain
  • Disable Custom Brand

Customize your web addresses with your domain

Customize your Organization's interface

The following interface options can be modified from the kSuite settings: :

• Add your logo to your Organization's interface.
• Added a 3-image panorama to the login page.
• Changed the text and button color on the login page.
• Customization of kDrive sharing (see this other guide).

This guide presents Infomaniak's Public Cloud offering, an Infrastructure as a Service (IaaS) solution based on OpenStack that provides the resources you need to develop your projects.

Introduction

• Infomaniak's Public Cloud, a platform powered by the open-source OpenStack technology, offers virtual instances with several performance profiles:
  • IOPS-optimized instances
  • RAM-optimized instances
  • Instances with the latest generation GPUs
• Range of tools available:
  • Object storage (compatible with S3)
  • Managed Kubernetes service
  • Managed databases
  • Load balancers
  • DNS management
  • Private network services
• Numerous integrations, including:
  • A unified API
  • A Terraform/OpenTofu connector
  • An Ansible collection
• The infrastructure is available in multiple regions in Switzerland, with several availability zones.

Getting started

• The Infomaniak Public Cloud user guide provides numerous tutorials, step-by-step guides, and best practices.
• You can also access all Public Cloud FAQs, including:
  • Create a new project
  • Take action on an existing project
• The list of scheduled maintenance and current issues can be found at https://status.infomaniak.cloud/.
• Discover the Public Cloud presentation (replay of the Infomaniak 2022 Webinar):
  
  
   
  • Understand simply what a Public Cloud (IaaS) is, its uses, and who it is for
  • Complete tutorial for deploying WordPress with OpenStack in Infomaniak Public Cloud (scripts included)
  • Frequently asked questions about Infomaniak Public Cloud (2022)

Pricing

• How billing works
• Estimate the cost of resources used

Community forum & Feedback

• Click here to share feedback or suggestions about an Infomaniak product.
• Access the Reddit page created to facilitate technical discussions with the user community.

This guide helps you identify and correct most email errors encountered after sending an email to a recipient.

Introduction

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

 1. Basic principles and error identification

How delivery failure reports work

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

A final non-delivery report (Final Delivery Failure Report or Undeliverable Mail) issued by the recipient's server is sent to the sender (via the Infomaniak mail server, which is why Infomaniak is mentioned 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) 

Here, the address of your contact is clearly 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 plain 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 external contact at Infomaniak appears to be full (Mailbox disk quota exceeded).

2. Most common cases

SPF Failure

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

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 your domain name configuration, and in particular, the SPF record if your website is hosted on 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

The recipient's mail server is experiencing temporary issues or is unavailable.

Solution: Wait a while, then try sending the message again later. If the problem persists, contact the recipient's technical support for assistance.

Blocked by SPAM Filter (or Content Rejected)

The recipient's mail server 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 verify if the message was filtered into the spam folder.

Please refer to this other guide about outgoing spam and this other guide about incoming spam.

Bad Reputation

The recipient's mail server 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 {{URL_5}} for more information.

Solution: check the reputation of the domain and determine if one of your email addresses has recently been unintentionally used for malicious purposes.

Domain Not Found (or DNS Error)

The recipient's domain name could not be resolved or does not exist.

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

The recipient's inbox is full, preventing the delivery of new 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, as they do not have a storage size limit.

Part of their network is on our block list

If the error message (usually received after sending an email from an online tool hosted on the server where your website is located, such as an order confirmation from PrestaShop or another online store you manage) contains the following:

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 originates from the server with a specific IP address, which is apparently blocked by the recipient for some reason (Infomaniak does not intervene to request unblocking). Therefore, configure the online tool to perform authenticated sending.

3. 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 recipient's mail server to send the message, but for an undetermined reason, it was unable to do so. This error message specifies that the Infomaniak server will continue to try to send your message during the period specified in the error message. If, after this period, the message has still not been delivered, you will receive a final error message indicating that your message could not be delivered and that your recipient did not receive it.

Greylisting Delay

This Greylisting Delay error occurs when the recipient's mail server uses a technique called "greylisting", as Infomaniak does. Greylisting imposes a temporary delay during the first attempt to deliver a message from an unknown sender. The Mailer Daemon may send an error report indicating that the delivery was delayed due to greylisting. The error may also mention banned sender. You should retry your sending attempt a few minutes/hours later.

Malware message rejected

This Malware message rejected error occurs when the message contains an attachment, a link to a storage site such as Dropbox, or dynamic content, including in the "forwarded" part of the message (in the case of a message forward, for example). Try forwarding the message from the Infomaniak Mail web app (online service ksuite.infomaniak.com/mail) instead of using a messaging application, and remove any content that may be causing this error.

Message Size Exceeded / File Too Large

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

Rate Limit Exceeded

This Rate Limit Exceeded error occurs when the sender has exceeded the frequency or volume limit allowed by the recipient's email server. Email servers may impose limits to prevent spam or system overload.

Sender denied: auth guards failed

Refer to this other guide if you encounter the 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, such as a heart ♥, in the body of the email, the subject, or especially in the full name. The risk of rejection by providers is very high: it is best to keep the use of signs, characters, and fonts as simple as possible.

This guide explains how to obtain your email address(es) from the Swiss hosting provider Infomaniak.

Introduction

• With the exception of certain free offers (❓: help), an email address with Infomaniak is always created within a Mail Service.
• This Mail Service is based on a personalized domain name which must exist and be configured for the email to function.
• Example: if you want the address jean.dupont@domain.xyz, you need to:
  1. Own the domain name “domain.xyz”.
  2. Obtain a Mail service for “domain.xyz”.
  3. Create the email address “jean.dupont”.
• All of this is offered and requested during the ordering process on infomaniak.com, preceded by the mandatory creation of a user account (for which you will need to provide your personal email address, or an existing address in any case).
• If your domain name is already registered with an external registrar, you may need to enter the correct MX record (❓: help) in the DNS zone.

Order email addresses for a custom domain

Before or after your registration:

• Consult this other guide to choose the email plan that best suits your needs and follow the instructions to start using the services.
• Once the Mail service has been ordered, you can create the email addresses and then, if necessary, the associated passwords.

Once the Mail service is activated

• Create your email addresses (❓: help).
• Configure your emails on your computer and devices (❓: help).
• Sync your contacts & calendars across your devices (❓: help).
• Migrate your content (❓: help), including content from another provider.

Add an Additional Mail Service

To add a new Mail Service (in order to obtain new addresses on a different domain):

1. Click here to access the Mail Service management in your Infomaniak Manager (❓: help).
2. Click on the Order button above the table that appears:
   

Increase the number of available email addresses on an existing Mail service

To increase the quota of available addresses if necessary, please refer to this other guide.

This guide explains how to register a domain name with Infomaniak.

Introduction

• With a new domain name or an additional domain name, many possibilities open up to you, including access to free services, such as:
  • an email address with contact and calendar management (❓: help),
  • 10 MB of web space (❓: help),
  • newsletter sending (❓: help).
• You can also:
  • use your existing Mail Service (❓: help) or website (❓: help) but with a different spelling/name,
  • host a website here or with a third-party hosting provider,
  • etc.

Order your first domain name

To do this:

1. If necessary, create an Infomaniak account (❓: help).
2. Click here to access the domain management section in your Infomaniak Manager.
3. Click to open the Shop:
   
   • If applicable, select the Organization in which to order your domain:
     
4. Once in the Shop, enter the domain name to register and search for it:
   
5. Check or uncheck the additional options and extensions offered, and click Next to proceed.
6. Choose the desired options on each page, such as the Mail service associated with the domain name:
   
7. Choose the desired options on the following pages, such as the web hosting associated with the domain name:
   
8. Enter the contact details related to the domain name.
9. Complete the purchase, remembering to read and accept the Terms and Conditions (you may need to scroll down the page first):
   

Order an additional domain name

To do this:

1. Click here to access the domain management section in your Infomaniak Manager (❓: help).
2. Click on the button to Order an additional domain:
   
3. Follow the first guide above, starting from step 4.

Check the availability of a domain name

See this other page which allows you to quickly check if a domain is available for registration or not.

At least 3 main indications can be identified:

• Available — in this case, it's good, you can book it.
• Transferable — you must own it with another provider in order to ‍transfer it to Infomaniak‍ (❓: help).‍
• Unavailable – unfortunately, it will not be possible to order it until it is released by its current owner.
  ‍‍

This guide explains which protocols and ports can be used with Infomaniak's email services (including the Mail Service).

Recommended ports and settings for client configuration

When prompted during the configuration of software/email client (Outlook, Thunderbird, mobile, etc.), use the settings below.

Settings common to all accounts

• Server name: mail.infomaniak.com
• Authentication: required (username = full email address)

Technical note: port 587 with STARTTLS is the IETF standard practice for secure email submission. Port 465 is a secure alternative using implicit encryption.

If you specify other settings or disable encryption, email errors may occur.

Other supported ports (unencrypted or for backward compatibility)

Alternative ports:

• Port 143: standard port for IMAP reception (unencrypted, use 993 instead).
• Port 110: standard port for POP3 reception (unencrypted, use 995 instead).
• Port 995: secure port for POP3s reception (secure POP3 option).
• Port 25: standard port for server-to-server transfer (can support STARTTLS for submission, but port 587 remains the standard for clients).

Authentication and encryption compatibility:

• STARTTLS authentication is supported on unencrypted ports (143, 110, 25) to enable TLS encryption.
• SMTP authentication is supported via the LOGIN or PLAIN methods.

Using the API and securing transfers

The Infomaniak API does not offer direct connections to the email service, as IMAP and SMTP already serve as interfaces ("APIs"). To interact with the email service programmatically, use a dedicated library (for example, in Python: email.examples and imaplib).

Example of how to display emails from PHP:
imap_open("{mail.infomaniak.com:993/imap/ssl}", $email, $password);

The MTA-STS mechanism is not implemented or verified; Infomaniak uses DANE (DNS-based Authentication of Named Entities) instead to guarantee an encrypted connection between servers when the following conditions are met:

• The client sends an email to a domain that has configured DANE.
• The client receives an email from an SMTP server that uses DANE.

In all other cases (in the absence of DANE), the encrypted connection remains opportunistic.