Navigation: Schema: mail > Tables

alias

Email Aliases

Catalog: Odoo

Schema: mail

Documentation:

A Mail Alias is a mapping of an email address with a given Odoo Document

model. It is used by Odoo's mail gateway when processing incoming emails

sent to the system. If the recipient address (To) of the message matches

a Mail Alias, the message will be either processed following the rules

of that alias. If the message is a reply it will be attached to the

existing discussion on the corresponding record, otherwise a new

record of the corresponding model will be created.

This is meant to be used in combination with a catch-all email configuration

on the company's mail server, so that as soon as a new mail.alias is

created, it becomes immediately usable and Odoo will accept email for it.

The data in this table is partitioned per value of the column.

This is a read-only table. The Odoo API may not support changing the data or the Invantive SQL driver for Odoo does not cover it. In the latter case, please use the table NativePlatformScalarRequests to upload data to the Odoo API.

Table Columns

The columns of the table alias are shown below. Each column has an SQL data type.

Name	Data Type	Label	Required	Documentation
alias_bounced_content	string	Custom Bounced Message	☐	If set, this content will automatically be sent out to unauthorized users instead of the default message.
alias_contact	string	Alias Contact Security	☑	Policy to post a message on the document using the mailgateway.- everyone: everyone can post- partners: only authenticated partners- followers: only followers of the related document or members of following channels
alias_defaults	string	Default Values	☑	A Python dictionary that will be evaluated to provide default values when creating new records for this alias.
alias_domain	string	Alias domain	☐
alias_force_thread_id	int32	Record Thread ID	☐	Optional ID of a thread (record) to which all incoming messages will be attached, even if they did not reply to it. If set, this will disable the creation of new records completely.
alias_model_id_label	string		☐	The model (Odoo Document Kind) to which this alias corresponds. Any incoming email that does not reply to an existing record will cause the creation of a new record of this model (e.g. a Project Task)
alias_model_id	string		☐	The model (Odoo Document Kind) to which this alias corresponds. Any incoming email that does not reply to an existing record will cause the creation of a new record of this model (e.g. a Project Task)
alias_name	string	Alias Name	☐	The name of the email alias, e.g. 'jobs' if you want to catch emails for <jobs@example.odoo.com>
alias_parent_model_id_label	string		☐	Parent model holding the alias. The model holding the alias reference is not necessarily the model given by alias_model_id (example: project (parent_model) and task (model))
alias_parent_model_id	string		☐	Parent model holding the alias. The model holding the alias reference is not necessarily the model given by alias_model_id (example: project (parent_model) and task (model))
alias_parent_thread_id	int32	Parent Record Thread ID	☐	ID of the parent record holding the alias (example: project holding the task creation alias)
alias_status	string	Alias Status	☐	Alias status assessed on the last message received.
alias_user_id_label	string		☐	The owner of records created upon receiving emails on this alias. If this field is not set the system will attempt to find the right owner based on the sender (From) address, or will use the Administrator account if no system user is found for that address.
alias_user_id	string		☐	The owner of records created upon receiving emails on this alias. If this field is not set the system will attempt to find the right owner based on the sender (From) address, or will use the Administrator account if no system user is found for that address.
create_date	datetime	Created on	☐
create_uid_label	string		☐
create_uid	string		☐
display_name	string	Display Name	☐
id	int32	ID	☐
write_date	datetime	Last Updated on	☐
write_uid_label	string		☐
write_uid	string		☐

01-03-2023 15:29 Version 22.1.135-BETA+3826

Important Safety and Usage Information

Intended Use and Limitations: This software, developed by Invantive, is designed to support a variety of business and information technology data processing functions, such as accounting, financial reporting an sales reporting. It is important to note that this software is not designed, tested, or approved for use in environments where malfunction or failure could lead to life-threatening situations or severe physical or environmental damage. This includes, but is not limited to:

Nuclear facilities: The software should not be used for operations or functions related to the control, maintenance, or operation of nuclear facilities.
Defense and Military Applications: This software is not suitable for use in defense-related applications, including but not limited to weaponry control, military strategy planning, or any other aspects of national defense.
Aviation: The software is not intended for use in the operation, navigation, or communication systems of any aircraft or air traffic control environments.
Healthcare and Medicine Production: This software should not be utilized for medical device operation, patient data analysis for critical health decisions, pharmaceutical production, or medical research where its failure or malfunction could impact patient health.
Chemical and Hazardous Material Handling: This software is not intended for the management, control, or operational aspects of chemical plants or hazardous material handling facilities. Any malfunction in software used in these settings could result in dangerous chemical spills, explosions, or environmental disasters.
Transportation and Traffic Control Systems: The software should not be used for the control, operation, or management of transportation systems, including railway signal controls, subway systems, or traffic light management. Malfunctions in such critical systems could lead to severe accidents and endanger public safety.
Energy Grid and Utility Control Systems: This software is not designed for the control or operation of energy grid systems, including electrical substations, renewable energy control systems, or water utility control systems. The failure of software in these areas could lead to significant power outages, water supply disruptions, or other public utility failures, potentially endangering communities and causing extensive damage.
Other High-Risk Environments: Any other critical infrastructure and environments where a failure of the software could result in significant harm to individuals or the environment.

User Responsibility: Users must ensure that they understand the intended use of the software and refrain from deploying it in any setting that falls outside of its designed purpose. It is the responsibility of the user to assess the suitability of the software for their intended application, especially in any scenarios that might pose a risk to life, health, or the environment.

Disclaimer of Liability: Invantive disclaims any responsibility for damage, injury, or legal consequences resulting from the use or misuse of this software in prohibited or unintended applications.

Please enable JavaScript to view this site.

Odoo API Data Model

alias

Table Columns

Important Safety and Usage Information