Email Alias
A basic routing mechanism in email systems whereby multiple recipient addresses are registered under a single underlying mailbox account and the mail server delivers messages to the same inbox according to the recipient address; aliases create no new storage space or separate credentials.
Timeline (last 90 days)
Email aliases are multiple recipient addresses registered under the same underlying mailbox account; the mail server delivers messages to the same inbox based on the recipient address, and aliases do not create new storage space or separate credentials.
In self-hosted email systems, aliases are usually implemented through Postfix's virtual_alias_maps or Dovecot's alias configuration.
Under the email alias approach, all agents share the same underlying mailbox credentials, so security isolation exists in name only; once an agent has a vulnerability or needs to be outsourced to a third party, the shared inbox becomes a data-leak risk.
It is recommended that externally facing agents (such as customer service and sales) use separate inboxes or API dynamic creation, internally facing agents (such as reporting and alerting) use aliases or shared inboxes, and temporary, experimental agents use API on-demand creation.
All Facts (4)
Email aliases are multiple recipient addresses registered under the same underlying mailbox account; the mail server delivers messages to the same inbox based on the recipient address, and aliases do not create new storage space or separate credentials.
50%UnverifiedIn self-hosted email systems, aliases are usually implemented through Postfix's virtual_alias_maps or Dovecot's alias configuration.
50%UnverifiedUnder the email alias approach, all agents share the same underlying mailbox credentials, so security isolation exists in name only; once an agent has a vulnerability or needs to be outsourced to a third party, the shared inbox becomes a data-leak risk.
50%UnverifiedIt is recommended that externally facing agents (such as customer service and sales) use separate inboxes or API dynamic creation, internally facing agents (such as reporting and alerting) use aliases or shared inboxes, and temporary, experimental agents use API on-demand creation.
50%