Thibault Delavallée
84e2d6ea55
'alias_user_id' field allows to set a user when creating records through the
mail gateway. This is however quite wrong and eases spoofing. The alias owner
is not the creator of any record, nor responsible.
Current possible ways of being owner / responsible of records created through
the mailgateway
* when you send an email to an alias: if you are recognized you are already
set as creating user and logged message author;
* it is possible to use alias_defaults notably to set fields like 'user_id'
if you want to be notified / responsible of records created through this
specific alias;
Those usages are therefore sufficient, no need to have another way to spoof
users. Moreover it is hidden in technical view of aliases, no model allows
to configure it by default. Moreover since odoo/odoo@3edf181 no default
value is given to alias_user_id as it adds more (ACLs / creator) issues than
really helping setting up mail gateway flows.
Task-3453482
Prepares Task-36879 (Mail: Multi-Domain Aliases)
closes odoo/odoo#138213
Related: odoo/upgrade#5259
Related: odoo/enterprise#48692
Signed-off-by: Thibault Delavallee (tde) <tde@openerp.com>
19 lines
691 B
XML
19 lines
691 B
XML
<?xml version="1.0" encoding="utf-8"?>
|
|
<odoo><data noupdate="1">
|
|
<record id="sales_team.team_sales_department" model="crm.team" forcecreate="False">
|
|
<field name="alias_name">info</field>
|
|
</record>
|
|
|
|
<record id="sales_team.salesteam_website_sales" model="crm.team" forcecreate="False">
|
|
<field name="use_opportunities" eval="False"/>
|
|
</record>
|
|
|
|
<record id="sales_team.pos_sales_team" model="crm.team" forcecreate="False">
|
|
<field name="use_opportunities" eval="False"/>
|
|
</record>
|
|
|
|
<record id="sales_team.ebay_sales_team" model="crm.team" forcecreate="False">
|
|
<field name="use_opportunities" eval="False"/>
|
|
</record>
|
|
</data></odoo>
|