Knowledge base

1000 FAQs, 500 tutorials and instructional videos. Here, there are only solutions!

Understanding mail ports and protocols

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

 

Recommended ports and parameters for client configuration

When prompted during a software/messaging client configuration (Outlook, Thunderbird, mobile, etc.), prioritize the following parameters:

 IMAPs - Incoming Traffic (Recommended)SMTP - Outgoing Traffic (Option 1: IETF standard)SMTPs - Outgoing Traffic (Option 2: Implicit Encryption)
Ports993587465
Security MechanismSSL / TLS (implicit)STARTTLS (explicit)SSL / TLS (implicit)
Server Namemail.infomaniak.com
AuthenticationMandatory (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 indications or disable encryption, email errors may occur.

 

Other supported ports (unencrypted or backward compatibility)

  • port 143 (Standard port for IMAP reception - unencrypted, use 993)
  • port 110 (Standard port for POP3 reception - unencrypted, use 995)
  • port 995 (Secure port for POP3s reception - secure POP3 option)
  • port 25 (Standard port for server-to-server transfer - may support STARTTLS for submission, but 587 is the standard for clients).
  • STARTTLS authentication is supported on unencrypted ports (143, 110, 25) to enable TLS encryption.
  • SMTP authentication supported (LOGIN or PLAIN methods).

 

API Usage and Transfer Security

The Infomaniak API does not offer any email connection as IMAP and SMTP are the "APIs". Use a library (such as Python: email.examples and imaplib) that uses IMAP and SMTP.

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

The MTA-STS mechanism is not implemented or verified, as Infomaniak uses DANE (DNS-based Authentication of Named Entities) to ensure 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.

Has this FAQ been helpful?