This guide explains how to link an external website (hosted by an all-in-one website creation service, for example) to your Infomaniak mailbox.

This will be useful in cases where, for example, your webmaster has modified the technical information (DNS) of your domain name to direct it to your external website and this has interrupted your mailbox.

Prerequisites

• Your domain name includes the DNS corresponding to the provider of your external web service (as this is the DNS zone with this provider that you will edit).
• Note the Infomaniak MX mta-gw.infomaniak.ch or sometimes mta-gw.infomaniak.ch. (presence of a final point).
• Note the Infomaniak SPF v=spf1 include:spf.infomaniak.ch -all.
• Note the Infomaniak DKIM.
• Understand that any DNS addition/modification can take up to 48 hours to propagate.

Specific guides

Click on the link corresponding to the web site provider:

• Wix
• Wordpress.com
• Shopify
• Jimdo (guide A | guide B)

Guide for any other web provider

In general, you need to find the place on your web provider's dashboard where you can add the technical information (the 3 indications listed in the prerequisites above) to make your Infomaniak mailbox work while your domain name directs all traffic to this web provider:

1. The MX of Infomaniak.
2. The SPF is a verification method that ensures an email is sent by the sender it claims to be, helping to combat spam and fraudulent emails; this is often added in the form of a TXT record addition.
3. The presence of a DKIM has become essential for the optimal functioning of your Infomaniak mailbox.

This guide explains how to add a synonym domain to a domain name.

Preamble

• A synonym domain is a domain name that can serve as a secondary name for another domain.
• When a synonym domain is added, it automatically inherits the content of the DNS zone of the main domain (including MX, A, etc. records), as well as its Web and Mail hosting.
• Alternatively, you can also add a (domain) alias to a website or add a (domain) alias to a Mail Service.

Add a synonym domain to a domain

Prerequisites

• The domain name of the future synonym or the management of its DNS zone…
  • … must be reserved with Infomaniak,
  • … must be configured with the Infomaniak DNS,
  • … must not be linked to any product yet.
• The domain name on which the synonym will be placed…
  • … must not be associated with the Infomaniak Newsletter product.

To access your domain names:

1. Click here to access the management of your product on the Infomaniak Manager (need help?).
2. Click directly on the name assigned to the product in question.
3. Click on Synonym Domains in the left sidebar.
4. Choose to add a synonym.
5. Click on Next:
   
6. Choose an existing domain in the current Organization, or order a new domain in advance.
7. Click the button to Confirm:
   
8. That's it:
   

Refer to this other guide if you are looking for information to dissociate a synonym domain name.

This guide introduces the Global Security tool, which allows you to verify that the relationships between a domain name and an Infomaniak Mail Service are optimal in terms of security. This involves checking the SPF / DKIM / DMARC records, and the Global Security tool allows you to intervene in the configuration if necessary.

Access the Global Security diagnostic tool

To access Global Security:

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

Verify the optimal functioning of email

Once you have arrived at Global Security, familiarize yourself with and verify the three security mechanisms inherent to emails: SPF, DKIM, and DMARC policy. These indications should be displayed in green:

Click on Edit or Create to configure SPF, DKIM, and DMARC according to the recommendations below to secure your Mail Service against potential identity theft:

SPF (Sender Policy Framework)

SPF (click here to configure) allows the owner of a domain name to specify which servers are authorized to send emails on behalf of that domain. This helps to reduce the risk of spam and phishing, as the recipient's mail server can verify if the sender is authorized by consulting the sender domain's DNS records:

Under these conditions and in case of a detected problem, you will find a Correct button that will allow you to automatically update your SPF.

If correcting one or the other of the mentioned issues is not possible, it is because it must be done on the configuration set up by the owner or technician of the sender's domain name.

If your domain name points to Wix or another provider, the SPF must be configured with the relevant provider.

DKIM (Domain Keys Identified Mail)

DKIM (click here to configure) is a protocol that allows emails to be signed when they are sent.

When your domain name (or its DNS zone) is managed elsewhere, you will find in this section Global Security > DKIM the DKIM record to add in the DNS zone:

You can configure multiple DKIM records on your domain without a fixed limit, unlike DMARC or SPF, which is crucial if you use multiple third-party email providers for your daily communications.

DMARC (Domain-based Message Authentication, Reporting, and Conformance)

DMARC (click here to configure) allows you to indicate to other mail servers (the email providers of the contacts to whom you send an email) the policy to follow in case of receipt of a "suspicious" email (e.g., not authenticated) from your mail server (hosted by Infomaniak). Additionally, you can be notified of the "incident" by a summary message (called a "DMARC report") providing information on the recent activity of your email related to the domain name.

DMARC requires a valid SPF and DKIM. A wizard allows you to configure DMARC according to Infomaniak recommendations in simple mode or entirely as you wish in advanced mode (this expert mode allows you to enter the record of your choice):
The corresponding necessary entries (type TXT) will then be automatically applied in the DNS zone of the concerned domain name (if administratively possible - domain managed in the same Organization, for example).

To verify the records within your DNS, you can also use an external and free service like the one mentioned at the bottom of this other guide.

Refer to this other guide if you are looking for information on the fourth point of the Overall Security page.

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).

Preamble

• To redirect traffic, you will need to act…
  • … either on the domain name itself (it must be hosted by Infomaniak and its DNS must also be those of Infomaniak),
  • … or on the code present in your pages (page .htaccess, home page, etc.) if you have a website.
• If necessary, local partners referenced by Infomaniak can handle these procedures: launch a free call for tenders; they take care of everything, freeing you from technical details.

Act on the domain name

via Web Redirection Tool

The tool available on the Manager allows you to act simply on the domain name (or subdomain) in order to redirect it to the Internet address of your choice.

via DNS modifications or A record

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

Act on the page code…

… via HTML code to insert

Insert this line of code between the <head> and </head> tags of your home page (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).

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

… via PHP code to insert

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

header("refresh: 5; url=INSERT-HERE-NEW-PAGE-URL");

… via .htaccess file

To redirect all traffic targeting your site (regardless of the page called) to another address, insert this in the .htaccess file at the root of your site:

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

To target the page that needs to be redirected:

Redirect permanent /ancienne_page.html insérer ici adresse URL de destination

Redirectpermanent, Redirect permanent and Redirect 301 are equivalent commands.

Here 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 on this subject.

This guide explains how to add a new domain name to a Web site Infomaniak.

Preamble

• When you add a new domain name to a website, it is referred to as a linked domain but also as an alias.
• In this case, an alias domain is an additional domain name, also linked to an existing site.
  • For the website domain.xyz to be reachable with a completely different domain name such as private.abc for example, you need to add private.abc as an alias to the website.
  • Second example, for the site domain.xyz to also be reachable with www.domain.xyz, you need to add it as an alias to the domain domain.xyz. In this example, domain.xyz is the parent site of the alias www.domain.xyz. Generally, the alias www is already added automatically and present…

Adding an alias to an existing site

Prerequisites

• If the domain name (intended to become an alias) or its DNS zone is managed by Infomaniak, everything is OK. If not:
  • The A record of the domain name must point to Infomaniak.
  • To simplify, you can delegate the management of the domain to Infomaniak.
• It is also necessary that the future alias is not already one, in which case it will be necessary to unlink it from the current site beforehand (same if synonym).

To add an additional domain that will be linked to your website:

1. Click here to access the management of your product on the Infomaniak Manager (need help?).
2. Click directly on the name assigned to the product concerned:
   
3. Then click on the chevron ‍ to expand the Domains section of this site.
4. Click on the Add a domain button:
   
5. Enter the domain name(s) to be added, separating them with the Enter key.
6. If the alias or its DNS zone is managed by Infomaniak, it is possible to automatically update the DNS entries. In the opposite case, make any necessary changes with your registrar or transfer the management of the domain name to Infomaniak.
7. If you have an SSL certificate such as Let's Encrypt, for example, you can request to update it here to include the new names.
8. Click on Validate to complete the procedure:
   

To set the alias as the main domain, refer to this other guide.

This guide helps you resolve configuration errors if you encounter difficulties linking your domain name to Site Creator.

Common issues and solutions

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

This guide explains how to restore backups of previous versions of your files and other web data from your Infomaniak hostings, and how to set up an effective backup policy if the automatically and freely provided backups no longer meet your availability or security needs.

Web Hostings (Starter, Shared, Cloud Server)

Refer to these guides to restore automatic backups:

• of an entire hosting (FTP + MySQL),
• of specific files on the hosting,
• of specific databases,
• of a Web Application (Wordpress & Apps),
• of Cloud Server SSH crons.

Refer to these guides to backup and restore:

• a hosting with Swiss Backup and Restic (advanced),
• WordPress with Swiss Backup,
• WordPress with an extension.

Also refer to https://faq.infomaniak.com/snapshot.

Messaging

• Restore messages from Infomaniak automatic backups.
• Restore contacts or calendar events.
• Backup the current content of an email account:
  • by downloading the current content locally,
  • by duplicating all current content to a backup box,
  • by copying future emails as they arrive to a backup box.

Domains / DNS Zones

• Restore deleted DNS records from Infomaniak automatic backups.
• Restore an expired domain in redemption period.

This guide explains how‍ to create subdomains on an existing Infomaniak hosting using a .htaccess file.

Introduction

• The hosting can be on an offer of Shared Web Hosting or on Infomaniak Cloud Server but this function is impossible with a Starter hosting.
• Subdomains can be added very easily to your current hosting since you have in the basic offer 20 sites per hosting (sites = subdomains).
• If you do not want to use this site volume available to you, you can follow the method below.

Create a subdomain as a shortcut

The subdomains thus created make it easier to organize a hosting. For example the address vlog.domain.xyz will be the shortcut of the address domain.xyz/vlog. In other words, the address vlog.domain.xyz will redirect to the vlog folder which must be located at the root of the website domain.xyz. In this example, vlog is the subdomain of domain.xyz.

1. Add the subdomain as an alias of your website

To do this:

1. Follow the procedure for adding an alias but please read the points 2 and 3 below.
2. In the field to add the related domain, enter the full address of the subdomain (for example vlog.domain.xyz).
3. If your domain or its DNS zone is managed at Infomaniak, activate the following two options: Update DNS entries for this domain and Replace existing entries ; if this is not the case, create a A record with your registrar with the following information:
   • field: the full URL of the subdomain (for example vlog.domain.xyz)
   • target: the IPv4 address (A record) of your site (refer to this other guide to find the A record of your site)

2. Modify the .htaccess file of your website

Using your FTP software/client or Web FTP on the Manager, add and adapt the following code in the .htaccess file located at the root of your website:

RewriteCond %{HTTP_HOST} ^(.*)\.domain\.xyz [NC]
RewriteCond %{DOCUMENT_ROOT}/%1/ -d
RewriteCond %1::%{REQUEST_URI} !^(.*?)::/\1/?
RewriteRule "^(.*)$" "%{DOCUMENT_ROOT}/%1/$1" [L]

Explanation for the third line: https://stackoverflow.com/a/15981056

Replace on the first line:

• domain with your domain name
• xyz with your domain extension (ch, fr, etc.)

Now, the address vlog.domain.xyz should display the content of the vlog folder located at the root of your website. If this is not the case, check that the vlog folder exists at the root of your website.

This guide explains how to move a Web Hosting (and all the sites it contains) from a Cloud Server to another managed Cloud Server.

Preamble

• FTP & MySQL
  • When moving a hosting from one Cloud Server to another:
    • FTP access and databases do not change.
    • Only the supported versions of PHP and MariaDB, as well as the server's IPv4 and IPv6 addresses, change at the hosting level.
    • Hostnames do not change and are automatically updated to point to the new IP addresses.
• Temporary interruption:
  • The sites in the hosting will be unavailable during the data migration.
  • This process can take several minutes depending on the number of files to transfer to the new Cloud Server.
• Possible switch to HTTP/2:
  • HTTP/2 is active on the new servers.
  • Some directives that may be present in your server's .htaccess file could require adaptation.
• Traffic redirection:
  • A proxy is set up for 7 days to redirect traffic from the old server to the new one.
  • It is therefore advisable to consider this during this period, especially for crons (see below).
• Crons not migrated:
  • SSH crons are not migrated.
  • Files and crons are generally not deleted immediately, which can result in duplicates.
  • Managing crons is your responsibility; depending on the progress of your migration, you need to:
    • deactivate and activate crons via SSH if you have them, to avoid any execution conflicts,
    • check your crons,
    • ensure they are properly configured on your new Cloud Server.

Move hosting

Prerequisites

• Both servers must be in the same Organization and accessible to the user performing the operation.

Once the second Cloud Server is in service:

1. Click here to access hosting management on the Infomaniak Manager (need help?).
2. Click directly on the name assigned to the hosting concerned.
3. Click on the Manage button.
4. Click on Move to another server in the menu that appears:
   
5. Choose the desired destination server.
6. Click on Confirm.

Adjust the DNS zone and finish

If your domain names are not managed by Infomaniak or in the same Organization as the Cloud Server:

• Adjust the A record of the domains concerned.
  • Any DNS addition/modification can take up to 48 hours to propagate.
  • It is therefore recommended not to cancel the old Cloud Server before this period.
• Cancel the old Cloud Server if necessary.

This guide explains how to set up a DMARC policy for your email hosted by Infomaniak, an essential element to prevent potential delivery issues.

Preamble

• The DMARC (Domain-based Message Authentication, Reporting, and Conformance) protocol enhances the security of your domain by relying on SPF and DKIM checks.
• It instructs recipient servers on how to handle emails that fail these authenticity tests, with three protection policies (None, Quarantine, Reject) detailed below.
• In case of authentication failure, the recipient can send you a DMARC report; this data is essential to identify configuration errors or stop phishing attempts using your domain name.

DMARC Policy and Acceptance Percentage

For the instructions that can be given to recipient servers when a suspicious message is detected, 3 policies (p = policy) exist and can be refined with a percentage (pct):

None (none): The email is delivered normally (observation mode)

With "p=none", no email is rejected or quarantined based on the DMARC verification. However, the reception percentage can be used to collect data on unauthenticated emails, indicating how many of these emails should be subject to the DMARC policy. E.g., "p=none; pct=10" means that 10% of unauthenticated emails will be subject to the DMARC policy, while the remaining 90% will be accepted.

Quarantine (quarantine): The email is sent to spam

With "p=quarantine", unauthenticated emails can be quarantined, but the reception percentage determines the proportion actually subject to this policy. E.g., "p=quarantine; pct=50" means that 50% of unauthenticated emails will be quarantined, while the remaining 50% will be accepted.

Reject (reject): The email is purely and simply blocked/deleted

With "p=reject", unauthenticated emails are rejected. The reception percentage determines the proportion of unauthenticated emails that will actually be rejected. For example, "p=reject; pct=20" means that 20% of unauthenticated emails will be rejected, while the remaining 80% will be accepted.

Create a DMARC Record

There are 2 ways to manage DMARC.

If you have a Mail Service with Infomaniak, the simplest way is to go to the Global Security tool to manage your DMARC security policy and reports:

However, since the DMARC record is a type of DNS record, usually of type TXT, you can also manage it from the DNS zone of the domain name:

1. Click here to access the management of your domain on the Infomaniak Manager (need help?).
2. Click directly on the name assigned to the domain in question.
3. Click on DNS Zone in the left sidebar menu.
4. Click the button to add a record:
   
5. Click the radio button DMARC to add a record.
6. Click the Next button:
   
7. Leave (or add if necessary) the value _dmarc in the Source field.

8. The Target field must contain the parameters you wish to use, separated by ;:

   Tag Name	Purpose	Example
   v	Protocol version	v=DMARC1
   pct	Percentage of messages subjected to filtering	pct=20
   ruf	URI for forensic reports	ruf=mailto:authfail@domain.xyz
   rua	URI for aggregate reports	rua=mailto:aggrep@domain.xyz
   p	Policy for the organizational domain	p=quarantine
   sp	Policy for the subdomains of the organizational domain	sp=reject
   adkim	DKIM alignment mode	adkim=s
   aspf	SPF alignment mode	aspf=r

   which can result in, for example, v=DMARC1;p=reject;pct=100;rua=mailto:postmaster@dmarcdomain.com (source)

9. Leave the default value for the TTL.
10. Click the Save button:
    

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

Preamble

• 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 DNS of the domain is managed by Infomaniak and if Custom Brand is not activated.
  • Any addition/modification may take up to 48 hours to propagate.
• If necessary, create a redirection of 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 management of your product on the Infomaniak Manager (need help?).
2. Click directly on the name assigned to the product concerned.
3. Click on Web Redirections in the left sidebar.
4. Click on the Add a redirection button:
   
5. Enter the destination address (under To).
6. Choose between a 301 or 302 type redirection.
7. The advanced options allow you to specify a redirection in the form of an iframe (invisible, but not recommended).
8. Click on the button to Confirm:
   

This guide explains how to transfer to Infomaniak data (Web, Mail, Domain, and even Cloud) currently hosted elsewhere. You remain the obvious owner of your data, without loss or interruption!

Preamble

• By consolidating your domain names, websites, and email addresses with Infomaniak, you simplify the management of your invoices and services.
• Additionally, linking your domains will be done automatically with your site and email address.
  • You will not need to manually configure the DNS of your domains with another registrar.
• If needed, local partners referenced by Infomaniak can handle these procedures: launch a free call for tenders; they handle everything, freeing you from technical details.

Specific Guides

Click on the link corresponding to your current host:

• Swisscom: complete guide to migrate Web, Mail, and domain name data

Guides for any other host

To not interrupt your site and emails and not lose any content when importing your existing data, migrate your services in the indicated order:

1. Import Web data (all PHP, HTML sites, etc.)

   • For WordPress specifically, refer to this other guide…
      

2. Copy Mail data (addresses and mailbox content, etc.) to kSuite or a simple Mail Service

3. Transfer the domain name (domain management, DNS zone, etc.)

You can also bring other types of data to Infomaniak servers:

• Dropbox, Google Drive content, etc.: refer to this other guide
• Data on Synology or QNAP NAS: refer to this other guide

This guide explains how to replace the main domain name associated with a Mail Service in case you want to modify the spelling of everything that comes after the at sign @ of your email address (= the domain name). If your Mail Service is part of a my kSuite, then you will need to act on the my kSuite domain directly.

Preamble

• You can also follow this procedure if the goal is to have completely new email addresses while keeping the history of your emails in Mail (since the email address will continue to exist, for example info@first-domain.xyz will become info@new-domain.xyz without modifying its content).
• Indeed, it is not possible to simply modify the spelling of the domain name concerned; it is therefore necessary to replace the current domain name associated with your email addresses with another domain name.
• To simply add an additional domain name, refer to this other guide.
• To rather modify the part of your email address that comes before the at sign @, refer to this other guide.
• Also note that you can rename your product (example) on the Infomaniak Manager but changing the name of a Mail Service has strictly no impact on its addresses; you need to act on the domain name.

Modify the domain name of the Mail Service

Prerequisites

• Own the new domain name (if necessary, create it in advance).
• Refer to the instructions of this other guide by applying the instructions corresponding to your situation (this is so that the domain name works when it is linked to your Mail Service).

Once the new domain name is ready to be used in place of the old one, you need to add it to the Mail Service and then perform a reversal:

1. Click here to access the management of your product on the Infomaniak Manager (need help?).
2. Click directly on the name assigned to the product in question.
3. Click on Domain Management in the left sidebar
   
4. Click on Service-related domains in the left sidebar.
5. Click the blue button Add a linked domain:
   
6. You can:
   
   1. Search for an existing domain within the Organization you are connected to; this will link and automatically update the DNS zone of the added domain.
   2. Add a domain name or subdomain to manually specify the domain name or subdomain to use (ideal if the domain name is hosted elsewhere).
   3. Buy a new domain name (see prerequisites above).

a: The domain exists within the Organization

1. Click on the proposed domain name.
2. Click the blue button Link this domain:
   
3. Click on the icon ⋮ to the right of the newly added domain name.
4. Click on Set as primary domain (you must have dissociated the alias domain name from the primary domain name if there was a previous association):
   
5. Confirm the reversal and then wait for the operation to complete.
6. Click on the icon ⋮ to the right of the old domain name.
7. Click on Unlink the domain:
   
8. Confirm the detachment by verifying if you want to delete the associated DNS records during the detachment operation.

That's it, the Mail Service now responds to a new domain name.

b: The domain exists but elsewhere

1. After clicking on Add a domain or subdomain, enter the domain name that will replace the current name.
2. Enable DNS entry updates (if the domain name situation allows it, the DNS zone of the domain name will be automatically updated).
3. If the point above is active, then enable the replacement of any existing entries.
4. Enable reversal of the domain name (to avoid additional steps as in point "a" above).
5. Click the blue button Link this domain:
   
6. Wait for the operation to complete.
7. Click on the icon ⋮ to the right of the old domain name.
8. Click on Unlink the domain:
   

This guide explains how to add an additional website to an existing Infomaniak hosting plan.

Preamble

• The hosting can be on a shared web hosting plan or on an Infomaniak Cloud Server.
• The additional site can be either:
  • a second domain name (for example. domain2.xyz),
  • or a subdomain (for example. abc.domain.xyz) of a domain name that you already own.
• In this multisite/multidomain management (virtual host), the total disk space and resources of your hosting are shared between your sites/subdomains.

Access site management

Prerequisites

• If the 20 site slots offered in the Web hosting are already in use, order additional sites.

To access a web hosting plan and add a site:

1. Click here to access the management of your products in the Infomaniak Manager (need help?).
2. Click directly on the name assigned to the product in question.
3. Click the blue button Add:
   
4. Choose the optional content for the new site (A) or other specific installation, blank space, advanced technologies (Node.js for example) (B):
   
5. Click on Next.
6. Choose the type of domain to assign to this new site:
   1. an already acquired domain name
   2. a subdomain created from an already acquired domain name
   3. a domain name still available and to order
7. Enter the domain name (domain2.xyz, for example) or the subdomain.
   
8. Choose the optional advanced options, including:
   1. By default, the new site is added to the directory /sites/domain2.xyz on your FTP server.
   2. To manually set another directory, check Set location manually and indicate the path and name.
   3. Create a new folder if necessary:
      
9. Click on Continue.

This guide explains how to manage the email address used to send your invitations with the Infomaniak Guest Manager.

Preamble

• Any of your email addresses can be specified for sending Guest Manager invitations.
• There will be no issue with an email address already configured to be used with Infomaniak.
• For an email address from a generic domain such as outlook.fr or gmail.com the email address no-reply@infomaniak.com will be automatically used as a replacement sending address, the same applies to all domain addresses for which you cannot modify the SPF (read below).
• However, any responses will be sent to the email address you have provided.
• For an email address on a custom domain not yet configured to work with Infomaniak and for which you have access to the DNS zone, refer to the guide below to add the appropriate SPF.

Specify the sending email address

The email address from which your invitations will be sent must be entered in the first step of configuring your invitations (after creating your subscriber lists):

Depending on the specified email address, a popup appears when you click on Next warning you that the SPF must be correctly configured for the sends to be made from the address in question. Otherwise, the invitations will be sent from a no-reply@infomaniak.com address.

You can still review and modify the address in the last step by clicking on the pencil icon ✎:

Add the Infomaniak SPF in the DNS zone

If you want to use a custom email address to send invitations, it is necessary to check and, if necessary, modify the SPF record of your domain to authorize Infomaniak to send emails on your behalf.

Refer to this guide especially the chapter “Add multiple SPF” to not replace your SPF but simply add Infomaniak's: v=spf1 include:spf.infomaniak.ch -all

This guide explains how to have multiple denominations (everything that comes after the at sign @ of your email address) for an existing Mail Service, by adding linked domain names.

Preamble

• Email addresses (existing and future) are automatically valid with all linked domains.
• To completely transform and reverse the domain names of a Mail Service, refer to this other guide.
• To rather modify the part of your email address that comes before the at sign @, refer to this other guide.
• Note also that you can rename your product in the Infomaniak Manager, but changing the name of a Mail Service has no effect on its addresses. You need to act on the domain name.

Add a domain name to the Mail Service

Prerequisites

• Own the new domain name (if necessary it will need to be created beforehand).
• Refer to the instructions of this other guide by applying the instructions corresponding to your situation (so that the domain name works when it is linked to your Mail Service).

Once the new domain name is ready to be used alongside the old one, it must be added to the Mail Service:

1. Click here to access the management of your product on the Infomaniak Manager (need help?).
2. Click directly on the name assigned to the product in question.
3. Click on Domain Management in the left sidebar:
   
4. Click on List of domains linked to the service in the left sidebar.
5. Click the blue button Add a linked domain:
   
6. It is possible to…
   
   1. … Search for an existing domain on the organization to which you are connected; this will link and automatically update the DNS zone of the added domain.
   2. … Add a domain name or subdomain to manually indicate the domain name or subdomain to be used (ideal if the domain name is elsewhere).
   3. … Buy a new domain name.

a: The domain exists at the Organization level

1. Click on the proposed domain name.
2. Click on the blue button Link this domain:
   

It is done, the Mail Service now responds to a second domain name:

b: The domain exists but elsewhere (other Organization, other Registrar...)

1. Enter the domain name to add.
2. Activate the DNS entry update (if the domain name situation allows it, the DNS zone of the domain name will be automatically updated).
3. If the point 2 above is active, then activate the replacement of any existing entries.
4. Only reverse the domain name if you wish to set this new domain name as the main one (this is mainly an administrative rather than a technical issue).
5. Click on the blue button Link this domain:
   

Example of use

The email contact@une-super-entreprise-familiale.com is a long email address. The synonym domain contact@usef.com is shorter and easier to remember.

By adding the domain "usef.com" to the Mail Service "une-super-entreprise-familiale.com" you authorize all messages sent to contact@usef.com (the linked domain) to arrive among the messages that the address contact@une-super-entreprise-familiale.com already receives.

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 a mail address in a software/email client.

Preamble

• Generally, a mail error message follows…
  • … an incorrect configuration of the domain name used with your mail,
  • … a problem with (the mail provider of) your recipient.
• In all cases, a delivery failure report (Mailer Daemon or Mail Delivery Subsystem) containing the explanation is sent to the sender.

Finding and identifying the mail 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 pass 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 correspondent is visibly suspended by their mail 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 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 type 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 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 a certain amount of time, 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 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 verify if the message was filtered into the spam 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 there has been a recent unintentional misuse of one of your email addresses 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 do not have storage size limits.

Part of their network is on our block list

If the error message (obtained in principle following a send operation performed from an online tool, placed on the server where your website is located, for example a Prestashop order confirmation or another online store 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 originates 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 sends.

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 attempted to connect to your correspondent's mail server to send the message but was unsuccessful for an undetermined reason. This error message indicates that the Infomaniak server will continue attempting to send your message during the period specified in the error message. If, after this time, 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 correspondent did not receive it.

Greylisting Delay

This Greylisting Delay error occurs when the recipient's mail server, like Infomaniak, uses a technique called "greylisting" which imposes a temporary delay on the first attempt to deliver a message from an unknown sender. The Mailer Daemon may eventually send an error report indicating that delivery has been delayed due to greylisting. The error may also mention banned sender. You should try sending your message again 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 like Dropbox, or dynamic content, including in the "forwarded" part of the message (in the case of a message "forward", for example). You should try resending the message from the Infomaniak Mail Web app (online service ksuite.infomaniak.com/mail) instead of a mail application, and remove any content that may cause 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 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 Rate Limit Exceeded error occurs when the sender has exceeded the frequency or volume limit allowed by the recipient's mail server. Mail servers may impose 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 The message contains a unicode character in a disallowed header error may appear if you have inserted a special character like a heart ♥ for example 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.

This guide helps you if you receive error mails that mention SPF when you write to gmail, microsoft, or similar addresses.

Are all your services with Infomaniak?

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

Are some of your services elsewhere?

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

This guide is for you if you are experiencing issues with a Sectigo SSL certificate of type DV or EV.

Sectigo Change (June 2025)

Since June 2025, Sectigo uses a new validation infrastructure called MPIC, which performs the necessary checks to issue SSL certificates (including EV and OV) from servers located around the world, and no longer solely from the United States.

A challenge is a method used by the certification authority to verify that the applicant controls the domain. This can be done through an HTTP request, a DNS record, or an email. For EV and OV certificates, this challenge is combined with checks on the organization's identity.

With this new method, validation requests can come from any country or provider. If your site or server uses geoblocking rules, a web application firewall (WAF), or a service like Cloudflare with country or ASN access restrictions, these checks may be blocked, causing validation to fail.

Even though Sectigo primarily discusses OV and EV certificates, this change can also indirectly affect DV certificates, as domain validation still relies on the ability to access the necessary resources.

This guide explains how to resolve an SSL certificate (Let's Encrypt or Sectigo) installation issue if you are using Cloudflare with strict security rules, such as country or IP address filtering.

Adjust SSL / geoblocking settings

When an SSL certificate is requested via Infomaniak (free Let's Encrypt or Sectigo), the certification authority must verify that you are the owner of the domain. This verification can be done via HTTP (using special files placed on your site), DNS, or email:

• Let's Encrypt uses /.well-known/acme-challenge/.
• Sectigo usually uses /.well-known/pki-validation/ (or DNS / email depending on the option chosen).

If these verifications fail (for example, because Cloudflare blocks access), the certificate cannot be issued or renewed. However, Let's Encrypt no longer checks from a single location. For some time (and even more since March 2024), it performs its checks from multiple countries at the same time – including new ones like Sweden or Singapore. Result: if one of these countries is blocked by your Cloudflare settings, the certificate request may fail, even if everything else is correctly configured.

Worse still: even if you try to make an exception only for the challenge address (.well-known/acme-challenge), this does not always work with certain Cloudflare rules. Indeed, country or IP blocking rules are applied before any URL path-based exception.

Adjust SSL/TLS mode

In Cloudflare, use the Full or Full (strict) mode. These modes temporarily tolerate an expired or self-signed certificate, until the validation is complete:

Allow validation paths

Avoid blocking "IP Access Rules" and prefer "Custom Rules" that allow unrestricted paths:

• /.well-known/acme-challenge/ (Let's Encrypt)
• /.well-known/pki-validation/ (Sectigo)

Temporarily disable geoblocking

If necessary, temporarily disable geographic or IP blocking for the duration of the validation, then reactivate your protections after the certificate is issued or renewed.