Support case #739957 is open for this. I got one reply back that they needed to get the answer from development, but haven't heard past that yet.
Also, since opening the case and forum thread, I've discovered that this was also an issue in our previous version of DMRC (6.9). It was just not considered an error in Exchange till we upgraded to Exchange 2013 (about the same time of the DMRC upgrade).