Exchangepedia Blog is read by visitors from all 50 US States and 150 countries world-wide
This is one of the more frequently asked questions in different forums - how do I send as an alternate address?
You can use Exchange (2003/2007) Server's Recipient Pollicies (EmaiAddressPolicy in Exchange Server 2007), or the E-mail Addresses tab in AD Users & Computers, to add additional email addresses for recipients (e.g. mailbox-enabled or mail-enabled users, Distribution Groups, mail-enabled Public Folders, Contacts).
The email addresses are stored in recipients' proxyAddresses attribute in Active Directory. This allows recipients to receive inbound email on any email addresses in that attribute.
However, sending messages is a different story. For new messages, you can specify any of your email addresses (in the proxyAddresses attribute) - the address automatically gets resolved to your Display Name, and gets sent using the primary email address. This is the address displayed using (upper-case) SMTP: in the proxyAddresses attribute.
This behavior also manifests itself when replying to a message that was received on an address other than the primary email address.
There are workarounds to accomplish this, but they are as annoying as the problem itself.
1. Creating additional recipient(s):
- Create a new mailbox (you can also other recipient objects like Distribution Groups for this, but for this post I'll assume you're using a mailbox) for each address you want to use to send outgoing mail as.
- Ensure this address is set as the primary address of the new mailbox.
- Assign your primary account Send As permission on the new account(s)
- When sending a new message, or replying to a received message, manually populate the From: field in Outlook with the Display Name or SMTP address (or any other attribute that can resolve to the new account)
- Additionally, if using a mailbox-enabled account for this purpose, the additional mailbox can be opened by the user in Outlook, along with his/her primary mailbox.
- Alternatively, inbound mail can be redirected to the user's primary mailbox by modifying Delivery Options in the properties of new recipient(s) created for this purpose.
2. Using SMTP clients: SMTP clients like Outlook Express can be configured to send using the alternate email address. This is equally annoying - every time a message needs to be sent as an alternate address, you will need to fire up Outlook Express (or your SMTP client of choice) to send the message.
3. Using third-party tool - IvaSoft ChooseFrom: IvaSoft makes nifty utilities for Exchange/Outlook that allow you to accomplish tasks that Exchange/Outlook do not allow you to do natively. Their ChooseFrom utility can be used to choose from any address listed in the proxyAddresses attribute, without the pain of the workarounds mentioned above. It uses a transport event sink installed on Exchange server, and is licensed per server.
A separate version - ChooseFromOWA - enables this functionality from Outlook Web Access.
There's no solution to this issue in Exchange Server 2007/Outlook 2007 as well. IvaSoft has released ChooseFrom for Exchange Server 2007.
(As with most third-party software, install and test in a lab environment before you decide to install it on a production server.)
You can use Exchange (2003/2007) Server's Recipient Pollicies (EmaiAddressPolicy in Exchange Server 2007), or the E-mail Addresses tab in AD Users & Computers, to add additional email addresses for recipients (e.g. mailbox-enabled or mail-enabled users, Distribution Groups, mail-enabled Public Folders, Contacts).
The email addresses are stored in recipients' proxyAddresses attribute in Active Directory. This allows recipients to receive inbound email on any email addresses in that attribute.
However, sending messages is a different story. For new messages, you can specify any of your email addresses (in the proxyAddresses attribute) - the address automatically gets resolved to your Display Name, and gets sent using the primary email address. This is the address displayed using (upper-case) SMTP: in the proxyAddresses attribute.
This behavior also manifests itself when replying to a message that was received on an address other than the primary email address.
There are workarounds to accomplish this, but they are as annoying as the problem itself.
1. Creating additional recipient(s):
- Create a new mailbox (you can also other recipient objects like Distribution Groups for this, but for this post I'll assume you're using a mailbox) for each address you want to use to send outgoing mail as.
- Ensure this address is set as the primary address of the new mailbox.
- Assign your primary account Send As permission on the new account(s)
- When sending a new message, or replying to a received message, manually populate the From: field in Outlook with the Display Name or SMTP address (or any other attribute that can resolve to the new account)
- Additionally, if using a mailbox-enabled account for this purpose, the additional mailbox can be opened by the user in Outlook, along with his/her primary mailbox.
- Alternatively, inbound mail can be redirected to the user's primary mailbox by modifying Delivery Options in the properties of new recipient(s) created for this purpose.
2. Using SMTP clients: SMTP clients like Outlook Express can be configured to send using the alternate email address. This is equally annoying - every time a message needs to be sent as an alternate address, you will need to fire up Outlook Express (or your SMTP client of choice) to send the message.
3. Using third-party tool - IvaSoft ChooseFrom: IvaSoft makes nifty utilities for Exchange/Outlook that allow you to accomplish tasks that Exchange/Outlook do not allow you to do natively. Their ChooseFrom utility can be used to choose from any address listed in the proxyAddresses attribute, without the pain of the workarounds mentioned above. It uses a transport event sink installed on Exchange server, and is licensed per server.
A separate version - ChooseFromOWA - enables this functionality from Outlook Web Access.
There's no solution to this issue in Exchange Server 2007/Outlook 2007 as well. IvaSoft has released ChooseFrom for Exchange Server 2007.
(As with most third-party software, install and test in a lab environment before you decide to install it on a production server.)
Labels: Administration, Mailbox
7 Comments:
A possible 4th option is to have a distribution list that you specify in the "From" textbox and you previously have given rights to the user to send from that distribution list.
I use outlook as my RSS reader and all your Posts show up as 1/1/2007. No other blog does this, any reasons why?
Murray,
Just noticed that myself - deleting the feed in Outlook and adding it again resulted in all posts dated 12/31/2006!
- Checked the feed XML file which is produced automatically by Blogger - and that looks OK.
- Subscribed to the feed using Google Reader and My Yahoo - posts show up with the correct date.
Looks like it's an Outlook 2007 issue. Please let me know if you find this happening with other readers as well, or a way to fix this with Outlook.
Bharat
I've been looking into a related problem for a customer for some time now and am completely stumped... I've added the alternating e-mailadresses through extra accounts and have set the user rights accordingly (the send as). The strange thing is, when i test everything through rpc over https in outlook 2003, everything seems to be working fine, i'm sending mails back and forth and all is well. The problem arises when the customer logs in to his computer on their network and starts up Outlook 2007. When she tries te send a mail using send as she always imidiatly gets an NDR stating that she doesnt have the permissions to send mail to the recipients. Anyone that can point me in the right direction please?
Kind regards,
Phil
I have implemented an solutuion to this for myself that works for mail coming from any source (OWA, Outlook, SMTP). The from address is specified in the subject using a special format "{{From:Name <email_addr_here>}} Subject" or "{{From: email_address_here}} Sucject", and is then removed by the exchange server before sending out. If anyone is interested in purchasing, I am willing to modify to your exact situation, unlimited usage license for between $50-$100 depending on the features you need added.
Easy way to solve this, is to create a POP account for the secondary Email alias. Then go into Send/Receive settings and disable Receive new items on the POP account. Otherwise you will get crazy amounts of doubled emails. But now you will be able to select either account to send from, with no problem. This will only work from Outlook 2k3 or 2k7. No dice on OWA, for that you will have to use an aftermarket app.
We are looking for a solution to this issue as well. We need to be able to sen out email as the alias and can't create seperate email accounts or POP3 accounts. I would be interested in the solution you are using.
Post a Comment
Links to this post:
Create a Link
<< Home