An email alias is simply a forwarding email 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 email alias as an address that is forwarded in a simplistic fashion.
Email aliases can be created on a Mail server. Each email alias simply forwards email messages on to each specified email address. Email aliases are often used to create handy replacements for long or difficult-to-remember email addresses. They can also be used to create generic email addresses such as email@example.com and firstname.lastname@example.org.
On UNIX-like systems, email aliases may be placed into the file /etc/aliases and have the form:
local-alias-name: adifferentlocaluser, anotherlocaluser, email@example.com
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. However, if VERP or BATV are being used (e.g. to prevent email backscatter), the electronic mailing list software will send individual messages to each recipient with a different SMTP FROM address.
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.