Mail Route
by Viindoo
| Lines of Code | 868 |
| Technical name | viin_mail_route |
| License | OPL-1 |
| Website | https://viindoo.com/apps/modules/17.0/viin_mail_route |
| Read description for | v 15.0 v 16.0 v 18.0 |
| Required Apps | Discuss (mail) |
| Extensions | Test Mail Route Mail Route - Employees |
Replies that find their way back to the right record
Email threading kept intact between two Odoo systems - and a way to move a whole conversation to another record.
Mail Route (technical name viin_mail_route) is an Odoo 17.0 app for Odoo Community and Odoo Enterprise and Viindoo Cloud, built for support, project manager, sales, it.
At a Glance
The facts of Mail Route, version 0.1.2, in one place. Published by Viindoo.
How It Works
Three screens.
The thread
Where the conversation lives - and where a reply has to come back to.
The action
Added to the record's action menu, for users in the group.
The move
Pick the destination; the messages and future mail follow. It cannot be undone.
What You Get
Original Message-ID and References stored on the record
Those headers replayed on outgoing replies
Threading survives between separate Odoo systems
Move an entire message thread to another record
Future incoming mail follows the move
Restricted to a dedicated group
More Screens
Everything below was taken on a database seeded with real business data, on this series - not a mock-up and not a screenshot from an older version.
The action menu
What This App Does Not Do
Read this before you buy. Everything below is something the app deliberately leaves to another app or to you.
The wizard says so before you apply.
Only the messages move.
Routing here is about headers, not delivery.
Give the group to the people who should have it.
Works Well With
Apps from the same stack, built to fit this one:
Who Should Use Mail Route?
Support
Keeps one conversation in one place.
Project manager
Moves a thread filed on the wrong task.
Sales
Replies to a partner system and gets the answer back.
IT
Stops explaining why threads fork between two Odoos.
Frequently Asked Questions
What does Mail Route do?
Email threading kept intact between two Odoo systems - and a way to move a whole conversation to another record.
What does Mail Route not do?
Moving a thread cannot be undone. The wizard says so before you apply. It does not merge records. Only the messages move. It does not fix a broken mail server. Routing here is about headers, not delivery. The action is group-restricted. Give the group to the people who should have it.
Who is Mail Route for?
Support: Keeps one conversation in one place. Project manager: Moves a thread filed on the wrong task. Sales: Replies to a partner system and gets the answer back. IT: Stops explaining why threads fork between two Odoos.
Which Odoo version and editions does it support?
Odoo 17.0 - Odoo Community, Odoo Enterprise, Viindoo Cloud. Upgrades to a newer Odoo series are a separate purchase for that series.
What does it depend on?
It installs on top of: mail. Odoo installs them with it.
How do I set it up?
Three screens.
What works well with it?
Mail Route - Employees (viin_mail_route_hr): Keeps the headers off a public employee profile. Helpdesk (viin_helpdesk): Where misfiled threads hurt most. Mail extensions (viin_mail): The rest of the mail layer.
Can I try it before buying?
Yes - the Live Preview button at the top of this page opens the module's own screen on a working database.
How do I get support?
Write to apps.support@viindoo.com with your Odoo version and the technical name viin_mail_route; pre-sales questions go to sales@viindoo.com.
See Mail Route in Action
Live demo: v17demo-int.viindoo.com/web#action=project.action_view_all_task
Need help with Mail Route?
For questions, implementation support or a custom feature, contact Viindoo.
Pre-Sales & Partnership
sales@viindoo.comUpgrades to a newer Odoo series are a separate purchase for that series.
All Viindoo apps: apps.odoo.com/apps/modules/browse?author=Viindoo
Technical Requirement
Changes log
0.1.2 - Latest on the 17.0 line
- Routing headers live in their own prefetch group, so they never join an unrelated read.
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.