This release is a pre-release and may not be stable for production use.
Default Thread For Unbounded Emails
This module extends the functionality of mail fetching to support choosing a mail thread that acts as a mail sink and gathers all mail messages that Odoo does not know where to put.
Dangling emails are really a problem because if you do not care about them, SPAM can enter your inbox and keep increasing fetchmail process network quota because Odoo would gather them every time it runs the fetchmail process.
Before this, your only choice was to create a new record for those unbounded emails. That could be useful under some circumstances, like creating a crm.lead for them, but what happens if you do not want to have lots of spammy leads? Or if you do not need Odoo’s CRM at all?
Here we come to the rescue. This simple addons adds almost none dependencies and allows you to direct those mails somewhere you can handle or ignore at wish.
Table of contents
Configuration
To configure this module, you need to:
Go to Settings > General Settings > Configure the incoming email gateway.
Create or edit a record.
Configure properly.
Under Default mail thread, choose a model and record.
Tip: if you do not know what to choose, we suggest you to use a mail channel.
Usage
To use this module, you need to:
Subscribe to the thread you chose as the Default mail thread.
You will be notified when a new unbound email lands in that thread.
Do what you want with it.
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
-
Jairo Llopis
David Vidal
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/social 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 odoo11-addon-fetchmail-thread-default 11.0.1.0.0.99.dev6
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 |
|---|---|---|---|---|
| odoo11_addon_fetchmail_thread_default-11.0.1.0.0.99.dev6-py2.py3-none-any.whl | Python 3, Python 2 | none | any | Details for odoo11_addon_fetchmail_thread_default-11.0.1.0.0.99.dev6-py2.py3-none-any.whl |
Release files / odoo11_addon_fetchmail_thread_default-11.0.1.0.0.99.dev6-py2.py3-none-any.whl
| Download URL | odoo11_addon_fetchmail_thread_default-11.0.1.0.0.99.dev6-py2.py3-none-any.whl |
|---|---|
| Size | 37.1 kB |
| Tags | Python 2 Python 3 |
|
SHA-256 checksum How to use checksums |
1e70af4862367eb380b7cc0aa59a2cac9e27312e26d77baf9e4bcac1dec18e18
|
|
BLAKE2b-256 checksum How to use checksums |
cf08ab0cfc40ef675cd39728312c2f0c21713b315f6cfeb0ed0283bbcd968188
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.1 CPython/3.8.10
|
Security for odoo11-addon-fetchmail-thread-default 11.0.1.0.0.99.dev6
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.
