Victor Feyens
42bad1a6d2
Remove most values uselessly specified because giving the same value as the default one (see _DEFAULT_MANIFEST in odoo/modules/module.py) * auto_install is Falsy by default * author is Odoo SA by default * summary & description are empty strings by default * application is False by default * test, demo, depends and data are empty lists by default This will reduce noise/inconsistencies between manifests specifications, simplify analysis of manifests content, ... closes odoo/odoo#90209 Related: odoo/enterprise#26807 Signed-off-by: Victor Feyens (vfe) <vfe@odoo.com>
48 lines
1.8 KiB
Python
48 lines
1.8 KiB
Python
#-*- coding:utf-8 -*-
|
|
# Part of Odoo. See LICENSE file for full copyright and licensing details.
|
|
|
|
{
|
|
'name': 'Email Gateway',
|
|
'version': '1.0',
|
|
'depends': ['mail'],
|
|
'category': 'Hidden/Tools',
|
|
'description': """
|
|
Retrieve incoming email on POP/IMAP servers.
|
|
============================================
|
|
|
|
Enter the parameters of your POP/IMAP account(s), and any incoming emails on
|
|
these accounts will be automatically downloaded into your Odoo system. All
|
|
POP3/IMAP-compatible servers are supported, included those that require an
|
|
encrypted SSL/TLS connection.
|
|
|
|
This can be used to easily create email-based workflows for many email-enabled Odoo documents, such as:
|
|
----------------------------------------------------------------------------------------------------------
|
|
* CRM Leads/Opportunities
|
|
* CRM Claims
|
|
* Project Issues
|
|
* Project Tasks
|
|
* Human Resource Recruitments (Applicants)
|
|
|
|
Just install the relevant application, and you can assign any of these document
|
|
types (Leads, Project Issues) to your incoming email accounts. New emails will
|
|
automatically spawn new documents of the chosen type, so it's a snap to create a
|
|
mailbox-to-Odoo integration. Even better: these documents directly act as mini
|
|
conversations synchronized by email. You can reply from within Odoo, and the
|
|
answers will automatically be collected when they come back, and attached to the
|
|
same *conversation* document.
|
|
|
|
For more specific needs, you may also assign custom-defined actions
|
|
(technically: Server Actions) to be triggered for each incoming mail.
|
|
""",
|
|
'data': [
|
|
'data/fetchmail_data.xml',
|
|
'security/ir.model.access.csv',
|
|
'views/fetchmail_views.xml',
|
|
'views/mail_mail_views.xml',
|
|
'views/res_config_settings_views.xml',
|
|
],
|
|
'installable': True,
|
|
'auto_install': True,
|
|
'license': 'LGPL-3',
|
|
}
|