embedded email attachments

Thanks, but that is already the way I do it when it comes out embedded.

How do they need to have their email client set? It is always pc users that have this problem and they say they are not able to save the attachment elsewhere because there is not the usual option to save the attachment available, when the attachment is embedded with the text.

However, I don't have the answer to that one.
I have OE running on a test machine at the house and it has attachments embedded and available for saving elsewhere.
At work I use Outlook/Exchange and have no problem with emails from Mac users.
Are these people AOL users? That would explain a lot.
This problem surfaces every now and again and there is always much difference of opinion as to what the cure is.
If the OE user sets their email to NOT display images, then they should be available as separate files but that seems a little drastic. When I receive embedded graphics, they are always available for saving.

P

I'm glad this came up. I have had a problem with embedded attachments, too, but on the receiving end, and from a PC user (not AOL, though that has presented its own problems for me--that is, opening attachments from some AOL subscribers). I think she was doing what the original poster to this thread did, and with the same result.

I tried everything I could to get at the attachment--different email programs( Earthlink WebMail, Eudora) and such--and asked advice of some computer mavens I know, but nothing helped. One suggested a few things that didn't work and made some heady but dead-end suggestions about Unicode and other matters, but I never did succeed in opening what was clearly an attachment, which looked like this: <name of attachment>.

Now, how does one save the attachment to another place under such circumstances? I have Stuffit (which someone suggested using) and MacLinkPlus, but nothing did the trick.

By the way, I haven't the faintest idea of what the aforementioned (my father was a lawyer) correspondent did to change things, but I now can read her attachments, which emerge as regular ones in Word.

Jenny (clueless as to answers to any of the above)

you can set the type of attachment that you want to send.
I use UUencode as the type as just about any OS can open them after they have been encoded that way.
The other wonderful thing about receiving email from MS people is the attachment that says <TNEF name of attachement>. Gotta love Exchange Servers.
Even with the attachment, JPEG for example, showing up in the text, it is still an attachment and, as such, can (or should) be accessible as such.
Stuffit and MacLink have nothing to do with the problem. Do people still compress attachments?

P

If you send it to someone, and it opens fine, and they forward it, and it arrives broken, then the problem is between them. Nothing you can do but teach them to send attachments as well as you do!

Lampie

It may be that it's arriving "embedded" and they are just forwarding it on.

Sorry if I'm resurrecting an old thread here but I was searching to see if there was something the PC using recipient could do when receiving images from a Mac user. I already know for sure that if the sender (the Mac user) selects plain text format when sending the images arrive as attachments in the normal way and can be directly accessed by the PC user.

By experimentation we have found that the recipient PC user is able to right-click on the image and use "save picture as". The only file format is .bmp and s/he has to rename the image but the resolution is unchanged and can therefore be resaved in jpeg or tif format using a picture editor