https://bugs.openldap.org/show_bug.cgi?id=10080
--- Comment #6 from Ondřej Kuzník ondra@mistotebe.net --- Yeah, you're right, there's another bug somewhere in how rwm deals with the response, not renaming the request DN to the original on the way back. Not sure if there's a good way to fix this that could be backported to 2.6 and below.
syncprov should also really be able to keep itself to the backend it was configured on so rwm wouldn't be involved at all. I assume that's because of how it handles its "fake" response but I might be wrong here.