# Per-user alias address

[TOC]

!!! attention

    * This document is applicable to iRedMail-0.9.7 and later releases.
    * Here's [doc for iRedMail-0.9.6 and earlier releases](./user.alias.address-20170701.html).

Since iRedMail-0.9.3, we have per-user alias address support, that means mail
user `john.smith@domain.com` can have additional email addresses like
`john@domain.com`, `js@domain.com` and more, all emails sent to these addresses
will be delivered to same mailbox (`john.smith@domain.com`). With per-user
alias address support, you don't need to create separated mail alias accounts
anymore.

## Manage per-user alias addresses with iRedAdmin-Pro

You can manage per-user alias addresses with iRedAdmin-Pro in user profile
page, under tab "Aliases".

![](./images/iredadmin/user_profile_aliases.png){:width="1024px"}

## SQL backend: Manage per-user alias addresses with SQL command line

Add additional email addresses `sales@domain.com`, `bill@domain.com` for
__existing__ user `john@domain.com`:

```
sql> USE vmail;

sql> INSERT INTO forwardings (address, forwarding,
                              domain, dest_domain,
                              is_alias, active)
                      VALUES ('sales@domain.com', 'john@domain.com',
                              'domain.com', 'domain.com',
                              1, 1);

sql> INSERT INTO forwardings (address, forwarding,
                              domain, dest_domain,
                              is_alias, active)
                      VALUES ('bill@domain.com', 'john@domain.com',
                              'domain.com', 'domain.com',
                              1, 1);
```

* Account `sales@domain.com` and `bill@domain.com` are NOT existing mail user
  accounts.
* In above sample, `bill@domain.com` could be an email address which belongs
  to your alias domain.
* You can add as many additional email addresses as you want.

## LDAP backend: Manage per-user alias addresses

For LDAP backend, per-user alias addresses are stored in LDAP attribute
`shadowAddress` of user object, and attribute/value pair
`enabledService=shadowaddress` is required. For example:

```
dn: mail=john@domain.com,ou=Users,domainName=domain.com,o=domains,dc=xxx,dc=xxx
enabledService: shadowaddress
shadowAddress: sales@domain.com
shadowAddress: bill@domain.com
...
```