Mail Carbon Copy and Blind Copy
This module extends Odoo’s mail functionality to add support for Carbon Copy (Cc) and Blind Carbon Copy (Bcc) recipients when sending emails.
Key features:
Send emails to Cc and Bcc recipients without requiring partner records
Add Cc and Bcc fields to mail composer wizard
Support Cc and Bcc in mail templates
Properly handle Cc and Bcc recipients when sending emails
Store Cc and Bcc information in mail messages for audit purposes
Works with mass mailing functionality
Table of contents
Configuration
No configuration is needed. The module is ready to use after installation.
If you want to use Bcc in email templates:
Go to Settings > Technical > Email > Templates
Select or create an email template
Set the Bcc field with the desired email addresses (comma-separated)
Usage
To use Cc and Bcc when composing emails:
Open any record with the chatter (e.g., a sales order, helpdesk ticket, etc.)
Click on Send message or use any action that opens the mail composer
You will see three email fields:
To: Primary recipients
Cc: Carbon copy recipients (visible to all recipients)
Bcc: Blind carbon copy recipients (hidden from other recipients)
Enter email addresses in any of these fields (comma-separated for multiple addresses)
Compose your message and click Send
The Cc and Bcc recipients will receive the email, and the Cc information will be stored in the message for reference.
Note: When using mass mailing, the Cc and Bcc fields will be applied to all emails sent in the batch.
Changelog
16.0.1.0.0 (2026-02-05)
[ADD] Initial implementation of Cc and Bcc support for email composer
[ADD] Cc and Bcc fields in mail.message model
[ADD] Bcc field in mail.template model
[ADD] Extended mail.compose.message wizard with To, Cc, and Bcc fields
[ADD] Override of mail.mail._send method to properly handle Bcc recipients
[ADD] Support for mass mailing with Cc and Bcc fields
Bug Tracker
Bugs are tracked on GitLab 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.
Credits
Contributors
-
Juan Manuel Regalado <juanmanuel.regalado@somitcoop.coop>
Maintainers
This module is maintained by Som It Cooperatiu SCCL and Som Connexió SCCL.
This module is part of the OCA initiative. 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.
To contribute to this module, please visit https://odoo-community.org.
Metadata
Release files for odoo-addon-mail-cc-bcc 16.0.1.0.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| odoo_addon_mail_cc_bcc-16.0.1.0.0.tar.gz | 33.6 kB | Without provenance | Details |
Release files / odoo_addon_mail_cc_bcc-16.0.1.0.0.tar.gz
| Download URL | odoo_addon_mail_cc_bcc-16.0.1.0.0.tar.gz |
|---|---|
| Size | 33.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
6ca5939cb4336280c58a5453e09e3029b3341fb25ec4c8e115a6501cf7ea6567
|
|
BLAKE2b-256 checksum How to use checksums |
79b0600fd63ea7ddd4a7c93fe4e45da4303897e210aad5f4e7f24e6300d69c91
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.10.12
|
Security for odoo-addon-mail-cc-bcc 16.0.1.0.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.