Skip to Content

Connecting Odoo and Infomaniak kSuite: email, calendar, contacts

What I actually connected between my self-hosted Odoo and kSuite, what works day to day, and the limits.
November 15, 2026 by
Connecting Odoo and Infomaniak kSuite: email, calendar, contacts

Odoo and Infomaniak kSuite: what I connected, and how

Sector: ERP, email, calendar

Period: August and September 2026, then day-to-day operation

Role: client and implementer, for my own company

My email and calendar are with Infomaniak, in kSuite. My ERP is Odoo 19 Community, installed on my own server since my migration in August 2026. Here is what I connected between the two for email, calendar and contacts, what works day to day, and what does not.

Context

kSuite is the online suite of Infomaniak, a Swiss hosting provider: email, calendar, contacts, storage (kDrive) and video meetings (kMeet). Odoo, for its part, sends emails (quotes, invoices, confirmations), handles online bookings and keeps its own calendar. Without a connection, you live with two calendars that ignore each other, and emails that leave from who knows where.

Problem

  • Emails sent by Odoo must go out in the name of each website, without ending up in spam.
  • A client booking an appointment online must never land on a slot that is already taken in my kSuite calendar.
  • An appointment set in Odoo must appear in kSuite, and therefore on my phone.
  • And none of this must be able to damage my personal calendar.

Solution

1. Email: Odoo sends through Infomaniak's server

Odoo sends its emails through the outgoing (SMTP) server of my Infomaniak mailbox, with a single account. My websites' domains are declared at Infomaniak as aliases of the main domain: each message goes out in the name of the relevant website's address, and replies are directed to that same address. The sender address and the return address are always on the same domain, and that domain authorises Infomaniak in its SPF record: this is what lets messages pass the DMARC checks of your clients' mail providers.

Two traps along the way. Infomaniak rejects a message whose envelope address does not exist in kSuite (error “550 Sender mismatch”): the technical addresses inherited from the old online Odoo had to be replaced. And carelessly widening the list of domains allowed to send breaks DMARC alignment: only domains actually attached to a company should be in it.

2. Calendar: a two-way CalDAV synchronisation

CalDAV is the standard protocol for exchanging calendars, and kSuite speaks it. I use a free CalDAV synchronisation module for Odoo, which I hardened: an appointment I create in kSuite appears in Odoo and blocks the slot there, and an event created in Odoo appears in kSuite. The synchronisation runs every fifteen minutes, over a window from a few days back to three months ahead: the calendar's history is never scanned or modified.

3. Online bookings, each with its own video room

For public booking, a module of my own reads my availability in kSuite through Infomaniak's API and removes the slots where I am busy from the booking page. When a client books, it creates the event in my calendar with a kMeet room dedicated to that appointment. Only a generic label (“busy”) enters Odoo: never the title, description or attendees of my private appointments.

4. Contacts: no automatic synchronisation

I have not set up any contact synchronisation between kSuite and Odoo. Odoo remains the reference for clients and leads; my kSuite address book stays personal. If you need it, it is a development to scope, not a box to tick.

What was difficult

  • A write to a calendar cannot be undone. A deletion sent to a remote server cannot be rolled back. That is why no deletion can travel from Odoo to kSuite: deleting an event in Odoo leaves it in kSuite.
  • Several calendar sources in the same Odoo. My Odoo also receives a Google calendar and bookings. They had to be kept apart so that no event is exported twice, or deleted by the wrong connector.
  • Recurring events. This is the trickiest family of cases in CalDAV, and the least proven on my side: I keep a close eye on it.
  • Replies to emails do not reach Odoo. No inbox is connected to Odoo: when a client replies, the message lands in kSuite, not in the history of their record. It is a choice of simplicity, with that limit.
  • Infomaniak's calendar API is not a contractual interface. It can change. Infomaniak's official MCP server for the calendar is currently its best documentation, and it is what I watch.

Result

  • Emails that go out in the name of each website, through Infomaniak's server.
  • One calendar seen from both sides: the booking page only offers slots that are actually free.
  • A dedicated kMeet room for every appointment booked online.
  • A protected personal calendar: no deletion leaves Odoo.

Who I recommend it to

If your email and calendar are already with Infomaniak and you are moving to Odoo, this connection saves you from changing your daily tools. It needs someone to run it: an update of the synchronisation module is tested on a copy, never directly on your calendar.

Want to connect your tools the same way? See Systems & infrastructure, or book a 20-minute discovery call.

Sources

Tags: Odoo, kSuite, Infomaniak, CalDAV, email, calendar, kMeet, self-hosting

Tariffs and small business: diversify suppliers and markets, an importer's lesson
The rate has changed four times since April 2025: rather than betting on the next one, reduce your dependence on a single supplier or market.