I have received a request from the owner of our company who owns multiple companies asking the ability to send and reply to messages specific to one of his secondary companies using that companies domain name due to governmental regulations etc.
Currently he has one primary email account which all of his company emails from the various companies go to one exchange server. So if some wants to send him an email email@example.com, firstname.lastname@example.org, email@example.com etc... all the emails go to firstname.lastname@example.org and he replies back to all of the messages from email@example.com, but now when he receives or sends an email from firstname.lastname@example.org he needs to use email@example.com.
The owner of the company does not want to constantly be opening and closing outlook throughout the day, but want to manage his emails from the large number of companies he owns from one Outlook session.
Originally I thought I would be forced to take out firstname.lastname@example.org out of his email allias and establish a separate account for email@example.com and give delegate rights to his primary account firstname.lastname@example.org, but I can't seem to get this to work although I went through the following kb article on Microsoft's website http://support.microsoft.com/kb/291626
but when the primary email email@example.com sends a message on behalf of firstname.lastname@example.org I get an undeliverable message immediately saying the following Delivery has failed to these recipients or distribution lists:
You are not allowed to send this message because you are trying to send on behalf of another sender without permission to do so. Please verify that you are sending on behalf of the correct sender, or ask your system administrator to help you get the required permission.
Does anyone have any suggestions on how to approach this issue in which I am not thinking of right now, or knows why even when I go through the exact procedure listed by Microsoft "MANY TIMES NOW USING MANY ACCOUNTS" that it fails. Could the issue on sending on behalf be a setting that is on the exchange server its self?