We help IT Professionals succeed at work.

Setting up an Email Alias

Medium Priority
Last Modified: 2013-12-17
I just need general information on how to setup an Alias. I assume the process is simular accross all clients and providers?
Could someone just give me an example?
I need to setup get an employee to setup another email address from his provider, and go in and change it so that the address displayed to everyone is user@mydomain instead of what the actual  provider address is, and then setup forwarding on his actual @mydomain email and have it forwared to his provider's email.

Watch Question

What you should do is create a mail enabled user on the local domain (not a mailbox).  Configure the user account to have the external address of the user, but also a local domain address set as the primary (in bold with capital SMTP).  Thus the Email Addresses tab would look like this:

smtp    user@providersdomain
SMTP:   user@mydomain

Here's the trick, go to the Exchange General tab and click the Modify button and set the target address user@providersdomain.  Now you should see "E-mail     SMTP: user@providersdomain" from this tab.  As a result you'll have this person in your local address book, but the messages will be redirected to the external mailbox.  Furthermore email sent to the local domain address from the Internet will be accepted by your Exchange server since it has a local address, but Exchange will then relay the message to the Internet using the target address.  It will also retain the original header TO: user@mydomain.  It gets trickier if you want the user to be able to "Send As" his user@mydomain account, but it can also be done.
1. Create contact in Active directory  with his ISP email address. Test it can receive mail from your site.
2. Forward mail from his account out to that contact. You do this on the "Exchange General" tab in Active Directory. Click on the "Delivery Options" button and choose the contact you created in step 1 to forward the mail to.
3. In active directory, under "Exchange Advanced" tab, select "Hide from Address book" for the contact from step 1. This prevents users from sending directly to the contact. Optional, but I always do that to keep the users home/personal email address private.



Thank you both
A much better solution than my original plan.
Question for millema: how do you create a mail enabled user if you're not creating a mailbox for them, I assume by default the user will be mail enabled even if you choose not to create an exchange mailbox? Or is there something else that must be done during of after account creation?
With your method it's strictly a redirection as there would be no mailbox for the @companydomain.com address.

With drothbart I can take his exsisting exchange mailbox and just forward the mail to the external address, which would be linked to a newly created user account.

Both accomplish the same result. I will have to split the points later after I try both of these methods.

Thank you


What will happen with incoming email, will it also get forwarded to the contact?
The problem is our employee is working from home, and cannot connect to our vpn. So he will be assesing his external account to do everything. Will your method allow him to send and recieve from what appears to me user@mydomain.com?
Will he receive incoming messages to user@mydomain.com at his external address?


He cannot access his domain account. So he will be replying to his messages and sending messages from his external address. So he will need to send as @workdomain.com

Mail enabled means their is an email address for the object, in this case it's the external address of the user although it could be an internal address.  Mail enabled objects are non-mailbox recipients such as a Public Folder or an application server.  Mailbox enabled means that it has a mailbox on the Exchange server database in your local Exchange organization.  drothbart's suggestion will also work if you have an existing mailbox for the user that you want to keep.  Creating a mail enabled contact as the alternate delivery location while hiding the mailbox will result in the user having a recipient in the address book that shows with a globe next to it which is nice since it indicates the recipient is external to your organization.

Sending as your domain while the user is on his home Internet connection gets complicated.  Most ISPs will block address spoofing to prevent spam, mass mailing worms, and other malware.  Personally I would configure Outlook Web Access for the user.  If this is not acceptable then you may need to consider more complex scenarios such as a Front-End Exchange server that will allow the user to relay SMTP mail.  This creates BIG security implications so you'll want to do things such as require SSL, use TLS, and also use an alternate TCP port.  Furthermore since the user's ISP almost certainly will block outbound port 25 that bypasses its internal mail relays you'll need an alternate port for SMTP.

You'll also have to correctly configure the user's email client depending on whether it's exclusive business use or personal email will be involved (i.e. sending as the external address).


Hmmmm... I see, OWA is definitely the way to go then. It's either that or just have him use the providers "Send as" option, hopefully they will allow the changing of the displayed address so that when a recipient receives the mail, it shows @workdomain.com instead of
From: @providerdomain.com
Reply to: @workdomain.com
Would you be so kind as to pointing me to an OWA setup article for exchange 2000, is it hard?
Or Is it something you can walk me through quickly?
Thanks so much

These are good articles (you'll need to register first)


This is a good security article.  It specifically addresses Exchange 2003 but most of it should apply to 2000.


Methodman85 - my suggestion is one-way only (ethically). The user would receive only, to send would require spoofing their sending address. OWA is a great tool to use for outside connection to your Exchange server if the user has an active directory account.

I use the method I listed if a user is out of the office for an extended period and wants their mail forwarded home for information only, and doesn't want to connect into the system at all. We also use it to hide a users home address if they don't have an AD account.

Research OWA, that is definitely more in line with your needs.


Is it me, or is there something wrong with the first article?
The Configuring and Using OWA in Exchange 2000 Server section contains 2 repeating paragraphs that say nothing about configuration. And then the article jumps to OWA: What's It All About?
Do you know of any other articles that would cover the basic configuration.
Thank you for your time.


Thank you for all of your help.

Explore More ContentExplore courses, solutions, and other research materials related to this topic.