|
FastMail Forum All posts relating to FastMail.FM should go here: suggestions, comments, requests for help, complaints, technical issues etc. |
|
Thread Tools |
18 Sep 2018, 01:11 AM | #1 |
Cornerstone of the Community
Join Date: Jul 2003
Posts: 692
|
Anyone else seeing failure of FM client to detect an .MHTML attachment from Gmail?
Gmail shows the message fine https://i.imgur.com/9C7jnSR.png
But Fastmail pretends there is no attachment https://i.imgur.com/cA5rATu.png . In Chrome and Firefox. Anyone else see this? This is a rather serious misrep of the message content by Fastmail. |
19 Sep 2018, 02:54 PM | #2 |
Intergalactic Postmaster
Join Date: May 2004
Location: Irving, Texas
Posts: 8,929
|
MHT and MHTML transfer as email attachment is not reliable
".mht" and ".mhtml" attachments are treated in different ways by various email systems.
Last edited by n5bb : 19 Sep 2018 at 03:07 PM. Reason: Added more results sending between various email systems |
20 Sep 2018, 03:22 AM | #3 | ||
Cornerstone of the Community
Join Date: Jul 2003
Posts: 692
|
Thanks for that info.
Quote:
Content-Type: multipart/related; name="Chris's Home Page.mhtml" Content-Disposition: attachment; filename="Chris's Home Page.mhtml" Content-Transfer-Encoding: base64 X-Attachment-Id: f_jm2c5v5b0 Quote:
Still I'd be interested to hear if anyone else gets this. Again, I see different in what Fastmail sends for MHTML: Content-Disposition: attachment; filename="Chris's Home Page.mhtml" Content-Id: <1536949649.3564772.d2b39525c9c2d89d8243885531907724a2abcc08.636CFA99@content.messagingengine.com> Content-Transfer-Encoding: 8bit Content-Type: application/octet-stream; name="Chris's Home Page.mhtml" |
||
20 Sep 2018, 08:35 AM | #4 |
Intergalactic Postmaster
Join Date: May 2004
Location: Irving, Texas
Posts: 8,929
|
My point is that Outlook.com to Fastmail works fine. It’s the Gmail outbound that seems to create an odd message format which can’t be read by Fastmail or Outlook.com. I sent a message from Gmail with To addresses at Fastmail and Outlook.com (one message with two recipients) and they were both received in a way which I think indicates that they were not properly parsed. Each receiving system interpreted the Gmail MHT attachment differently and neither was correct.
The problem is the Content-Type in the MIME block encapsulation and the MIME formatting. Look for the Content-Type header down at the start of the MIME block, not in the main contiguous header list before the first blank line. Both Fastmail and a Outlook.com can’t parse what Gmail is sending, leading to what both you and I reported. I found this old complaint; https://support.google.com/mail/foru...Gm4nj4M/?hl=en I created my MHT and MHTM files using both of these methods and they both work as I described:
Bill |
20 Sep 2018, 11:51 PM | #5 | ||
Cornerstone of the Community
Join Date: Jul 2003
Posts: 692
|
Quote:
Quote:
Chrome Save. Gmail web interface. |
||