The example you gave isn't a problem if you interpret newlines correctly.
Remember that the *only* Internet standard for newlines is CR LF.
Host B made a mistake by interpreting the newline in quoted-printable as a
local newline. It should not do this unless the data in question has been
definitely identified as textual data (and thus subject to newline
To avoid a layering violation, you should keep everything in the CR LF format
and convert newline conventions only at the upper level when you are dealing
with binary vs. text objects. You'd probably only do this for content-type
Believe me, I had to deal with this problem. It is possible to do the right
This sort of confusion is an example of why quoted-printable is probably
unsuitable for binary data in the general case; not that it won't work but
rather that it is hard to do right.
-- Mark --