The official blog for Windows Server Essentials and Small Business Server support and product group communications.
EPS Team Blogs
[Today's post comes to us courtesy of Damian Leibaschoff]
DISCLAIMER: There are many different ways to implement this solution, this is just one of them.
A very common request we get is people wanting to be able to send outbound Internet e-mails from Outlook using different addresses as the originating address. This is different than just using a delegation or Sending on Behalf, this is truly sending the e-mail with a different “From:” address. The solution presented here will focus in using Outlook and Exchange without the need to create new accounts in Outlook. It will not only allow a user to send using a different e-mail address, it will also allow a user or a group of users to send using the e-mail address of a mail enabled security group.
An example would be: You have a mail enabled security group or a distribution group with an address of firstname.lastname@example.org and you want to send your replies as coming from that address instead of your personal one. The same concept can be used for a single user that wants to be able to send using other addresses.
This first step is optional and it really depends on where you are in the implementation of this process. If you already have a mail enabled security group or distribution group with the desired e-mail address, then you can skip it. On the other hand if your user already has the address you want to use to send as (as a secondary e-mail address in Active Directory), we will need to remove it from the user itself, we cannot have two objects in active directory with the same e-mail address. We will need to add this e-mail address to another object that we will create shortly, so for now, we need to remove it. Remember, Exchange will always use your default e-mail address as the reply-to/from address, so we need to work around this limitation.
Wait a few minutes for the object to be stamped by the Exchange Recipient Update Service.
We will be working on the properties of the Security Group we just created, but before we continue, we need enabled the Advanced Features in AD Users and Computers.
Now we can open the properties of the Security Group we just created.
Now we need to set up the proper security. We will need to add the user or group accounts we will want to allow to send as using this Security Groups primary e-mail address. This is the key step that will allow us to use the e-mail address as our new From. Keep in mind that Domain Administrators and Account Operators will already be able to Send As this group and no changes are needed.
Picture showing the allow just on a per user basis scenario:
Picture showing the allow all group members to Send As:
At this point all the pieces should be in place. Mail should be flowing to the e-mail address in question and the only thing left is for the user to learn how to pick which account to use when sending outbound e-mail. Please note that this will not happen automatically, the user will have to take action for every e-mail they want to use a different address for.
Your message did not reach some or all of the intended recipients. Subject: Test Sent: 10/31/2007 2:27 PM The following recipient(s) could not be reached: email@example.com on 10/31/2007 2:27 PM You do not have permission to send to this recipient. For assistance, contact your system administrator. MSEXCH:MSExchangeIS:/DC=local/DC=MSFT:SERVER
Your message did not reach some or all of the intended recipients.
Sent: 10/31/2007 2:27 PM
The following recipient(s) could not be reached:
firstname.lastname@example.org on 10/31/2007 2:27 PM
You do not have permission to send to this recipient. For assistance, contact your system administrator.
The Official SBS Blog : How to Send E-mails with Exchange Using a Different “From” Address: http://blogs
I much prefer the method of using a "Dummy" POP3 account as demonstrated here: http://sbsurl.com/dummy
Het laatste Satelliet TV Nieuws [Archive]-Page 6....
You can also use Proxy Manager (http://www.dimastr.com/proxyman). It is implemented as an Outlook 2010/2013 addin, so everything is done on the client side - messages are sent over SMTP even though to an end
user it looks like Outlook sends them through Exchange.