I have Outlook 2013 connecting to Exchange 2013 in Online Mode and not cached mode. Using ECP, I have a user full access rights and send as rights to a shared mailbox. The user can see,delete, and read emails in the shared mailbox. When the user tries to send mail as the shared mailbox, the email is getting stuck in the user's outbox folder and never sends. Not even after manually clicking on send and receive. I also do not have the registry key DelegateSentItemsStyle
Any idea how I can fix this?
We have exactly the same problem here and I could be more specific for my case:
Exchange 2013 with CU1 installed.
1) with the SendAs function, the message is stuck in the outbox folder
2) with the SendOnBehalf function, the message is delivered but contains an incorrect smtp address; in fact the field is replaced by content of the attribute "legacyDN" from the AD (CN=xxxxxxx,OU=xxxxxxx,xxxxxxx)
On both case this problem is affecting Outlook 2010 and Outlook 2013 as sending client and not OWA client
On both case we see that activating the cache mode for Outlook is a workaround on this problem; but it creates other problems like allocating GB of storage for .OST files (in particular if an user add other's people accounts in the client).
On both case we see that purging the auto-complete (in Outlook or with MFCMAPI) cache does not fix the problem.
We have to deploy Exchange 2013 the next week-end for 120 users. We are researching an other and much better workaround. We will at least deploy a GPO to configure cache mode properties if this is the only workaround.
I would be very happy to have a fix for this rapidely. We have now open a SR (113040410339300) by Microsoft but without any success at current time.
- Proposed as answer by Valery Tyurin Saturday, October 05, 2013 6:16 PM
Answer from microsoft support :
I have tested the issue at my lab environment and I have the same issue with yours. There is a bug on this issue based on my research on our internal data. Please wait for some time and it will be fixed later. Thanks for your patience and time.
After asking when this will be fixed :
I have submitted the feedback about this issue to Microsoft Exchange 2013 product Team and if I get any reply from them, I will update it to this post. Thanks for your understandings and time.
For information, in the case of "SendOfBehalf" message, we get always 3 error messages in the application event log in sequence:
1) Event ID 4007 Rules
Transport engine failed to evaluate condition or apply action. Details: 'Organization: '' Message ID '<bf7dca790f774a76b14d96e697af239c@EXCHMB.dsa.dom>' Rule ID '361cd6ea-84a8-42f9-a201-3e4906295fe3' Predicate 'senderAttributeContains' Action ''. ArgumentOutOfRangeException Error: System.ArgumentOutOfRangeException: The address '/o=Devi/ou=Exchange Administrative Group /cn=Recipients/cn=ec91c813c8a34033bf384bb2174d33c0-yankee1' is not a valid SMTP address.
at Microsoft.Exchange.MessagingPolicies.Rules.TransportUtils.UserAttributeContainsWords(TransportRulesEvaluationContext context, String user, String attributeList, String tagName)
at System.Linq.Enumerable.Any[TSource](IEnumerable`1 source, Func`2 predicate)
at Microsoft.Exchange.MessagingPolicies.Rules.AndCondition.Evaluate ...
This would say that the smtp address is already fitted wrong with the legacyDN by the Outlook client (when entry was taken from the GAL ?)
2) Event ID 10003 Poison Message
3) Event ID 4999 General
For the "SendAs" case, no event log in Exchange as the message is stuck already in the Outlook client.
If this is a known issue, i don't think that i have to open a case. If Microsoft offers this product with a online mode, they have to support without a case to send a fix. It's not a isolate case, and affects everyone that buy the exchange. The option of online mode is offers in this product, if dont work with online mode, don't sell with this option or just solve this problem and and release the fix to all.
We still does not have a better solution from Microsoft for this issue. So we added:
- a 300GB HDU (no Raid) to store the cache of the users in off-line mode (.ost files)
- we have designed a group of users that absolutely need for now the SendonBehalf and SendAs features
- for this group we have pushed by GPO the "force cached mode", the location of .OST and the fact that additional mailboxes loaded in Outlook are NOT cached (to limit the cache). This works properly.
- we use terminal server, so we decided that users does not need to have more than 1 session opened but may use any of the TS available so we have set only 1 cached files location, independant of the user profile (otherwise you get error loading outlook if the cached .ost files are already opened by an other session)
- we started production for 120 users mailboxes 2 weeks ago, with 40 users with the cache active, and it seems to work so until better solution
We also regret that this bug, which has been reproduced by Microsoft according to the man in charge the service request we opened, is still not resolved. For a more important deployement it could be a major isssue.
Have the exact same issue, large number of users on Citrix that need to be able to send emails with different FROM addresses (more than one). My only little bit of success was adding all the FROM email addresses (departments) from the GAL to a users Contacts. I set the address book then to first check in the users contacts (by default it was the GAL). So I create a new email, select FROM via the contacts I just added and it works. What doesn't work though is doing it again, using the dropdown menu/history next to the FROM button. If I select a FROM address via the drop down I get "you do not have the permission to send on behalf of this user". If I press the FROM button, go to the user's contacts, select a FROM email address and send the email it works, again and again. If I select it via the FROM dropdown it does not. Now, this along with the omission of the very usefull DelegatesSentItemsStyle (option to have outbound emails in the delagates Sent Items as well as the shared mailbox's) is giving me and my company headaches. The SentItemsStyle issue I have managed to emulate via transport and mailbox rules, this FROM issue though I can't. It was nice finding this post though as I was going crazy, trying a lot of weird and dangerous things.
OK guys, I think I have a pretty good workaround after "refining" my previous workaround. I selected all the contacts from the GAL that I would like to be able to send email as and added them to the user's contacts. I then opened the Address book's properties and removed the GAL from "check address lists in this order", after selecting Custom of course. This way I can fire up a new email, click FROM-Other email address and type in there any part of the FROM addresses I have in my contacts, press OK and then send. This way no GAL lookup is done (it seems). The only thing that doesn't work is using the history dropdown of the FROM button, this seems to have the same effect as selecting a contact from the GAL.
Hope this helps,
- Proposed as answer by Vectivus Monday, July 01, 2013 2:57 PM
We have a simular problem but are solution is :
don't create you outlook profile via outlook but create it via Start/configuration/e-mail. Add all e-mail account to the new created outlook-profile. (best is to delete the existing outlook-profile)
We don't now the difference between creating via outlook are creating vin start/configuratio.e-mail but all are hanging mailproblems are solved.
Hope this helps;
I have tried your method, but when I try to select the address from my contacts list i get " Cannot perform the requested operation. the coomand selected is not valid for this recipient"
I have also tried the method below (manual config) and then it just stays in the Outbox-
Really getting frustrating as we need to send as- but cannot load the terminal server with all these OST's in cached mode.
You would expect something a little more efficient considering the thousands of dollars spent on this.
I have been using this method for days now on several users, testing SEND AS before we go live, so at least in my environment it works as described 100%. I can see your error popping up around the internet so something else must be wrong in your environment. I would suggest you create a brand new user/mailbox and:
- Switch Outlook to online mode
- Go to the GAL, select the FROM contacts you would like to send as, right click and select add to contacts.
- Then go to Address book (in inbox), go to tools-options and under "when sending email, check these address lists first" select custom, remove the GAL and leave only the user's Outlook contacts in there. The last bit is important, as I observed a case where a user had two accounts in Outlook (an Exchange one and a POP3 one), with two Contact folders, both set to be used as an address book and my trick was not working. I had to remove everything but the Exchange mailbox Contacts and Suggested Contacts for it to work.
Again I would suggest you tried this with a "clean" user (mailbox, .nk2 cache file). Our goal is for Outlook to use the users contact whenever its trying to validate/lookup the FROM address/display name.
If it works with a brand new user, then you can begin troubleshooting why it doesn't work with an old one.
- Edited by Vectivus Thursday, July 04, 2013 10:46 AM addressed to wrong person (Peter instead of a0j).
Yes working ok now with CU2 installed :)
My version is Exchange 2013 RTM. It's delighted to hear that if CU2 can fix it.
My client encountered the problem only have shared mailbox and it happened randomly.
I tried re-created client outlook profile, add shared mailbox manually rather than auto-add by Exchange 2013.
Both of the two method are fail.
My workaround is uncheck cached mode and no mail stuck in outbook.
But the method would cause server loading heavy and unconvenience for roaming users.
Is it any risk to upgrade to CU2 ? What shall I pay attention?
Yes, it works now for plain online mode, but with DelegateSentItemsStyle it's still confusing:
The mail will be sent, but gets stuck in my outbox folder.
Indeed it's not satisfying that there is no working way to have the DelegateSentItemsStyle behavior on server side, the reg key just seems to be a dirty client hack.