I have a relatively new installation of Exchange 2013 and I have two clients that receive the pictured error 2-3 times per week. MSFT TechNet published this: "The issue does not occur in Exchange 2013." I beg to differ.
Both clients are using Outlook 2010. Does anyone else see this issue? Any solution to offer?
