Post by: RobW on June 07, 2003, 02:18:09 PM
I've been helping (via email and telephone) a family member who's new to computers and especially to Macs. She's having some problems sending pictures (jpegs) to PC users. (I get them fine.) She uses Mail on her relatively new iMac which she bought a few months ago.
I use Entourage and know how to set attachements, encoding settings, etc., but don't have any idea what to tell her to check with Mail to make sure her PC friends can open the pictures.
Any thoughts or links for her???
Post by: Bill on June 07, 2003, 03:38:28 PM
I use mail in Jag. I looked around in the mail preferences and it appears the 'viewing' tap is for incoming.
Sending wise,you have two choices. Either click (see pic) or up in the menu - edit>scroll down to 'attach file'! Both send you through your computer till you find what attachment you want to send.
Forgot about a third way of sending. Plain old dragging.
You mentioned jpeg. I take it your friend is making sure there is a jpeg or jpg .. gif .. etc at the end of the sent file.
If so,got a hunch the problems at the receivers end. Settings off ... aol ... lives near Bernie. <gr>
Post by: RobW on June 07, 2003, 05:48:12 PM
) Unless there's a setting in Mail my cousin has to change for PC users to open files she sets. In Entourage, there are "encode" settings that can be changed if necessary.
Post by: Bernie on June 07, 2003, 07:26:19 PM
"palws@ ************ 
Post by: Paddy on June 07, 2003, 09:19:21 PM
clarification: we made the CD's into mobiles...not the preschoolers.
Post by: krissel on June 08, 2003, 12:06:24 AM
If that doesn't help or other factors are involved, try reading these threads from the archives:
sending files to PCs
seeing jpgs on PC
Paddy, gee, I conjured up a really interesting visual image of the little tykes hanging by their jumper straps, spinning in the wind...
Post by: RHPConsult on June 08, 2003, 01:16:53 AM
The only AOLer I know who understands it, and even likes it, is Harv.
Send him a note and see if he has an idea for you, and your kinfolk.
I'll probably be iChatting with him tomorrow, and I'll suggest he look in on this thread.
PS: Interesting Sidebar . . . just out of curiosity, I checked the posts of the 6 of us on this thread and they total 18,767! Put that in your CPU and smoke it!
Post by: pendragon on June 08, 2003, 08:11:59 AM
As a quite happy AOL user...
When sending attachments, especially large attachments such as pictures, I always first stuff them with Stuffit, ZipIt, or other similar program. Since most all PC users can open a zip file, I typically use that.
When AOL sends large attachments (I do not know the exact size), it will automatically stuff the attachment using some (admittedly) facockta mime algorithm of theirs. (I am not certain AOL uses mime for stuffing, but I think so.) This gives some users fits, as they do not know what to do with the mime encoded file when it is received, e.g. they can't open it. So, to preclude AOL from automatically doing the stuffing, I first stuff the attachment before sending it. AOL then sees that the attachment is already stuffed, does not do any further stuffing, and merrily sends the attachment along the way.
If you are on a Mac and receive a mime encoded file, it is easily unstuffed using Decode da Code or similar program. Just drag and drop the mime attachment on to the icon and voila!
It's so easy even Bernie can even do it (but not Dick).
I believe Tacit is also a happy AOL user. If so, perhaps he can clarify what I have muddied.
BTW, I do wonder how many of those who fault AOL have (even) tried the new AOL 10.3 for OS X.
Harv
Post by: RobW on June 08, 2003, 10:03:43 AM
Part of the problem in me helping her is that the people she sends the attachments to who use PCs are also not real experienced--so it's been hard to get information from them on what's going on at the other end.
What I want to do is to make it as easy as possible for my cousin, using Mail, to send the attachments to PC users who will be able to open it without much effort--or me being called to intervene. Harv, I have to see what compression programs she has. This certainly might explain what the issue is. I didn't know that AOL compresses those on their own. Also, while I've used the word "facockta" often, I've never seen it in written form before.
Paddy, you're idea of having her put the images online is a great idea. I know she has a dialup modem, but actually, it's more of a time saver to upload once then to have to send a jpeg a bunch of times. Even so, I still want to figure out how to have her do the email attachments somewhat easily and pain free.
Post by: RHPConsult on June 08, 2003, 11:29:59 AM
QUOTE
Hey RHP, can you imagine the total combined posts if Kelly joins this thread??
How's this for a number, Rob?
26,332 mol !
Post by: tacit on June 08, 2003, 12:56:24 PM
AOL *also* compresses attachments if you attach more than one file, or if you attach a folder. It's based on the number of files, not on the size of the attachment. One file: MIME encoding. Multiple files, or one folder: MIME encoding plus compression.
Now, here is where it gets complicated:
Mac files have two "parts," called a "resource fork" and a "data fork." Other computers do not use or understand two-part files.
Apple has invented a type of encoding called AppleDouble to handle two-part files. The file is broken into TWO files: One part of the data fork, one part for the resource fork plus special Mac information (icon, Type code, Creator code, and so forth).
Each of those two parts is encoded using MIME. Then both parts are emailed.
Some mail programs do not understand AppleDouble. The person who receives the email sees TWO attachments, not one. One attachment is the file. The other attachment is the resource fork and Mac information. The first attachment is useful, the second attachment can not be used on a PC and sould be ignored.
AOL gets very confused by AppleDouble emails. AOL will not show you the attachment. Instead, if you send an AppleDouble attachment to an AOL user, the AOL user will see this:
"This email has an attachment encoded using MIME. AOL can not decode the attachment. To decode the attachment, you will need to download the email and then use a decoder program. For more information, visit Keyword: MIME."
The message means exactly what it says. The attachment can't be decoded by AOL. In order to use it, the AOL user will need to download the email and then run a MIME decoder program. (I believe the newer versions of Stuffit Expander can decode MIME.)
Unfortunately, there is no way to turn off AppleDouble in Mail.app. As a result, I don't use Mail.app.
Post by: sandbox on June 08, 2003, 01:16:29 PM
Post by: pendragon on June 08, 2003, 01:29:54 PM
Harv
Post by: Pascalin on June 08, 2003, 02:34:37 PM
What sugestions do you have for OS X 10.2.6?
I have a couple friend with AOL and asked them to open an account with Yahoo or similar.
or may be transfer the file with iChat?
Post by: Dreambird on June 08, 2003, 04:54:34 PM
I think there is a Windows version of Stuffit expander too, at least there was... I've used it and it worked well.
And then...
there's Bill... Another excellent illustration... is that your errr... "beer belly"?
Post by: RobW on June 09, 2003, 08:12:55 AM
One thing I was wondering--(well, one of many)--if an AOL user on a PC had a webmail email account--such as Yahoo, hotmail, etc., would they be able to open a jpeg attachment (assuming it had the .jpg extension) that was sent from a Mac user using "Mail"?? Or would the whole AOL/Mail/AppleDouble issue still be a problem as if the attachment was sent directly to the PC user at their AOL email address??
Post by: tacit on June 09, 2003, 03:31:33 PM
QUOTE(RobW @ Jun 9 2003, 1:12 PM)
One thing I was wondering--(well, one of many)--if an AOL user on a PC had a webmail email account--such as Yahoo, hotmail, etc., would they be able to open a jpeg attachment (assuming it had the .jpg extension) that was sent from a Mac user using "Mail"??
Most likely, yes. Most Web email accounts can handle multiple MIME attachments (which is all AppleDouble really is) without difficulty.
Post by: RobW on June 09, 2003, 08:09:20 PM