How can I prevent mail attachments embedding when sending mail

In even simpler terms...

Program worked fine.

Program still works fine.

People can still send e-mail messages with attachments.

Logically,

No bug.

Yep, we can still send.

Problem is those on the receiving end do not receive it.

😉

If the program worked fine, we'd not be having this discussion.

Yes they do. That statement is obviously false.

Why are we having this conversation? The question originally asked has been answered a long time ago. Now you are trying to dredge up some issue that is not only completely unrelated, but provably false.

Before I upgraded to Lion, when I attached images they arrived at the destination as attachments. When I put images inline, they arrived at the destination inline. Now, images arrive inline whether I attach them or place them inline. I just want the previous, normal, expected behavior.

How about you let those of us who care about this issue talk about it, and not autorespond with "you're wrong" messages?

You will have to take that up with Jeremy. He says the attachments do not arrive at all. So one of you must be wrong. Either the attachments do not arrive or they only arrive as inline images. Are you claiming that attachments arrive both as inline images and as images that do not exist? Perhaps that explains why Outlook 2007 users have so much trouble saving them. The image attachment never arrives. All you every get is an exact copy of the original image attachment as an inline image.

Alas, this quantum attachment behavior is new in Lion. Aside from the five or six suggestions that have been made that clearly describe how to fix the problem, there is no solution to the problem.

Chris, you'll be fighting a losing battle. Etre would tell that the sun is cold. And if Apple said so, well, he'd drink that kool-aid right up.

The reality is, it worked correctly prior to Lion, and now does not work as it did before.

To clarify, from a Windows users perspective, the attachments do not arrive because they are too stupid to figure out where they are. But, again... not everyone sends things like Apple. So what seemed easy before to those recipients looks very foriegn now.

Whether or not we know how to send them does not matter. I've been using Apple products since 76ish near as I can remember. I love them to death. However, not everyone uses them. I know that's news to Etre since he seems to believe that everything Apple does is not only as intended, but the right way.

The reality is things do not work as they once did. While they may work as intended now, from the end users perspective they are broken.

I'd have to agree. I'm really not sure what the intent was. While it may have accomplished a goal set forth by the engineering team, its taken all of us a huge step backwards with regards to communicating with the rest of the world.

I don't live in Etre's world and near as I can tell, neither does anyone in this thread.

As to the solution? Well its in the problem.

Well, my solution was to pay $14.99 for Attachment Tamer, which fixes the bug. Presumably Apple could implement the same or similar code...

Or just revert.

Christopher Shaffer wrote:

Presumably Apple could implement the same or similar code...

That code already exists in Apple Mail and has for years. If you read this thread closely you will find a trick to trigger it again. Of course, then you will have another set of Outlook bugs to deal with.

Christopher,

I answered why this is different in Lion vs earlier versions of Mail long ago in this topic. I further reported on the communication I got from Apple engineering about this, and the substance of that communication was that the sending in HTML is deliberate and is working as they intend. Furthermore I have presented a way to work around the problem (which succinctly is failure to achieve Plain Text) by attaching a simple text attachment as the last attachment.

Now I disagree with the choice Apple has made in this regard, but it would not meet the test of a Bug, since 1) they know about, and 2) they state it is by design.

But there are bugs in Outook (correctable with settings by the user) and choices that have been made in some, but not all render engines that are used in email programs and browsers.

Ernie

Just made the same test to an account provided by my ISP that I made at your suggestion with Gmail. I then accessed that account with the webmail interface of that provider, with Safari, and got a different result than with the webmail interface of Gmail. With this interface and account, while the images viewed in place, the message was also indicated to have attachments. So the interface and/or render engine can make a difference.

With than interrface I notice that the list of attachments is only listed when one or more of them will not view in place, regardless of the sending computer or email program.

Ernie

This is just mental, I'm loosing business until Apple takes notice and fixes this - I'm annoyed at how stuborn they are.

It simply does not work. Apple read your customers complaints and DO something about this.

Thanks I'll take a look while I'm waiting for Apple to get up out of bed.

Hi Koshington,

Can you explain to me how this 'feature' in Mail is causing you to loose business?

Mail is just an Application that is built into OS X.

You don't have to use it if it does not fit your purpose.

There are plenty of email applications you can use that may fit your purpose better.

If you don't want to pay for one, you could try Thunderbird for example.

http://www.mozilla.org/en-US/thunderbird/