First an apology:I am aware that there are already several other threads on this subject - I apologise for not using one of those but I thought it best to start afresh.A bit of background: We have Exchange 2007 installed on our single domain; single forest. The domain was created from scratch and Exchange 2007 was a clean install. User accounts were re-created and mailboxes transferred from our old domain, with Exchange 2003, using ExMerge. We have a disproportionally high number or shared mailboxes within the organisation. And now the problem:There seems to be an issue with granting the Send-As permission to some shared mailboxes.It was my understanding that in Exchange 2007 granting a user Full Access to a shared mailbox implicitly granted that user the Send-As right. Indeed I have a number of users that are able to successfully Send-As in this manner and the only rights they've been granted is Full Access.That said if I grant Full Access to the shared mailbox to a different user they appear to be able to perform all tasks other than Send-As. To my mind this would indicate that the Full Access permissions have taken affect.Initially granting rights was performed using the command shell, it has been tried through the GUI updates in SP1 and I have tried since using the command shell just in case it was a GUI issue.In a futile attempt I also tried explicitly defining the Send-As right but this had no affect. I've since removed this.How you can help: Have you come across the same problem? Were you able to fix it? Are there any diagnostics I can perform for more information? Are there any event/process traps I might be able to monitor? Give me millions of pounds (or dollars; I'm not fussy!) so I can quit my job and not have to worry about this any more...

Send-As and Full Mailbox Access are different permissions. Full mailbox access does not give the granted account to Send-As the mailbox. how is mail sent, outlook/MAPI or with SMTP

That'll be why it isn't working then! I would have sworn that I'd read that Full Access gave Send-As rights... I feel quite silly now. PS: Email is sent from the Outlook client via MAPI.

Hmm... Just tried adding Send-As rights for a user but it doesn't seem to be working. Would there be some replication delay? Thanks again,

NowI feel like a real idiot! I'd assumed that there was a problem because some were working and others were not. It seems that the users that were working were actually sending 'on behalf of' rather than 'send-as'. I hadn't even questioned my belief in the implicit Send-As granted with Full Access because some accounts 'worked' and they had Full Access but no Send-As.

I ran it to the same issue. This thread helped me to understand what's going on.Hope this helps.

i got this same issue...... dam irritating.. ihave set everithing as instructed!!! previously i done one of the user is working fine... now all is not working@!!!HL Tan

In my case, the OUTLOOK clients were all remote clients using http/rpc. The solution for me was to recreate the users' OUTLOOK profile. The issue was not on the server. I don't understand why, but it worked perfectly in a new outlook profile. Also, I am certain that FULL ACCESS includes SEND AS. I am experimenting with deleting the OST file, to see if that will solve it with less pain. Will let you know.

I closed OUTLOOK, renamed the users' OST file to xxx-OLD and restarted OUTLOOK. problem solved....

Hi, Apart from replication delay causing perceived issues after configuring Send-As, local nickname cache can also cause the issue as permissions appear to be sync'd down with the nickname. So, if you update permissions later you need to clear the nickname (or entire cache) and then try it again after selecting the user from the GAL. Disclaimer: The opinions expressed and/or postings on this site are my own personal opinions. They do not represent or reflect the opinions of my employer.

I had this exact same problem with an SBS2008 platform running Exchange 2007 and Outlook 2007 After reading this post I managed to fix this by adjusting the settings within AD. It appears that even though you apply full access and send as permissions the only thing added within AD permissions is send as: To Fix 1. Open AD 2. Turn on Advanced Features - View/Advanced Features 3. Right click the account you are trying to apply send as permissions to 4. Select security tab 5. Next you will a dialog box as if you were adding permissions to a file/folder 6. If you have completed the send as permissions within exchange you will see the user you wish to have send as permissions will be listed in the user section 7. Select the user 8. Apply Permissions to suit Below is a screenshot in my test environment I have applied full control, but please ensure you follow security procedures Hope this helps Regards, Dan

In my experience, Outlook caches an AD permission in the .OST. The delay in Send As taking effect only seems to apply to cached mode. Go to online mode, Send As works. Go back to offline mode (same OST), Send As does not work. Go create a new outlook profile (new OST), Send As works. Go back to old profile in offline mode (same OST), Send As does not work. If you set Full Access mode for a user, it works right away because that is an Exchange permission. If you set Send As, it caches somewhere in .OST because that is an AD permission? I've seen a lot of conflicting information on this topic straight from the keyboards of microsoft engineers, the above is though my own experimentation.

Just remove Outlook from Cache mode and remove send as permission in AD properties of the user, if any.