Thibault Delavallée
213d5d396c
RATIONALE Currently most of mail related failure types are computed in mass mailing. This is mainly due to historical reasons. We could move some of this computation directly at mail level and store failure information directly in mail.mail records. SPECIFICATIONS Overall purpose is to get near SMS implementation where base composer prepare more advanced pre computation: blacklist, optout, seen list. Detect and store failure types directly on mail.mail: blacklist, optout, duplicates, missing email, wrong email, ... State computation is moved from mass mailing to mail. It is also improved as currently everything is based on "first recipient found". This is globally valid for mass mailing who uses default recipients (customer). However when dealing with generic mailing this is not true anymore. We choose to store and update status on mail.mail records only when having a single recipient. When several recipients are defined on a given mail.mail we cannot really decide a status prior to sending it and skip this computation. Mass mailing override now uses information from mail.mail to update its linked traces as computation is now delegated to base composer model. LINKS Task ID-2377974 Community PR odoo#61467 Enterprise PR odoo/enterprise#14633 Upgrade PR odoo/upgrade#1907
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, ...
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.
To learn the software, we recommend the Odoo eLearning, or Scale-up, the business game. Developers can start with the developer tutorials