Hello everyone,
we had the same error. What helped for us was to change parameter "Behavior for mismatched footer or heading encoding" in "localeconfig" from "Only try encoding from message body" to "Try both body and footer or heading encodings".
Maybe it works as a workaround for somebody else.
Regards.
