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

Specific guides

Click on the link corresponding to your current host:

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

Guides for any other hoster

To retrieve any other data, follow the procedures below:

1. Guide to copy Web data (all PHP, HTML sites, etc. - for WordPress refer to this other guide)
    
2. Guide to copy Mail data (email addresses, mailbox content, etc.)
    
3. Guide to transfer the domain name (domain management, DNS zone, etc.)
    

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

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

Why join Infomaniak?

By grouping your domain names, websites, and email addresses with Infomaniak, you simplify the management of your invoices and services. Moreover, your domains will automatically link with your site and email address. You will therefore not need to manually configure the DNS of your domains with another registrar.

Learn more about Infomaniak

• Infomaniak, the Ethical Cloud
• Infomaniak's eco-responsible approach

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

Web Hosting (Starter, Shared, Cloud Server)

Check out 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),
• the SSH crons of Serveur Cloud.

Check out these guides to backup and restore:

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

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

Hostings v1 (old 60 Go offer)

• View and/or download the automatic backup (versioning) of your data on your FTP space under /backups and /backup_mysql at the root of the domain (above /web).
• Restore this data.

Mail

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

Domains / DNS Zones

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

DNS Fast Anycast replicates your domain's DNS worldwide to reduce latency and increase the availability of your websites.

Introduction

• With DNS Fast Anycast, the DNS of your domain are replicated across several Points of Presence (POP) around the world (list below).
• No matter where your visitors are located, they are redirected to the nearest DNS server to them, which on average increases (DNS resolution) the speed of access to your site by 34%.
• Moreover, if one of your DNS servers becomes unavailable, the nearest server automatically takes over, allowing your visitors to continue accessing your site.
• The replication of your domain's DNS is automatic and no modification of your code is required.

Manage DNS Fast Anycast

Prerequisites

• DNS Fast Anycast is compatible with all websites, regardless of your hosting provider.
• All you need is a domain name managed by Infomaniak: transfer the management of your domain to Infomaniak if necessary
  • Refer to this other guide to manage external domains.

To access the DNS Fast Anycast option:

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. Activate DNS Fast Anycast from the dashboard:
   

POP - 'Point of Presence'

By activating DNS Fast Anycast on your domain, your DNS will be automatically replicated in the following points of presence:

Network 1

New York, USA (2x)
Paris, France (2x)
Warsaw, Poland (2x)
Dublin, Ireland (2x)
Singapore (2x)
Johannesburg, South Africa
Stockholm, Sweden
Vienna, Austria (2x)
Frankfurt, Germany (2x)
London, United Kingdom
Dallas, USA
Los Angeles, USA (3x)
Amsterdam, Netherlands
Sydney, Australia
São Paulo, Brazil
Miami, USA (2x)

Network 2

Hong Kong, China
San José, USA
Dallas, USA
Reston, USA
Chicago, USA
Seattle, USA
London, United Kingdom
Frankfurt, Germany
Amsterdam, Netherlands
Vienna, Austria
Toronto, Canada
Sydney, Australia
Sāo Paulo, Brazil
Johannesburg, South Africa
Miami, USA

The points of presence are distributed across two networks that are used randomly when one of your visitors accesses your website.

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 act…
  • … or on the domain name itself (it must be hosted by Infomaniak and its DNS must be Infomaniak's as well),
  • … or on the code present in your pages (page .htaccess, homepage, etc.) if you have a website.
• Make your life easier! If needed, **local partners recommended by Infomaniak can handle these procedures**. Launch a **free call for tenders**. They take care of everything, freeing you from the technical details.

Act on the domain name

via Web Redirection Tool

The tool available on the Manager allows you to easily redirect the domain name (or subdomain) 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 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 redirection).

The search engine Google indicates that it is preferable to use a 301 redirect on the server side (read more 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 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 /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 topic.

This guide describes the meaning of TTL, an abbreviation for «Time To Live» as well as the principle of DNS propagation delays, important concepts in the operation of domain name-related services.

Preamble

• The TTL determines how long DNS information is cached before being updated.
• This directly affects the speed at which DNS changes propagate across servers worldwide.
• While reducing the TTL can speed up propagation, the behaviors of ISPs and their caches can introduce additional delays.

The TTL (Time to Live)

The TTL (Time to Live) is a key parameter in managing DNS records. It represents the duration, expressed in seconds, during which DNS information can be stored in cache before being updated. When a DNS server or Internet Service Provider (ISP) queries a DNS zone, it temporarily keeps the responses obtained to reduce the load on servers and speed up browsing for users.

For example, if the TTL is set to 24 hours (86,400 seconds), the DNS information related to a domain will be cached and will not be updated for the entire duration, even if you have modified parameters such as the domain's IP address. This means that DNS changes will only take effect once this delay has elapsed.

It is possible to speed up the application of changes by reducing the TTL before proceeding with updates. For example, lowering the TTL to one hour (3600 seconds) allows DNS servers to check the new information more quickly after a modification.

DNS propagation

The TTL is directly linked to the DNS propagation process. DNS propagation refers to the time required for changes made to a DNS zone to be disseminated across all DNS servers worldwide. This delay depends not only on the configured TTL, but also on how Internet Service Providers (ISPs) and other DNS servers manage their caches.

When you modify DNS records, DNS servers and ISPs must wait for the TTL period to expire before fetching the new information. Thus, the shorter the TTL, the faster the changes propagate through the network. However, some ISPs sometimes ignore the TTL duration and keep the information cached for a longer period (for example, 24 hours or more), which can slow down the propagation of DNS changes, even if you have configured a reduced TTL.

This guide concerns the configuration of the Infomaniak product Newsletter in the case where the domain name used for sending your emails is not managed by Infomaniak.

Preamble

• For automatic use of the Newsletter tool, it is necessary to manage the domain name from which you send your newsletters (as well as its DNS zone) with Infomaniak.
• For example, if you send your newsletters from the address news@domain.xyz, the domain domain.xyz must be managed by Infomaniak.
   

Specific DNS Configuration

To use the Newsletter tool with a domain not managed by Infomaniak, you will need to add specific entries to your DNS zone provided in your Manager:

Refer to this other guide to add the DNS entries mentioning ._domainkey ensuring to first choose a DKIM type, then the CNAME subtype when adding the DKIM.

In case of domain transfer out

If the domain name currently managed by Infomaniak (and corresponding to the Newsletter) is transferred to another registrar, the Newsletter tool will be deactivated within the next 30 days if no consequent DNS modification is made.

This guide explains how to find and display DNS information for any domain name registered with Infomaniak (or elsewhere).

Domain at Infomaniak

To access your domain names and view the DNS servers listed:

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 relevant product.
3. Click on DNS Servers in the left sidebar:
   
   

WHOIS Search

To display the DNS information for another domain name, use a WHOIS service like https://whois.infomaniak.com/ for example or https://who.is (beware of advertisements on all these third-party services).

You will thus get a clear answer about the DNS situation of a domain name at a given point in time.

DNS records are often displayed in pairs and start with ns... followed by numbers and the name of the registrar or host.

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

Available as an option with any Infomaniak offer or included with kSuite Entreprise, discover this customization tool to make your web addresses unique, add a logo or an image slideshow to your login page for your Infomaniak Organization.

Prerequisites

• Have a domain name with an extension supported by Infomaniak - note that this also works with a subdomain.
• Host your domain name with Infomaniak (transfer it to Infomaniak if necessary) or manage its DNS zone with Infomaniak.

Custom Brand customization guides

• Customize the URLs and interface / disable Custom Brand
• Troubleshoot an issue:
  • domain verification associated
  • domain blocking associated

Customize your Web addresses with your domain

Customize your Organization's interface

The following interface options are customizable from your space:

• Adding your logo to your Organization's interface.
• Adding a panorama of 3 images on the login page.
• Changing the color of the text and the button on the login page.
• Customization of kDrive pages.

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.

This guide explains how to modify the DNS (Name Servers) of a domain registered with Infomaniak.

Prerequisites

• Own a domain name with Infomaniak or at least a DNS zone.
• Understand:
  • the operation of a domain and a DNS zone before modifying the latter.
  • that any DNS addition/modification may take up to 48 hours to propagate.

DNS Modification

To modify the DNS of a domain managed by Infomaniak and thus control the direction that web and mail traffic should take:

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 relevant product.
3. Click on DNS Servers from the left sidebar.
4. Click the blue button Edit DNS Servers:
   
5. If your website is hosted with Infomaniak, check Infomaniak Name Servers; otherwise, check Custom Name Servers:
   

Batch modification

To modify the DNS of multiple domain names in bulk:

1. Click here to access the management of your product on the Infomaniak Manager (need help?).
2. Select the relevant domain names.
3. Click on ⋮ at the bottom of the screen if necessary.
4. Click on Edit DNS servers: