135      iPhone_iPad_Mac_apple

Mail "attachment anti

Problems: my paying customers cannot see or receive correctly the attachment files I send with Mail if Clive Galenis Anti-inline plugin not attached

Hi!

I have had this problem for ages (since Snow Leopard or other cat) and yet it appears again every single time when Apple upgrades its operating system. The problem is that the attachement files sent with Mail do not appear correctly, do not appear at all or do not go through the systems my clients ate using. The reason is Mails way of inlining the attachements and "Show as icons" does not solve the problem at all. The only thing that solves the problem is "Anti Inline-Plugin" that Mr. Galeni provides https://clivegaleni.com/os-x-mail-anti-inline-plugin/ but when anytime Apple upgrades its system the Anti-inline needs upgrading too, and when waiting the upgrade I´m in deep trouble - like now.

So what to do? I have been using Mail since the Mac OS X and very painful question is should I stop using Mail and change the mail client - or is there any other way to avoid the "Mail Inline-problem"?

A problem for years. Still a problem. Maybe a problem forever. I do not understand why Apple refuses to change the programming.

Why won't all other email client developers (ok, it's just Microsoft) write an email client that supports email standards?

A problem for years. Still a problem. Maybe a problem forever. I do not understand why Apple refuses to change the programming.

The only solution: zip all attachments. Or change to another mail client. Or accept the bug and let mail keep people pointing their fingers on you and shaking their heads why you still use Apple software. Pain in the a..

A problem for years. Still a problem. Maybe a problem forever. I do not understand why Apple refuses to change the programming.

Why won't all other email client developers (ok, it's just Microsoft) write an email client that supports email standards?

Zipping won't do if I have to send .jpg files to certain media systems that demand .jpg files. I willl try Postbox or Thunderbird instead.

It's not about only Microsoft - try sending to gmail more than one image and see what happens.

And what "standard" is Mails way of inlining?

It's not about only Microsoft - try sending to gmail more than one image and see what happens.

I have and gmail has no problem displaying the attachments. I checked both on the Gmail web portal and on the Gmail iOS app. I tested with just images and with images interspersed with captions and text. Google had no problem displaying the message as sent.

And what "standard" is Mails way of inlining?

There is no such thing as "inlining." An attachment is an attachment.

In standards-compliant email, you can add "hints" to your message that tells the client how the sender intends it to be displayed: font, color, size, and whether the attachments should be viewed inline or not. The hint for attachment handling is "content-disposition." There are about a dozen options for this. The two that seem most popular are "inline" and "attachment." Inline means show it automatically with the message, as it appears in the order of components in the message. Attachment means that it is not part of the message and should be displayed separately.

There is nothing that forces a client to follow any of the hints provided.

There is no difference between an attachment that has been marked as inline and one that has not. It is up to the client receiving the message to either follow the inline directive or not. It doesn't change how the attachment is encoded into text so that it can be sent via the email protocol.

Here is an Inline header:

--Apple-Mail=_8BCAB9C8-741E-46DF-8258-8B5372DF99DD

Content-Transfer-Encoding: base64

Content-Disposition: inline;

  filename=IMG_0777.jpeg

Content-Type: image/jpeg;

  name="IMG_0777.jpeg"

Content-Id: <9549C653-DD97-4772-A900-2D62AA4A15B9>

<base64 encoded file data>

Here is an Attachment header example:

--Apple-Mail=_8BCAB9C8-741E-46DF-8258-8B5372DF99DD

Content-Transfer-Encoding: base64

Content-Disposition: attachment;

  filename=IMG_0777.jpeg

Content-Type: image/jpeg;

  name="IMG_0777.jpeg"

Content-Id: <9549C653-DD97-4772-A900-2D62AA4A15B9>

<base64 encoded file data>

Notice that there is no difference short of that Content-Disposition value. All Microsoft has to do is ignore the disposition and display the attachment as they want, but their software engineers can't seem to figure it out.

If you Initially change the Font or color in the message, and use the option to add attachments to the end of the message, it will sometimes fool Outlook into rendering the attachments correctly.

To make changing the Font easier, some have set their signature font to be different than the default display font, and in a font that they want the message to use, then when a new message opens with the signature, put the insertion point at the beginning of the Signature's first line and start typing the message. It will then have the font changed.

..well, I'd be glad to hear why everything works fine if Clive Galenis "Anti-Inline plugin" is installed:

https://clivegaleni.com/os-x-mail-anti-inline-plugin/

Except now again, when upgraded Sierra denies installing the current version of that plugin. And why an earth could not Apple provide us similar plugin to help us solve our problems?!

Anyway, I'll test Postbox tomorrow with the very-very-important client..

Cheers,

Petteri, photographer

PetteriKivimäki wrote:

 

..well, I'd be glad to hear why everything works fine if Clive Galenis "Anti-Inline plugin" is installed:

 

It works because he rewrites the encoding such that Microsoft can understand it. So, he chases Microsofts poor coding to rewrite the message to meet Microsoft "standards," not internet email standards.

PetteriKivimäki wrote:

 

It's not about only Microsoft - try sending to gmail more than one image and see what happens.

 

And what "standard" is Mails way of inlining?

FWIW, I sent an email with 3 images from Mail to my Gmail account and this is what I saw happening…

the bottom image was a wallpaper I cropped so it wouldn't take up space on here.

The bottom line is, it sent and was received just fine by Gmail.

Oh yeas, it works. I did try several months ago with my colleague and the we both had problems with multiple images; one image went ookoo but sending more images made a mess.

But what is important - the Postbox does the job! Juhuu, the images that I send to the system on the biggest finnish media group go through and also the persons using Outlook will the the images so I'm able to do my work with confidence. I'm happy with that even if I have to pay 40€ for Postbox.

I will not bother Apple anymore with the my "non-standard need"..

Cheers,

Petteri

Can't tell you what you guys did "several months ago" but as you can see sending several images worked just fine for me. I also forwarded the email from my Gmail account to my Outlook account and it arrived just fine as well.

Glad you found yourself a solution though.

I don't know if you're still searching for a solution, but when I got the same problem like you that the  "Anti Inline-Plugin" from Mr. Galeni didn't work anymore I found this amazing tool: https://code2k.net/products/mailpluginfix/. It saved my life :-)

Have you tried with Tamer?

Thanks

aktivomat,

Thanks for the link to mailpluginfix. It worked great in Mail 10.3/Sierra 10.12.4.

最後更新：2017-08-19 05:31:13

  上一篇： Photos export to SD/Flash OS X 10.12.6

  下一篇： Is it legal to install MacOS on PC