OdooWiki OCA HUB

Default Thread For Unbounded Emails

fetchmail_thread_default folder_open OCA/social open_in_new
Discuss License: AGPL-3

This module extends the functionality of mail fetching to support choosing a mail thread that acts as a mail sink and gathers all mail messages that Odoo does not know where to put.

Dangling emails are really a problem because if you do not care about them, SPAM can enter your inbox and keep increasing fetchmail process network quota because Odoo would gather them every time it runs the fetchmail process.

Before this, your only choice was to create a new record for those unbounded emails. That could be useful under some circumstances, like creating a crm.lead for them, but what happens if you do not want to have lots of spammy leads? Or if you do not need Odoo's CRM at all?

Here we come to the rescue. This simple addons adds almost none dependencies and allows you to direct those mails somewhere you can handle or ignore at wish.

auto_awesome What this module does

AI-generated from the code · Odoo 18.0

Lets you pick a default mail thread on an incoming mail server so that emails Odoo cannot route anywhere are posted there instead of being lost or turned into new records.

When Odoo fetches incoming email, some messages have no clear destination. This module adds a "Default mail thread" field on the incoming mail server configuration screen, right after the existing destination record field.

  • You choose any record that can receive messages (any model that supports the chatter, such as a discussion channel) as the default thread.
  • If a fetched message has no destination model or thread, it is posted as a new message on that default thread instead of creating a new record.
  • The two destination settings are mutually exclusive: setting a default thread clears the normal destination record, and setting a destination record clears the default thread.
  • Messages posted this way do not subscribe the sender or recipients, so the thread does not grow its follower list unexpectedly.

It touches the incoming mail server configuration (fetchmail.server) and the message processing logic shared by all chatter-enabled models (mail.thread). A demo data set shows a discussion channel named "mailsink" used as the default thread of a demo POP server.

Depends on

mail
Models and fields (2)
  • mail.thread · extends an existing model
  • fetchmail.server · extends an existing modeldefault_thread_id (Default mail thread)

Text generated by AI (DeepSeek) from reading the Odoo 18.0 code on GitHub; it may contain mistakes, so check the code before deciding. View the code on GitHub

Availability by version

Reviewed: 2026-11-03
Confirmed (verified in repository and branch) Estimated (unverified) No information

Confirmation status: 5 confirmed, 4 with no information of 9 versions.

terminal Installation and usage

OCA documentation · Odoo 18.0

Configuration

Source · Odoo 18.0

To configure this module, you need to:

  • Go to Settings \> General Settings \> Configure the incoming email gateway.
  • Create or edit a record.
  • Configure properly.
  • Under Default mail thread, choose a model and record. Tip: if you do not know what to choose, we suggest you to use a mail channel.

Usage

Source · Odoo 18.0

To use this module, you need to:

  • Subscribe to the thread you chose as the Default mail thread.
  • You will be notified when a new unbound email lands in that thread.
  • Do what you want with it.

No verified information in OCA: Installation.

info

Data imported from GitHub: this sheet reflects the latest catalog review, not a live lookup. Always check the module documentation and staging before installing in production.