Infomaniak Mail · SPF, DKIM, and DMARC
DMARC for Infomaniak: from Global Security to reject.
Infomaniak can check and sometimes correct its own mail signals through Global Security. Your complete sender inventory still controls a safe rollout: newsletters, CRM, billing, and website mail must also align before strict DMARC enforcement.
Reviewed: July 19, 2026 · Primary sources below
Inventory every sender for the domain
List Infomaniak Mail, newsletters, CRM, billing, support platforms, website forms, and other SMTP services. Global Security understands the Infomaniak Mail Service relationship, but it cannot automatically know every external platform using your visible From domain.
Open Global Security for the Mail Service
In Infomaniak Manager, open the affected Mail Service and then Global Security. Review SPF, DKIM, and DMARC separately. Infomaniak notes that this diagnostic is meaningful only when the domain correctly points to that Infomaniak Mail Service.
Keep exactly one root SPF record
If Infomaniak is the only sender, its strict default is the correct starting point. Other platforms must be merged into the same SPF policy or use aligned DKIM. Never publish multiple SPF records, and keep the DNS lookup limit in view.
v=spf1 include:spf.infomaniak.ch -allVerify DKIM instead of guessing a selector
DKIM is enabled by default when Infomaniak manages both the Mail Service and DNS zone. With external DNS, Global Security displays the specific DKIM record to publish. Copy that exact value, wait for detection, and verify an externally delivered test message for aligned DKIM=pass.
Start DMARC with aggregate reports
Use the DMARC assistant in Global Security or publish one TXT record at _dmarc. With an unknown sender landscape, begin at p=none and add a rua destination for daily aggregates. RUF failure reports can include message content and are not required for a normal rollout.
v=DMARC1; p=none; rua=mailto:dmarc@example.comMove to reject only after real reports
Identify every legitimate source and fix SPF or DKIM alignment failures. Then move deliberately through quarantine to p=reject while continuing to review aggregate reports. Infomaniak warns that DNS changes can take up to 48 hours to propagate.
Important
One-click correction does not know your entire sender landscape.
An automatic SPF correction can be appropriate for Infomaniak-only sending. If newsletter, CRM, billing, or website systems also send, preserve their authorization and alignment before changing DNS. Review the existing record and real reports first.
If you need continuous monitoring
See who really sends in your name.
DMARCTrust is an external platform for DMARC reports, alerts, and sender inventory. Its free evaluation tier is limited to one domain; paid business plans start at $19/month for two domains. The MX Audit score remains independent.
Where are SPF, DKIM, and DMARC in Infomaniak?
Open the affected Mail Service in Infomaniak Manager and select Global Security. When DNS is hosted elsewhere, publish the records shown there at the external DNS provider.
What SPF record does Infomaniak Mail use?
Infomaniak documents v=spf1 include:spf.infomaniak.ch -all as the strict default when Infomaniak is the authorized sender. Other platforms must be included in the same policy or authenticate with aligned DKIM.
Is DKIM automatic with Infomaniak?
The provider says DKIM is enabled by default for Mail Services whose DNS zone is managed at Infomaniak. With external DNS, Global Security provides the specific record to copy.
Should I enable RUF failure reports?
Aggregate RUA reports are enough for a normal rollout. Infomaniak notes that RUF can contain parts of the failed original message, so it requires a separate privacy decision.