Mail Operating Unit
This module allows companies working with multiple Operating Units to send emails with the appropriate email domain and, optionally, the appropriate outgoing mail server depending on the Operating Unit context.
It lets you define an Alias Domain on an Operating Unit and use that domain automatically when emails are generated from templates or records linked to that Operating Unit.
It also allows you to define an Outgoing Mail Server on an Operating Unit and automatically route emails through that server when no mail server is explicitly defined on the email template.
This is especially useful in multi-brand or multi-entity environments where each Operating Unit must send emails using its own domain and SMTP server, while still keeping the standard Odoo behavior as a fallback when no specific Operating Unit configuration can be determined.
Table of contents
Configuration
To configure this module, you need to:
Assign an Alias Domain to each Operating Unit that should use a specific email domain.
Assign an Operating Unit to an Email Template when emails sent from that template must use the alias domain of that operating unit.
Optionally assign an Outgoing Mail Server to an Operating Unit when emails should be routed through a specific SMTP server.
When no operating unit is defined on the template or on the target record, the standard Odoo alias domain behavior is applied.
When no unambiguous Operating Unit mail server can be determined, the standard Odoo outgoing mail server selection is applied.
Bug Tracker
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.
Credits
Contributors
Vincent Van Rossem <vincent.vanrossem@camptocamp.com>
Italo Lopes <italo.lopes@camptocamp.com>
Maksym Yankin <maksym.yankin@camptocamp.com>
Maintainers
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/operating-unit project on GitHub.
You are welcome to contribute. To learn how please visit https://odoo-community.org/page/Contribute.
1 maintainer
Metadata
1 maintainer
Release files for odoo-addon-mail-operating-unit 17.0.2.0.2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| odoo_addon_mail_operating_unit-17.0.2.0.2-py3-none-any.whl | Python 3 | none | any | Details for odoo_addon_mail_operating_unit-17.0.2.0.2-py3-none-any.whl |
Release files / odoo_addon_mail_operating_unit-17.0.2.0.2-py3-none-any.whl
| Download URL | odoo_addon_mail_operating_unit-17.0.2.0.2-py3-none-any.whl |
|---|---|
| Size | 36.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
00a300ef10ce0e49194ec1475fd79b68cbb06e19b89505b5b08d4eda72bd6782
|
|
BLAKE2b-256 checksum How to use checksums |
eb7521294a4ec4817660e21f8aac535d465393c5bc65d55a39d82cd0beb6f1a0
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.14.4
|
Security for odoo-addon-mail-operating-unit 17.0.2.0.2
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.
