Re: Exchange 6.5 build 7638.2 (NOT send on behalf)



Configure "Send As" rights rather than "Send on Behalf" Go to
properties of your ableandable MB. Go to the security tab. Add your
users and give them the "Send As" rights. If you do not see the
security tab, go to view and click advanced settings in your AD
console. Try this first and see if your second issue goes away .

James Chong
MCSE M+, S+, MCTS, Security+
msexchangetips.blogspot.com

microsoft wrote:
Exchange gurus,



I am running Exchange 6.5 build 7638.2 on windows server 2003 service pack
1. We are using a very basic smtp setup with a domain.



Here's where things are not basic; We have a lawgroup and they want everyone
to be able to send email as the same user. we will call him
ableandable@xxxxxxxx Well seemed easy enough. We gave domainusers full
mailbox rights and send on behalf rights to the user ableandable. We then
added this mailbox to everyone's outlook. If they want to send an email as
themselves they just send an email. If they want to send an email as
ableandable@xxxxxxx they just click on the from box and select ableandable.



This works great however there are two problems.



1. When sending an email as ableandable@xxxxxxx and not as themselves, the
email when read by the recipient says in the from line "From John Doe
[johndoe@xxxxxxx] on Behalf of ableandable [ableandable@xxxxxxx].



We do not want it to appear this way. We want it to appear as the email
actually came from ableandable@xxxxxxx not on behalf of.



2. When sending an email as ableandable@xxxxxxx and not as themselves
sometimes the email will not go through to certain recipients outside of the
domain. It returns with an error "message did not reach all of the intended
recipients because I do not have permission to send to this recipient" But
if they try to send the same email to the say recipient as themselves it
goes through!



We know we could make ableandable the default email for everyone and make
their individual email "send on behalf" as a temp fix but his is not the
answer.



Any ideas?

.



Relevant Pages

  • Re: Want to stop sharing Outlook Today folders
    ... I can see two places that affect security of a user's personal information, ... the security tab as you suggested and the Exchange Advanced | Mailbox Rights. ... I am assuming that these two areas affect only rights that others have to ... Wouldn't adjusting the permissions in the MailBox Rights be enough to keep ...
    (microsoft.public.exchange.clients)
  • Re: user security tab
    ... * This posting is provided "AS IS" with no warranties and confers no rights! ... some users are not getting security from the parent because the box isn't ... from parent is set on the advanced tab of the security tab? ...
    (microsoft.public.win2000.active_directory)
  • Account Operator Security Rights
    ... lists which are created as ActiveDirectory Security Groups with Exchange ... I added the user who would be making the changes to the "Account Operators" ... Next, I added the individual user to the Security tab of the list, and gave ... I'm curious why the rights didn't flow through the Account Operators group ...
    (microsoft.public.windows.server.active_directory)
  • Re: Audit delegation of rights
    ... Click Start, point to Administrative tools, and click Active Directory ... Place a check beside Advanced Features. ... >I don't have a security tab in the properties of users or groups in the ... >> has been delegated and the rights assignment will also be visible. ...
    (microsoft.public.windows.server.active_directory)
  • Re: Delegate control questions
    ... You can rerun the delegation wizard again or do it manually in security tab. ... You can deny read access, that's one of the reasons for OU creation, but rather then denying to a user you should do this to a security group, same applies to delegation of control. ... Have delegated control to the local admin, so he can create users and groups, reset passwords, add computers to domain. ... Where and how can I see what rights I have delegated to him? ...
    (microsoft.public.windows.server.active_directory)