Email photo as attachment, not embedded, in iOS 14

I have visited this thread regularly, after being immensely frustrated by this issue. I was not a member, but would visit regularly to see if some had a viable solution. Yours is the most logical path to a solution yet, enough so, that I've joined and am following your advice. Let's not just discuss it amongst ourselves, let Apple know! I for one, have just sent my feedback. Hopefully, others will follow suit. Like others, I thought this forum was monitored by Apple support staff.

Certainly! I would imagine that I need to provide device info (11 Pro Max), iOS version 14.3, the fact that I am using an outlook account with a plain text (default) email signature. If you can think of anything else I might want to mention, to make it quicker for both me and the support agent, please do :) Cheers!

RussTuff wrote:

So... we have a choice, we "walk away" from Apple because their product doesn't do what we bought the product to be able to do,

Last time I checked, iOS Mail app allows me to save multiple images even though they appear as embedded into body of the received email message. I guess this leaves us with Outlook as the only app missing such basic functionality…

The company I work for has luckily supplied the solution by buying a couple of thousand Samsungs for its staff to move away from iPhones so this ridiculous issue will soon be of no issue to me but perhaps Apple would take note

Well, Mark-my-words, that is a “workaround”, and, like all “workarounds”—which is all we will ever have, unless and until Outlook (and its derivatives) are corrected (in their misbehavior)—it is fragile: subject to being easily broken by any of a myriad tiny changes in the web of interactions involved in email transfers.

That is only one of a myriad “workarounds”, golferskier.

(Of course, that is to say nothing of your fundamental misunderstanding of what is actually going on.)

In all cases, one is not fixing the fundamental issue. Not addressing the fundamentally flawed software that Apple has no control of, and, hence, can do nothing to fix.

As a result, all “workarounds” are, fundamentally, fragile: prone to being easily broken by any tiny change in the web of myriad interactions involved in email transport.

It was only a call center operative who did not know and their recommendation was to complete the feedback form. They did not know.

Very very frustrating having to deal with the interlaced attachments.

https://www.apple.com/feedback/

Another “workaround”, N-K-O.

Since, as I’ve pointed out, all “workarounds” are fragile, we’ll see how long this one continues to work.

Anything short of fixing the misbehaving, very tiny subset of email clients (none of which are controlled by Apple), will be a fragile “workaround”.

Whatever works, for now, N-K-O.

This whole issue started when something minor broke a previous “workaround” (whether or not any of y’all knew you were working with a “workaround”, or not).

(This issue has a very long [years, and many major iOS versions] history of “popping up”, and people finding “workarounds”. The safe bet is that it will occur again and again, until the “root cause”—the misbehavior of a very tiny subset of email clients [none of which are controlled by Apple]—is corrected.)

Enjoy, while it lasts.

Judging purely by circumstantial evidence, I see, Mystified-OZ.

Simply repeating an allegation will not make it so.

Instead. You could do something constructive and get on the creator of that very tiny subset of email clients (apparently consisting of a single email client and its derivatives) that prevent users from performing bulk attachment operations (such as bulk-saves) based only upon their own, internal “reasons” (apparently, also reflected in how said email clients seem to display such received email); to actually fix their misbehaving software.

If it were iOS 14, why are there no other email clients with this misbehavior?

"Steve would be super disappointed about this one."

Yes... yes yes.... finally. This is the real disappointment. There is no way Steve would have put up with this ..... let's say "poor form".

It doesn't matter who we are blaming, or what we find out. Steve would be turning in his grave over this 'poor form'.

I wonder how far up the ladder this has gone. I wonder if anyone is aware, since, other than a customer service rep replying to someone, there has really been no reply from “Apple”. Maybe this has never gone beyond the call center in Bangalore.

CJCragg wrote:

I wonder how far up the ladder this has gone. I wonder if anyone is aware, since, other than a customer service rep replying to someone, there has really been no reply from “Apple”. Maybe this has never gone beyond the call center in Bangalore.

As has been pointed out, many times before, if y’all want to get your displeasure communicated to Apple, you should use their provided Feedback mechanisms.

Complaining here, is not one of their provided Feedback mechanisms.

ahungryhungarian wrote:

… Please read more of the thread before posting a useless comment.

I’ve read this entire thread as well as many others, on this subject.

I didn’t even start to comment, on such matters, until I, and others, had begun to figure out what was actually going on (beyond the superficial, circumstantial evidence).

Mystified-OZ wrote:

You have a lot of claims but no solution

The only actual solution is the same as we (those of us that actually understand the entire “picture”) have been always recommending: asking the creator of the very tiny subset of email clients (consisting of a single email client and its derivatives, so far as any that have actually tested, and reported on Apple Support Communities, can determine)—that have any problems allowing their users to perform bulk attachment operations (such as bulk-saves)—to fix their email clients, so they, like all other email clients, can allow y’all to perform bulk attachment operations (such as bulk-saves) on your received emails.

Anything else is a mere “workaround”.