This module lets you simulate an incoming email directly from Odoo, without a real mail server or SMTP client.
It adds a Simulate Incoming Email button (and matching Action menu entry) on the Incoming Mail Server, opening a small composer (From, To, Cc, Bcc, Subject, Body). On send, the email is used as if it had been fetched from a server, it is then routed by alias and creates the target record (helpdesk ticket, lead, task, ...).
It is meant for testing mail-driven flows on environments that have no inbound mail server, like test instances.
It also adds a Replay Email File button, which takes a raw message file (usually a .eml exported from a mail client) and feeds it to the gateway untouched. Useful to reproduce how a specific email that a customer received was handled, byte for byte.
auto_awesome What this module does
AI-generated from the code · Odoo 18.0Lets administrators simulate an incoming email or replay a raw .eml file directly from the Incoming Mail Server screen, so mail-driven flows (tickets, leads, tasks) can be tested without a real mail server.
This module adds testing tools to the Incoming Mail Server screen (fetchmail.server). Two buttons appear next to the existing fetch button: "Simulate Incoming Email" and "Replay Email File". Both are also available from the Action menu on the server list and form.
- Simulate Incoming Email opens a small composer with From, To, Cc, Bcc, Subject and Body. From defaults to the current user's email address, and From and To are mandatory. Pressing Send builds a raw email message and feeds it to the mail gateway exactly as if it had been fetched from the server, so aliases route it and the target record is created.
- Replay Email File opens a form where you upload a raw message file (usually a .eml exported from a mail client) and press Process. The file is sent to the gateway untouched, which is useful to reproduce how a specific real email was handled.
When the wizard is opened from a single server, that server is preselected; if several are selected, no server is preselected. After processing, a success notification shows the ID of the record created by the gateway. Access is restricted to system administrators.
Depends on
Models and fields (3)
- fetchmail.incoming.test · new modelbody, subject, email_cc (Cc), email_to (To), email_bcc (Bcc), email_from (From)
- fetchmail.incoming.test.eml · new modeleml_file (Email File), eml_filename
- fetchmail.incoming.test.mixin · new modelserver_id (Incoming Mail Server)
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-03Confirmation status: 1 confirmed, 8 with no information of 9 versions.
Sources · Odoo 18.0
Confirmed on 2026-11-03 in branch 18.0 of OCA/mail.
terminal Installation and usage
OCA documentation · Odoo 18.0Usage
Source · Odoo 18.0To use this module, follow these steps:
- Go to Settings > Technical > Email > Incoming Mail Servers.
- Open a saved server, or select one in the list.
- Click Simulate Incoming Email (button on the form, or the Action menu).
- Fill in the composer:
- To: the alias that routes to your target model, e.g. a Helpdesk team alias.
- From, Cc, Bcc, Subject, Body as needed.
- Click Send.
The message goes through the standard mail gateway and the created record (e.g. a Helpdesk ticket) appears, just as if the email had been received.
To replay a real email instead of composing one:
- Click Replay Email File (button on the form, or the Action menu).
- Upload the message file, then click Process.
The file is sent to the gateway as if it was received through fetchmail. Malformed HTML and unusual headers are preserved.
Both wizards reuse the Create a New Record model of the server they were opened from, exactly like a real fetch: when the email replies to nothing and matches no alias, the gateway creates a record of that model instead of refusing the email.
No verified information in OCA: Installation, Configuration.
Installation instructions, the distribution package, dependencies and configuration steps are not shown because they have not yet been verified in the module documentation for any version.
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.