C
Chris Pink
Guest
I see threads on the internet dealing with this since 2010. Ten years later it's time someone at Microsoft paid attention.
The issue;
If Outlook 2016 receives a message with inline attachments (the main sender being Apple Mail -any version) it renders that messages as <message><inline attachment><more message as attachment><inline attachment><more message as attachment>... repeat. Those inline attachments could be signatures in an email chain, quickly rendering the chain unreadable.
There is an Apple workaround (if you stumbled on this thread). Delete all unnecessary inline attachments and put necessary attachments at the end of the email. If your signature is a linked file you won't have this issue, if it's embedded as attachment you will.
I know for a fact this is an Outlook rendering issue because I have the same message in an IMAP box which can be read without this issue but Horde, Roundcube, Thunderbird... It will, of course, be perpetuated if the Outlook user replies or forwards the message once the attachments have been created.
So how about a solution from Microsoft?
Continue reading...
The issue;
If Outlook 2016 receives a message with inline attachments (the main sender being Apple Mail -any version) it renders that messages as <message><inline attachment><more message as attachment><inline attachment><more message as attachment>... repeat. Those inline attachments could be signatures in an email chain, quickly rendering the chain unreadable.
There is an Apple workaround (if you stumbled on this thread). Delete all unnecessary inline attachments and put necessary attachments at the end of the email. If your signature is a linked file you won't have this issue, if it's embedded as attachment you will.
I know for a fact this is an Outlook rendering issue because I have the same message in an IMAP box which can be read without this issue but Horde, Roundcube, Thunderbird... It will, of course, be perpetuated if the Outlook user replies or forwards the message once the attachments have been created.
So how about a solution from Microsoft?
Continue reading...