That's what I get for doing the conversion on the fly... the days have
long passed when I had to think in "hex" all the time. :-)
Your explanation of listproc as the culprit seems right on the money to
> Not to cavil, but =3d -> hex 3d -> 61 -> equals sign. IOW:
> =3D = "=".
> Ah, but at least you know it's a space supplied in the original
> and not the result of some line-breaking/rewrapping function somewhere
> along the line.
> I believe this is actually an artifact of how the Berkeley SunSITE's
> listproc removes undesirable attachments and sends only the part of
> message it considers to plain text. Either the original is encoded as
> quoted-printable without the appropriate Content-Transfer-Encoding
> header, or the listproc is ignoring (or doesn't know how to handle)
> header. I'm guessing it's the antique and much-patched listproc
> software that's at fault.
> Thomas Dowling
Received on Sat Mar 6 09:10:36 2004