Quantcast
Channel: Exchange Server 2010 forum
Viewing all articles
Browse latest Browse all 19214

User w/ Outlook 2007 Gets "...cannot send on behalf of user..." bounces when sending from his own account

$
0
0
Appears similar to this unanswered question: social.technet.microsoft.com/Forums/en-US/outlook/thread/9a26e337-817f-4a9b-a776-db8d0144dd78/ (link not allowed as my account is new)

Client is Outlook 2007 on Win 7 Pro x64, Server is Exchange 2010 Enterprise w/ SP2 RU3 

Due to a merger, we are migrating to a new Exchange 2010 org in a new forest from two old orgs in two old forests. One was Exchange 2003, the other was Exchange 2007. The migration has been for the most part trouble-free. The user affected by this issue has been migrated for nearly two weeks and had no problems until today.

User sends from his own account to ANY internal recipient and gets the following bounce message:

You can't send a message on behalf of this user unless you have permission to do so. Please make sure you're sending on behalf of the correct sender, or request the necessary permission. If the problem continues, please contact your helpdesk. Diagnostic information for administrators: Generating server: /O=MYCOMPANY/OU=EXCHANGE ADMINISTRATIVE GROUP (XXXXXXXXXXXXXXX)/CN=RECIPIENTS/CN=some_recipient#MSEXCH:MSExchangeIS:/DC=corp/DC=mycompany:EXCHANGE_SERVER[578:0x000004DC:0x0000001D]#EX

I had the user send from OWA, which he was able to do without issue. We had seen another user with a similar issue immediately after they were migrated, and downloading the OAB resolved. We removed all .oab and related files and re-downloaded, to no avail. Deleted .ost and restarted Oulook, to no avail. Finally, we created a new Outlook profile, which seems to have resolved the problem.

Despite knowing we can resolve the problem, I'm uncomfortable not having any real insight into the cause, and because it cropped up quite awhile after the user was successfully migrated, I'm concerned it could crop up randomly for other users. I'd love some help in ID'ing the root cause so that I can ensure it doesn't happen to our CEO during a board meeting as Murphy's Law would dictate. :) I'll be checking event logs for the client and server. A quick initial look didn't show anything that stood out.

Thanks!
J

Viewing all articles
Browse latest Browse all 19214

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>