Infomaniak puts much of the configuration in place for you when the Mail Service is created — which is convenient, and becomes a precise trap: the SPF record added by default is already strict.
SPF
The value added by default when the service is created:
v=spf1 include:spf.infomaniak.ch -allNote the -all: from day one, any server not on that list has its messages rejected. It is the right setting to arrive at — provided you add your other senders before they get refused. One SPF record per domain, always.
The matching MX record points to mta-gw.infomaniak.ch with priority 5.
DKIM
The key is found in the Mail Service, under Global security, and published in the domain’s DNS zone. A useful particularity: unlike SPF and DMARC, which allow one record each, several DKIM records can coexist on one domain, each under its own selector. That is exactly what you need when an email platform signs alongside your mailbox provider.
DMARC
Publish the monitoring policy on _dmarc.yourdomain.com:
v=DMARC1; p=none; rua=mailto:your-address@yourdomain.comStay there long enough to identify every legitimate sender before tightening. The progression, step by step.
Common mistakes with Infomaniak
- The default
-all, discovered the day the newsletter platform stops arriving. Add your third-party senders to the existing record; do not create a second one. - Propagation can take up to 48 hours. A check run ten minutes after the change proves nothing.
- A domain managed elsewhere: if the DNS zone is not at Infomaniak, none of these records is published automatically — they have to be copied by hand.
- Trusting the built-in check alone. Infomaniak verifies SPF, DKIM and DMARC on your domain, which validates the syntax. It says nothing about what other servers actually see — that is what aggregate reports are for.
Once it is in place, Clarsend reads your reports and shows you what passes, what fails, and who is sending without your knowledge — without opening a single XML file.