![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
Entry tags:
help! insufficient geekitude
I hate to admit it, but I need help figuring out how to d/load a file. The person who sent it to me has just gone out of town, so while the most logical thing to do is to ask him nicely to re-send it in a different format, I can't do that for a week, and I'd really like to open it before then.
It was sent to my work email address (it is loosely work-related) which uses a Campus Pipeline web interface. It's supposed to be a rather large jpg. The attachment, as it appears in the email, is marked "type: multipart/appledouble." When I click on it and choose "open," a message tells me that Windows doesn't know how to open it. When I choose "save", the file tries to save itself as a document (the only other option is "all files"). If I save it as a document, I can read it with MS Word and I get this:
--Boundary_(ID_hRlg4k0Bj7CoxmFDb18n/g)
Content-type: application/applefile; name=_ADB2388.jpg
Content-transfer-encoding: base64
Content-disposition: inline; filename=_ADB2388.jpg
Followed by a string of gobbledygook which I assume is the encoded jpg. Simply retitling the document with a .jpg extension does not make it readable, alas.
Because of the reference to Apple I borrowed my son's laptop, accessed the email, and tried to download the file, with the exact same non-results.
I did some googling and learned that this is apparently a MIME file which for some reason is not transparent to my email client. I tried to get something called munpack from an FTP site but when I downloaded it Windows wouldn't run it.
I also tried forwarding the file to different email addresses. It won't forward from the original message. I tried attaching the downloaded file to messages to myself at gmail, Yahoo, and AOL, none of which did any better.
Any suggestions would be very very gratefully accepted!
It was sent to my work email address (it is loosely work-related) which uses a Campus Pipeline web interface. It's supposed to be a rather large jpg. The attachment, as it appears in the email, is marked "type: multipart/appledouble." When I click on it and choose "open," a message tells me that Windows doesn't know how to open it. When I choose "save", the file tries to save itself as a document (the only other option is "all files"). If I save it as a document, I can read it with MS Word and I get this:
--Boundary_(ID_hRlg4k0Bj7CoxmFDb18n/g)
Content-type: application/applefile; name=_ADB2388.jpg
Content-transfer-encoding: base64
Content-disposition: inline; filename=_ADB2388.jpg
Followed by a string of gobbledygook which I assume is the encoded jpg. Simply retitling the document with a .jpg extension does not make it readable, alas.
Because of the reference to Apple I borrowed my son's laptop, accessed the email, and tried to download the file, with the exact same non-results.
I did some googling and learned that this is apparently a MIME file which for some reason is not transparent to my email client. I tried to get something called munpack from an FTP site but when I downloaded it Windows wouldn't run it.
I also tried forwarding the file to different email addresses. It won't forward from the original message. I tried attaching the downloaded file to messages to myself at gmail, Yahoo, and AOL, none of which did any better.
Any suggestions would be very very gratefully accepted!
no subject
The only time I've seen this is when AOL used to mangle images.
The problem here is the _ADB2388.jpg is not the actual image
it's a resource fork.
the image is ADB2388.jpg
It may be the jpg is too large and overran the buffer. I'm afraid they'll have to send it again, and suggest that they .zip it first before attaching. Unless your mail doesn't allow for that.
no subject
I've actually gotten larger pictures than this with no problem through my work email. So I thought, hey, maybe it's lying when it says it won't forward, and I tried One More Time. [Just clicking "forward," not trying to attach the messy version that I had downloaded.] I sent it through to my Yahoo address... and it worked!!!! Yahoo was able to read it with no problem and I saved it from there.
So thanks... you got me thinking sideways and it truly truly helped!