| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
Discuss (mail)
|
| Lines of code | 164 |
| Technical Name |
neuralmedic_mail_cc_bcc |
| License | OPL-1 |
| Website | https://neuralmedic.de |
| Versions | 18.0 19.0 |
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
Discuss (mail)
|
| Lines of code | 164 |
| Technical Name |
neuralmedic_mail_cc_bcc |
| License | OPL-1 |
| Website | https://neuralmedic.de |
| Versions | 18.0 19.0 |
Email CC & BCC
Add Cc, Bcc and Reply-To to the Odoo email composer — and keep every correspondence on the record.
Cc & Bcc, anywhere you compose
A Cc and a Bcc field are added right under the subject of the Compose Email window — in the chatter, on the Send by Email action of any document, and in mass mailing. Add as many addresses as you like, separated by commas.
Recipients do not have to be existing contacts: type any email address and Odoo will deliver to it.
Bcc that stays blind
Blind copies are delivered at the SMTP envelope level and the
Bcc header is stripped before the email leaves your
server. Bcc recipients receive the message, yet remain completely
hidden from everyone else on the email — exactly as Bcc should
behave.
See it in action
Cc, Bcc and Reply-To right in the Compose Email window
Company-wide defaults in Settings
Bcc delivered, yet blind â present in the envelope, absent from the headers
Pick your Reply-To
A Reply-To field lets you decide where answers should land — a shared support inbox, a sales alias, anywhere. When set, it overrides the automatic reply address.
Company-wide defaults
From Settings → General Settings → Discuss, define a default Cc, Bcc and Reply-To. They are pre-filled on every new email, so an archive mailbox or a compliance address is always copied without anyone having to remember it.
Everything is tracked
The Cc and Bcc used for a message are stored on the logged message and on the outgoing email, so the whole conversation stays auditable on the record. No ambiguity, no lost trail.
Highlights
- Cc & Bcc fields in the email composer
- Reply-To field with company default
- Any address — not limited to partners
- Bcc delivered blindly (envelope level)
- Default Cc / Bcc / Reply-To in Settings
- Cc / Bcc tracked on message and email
No strings attached
Runs entirely inside Odoo. No external service, no API key, no vendor lock-in — your data never leaves your server. Compatible with Odoo 18.0 and 19.0, Community and Enterprise.
Data & AI Engineering — Made in Germany
Built and supported by NeuralMedic GmbH.
Support & sales: info@neuralmedic.de
NeuralMedic GmbH · Haslangstraße 49, 85049 Ingolstadt, Germany · Geschäftsführer: Jonas Heinzmann · Amtsgericht Ingolstadt HRB 12717
Odoo Proprietary License v1.0 This software and associated files (the "Software") may only be used (executed, modified, executed after modifications) if you have purchased a valid license from the authors, typically via Odoo Apps, or if you have received a written agreement from the authors of the Software (see the COPYRIGHT file). You may develop Odoo modules that use the Software as a library (typically by depending on it, importing it and using its resources), but without copying any source code or material from the Software. You may distribute those modules under the license of your choice, provided that this license is compatible with the terms of the Odoo Proprietary License (For example: LGPL, MIT, or proprietary licenses similar to this one). It is forbidden to publish, distribute, sublicense, or sell copies of the Software or modified copies of the Software. The above copyright notice and this permission notice must be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Please log in to comment on this module