If a remote server sends Courier (0.45) what it claims is a uuencoded
message, but the message includes non-uuencoded valid bits (e.g. ^M
from a Mac); what does Courier do?
Hi All,
I should add a bit more detail, I realize. We've got a client who's
getting email from someone else's server, where Courier is modifying an
attachment "X-Mime-Autoconverted: from x-uuencode to 7bit by courier
0.45". The modified attachment can't be uudecoded on Windows or Unix
(but can on OS X), it appears, because of '\r' characters.
The message has an attachment named "2-17Notes.doc" (note that "Notes"
is plural here, and singular later. Odd. And why it's being saved as
uuencoded is odd -- I'd think "converted" would me "uudecoded; then
7-bit encoded"; but is it just applying a 7-bit encode on top of the
uuencoding?)
# file 2-17Notes.doc
2-17Notes.doc: uuencoded or xxencoded text
# ls -l 2-17Notes.doc
-rw-r--r-- 1 jeff users 258800 Feb 23 11:25 2-17Notes.doc
# uudecode 2-17Notes.doc
uudecode: 2-17Notes.doc: No `end' line
# cp 2-17Notes.doc 2-17Notes-safe.doc
# perl -pi -e 's:\r::gs' 2-17Notes-safe.doc
# ls -l 2-17Notes-safe.doc
-rw-r--r-- 1 jeff users 254689 Feb 23 12:46
2-17Notes-safe.doc
# uudecode 2-17Notes-safe.doc
# file 2-17Note.doc
2-17Note.doc: Microsoft Office Document
What the heck is going on? I'm lost!
Thanks!
Jeff