Email photo as attachment, not embedded, in iOS 14

Mystified-OZ wrote:

Great

sign away your privacy to make iPhone work like it should have

What privacy? You have no privacy. As Scott McNealy (founder of Sun Microsystems) said 30 years ago, “you have no privacy. Get over it."

Good luck in getting Apple to deal with this any time soon...I really have a hard time trying to figure out some of the "updates" they do and what they change (mind boggling, to say the least). It's like they are going a step backwards with some of their decision-making. Also, when Apple decides to make a change like this, they really should be deferring to their employees that actually use a particular functionality that they want to change (in this case, the person who decided to get rid of attachment's option, you likely will find doesn't deal with a lot of sending of photos...).

Lots of unhappy iPhone owners. I will stick to my 1st Gen SE for the moment. When I got this issue I told my daughter not to update her 6s from iOS13.7. She is very happy to be able to carry on attaching photos as before!!

Yes, carynfor.

There have been many that confuse appearance with actuality/reality/functionality.

It’s not about the way things appear.

It’s, ultimately, about functionality.

The only email client that embodies this confusion into its behaviors, that any of us have found, so far, is Microsoft Outlook.

Actually try the various email clients and see how they behave, rather than the fact that all email clients are supposed to render (display) rich-text email in a manner similar to webpages (since they use the same HTML for their formatting).

There’s much more, BienTech, than any circumstantial evidence.

That’s especially the case, with this issue: what has been «working normally» was a marginal use-case, far from the principle intent of the tool (email: the principle intent being human-to-human communication) being used. Such are always unstable situations, and subject to “breakdown” at any moment, due to forces outside the users’ control.

As for moderators: the moderators that “watch” these forums have no obligation to report technical issues to Apple Support or Technical personnel.

If you want something reported to Apple, you had best provide the Feedback via the supplied channels.

Anything else is a practice in futility.

In fact, simply complaining, within these fora, without any actual attempt to provide Feedback, or contact Apple Technical Support, yourself, can be taken as an indication that any actual response, from Apple, is far from your intent: you’re simply complaining to be seen complaining.

In other words, if you actually want change, then only complaining within these fora simply works against your claimed desires.

As explained, AthinaRP, they always go as attachments!

There is simply no other way, nor means!

The only thing that can be different is how the base email is formatted, and, therefore, how it may be displayed (rendered) by another email client.

Additionally, since the files always go as attachments, there should be no functional change in how the attachments should be manipulatable, by the receiving email client!

Unfortunately, a tiny subset of email clients (Microsoft Outlook being the only known case, so far) violates this principle: choosing, instead, to preclude certain bulk attachment operations based solely upon the way said email client chooses to display (render) a given received email!

Halliday, let me humbly suggest that you give up and stop following this thread. There are many new posts that need attention where your expertise might actually be appreciated, and it will be better for your serenity.

Unfortunately, to stop following is not easy due to a bug in the forum software, but it is possible:

1. Click Following at the top of this page; it will change to Follow
2. Redraw the page; it will probably change back to Following
3. Go to 1 and repeat until it no longer changes back to following.

You will have to repeat the loop roughly the number of times you have posted to the thread.

You, Mystified-OZ, seem to be having some different problems, vs. everyone else.

It’s already verified that GMail—whether using Google’s client or any other (with the possible exception of using the Microsoft Outlook email client)—works just fine for performing bulk attachment (like bulk-save) operations.

I have no idea what email server or email client you are using with your «own domain email». (For all I know, both are using Microsoft products. Only you can demonstrate otherwise.)

As for the «typing hesitates like slow processor», that is certainly a separate issue, and will need a separate Apple Support Communities Question submission.

Who knows what else may be affected by whatever is causing this issue.

Very interesting, MWoodleaf.

Yes. Very interesting indeed!

I wonder why no one, in this long discussion, has even mentioned giving a try to a change in the signature, or eliminating it altogether, as you did?

Some mentioned how making sure the signature had no formatting (no HTML) was a “solution” in some pre-iOS 14 versions, but no one, until you, made any mention of trying any such in any iOS 14 version.

Oh well. Chalk it up to human nature, I suppose.

(I haven’t had to touch a Microsoft Exchange server nor a Microsoft Outlook client for over five [5] years now. So I don’t have a means for testing the actual root causes of this issue. Nor can I test your solution.)

Incidentally, MWoodleaf, other than Microsoft Outlook, all other email clients, any of us have tested, will have the equivalent of the “paper clip”, regardless how a received email is displayed (rendered), since all such involve only attached files.

Sorry - I clearly don't know what variant you are referring to. I thought he was suggesting leaving the signature boxes blank. I have seen no other suggestion - possibly I missed it. I don't use Outlook for iOS. Only on my PC as part of MS Office 365.

Yes, Scamp468. «How odd!!»

Thank you for testing and verifying this «odd!!» new workaround!

Perhaps even having a blank signature causes some “residual” that is eliminated by deleting a signature.

It’s about as «odd!!» as the way that any method that avoids a direct Simple Mail Transfer Protocol (SMTP) transfer from Apple Mail to a Microsoft Exchange server, results in Microsoft Outlook allowing bulk attachment operations (such as bulk-saves) on attached files (such as photos).

Basically, is shows how fragile any method of trying to get Microsoft Outlook to “do the right thing”™️ really is: so long as Microsoft Outlook remains broken, the way it is, any method of getting it to work properly is fragile, at best.

If one is of the suspicious sort, MrDaveIII, one could suppose this is why Microsoft hasn’t fixed Outlook: lock users into their misbehaviors.

After all, Microsoft’s Outlook is the only email client any of us have seen, so far, that prevents users from performing bulk attachment operations (such as bulk-saves) based solely upon how the email client chooses to display (render) a received email.

So annoying that they did that with insertion of pictures instead of attaching. Now do an update and as if needed attached or imbedded. Use the attachment always for my business now my clients hate that the pictures are inbedded so not they cannot save and use in the future.....ANOYINGGGGGGGGGG

I have the same issue. Like the other I use my iPhone to take many photo at work and I used to transfert photo that way since it was the quickest and easiest way to do it. Yes there are other ways of doing it but they are cumbersome and slow. IPhone and iOs is all about optimization and quick way of doing thing and shouldn’t be cumbersome in any way.

Unfortunately I have read iOs 14.3 patch notice and unfortunately this issue don’t appear to have been added to this patch note.

Apple fix your **** OS