Skip to content

[16.0][IMP] base_mail_sender_bcc: avoid intempestive BCC#247

Open
arnaudlayec wants to merge 1 commit into
16.0from
16.0-mail-sender-bcc-fix
Open

[16.0][IMP] base_mail_sender_bcc: avoid intempestive BCC#247
arnaudlayec wants to merge 1 commit into
16.0from
16.0-mail-sender-bcc-fix

Conversation

@arnaudlayec

Copy link
Copy Markdown
Contributor

Intempestive BCC like:

  • When a user send its timesheet.sheet to manager's approval, the notification triggers an email to all the managers who choseed "Receive notification in email" (and not in Odoo). The user who just validated its timesheet was added in BCC of the "notification" mail
  • When an external partner (e.g. customer or supplier) responds to an email sent by Odoo (e.g. a purchase request), the email is processed by Odoo and sent back to the followers of the Purchase Request. In this "re-routed" email, the "from" address, meaning the supplier, is added in BCC of the re-routed mails.

=> This PR proposes to only add Odoo users in BCC for the email sent by the mail.compose.wizard.

…adding external partners in BCC of their reply to Odoo emails
@ak-git-bot ak-git-bot added series:16.0 mod:base_mail_sender_bcc Module base_mail_sender_bcc labels Jun 13, 2026
@arnaudlayec

Copy link
Copy Markdown
Contributor Author

@alexis-via: a small but useful improvement, what do you think?
For the example, ALUVAL users currently refused to use this module due to the issues described, though they really want the BCC feature

@alexis-via

Copy link
Copy Markdown
Member

With this change, I'm afraid overdue reminders will not be Bcc-ed because they don't go through the mail compose wizard.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

mod:base_mail_sender_bcc Module base_mail_sender_bcc series:16.0

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants