Thibault Delavallée
8c472b7b78
Incoming email servers have an action_id field holding a server action to run on newly created records. It comes from old implementation of mail gateways in Odoo. Since then mail gateway has evolved. Incoming mail servers are not linked to a unique model anymore. With aliases and automatic thread creation mails can create records in various models. As the server action is bound to a given model it causes issues. Either we have to give back the result of the mail gateway processing to ensure models match. Either we have to limit action_id to records created using the "default model behavior" of incoming mail servers. We choose to remove this field. Same result can be achieved with an automated action running on create trigger. If exactly the same behavior is intended the following rules should be applied * add automated action with model linked to the one you want to update depending on alias configuration and work flow; * set trigger to create; * set action as python; * if it is necessary to be linked to the mail gateway, check in record message_ids that there is a message with message_type being 'email' meaning it has received an incoming email; Using that heuristic migrating existing fetchmail action to server actions should be quite straightforward and will give more flexibility. This commit is linked to task ID 58641. Closes #23621 .
Odoo
Odoo is a suite of web based open source business apps.
The main Odoo Apps include an Open Source CRM, Website Builder, eCommerce, Warehouse Management, Project Management, Billing & Accounting, Point of Sale, Human Resources, Marketing, Manufacturing, Purchase Management, ...
Odoo Apps can be used as stand-alone applications, but they also integrate seamlessly so you get a full-featured Open Source ERP when you install several Apps.
Getting started with Odoo
For a standard installation please follow the Setup instructions from the documentation.
Then follow the developer tutorials