$ 0 0 BTW - this was a bug in Exchange 2010 SP2 RU6 and SP3. The fix is here:http://support.microsoft.com/kb/2833888