Re: Exchange 2003 full mailbox permissions

From: Will (info_at_whawes.co.uk)
Date: 03/14/04 

Date: 14 Mar 2004 07:43:34 -0800

Hi James,

Thanks for your reply. See my original post:

"Using KB article 821897 "How to Assign Service Account Access to All
Mailboxes in Exchange Server 2003" as a guide, I am trying to set up a
user account with full permissions on any mailbox in a particular
store.

Using Method 3 described in the article I used Exchange System Manager
to give my user account every available permission (i.e. all except
"Special Permissions", which is greyed out) on the mailbox store
object in the Servers container. I then restarted the exchange
computer and the client machine I am using to log in.

I am now able to read from and write to any folder for any mailbox in
the store. However, I cannot send an email as another user, with
Outlook returning the error "You do not have permission to send on
behalf of the specified user" whenever I try to use another name in
the From field of an email message. My understanding of the article is
that having assigned my user account "Send As" and "Receive As"
permissions for the entire store as part of the above procedure, this
should not be the case. I have checked the ACLs for all relevant
objects and there do not appear to be any inherited or explicit
denials in operation.

My user account is a member of "Domain Users" only.

It would be a bit inconvenient to have to expicitly assign these
permissions for each individual user. Can anyone clarify what
additional steps I need to take."

Regards

Will

"James Burrage [MSFT]" <jburrage@online.microsoft.com> wrote in message news:<#RP9j4GCEHA.1028@TK2MSFTNGP11.phx.gbl>...
> Hi Will,
>
> Could you give a little more information. What exactly is happening with the
> Full Mailbox Permissions?
>
> --
> Thanks,
> James Burrage
>
> This posting is provided "AS IS" with no warranties, and confers no rights.
> Please do not send email to this address, post a reply to this newsgroup.
>
> Use of included script samples are subject to the terms specified at
> http://www.microsoft.com/info/cpyright.htm
>
> "Will" <info@whawes.co.uk> wrote in message
> news:ff3a4031.0403120731.24194694@posting.google.com...
> > Does anyone have a solution to this? I find it hard to believe that
> > no-one has run into the same problem.
> >
> > Regards
> >
> > Will

Relevant Pages

  • RE: Mail delivered to the wrong addresses
    ... > wasn't Exchange, rather Outlook. ... We had people delegating permissions ... and when these people left the company and the account was ... > mailbox because the Exec set her up to have some permissions to his box. ...
    (microsoft.public.exchange.admin)
  • Re: No Permission to Use My Own Account to send Emails
    ... My own account is A. I added another account B into Outlook. ... > If you grant a user "Send As" permissions for another user's ... > mailbox, the can send mail as the ... > This posting is provided "AS IS" with no warranties, and confers no rights. ...
    (microsoft.public.exchange2000.general)
  • Re: Accessing an email account programmatically
    ... The only reason I thought of POP was that I ... > should be able to log into the mailbox using whatever protocol you like. ... > account on the Inbox. ... > the user account used for programmatic access is compromised the mailbox ...
    (microsoft.public.exchange.applications)
  • Re: Accessing an email account programmatically
    ... The only reason I thought of POP was that I ... > should be able to log into the mailbox using whatever protocol you like. ... > account on the Inbox. ... > the user account used for programmatic access is compromised the mailbox ...
    (microsoft.public.exchange.admin)
  • 2003 Minimum rights to create an id and restrict access to Mailbox Rights
    ... My testing was done using a test account within a single OU. ... permissions page of that OU. ... emailed each mailbox to cause the mailbox permissions to become ... When I clicked on the main user object properties OK ...
    (microsoft.public.exchange.admin)