Microsoft Exchange server (2010 or newer) users using the Outlook Web Access interface (web-based Exchange access), when attaching certain filetypes may get a Content-ID header supplied in the email headers even if there are no embedded files, only the attached files.
This will cause attachments from fMailbox's fetchMessage()/parseMessage() to be defined as inline and lose its filename and ability to be retained as a standard attachment.
Currently looking to see if there's a safe way to fix this without breaking other functionality.
Microsoft Exchange server (2010 or newer) users using the Outlook Web Access interface (web-based Exchange access), when attaching certain filetypes may get a Content-ID header supplied in the email headers even if there are no embedded files, only the attached files.
This is an issue with Microsoft Exchange 2010 when Silverlight is enabled on the Client Access Server. https://support.microsoft.com/en-us/kb/2400041
This will cause attachments from fMailbox's fetchMessage()/parseMessage() to be defined as inline and lose its filename and ability to be retained as a standard attachment.
Currently looking to see if there's a safe way to fix this without breaking other functionality.