S
Steve Chandler
Send on Behalf of behaving like Send As
Outlook as a client attached to an Exchange Server allows the ability for
users to send behaviorally like they were a different user in their
organization. There are 2 methods employed, Send on Behalf of and Send As.
Send on Behalf of allows a person to send an email choosing another user they
will send an email on behalf of and the email they send will have a sender
address of “User A on behalf of User B.†This behavior is something that can
be set client side – User B would add User A as a delegate in Tools / Options
/ Delegates in their Outlook client installation. This can easily be done by
end users as it is meant to be a visible sending stamp. The second scenario
is the ability to Send As someone. This right is set in Active Directory on
User B’s attributes, adding User A having a Send As permission. Send As
permissions override Send on behalf of permissions.
Problem:
When User B only has a delegate status enabled for User A, User A chooses
User B’s entry for sending from and the email behaves as if the Send As
permission is set even though clearly it is not set. Even editing User B to
explicitly Deny the Send As permission does not fix the problem.
Anyone ever seen this or have any idea what might be done to correct it?
Outlook as a client attached to an Exchange Server allows the ability for
users to send behaviorally like they were a different user in their
organization. There are 2 methods employed, Send on Behalf of and Send As.
Send on Behalf of allows a person to send an email choosing another user they
will send an email on behalf of and the email they send will have a sender
address of “User A on behalf of User B.†This behavior is something that can
be set client side – User B would add User A as a delegate in Tools / Options
/ Delegates in their Outlook client installation. This can easily be done by
end users as it is meant to be a visible sending stamp. The second scenario
is the ability to Send As someone. This right is set in Active Directory on
User B’s attributes, adding User A having a Send As permission. Send As
permissions override Send on behalf of permissions.
Problem:
When User B only has a delegate status enabled for User A, User A chooses
User B’s entry for sending from and the email behaves as if the Send As
permission is set even though clearly it is not set. Even editing User B to
explicitly Deny the Send As permission does not fix the problem.
Anyone ever seen this or have any idea what might be done to correct it?