Greg Earle writes:
Why did Courier attempt to alter the attachment encoding in the first place?
("X-Mime-Autoconverted: from x-uuencode to 7bit by courier 0.42")
Because âx-uuencodeâ is not a valid MIME transfer encoding, as defined by
RFC 2045.
Also, if it claims it "Autoconverted from x-uuencode to 7bit", why did
the rest of the attachment remain untouched, i.e. it's still there as
a uuencoded section? No actual conversion took place ...
Because x-uuencode is not a valid transfer encoding. As such, analysis of
MIME content determined that it only contains 7-bit data, so it is labeled
as such.
How can I fix/stop this from happening? This is a real show-stopper for me.
Have the sender reconfigure his mail program to generate a MIME-compliant
message format.
pgp00000.pgp
Description: PGP signature
