E-mail alias

An e-mail alias is simply a forwarding e-mail address. The term "alias expansion" is sometimes used to indicate a specific mode of email forwarding, thereby implying a more generic meaning of the term "e-mail alias" as an address that is forwarded in a simplistic fashion [RFC 5321 defines "alias" expansion as opposed to the "list" expansion of mailing lists, noting that the replacement of the address to whom bounce messages are returned makes a key difference.] .

Usage

Email aliases can be created on a Mail server. Each e-mail alias simply forwards e-mail messages on to each specified e-mail address. E-Mail aliases are often used to create handy replacements for long or difficult-to-remember e-mail addresses. They can also be used to create generic e-mail addresses such as [e-mail] and [e-mail].

On UNIX-like systems, email aliases may be placed into the file /etc/aliases and have the form:

local-alias-name: adifferentlocaluser, anotherlocaluser, [e-mail]

Control Issue

Messages forwarded through an email alias retain the original SMTP envelope sender and recipient. If the message is a blind carbon copy, the recipient can only tell whether the message was forwarded through the alias by examining the message headers. However, the standard does not mandate mentioning the envelope recipient in the headers. Therefore, recipients of a message may not be able to recover what email address has been used by the sender to eventually deliver the message to their mailbox.

Recipients who cannot trace what address the sender used, are unable to ask the sender to stop sending, because the sender most likely will not be able to associate their current email address with the one used for sending. Even if users are able to learn the exact address used for sending, their mail client may not provide a convenient way to submit a reply using the latter as the sender address of the response. In other words, aliasing is not reversible. This is particularly relevant in opt-out situations where the sender does not provide a reliable mechanism "in the body" of the message. Typically, newsletters sent to "undisclosed recipients" can be sent submitting the body "once" along with a list of recipients, which is much less resource intensive than submitting a different body for each recipient.

Abuse Issue

The recipient's SMTP server sees only the forwarding system's IP address. In general it has no reason to trust the Received: headerfield generated by the forwarding system and does not know the originating system's IP address. Therefore, recipients cannot reliably distinguish spam "to the alias address" from spam "generated on the forwarding system". When a recipient reports a message to his ISP as spam, the ISP credits that spam to the forwarding system. ISPs with low abuse thresholds may begin blocking email from the forwarding system.

ee also

*Email forwarding

Notes