Email photo as attachment, not embedded, in iOS 14

madisonNYC wrote:

…

Also, we've been urging everyone to send a message to Apple asking them to reverse the change they made in IOS 14 that affected the mail app.

That’s just fine.

However, only the other company (the creator of the very tiny subset of email clients that exhibit the failing of disallowing users to perform bulk attachment operations [such as bulk-saves] based only upon their own internal code) has the ability to truly fix the issue (which resides within that very tiny subset of email clients).

You need not believe me, madisonNYC. You can check by using the definitive test, provided at https://discussions.apple.com/thread/251807601?answerId=254806789022#254806789022.

(See also posts of other high level users, here, and within other Discussions on this subject. The issue is well researched, characterized, and appropriately attributed.)

The thing is, madisonNYC, that in all cases, the «pics» are being sent «as attachments», as anyone can verify by performing the definitive test found at https://discussions.apple.com/thread/251807601?answerId=254806789022#254806789022.

Don’t believe me.

Check for yourself.

However, only a single email client (and its derivatives) has any problem allowing its users to properly perform bulk attachment operations (such as bulk-saves) upon any given received email, based upon some internal criteria known only by its creators.

No one else have such troubles, since all «pics» (and other sent files) are provided «as attachments».

Run the definitive test and see for yourself.

Welcome, Boarderofvaldisere, to Apple Support Communities!

First, Apple doesn’t «monitor» these fora. We are just users, like yourself.

The thing is that, in all cases, all associated email files are being sent «as attachment[s]», as anyone can verify by performing the definitive test found at https://discussions.apple.com/thread/251807601?answerId=254806789022#254806789022.

Don’t believe me.

Check for yourself.

However, only a single email client (and its derivatives) has any problem allowing its users to properly perform bulk attachment operations (such as bulk-saves) upon any given received email, based upon some internal criteria known only by its creators.

No one else have such troubles, since all images (and other sent files) are provided «as attachment[s]».

Run the definitive test and see for yourself.

So. Unless and until the creator of that single email client (and its derivatives) corrects its behavior, there will be no actual fix.

Since Apple has no control over that single email client (and its derivatives), Apple can do nothing to actually fix the issue. (At best, they could find fragile workarounds for the issue. Fragile, because such workarounds are easily broken by any tiny changes in the web of interactions involved in transferring emails. This fragility was the cause of this breaking when iOS changed from 13 to 14, as well as many other times this issue occurred previously, through the years.)

(That single email client [and its derivatives] has been neglected by its creator for over a decade, now.)

VenomInMyVein wrote:

add also another type of file, like a pdf oder something to the mail and it will send the pictures as an attachment.

this is not a solution, but it works as a work-around.

Yes. This is a workaround that modifies the sort of attachment structure, used by the email, is within the more stilted and limited attachment structure the very tiny subset of email clients (consisting of a single email client and its derivatives) actually seems to recognize.

No other email clients have this limitation.

You don’t need to believe me. You can check for yourself by performing the definitive test found in my comment at https://discussions.apple.com/thread/251807601?answerId=254806789022#254806789022.

Is there anywhere that a community of actual users can collectively voice their concerns then ?

What part of the Feedback link provided here countless times does not fit that bill?

Feedback for Apple goes here >>> http://www.apple.com/feedback/

he concerns we had on here from Halliday were that it appeared the responses were automated and no-one was actually listening to us. Its not a personal attack but I take your points.

There are no bots. An assumption made in error by many. No bots are used here and no bot would form sentences like Halliday does. Halliday believes differently as is allowed.

And Halliday's offerings don't get removed by the hosts. Offerings mocking or attacking Halliday do.

It is well understood this approach is not popular. A strong sense of entitlement is displayed here quite often. This community is provided by Apple for a specific reason. It is not a complaint channel.

Not popular with who, Apple ?

Users who extend a conversation beyond its "logical' limits.

Who come back, page after page, demanding an answer from Apple. despite being told over and over Apple does not engage here.

There are users who sign in here, believing it's a chat service. They state a few words, wait 2 minutes, post again, wait another few minutes and then lose their mind because there has been no response.

VeryBusyBee wrote:

I'm in the same boat as everyone else - this update is a retrograde step and if anyone at Apple is listening, please revert back to sending images as attachments - without having to record a video. Thank you

The «images» are always sent «as attachments», at all times, since there is no International Internet Standard (governing the composition and interchange of emails) compliant method to do otherwise.

The only thing that can change is the underlying details of how the «attachments» are encoded, and how any given email client may render said email.

This can be tested and verified by simply performing the definitive test found in my comment at https://discussions.apple.com/thread/251807601?answerId=254806789022#254806789022.

Now, if all email clients complied with the full International Internet Standard (governing the composition and interchange of emails), there would be, absolutely, no issue, except for how any given email was rendered (displayed) by any given email client.

(Incidentally, the standard does not dictate how any given email client must render any given email, nor how any given email client must allow its users to perform bulk attachment operations [such as bulk-saves] upon received emails.)

In all cases, with the exception of a very tiny subset of email clients (consisting of a single email client, and its derivatives), email clients fully provide their users the ability to perform bulk attachment operations (such as bulk-saves) upon received emails.

Unfortunately, those users that receive their emails on one of the email clients in that very tiny subset, have found that they are having some troubles that no one else are experiencing: the inability to perform bulk attachment operations (such as bulk-saves) upon their received emails.

Further unfortunately, that very tiny subset of email clients (consisting of a single email client, and its derivatives) is not within Apple’s control!

So Apple can do nothing to truly fix this issue!

The most Apple could do would be fragile “workarounds”: that are subject to being easily broken by any tiny changes in the web of interactions involved in transferring emails.

In fact, it has been such fragile “workarounds” that broke, each and every time, in the past years, that lead to all past instances of this email issue: not just from iOS 13 to 14, but many times prior to that.

I’m sure not going to blame Apple for not wanting to continue playing such a loose-loose “game”.

Furthermore, the International Internet Standards compliance of that very tiny subset of email clients (consisting of a single email client, and its derivatives) hasn’t improved for more than the last Decade!

Isn’t it time that the creator of that very tiny subset of email clients (consisting of a single email client, and its derivatives) finally fix their software, rather than insisting that all other email clients “bow down” to it?

This is the reason we have International Internet Standards: to prevent any company from dictating to others.

Y’all are always free to provide Feedback to Apple, as you desire, through their designated Feedback Mechanisms: Product Feedback - Apple.

However, in order to obtain any actual fix for this issue—for yourself and others—you’ll need to provide your Feedback to the actual company responsible for that very tiny subset of email clients (consisting of a single email client, and its derivatives): get them to, finally, bring their email clients into compliance with the full International Internet Standards, governing the composition and interchange of emails.

Anything else is but a very fragile “workaround”.

[Edited by Moderator]

Again.

An opposing viewpoint is not spam.

Apple's awareness is not really in dispute.

Just thought you should know what we're facing here.

Which, for clarity, is the reality of this community not being the proper place for this conversation.

Feedback for Apple goes here >>> http://www.apple.com/feedback/

Welcome, JayZeeP, to Apple Support Communities!

Those are interesting results.

As one can verify, by simply performing the definitive test found in my comment at https://discussions.apple.com/thread/251807601?answerId=254806789022#254806789022, «pictures» are always sent as «attachments», regardless how they may appear (formatting of any email client).

There simply is no way to actually «embed» «pictures» in an email (not while being Standards compliant, which Apple demonstrably complies with). All that can ever happen is that the «attached» «pictures» are formatted inline with whatever text there may be as a part of the email.

Unless appearance is the only concern (seldom the case, and doesn’t appear to be the case with you), all email clients—with the exception of that very tiny subset of email clients (apparently consisting of a single email client and its derivatives)—allow users to perform bulk attachment operations (such as bulk-saves) regardless how they may display the «pictures».

Unfortunately, that very tiny subset of email clients (apparently consisting of a single email client and its derivatives) prevents its users from performing bulk attachment operations (such as bulk-saves), except under a very narrow subset of email compositions, subject to its own, hidden criteria.

Additionally, the email clients in that very tiny subset haven’t improved their International Internet Standards (governing emails) compliance in over a Decade.

Only that company can truly fix this issue with their email clients.

What you have found appears to be a rather interesting “workaround”, but, since it doesn’t actually fix that very tiny subset of email clients, it will, almost certainly, be very fragile: subject to being easily broken by any tiny changes in the web of interactions involved in transferring emails.

eyeliv wrote:

I was having this issue too and stumbled across how to fix the issue. Attach the photo as normal, which will cause it to be inserted into the body of the email. Once it is there, you can tap on the image and two options should appear “send as attachment” and “remove”. Select “send as attachment”.

Is this using the native iOS Apple Mail, or using some other email client?

We have been told these steps, before, but they turned out to be for a non-Apple email client.

Once it has been changed to an attachment, you change change it back to being inserted by tapping on the image again and selecting “send inline”.

I hope this works for you!

See, also, my comment, on the previous page, at https://discussions.apple.com/thread/251807601?answerId=255128606022#255128606022.

Rick2017 wrote:

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. …

If you wish to have Apple make this change, then you’ll need to provide Apple with direct Feedback, using their designated Feedback mechanisms: Product Feedback - Apple.

However, while the pictures may well be displayed/formatted inline with text and other email components, they are, indeed, contained, within the email, as attachments.

There is simply no other (allowed) way.

You need not take my, or anyone’s, word for this.

You can check for yourself by performing the definitive test found in my comment at https://discussions.apple.com/thread/251807601?answerId=254806789022#254806789022.

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

The «WHY» is because «HEIC» is a newer, far superior International Internet Standard, that provides superior results with smaller file sizes.

Just because Microsoft and other companies wish to charge you extra for this superior file format is no reason for Apple not to offer it to you.

However, Apple does offer you, the user, the option to have your device save your photos in the old, inferior, though more widely compatible JPEG format: Settings -> Camera -> Formats; change from “High Efficiency” to “Most Compatible”.

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

No “skin off my nose”, or that of anyone else within this forum. We are but fellow users.

Apple isn’t here.

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.

Contribute what?

Yes it is! No it isn't!! YES it is!!!, NO it isn't!!!

You do realize that nobody here is speaking for Apple?

The member you are venting at is not required to listen. Properly or otherwise. Not required to acknowledge anything in fact. You are not debating with Apple. You are debating with someone you disagree with. Fruitlessly.

In reality, this discussion is no longer useful or substantial. It is moot. Somewhat pointless.

Nobody here can change anything. Nobody here can resolve any concern being needlessly debated. Right and wrong mean nothing, since this is not the advocated forum for providing Apple Feedback.

That attachment behaviour changed with iOS 14 is well established. So too is that nobody here can undo this. In keeping with the intent of this community, workarounds have been offered.

Solutions have not. Undoing the change has not.

Feedback for Apple goes here >>> http://www.apple.com/feedback/

Nobody can stop contributions to the discussion if they follow the terms. Nobody can stop contributions that don't agree with your perspective on the issue.

Not the answer you may want to hear, but it is reality.

WAKE UP APPLE! FIX THIS OR MY AND PROBABLY THOUSANDS OF MACs AND IPHONES GO IN THE JUNK!!!!!!!!!!!!!!!

You are not screaming at Apple here. And your threat is meaningless to the volunteers that contribute here.

As has been shared numerous times, direct your concerns as below.

Feedback for Apple goes here >>> http://www.apple.com/feedback/.

Nonsense1025 wrote:

If you touch the photo while in the photos app you can select copy, share, delete … select Share and the. Select your email app and it will send as an attachment rather than embedded. Not perfect but it works.

The photo or photos are always «sen[t] as attachment[s]», never as «embedded». (There is no International Internet Standards compliant way to send photos in emails as «embedded».)

You need not take my, or anyone’s, word for this.

You can check for yourself by performing the definitive test found in my comment at https://discussions.apple.com/thread/251807601?answerId=254806789022#254806789022.

JoshuaVl wrote:

[SOLUTION]

Created an account just because this gave me the biggest headache.

You can send photos as attachments if you have the outlook app installed and signed in.

Just need to go to settings > Camera > Formats and change the format to "Most Compatible"

Then when you go to share photos from the Gallery just send them with Outlook (instead of Mail) and it adds it as at attachment.

Enjoy!

The photo or photos are always «sen[t] as attachment[s]», never as «embedded», with «Mail», as well as with «Outlook». (There is no International Internet Standards compliant way to send photos in emails as «embedded».)

You need not take my, or anyone’s, word for this.

You can check for yourself by performing the definitive test found in my comment at https://discussions.apple.com/thread/251807601?answerId=254806789022#254806789022.

However, «Outlook», on the receiving end, seems to be limited on what Standards compliant «attachment» methods it recognizes: So, the use of «Outlook», on the sender side, simply avoids the use of those Standards compliant «attachment» methods «Outlook» doesn’t seem to understand correctly.

bbdesign wrote:

I have this same issue. I want to transfer the files not embed them. Please provide the flexibility to do both.

If you are trying to address Apple, here, then you should use their designated Feedback Mechanisms: Product Feedback - Apple.

However, since Apple Mail is never sending images/pictures/etc. «embed[ed]», but always sending such as attachments—and the fact that there is only a very tiny subset of email clients (consisting of a single email client and its derivatives) that have any problem allowing users to perform bulk attachment operations (such as bulk-saves) upon received emails, even from Apple Mail—there is little, if anything, that Apple can do about this situation since Microsoft owns and develops the errant email clients.

The best path to a true fix is to provide Feedback to Microsoft. (After all, those errant email clients appear to have not been updated [in their underlying functionality] since sometime before 2010.)