On Dec 31, 2015, at 05:06, Yvan KOENIG <email@hidden> wrote:
All the messages behaving wrongly have only JPEG or PDF attached files.
When I look at their properties, in all messages I found : Content-Type: multipart/mixed; … In message behaving wrongly I saw: Content-Type: APPLICATION/PDF; -- SCAN_2015_12_08_162807.pdf they have a property : Content-Disposition: ATTACHMENT;
I'll have to test with a PDF next.
My current iCloud test is a 400+K jpg.
It does NOT have ANY header that says attachment.
The first Content-type header is:
Content-type: multipart/alternative;
But there are several, since there is mixed content (text & jpg).
Here's the jpg-related stuff:
Content-Transfer-Encoding: BASE64 Content-Disposition: INLINE; filename="Screen Shot 2015-12-30 at 12.13.57.jpg" Content-Type: IMAGE/JPEG; name="Screen Shot 2015-12-30 at 12.13.57.jpg"; x-mac-hide-extension=yes; x-unix-mode=0644
As I suspected this is registered as INLINE content.
I'll test with a PDF in a bit to see if it's the same.
While testing I found another terrible bug:
If I get the SOURCE of this problematic message with AppleScript it does not produce the same source as Mail's 'Raw Source' command.
Get source using AppleScript: 5015 characters Get source using Mail's Raw Source Command: 620031 characters
|