This module shows email notification tracking status for any messages in mail thread (chatter). Each notified partner will have an intuitive icon just right to his name.
Table of contents
If you're using a multi-database installation (with or without dbfilter option)
where /web/databse/selector returns a list of more than one database, then
you need to add mail_tracking
addon to wide load addons list
(by default, only web
addon), setting --load
option.
For example, --load=web,mail,mail_tracking
As there can be scenarios where sending a tracking img in the email body is not desired, there is a global system parameter "mail_tracking.tracking_img_disabled" that can be set to True to remove the tracking img from all outgoing emails. Note that the Opened status will not be available in this case.
When user sends a message in mail_thread (chatter), for instance in partner form, then an email tracking is created for each email notification. Then a status icon will appear just right to name of notified partner.
These are all available status icons:
Unknown: No email tracking info available. Maybe this notified partner has 'Receive Inbox Notifications by Email' == 'Never'
Sent: Sent to SMTP server configured
Delivered: Delivered to final MX server
Cc: It's a Carbon-Copy recipient. Can't know the status so is 'Unknown'
No Email: The partner doesn't have a defined email
No Partner: The recipient doesn't have a defined partner
If you want to see all tracking emails and events you can go to
- Settings > Technical > Email > Tracking emails
- Settings > Technical > Email > Tracking events
When the message generates an 'error' status, it will apear on discuss 'Failed' channel. Any view with chatter can show the failed messages too.
You can use "Failed sent messages" filter present in all views to show records with messages in failed status and that needs an user action.
- Integrate with the core mail.notification model. A soft way would be to write a notification event along with the mail.tracking.event ones. Another way could be to merge both models and build the module features on top of it. This might imply a refactor though.
Bugs are tracked on GitHub Issues. In case of trouble, please check there if your issue has already been reported. If you spotted it first, help us to smash it by providing a detailed and welcomed feedback.
Do not contact contributors directly about support or help with technical issues.
- Tecnativa
- Tecnativa:
- Pedro M. Baeza
- Antonio Espinosa
- David Vidal
- Ernesto Tejeda
- Rafael Blasco
- Alexandre Díaz
- Eezee-IT: * Asma Elferkhsi
- Vauxoo: * Agustín Payen Sandoval
- Odoo Community Association: Icon.
- Thanks to LlubNek and Openclipart for the icon.
This module is maintained by the OCA.
OCA, or the Odoo Community Association, is a nonprofit organization whose mission is to support the collaborative development of Odoo features and promote its widespread use.
This module is part of the OCA/social project on GitHub.
You are welcome to contribute. To learn how please visit https://odoo-community.org/page/Contribute.