This may be a corrupted TNEF stream
It's certainly a
record sequence which is confusing the TNEF converter. And no, on
the face of it, it does not make sense that TNEFBreakSMIME=1 would fix
this.
But please try it with debug still enabled and let's see what happens.