Email photo as attachment, not embedded, in iOS 14

konrad138 wrote:

As a graphic professional, I depend on being able to attach multiple images in my workflow. …

I CANNOT add ONE IMAGE AT A TIME.

This is CRAZY

Who said you need to «add ONE IMAGE AT A TIME»?

Admittedly, that very tiny subset of email clients (consisting of a single email client and its derivatives, so far as anyone’s reported research has found) does prevent users from performing bulk attachment operations (such as bulk-saves), under many circumstances. So, such email clients may cause you to need to «add ONE IMAGE AT A TIME», at the receiving end.

However, that very tiny subset of email clients is not under Apple’s control.

The best way is to set up a g-mail account, then use that as the default sending account on your iPhone, and send the pictures to that or any other g-mail account on a PC. Need to avoid any MS email clients or its derivatives such as Hotmail. Photos are then received/displayed as regular attachments and not displayed as "embedded". I do not believe Apple has any intention to change anything or it would have done so in the latest iOS 14.5.1. Hope this helps.

Apple you really ruined a good think you had. I am beyond frustrated with the way attachments work on my phone now. Fix this immediately it is dumb and annoying and whoever thought it was a good idea should be fired because this wastes so much of my time.

Sorry - this does not reach Apple.

A work around:-

The best way is to set up a g-mail account, then use that as the default sending account on your iPhone, and send the pictures to that or any other g-mail account on a PC. Need to avoid any MS email clients or its derivatives such as Hotmail. Photos are then received/displayed as regular attachments and not displayed as "embedded". I do not believe Apple has any intention to change anything or it would have done so in the latest iOS 14.5.1. Hope this helps.

I found a workaround, but take it with a grain of salt.

I asked some friends to send me some test pictures using different OS (Win, Linux, Android) and all came in as attachments except iOS 14.

Solution;

Make a random blank file (pdf, note, 15 sec video) and name it "iOSFluxCapacitor" or "iOSDiscombabulator" ... :-) or whatever you want.

Adding the file with the image (s) will force the email system to attach, not embed, all the files including the image (s).

NOTE: Hope this work for you guys. I know my life is a whole lot better now that I don't have to download each image one at the time, but all at once.

NelsonPR1 wrote:

I found a workaround, but take it with a grain of salt.

I asked some friends to send me some test pictures using different OS (Win, Linux, Android) and all came in as attachments except iOS 14.

Solution;

Make a random blank file (pdf, note, 15 sec video) and name it "iOSFluxCapacitor" or "iOSDiscombabulator" ... :-) or whatever you want.

Adding the file with the image (s) will force the email system to attach, not embed, all the files including the image (s).

This is a known workaround, which seems to work by changing the overall “container” type used to «attach» the attached files: the files are attached either way, but the email client you are using at your receiving end (a single email client or one of its derivatives) doesn’t seem to recognize some “container” types, even though the “container” types have been a part of the International Internet Standard since the ‘90s. (This seems to show how far behind that single email client and its derivatives truly are).

NOTE: Hope this work for you guys. I know my life is a whole lot better now that I don't have to download each image one at the time, but all at once.

Only a very tiny subset of email clients (consisting of the aforementioned single email client and its derivatives) have this issue with email attachments.

I agree! I have a business account with 50 phones, most of them send in their receipts via the phone. Saw a smart-*** Apple Tech correct everyone saying they are not embedded and ignored the question.

1st - changing pictures to embed in the emails is a pain. Change back to an attachment.

2nd - Apple also has changed their file format from JPG to HEIC, which Windows cannot open in its native photo viewer. WHY?

Samsung is an option Apple, we do not have to stay with you.

CRBbama wrote:

I have the same issue. Very frustrating that this capability was eliminated. I need this capability or a different phone.

If you read here, you’ll find all there is to find on workarounds and how to contact the owners of the errant programs, as well as contacting Apple.

Hint: the «capability» has never been «eliminated». All email clients—with the exception of a very tiny subset—allow all their users the ability to perform bulk attachment operations (such as bulk-saves) for all emails generated by Apple Mail.

The exception is that very tiny subset of email clients that exhibit an apparent inability to provide their users with the ability to perform bulk attachment operations (such as bulk-saves) under certain International Internet Standards’ compliant conditions.

(If you are experiencing this issue, you, apparently, use one or more email clients from that very tiny subset [consisting of a single email client and its derivatives].)

What’s with the subset stuff.

My Apple mail worked fine until IOS 14. Then all of a sudden it stopped attaching multiple photos and embedded them instead. The mail client never changed, nor did the Outlook in the computer where I sent the photos. Something went away with IOS 14. Final answer.

I don't believe you're listening properly to the complaints, since I know you are capable of reading beyond the level of the superficial, or pedantic, or the command-line. There's a problem with the way that a subset of users receive attachments from those using Apple Mail that didn't used to present as a problem. The update amounted to a downgrade for users expecting to be able to communicate with clients in the way to which those clients were accustomed, and hoped not to have to contact the clients to tell them to contact the developers to have them change their software so that this upgrade wouldn't create unfortunate hurdles. That's a terrible ask, and from any individual customer, would have the result of changing absolutely nothing, which the customer would know.

You might find some solace in stating that -- technically -- attachments are attachments, or that the subset should be written off as adhering to outdated specifications. I wouldn't agree that such a subset being affected by this change should be of no concern and should be of no consideration for those of us who proudly expect our apple software to minimize challenges in communication so that business can be conducted properly -- for the mere fact that they represent a minority of users, or even in such cases that they, hypothetically, might represent a very small minority. It's still a hurdle where no hurdle existed before.

In my specific case, as I think I commented before, the subset of such users who are represented among my customer base is not an irrelevant subset whatsoever, but probably represent a majority. It's true that many are older or less technically savvy, but this is not a sector of users I care to write off as unworthy of proper functionality, or who I should tell: why doncha just call bill gates about it then?

That would be absurd, and I think you'd agree that your dug-in heels have put you into a very absurd position where you'd rather not *hear* what people are saying, and would rather see no problem at all than to acknowledge a problem that, evidently, does exist, for however small and irrelevant you believe the subset to be. There might then be a more useful and substantial discussion at hand, for the very small subset of users who are taking the time to contribute here.

So why are you bothering to respond then?

Facts are Apple changed something in IOS14 that effects sending images to Outlook regardless of who’s fault it is and they are not worried about it. The only think on this forum that really winds people up is when we hear the quote “tiny subset of email clients” as that is an utter outright lie. I did a E Letter to just under 1 million clients yesterday, 2 hours later the statics told us that 89% of read emails were on outlook so I don’t feel that statistically Outlook falls into any “subset” where apple clients only accounted for 6% of the recipients. However to support Halliday and LACAllen I do support the fact that moaning on here is pointless and you are better sending individual feedback to Apple where you can be fobbed off one at a time as opposed to a group or community, it’s a bit of a divide and conquer thing

As I pointed out, axelnelson, this «hurdle» has «existed» many, many times «before.»

Many, many times before the iOS 14 update.

It has occurred many, many times throughout the years!

Since the root problem is a reticent manufacturer of a very tiny subset of email clients (consisting of a single email client and its derivatives), that hasn’t updated their standards compliance for more than a decade, it sure seems to be high time that said manufacturer be held accountable for the problems their lack of standards compliance has caused their users.

At the very least, their lack of standards compliance shouldn’t be holding the rest of the world back!

Back when I worked within the corporate and governmental sectors, I always researched out the root causes of issues we were having, and always went to the responsible parties to get things corrected.

While I did, indeed, have times when one company would blame another (such as a large data mining company that blamed an issue on Microsoft Windows [a very minor player, as far as the data mining company was concerned]), I would always pursue and research the issue until I knew what was actually going on.

(In the case of that data mining company, I was able to demonstrate that the issue was only in how they were coding their software for Microsoft Windows. They then had a corrected version of their software to me within a month.)

The best thing about getting the root cause corrected is that it helps the greatest number of people!

For instance, by getting that data mining company to correct their code, all their Microsoft Windows users were benefitted!

So why are you bothering to respond then?

In the seemingly futile belief that eventually contributors will read and heed.

Venting ends at some point. This discussion has passed that point.

Meaningless beating of the dead horse does not add to the value of this community and IMO, harms it.

New users coming here looking for answers see these multiple page discussions that do not cause change and likely do not return.

Forgive me for trying to prevent that from happening.

Those who enjoy a good online fight should go elsewhere.

I am going to be seeking alternatives if this doesn’t get fixed. My workflow has been hampered. Apple devices are suppose to work for me, not me work for apple’s whims in changing software

Ok. Best of luck.

euro37 wrote:

The only work around that has worked for my company is to record a tiny video (1 second or less) and attach it to the email along with the pictures. Then the pictures will be sent as attachments.

They are «sent as attachments» in any case.

However, the addition of the «tiny video (1 second or less)» helps “trick” Outlook (and its derivatives) into recognizing that fact.

That’s all. It simply tricks Outlook, and its derivatives, into “doing the right thing”™️.