Two possible reasons
- Your server has DK signing configured, but it is doing it improperly (DK incompatible)
- There's a server at the message path, that changes/adding message headers improperly(DK incompatible)
It's also possible, that destination server verifies the signature in wrong way - like it forgot to change bare "\n" to "\r\n"