Contributors mailing list archives
Re: Issues with outgoing email management in Odooby
ForgeFlow, S.L., Lois Rilo Antelo
Thanks for the insights, I will follow the discussion there to be notified if the work is finished.
On Thu, Jun 1, 2023 at 10:58 AM Cyril VINH-TUNG <email@example.com> wrote:
Hi LoisWe did not merge mail_body_notified_partner with mail_show_followers because they don't have same functionalitiesCheck final comment from rafael https://github.com/OCA/social/pull/855#issuecomment-1102348461We will definitely keep mail_body_notified_partnerBest regardsLe mer. 31 mai 2023, 21:42, Lois Rilo Antelo <firstname.lastname@example.org> a écrit :Hi all,Indeed this is really annoying while dealing with Odoo mailing.A bit inline with Cyril's answer, as far as I know mail_tracking does not provide the information of the cc'd recipients to the external people (who only receive the email). In our case we have used mail_show_follower module which is already migrated to recent versions, not sure if there is any big difference with mail_body_notified_partner and maybe they can converge in a single module.Kind regards,On Wed, May 31, 2023 at 8:27 PM Cyril VINH-TUNG <email@example.com> wrote:Hi AlexWe also faced long time issues with Odoo mail system and the worst part is that someone lost her job because of that 'unsual' email system (https://github.com/OCA/social/pull/855#issuecomment-1068256758)We solved this with :- mail_footer_notified_partner now renamed mail_body_notified_partner (better because the added text is located at the top of the body) + customization of the message saying 'WARNING if you reply to this email the following people will be cc :...'- disclaimer in the signature of every user that also ask people to reply to the mail with information about the subject and not reply with information that does not concern itWe also use the amazing mail_tracking as mandatory for all our customers but it does not warn the recipients about who will receive the reply.On the other hand, for incoming emails, we did a PR to mail_tracking that allows to show in the chatter the aliases who were in to and cc (https://github.com/OCA/social/pull/941/commits/d6443446ceca845792d50fd3daa3d1ebdb06c3f0)We think that Odoo's mail system is great because it organizes communication very well but it's also very hard to convince our customers. People have very bad habits with standard mail systems (they reply to email with information that have nothing to see with the subject, they start another thread instead of replying existing discussion... so on)That said, we have some customers who use Odoo as 'the' mail system of the company and therefore improve their 'information organization'.We wrote a blog about it a few years ago (in french) https://www.easypme.com/blog/blog-5/post/le-futur-de-la-messagerie-d-entreprise-55IMHO best configuration is- odoo as the main mail system of the company for almost all the employees (notifications in Odoo)- dedicated standard mailboxes (outside Odoo) for Managers (notifications by email) who might have very sensitive and private information to share directly with partnersBest regardsLe mer. 31 mai 2023, 05:11, Alexandre Fayolle <firstname.lastname@example.org> a écrit :
Hello everyone, This is a long standing topic in Odoo, but I'm facing it again with an unhappy customer. The way Odoo manages the sending of messages to followers of a "thread" by sending 1 email per follower, loosing all information from people who could have been in CC of an incoming mail, is really lame. Is there some knowledge hanging around about a way to change this so that Odoo would: * record the CC in a secondary field (say follower_cc_ids) for incoming message * promote a follower_cc to follower in case an incoming mail comes with this person in To: rather than CC: * send outgoing mails with 1 single mail with all followers in To: and follower_cc_ids in CC: I'm not super keen in touching this part of the Odoo source code, which I find quite obscure, and but maybe some have walked this path and could provide feedback, advice (or even maybe source code). Thanks for your help, -- Alexandre Fayolle Senior Software Engineer Tel : +33 4 58 48 20 30 Camptocamp France SAS 18 rue du Lac Saint André 73 370 Le Bourget-du-Lac France http://www.camptocamp.com--