Teams that live inside Odoo still bounce out to a separate mail client all day — reading a customer reply in Gmail, re-typing the context onto a CRM lead, then hunting for the same thread in a shared Outlook mailbox. Odoo's native Discuss and the incoming/outgoing mail plumbing (fetchmail.server for polling, ir.mail_server for sending) were built to log messages onto records and run mail gateways, not to be a day-to-day email client. There is no true unified inbox spanning personal and shared mailboxes, no OAuth2-based interactive folder browsing, and no way to triage raw email — read/unread, star, archive, reply — without leaving whichever record it happens to be attached to. That gap is exactly where a stock configuration runs out of road.

This is a build-to-order module that ECOSIRE designs, builds, and installs for you — not an existing apps.odoo.com download. We implement a first-class mailbox layer inside Odoo: new models (models.Model) for mail accounts, folders, and messages, plus a background sync worker driven by an ir.cron job so IMAP and Graph/Gmail API polling never blocks a user request. Accounts authenticate with OAuth2 against Gmail and Outlook/Microsoft 365 using the authorization-code flow with encrypted refresh-token storage, and with app-password or credential auth for generic IMAP servers. Folder and message state is modeled with typed fields and @api.depends compute methods (unread counts, thread grouping), rendered through OWL client-side components and standard XML views, so the inbox feels native to whichever Odoo version you run.

Under the hood the sync is incremental and idempotent: we track per-folder UIDVALIDITY/UID high-water marks for IMAP and delta/history cursors for the API providers, so a re-run never double-imports and a token refresh never loses a message. Access is governed the Odoo way — ir.model.access.csv for base CRUD rights and record rules so a user only sees their own accounts while shared team mailboxes are exposed to the right groups. Sends route through the account's authenticated transport, and every message can be logged back onto the related partner or lead via the existing mail.thread chatter, keeping your CRM the single source of truth. The JSON-RPC/XML-RPC API remains available for any external automation you need on top.

Delivery is build-to-order. We start with a short scoping call to confirm which providers, how many mailboxes, shared-inbox rules, and any record-logging behavior you need, then produce a fixed quote and build against your Odoo 17.0/18.0/19.0 (Community or Enterprise) environment. Typical delivery is one working week from confirmed scope, ending with UAT on staging, a rollback plan, and handover of the git repository. Pricing starts from $999 (indicative, single-company base scope); adding more OAuth provider integrations, shared-mailbox routing rules, high-volume historical email migration, or multi-company deployment increases the quoted scope.