MailFixIt

Infomaniak kSuite email configuration guide

Infomaniak kSuite: MX records not receiving mail

Incoming mail is not reaching Infomaniak kSuite because the public route or the destination account does not match the intended setup.

Problem description

A provider setup symptom may look like:

MX records not receiving mail after a provider DNS change.

Check the sending domain

What this usually means

Incoming mail is not reaching Infomaniak kSuite because the public route or the destination account does not match the intended setup.

Fix it

  1. In Manager, verify that the domain is linked to the intended kSuite Mail Service and create the recipient address first. Copy the MX values shown for that exact service.
  2. Confirm the domain is active and each required mailbox or alias exists before changing DNS.
  3. Publish the complete provider MX set for the exact domain in its authoritative DNS zone.
  4. Remove old provider MX records only for direct delivery. Preserve an intentional security gateway and fix its private next hop instead.
  5. Wait for cache expiry, inspect the public MX response, and send a new message to an existing address.

Common mistake

The registrar, DNS host, website host, and mailbox provider can be four different companies. Change MX only according to the service that should receive mail.

What MailFixIt can check

MailFixIt can find missing, conflicting, or invalid public MX evidence. It cannot activate Infomaniak kSuite, create a mailbox, or enable private account features.

Use the related guides for the exact DNS or authentication warning and verify the corrected path with a new test.

Frequently asked questions

What does MailFixIt check for Infomaniak kSuite?

It checks the public MX record and visible conflicts. The provider console and a new message or delivery test are still required.

Should I replace every existing DNS record with the provider values?

No. Confirm the exact record type and owner, preserve unrelated legitimate services, and change only the provider-controlled record required for the intended mail route.

Related email diagnostics

Email delivery delayed or rejected after a DNS migrationDiagnose email that stopped arriving after a DNS change. Compare public MX records with the intended provider and avoid false alarms for mail gateways. SPF is not configured for the envelope sender domainDiagnose SPF missing on a bounce or MAIL FROM subdomain. Check the exact envelope domain, add only authorized senders, and verify safely. DKIM public key record is invalid or revokedDiagnose an invalid or revoked DKIM public key record. Check the exact DKIM selector in public DNS before replacing a sender-provided key.

Primary sources: Infomaniak kSuite official setup guidance.