#2621 new
Joachim Tingvold

Can't upload imported message to Gmail

Reported by Joachim Tingvold | August 6th, 2020 @ 12:17 AM

Hi,

Running MM Version 1.13.1 (5671) on Catalina 10.15.6 Beta 3. Have several accounts Gmail/G-Suite accounts added.

Imported some messages to MM (from Outlook) without errors. It uploaded/synced most of the messages to Gmail just fine, but it complains about this one email (for now). See logs below.

Why is this happening? What is the error?

Is it that "charset=utf-8" at the top of the headers? If so; why did MM import the message without complaining?

The exported file from Outlook was stored as plaintext .eml-file, and the "Full headers" below is the 1:1 content of that .eml file.

Logs:

00:04:11 Trying to connect to imap.gmail.com on port 993 (CFNetwork) without STARTTLS (required)
00:04:11 Resolved hostname (imap.gmail.com).
00:04:11 Prepare secure connection...
00:04:11 Successful connection.
00:04:11 Initiating secure connection...
00:04:11  Returned (4)...
00:04:11 Protocol version: kTLSProtocol12
00:04:11 S: * OK Gimap ready for requests from <snip>
00:04:11 C: I0 CAPABILITY
00:04:11 S: * CAPABILITY IMAP4rev1 UNSELECT IDLE NAMESPACE QUOTA ID XLIST CHILDREN X-GM-EXT-1 XYZZY SASL-IR AUTH=XOAUTH2 AUTH=PLAIN AUTH=PLAIN-CLIENTTOKEN AUTH=OAUTHBEARER AUTH=XOAUTH
00:04:11 S: I0 OK Thats all she wrote! <snip>
00:04:11 Retrieving password (keychain or user request)
00:04:11 C: I1 AUTHENTICATE XOAUTH2 <snip>
00:04:12 S: * CAPABILITY IMAP4rev1 UNSELECT IDLE NAMESPACE QUOTA ID XLIST CHILDREN X-GM-EXT-1 UIDPLUS COMPRESS=DEFLATE ENABLE MOVE CONDSTORE ESEARCH UTF8=ACCEPT LIST-EXTENDED LIST-STATUS LITERAL- SPECIAL-USE APPENDLIMIT=35651584
00:04:12 S: I1 OK <snip> authenticated (Success)
00:04:12 C: I2 CAPABILITY
00:04:12 S: * CAPABILITY IMAP4rev1 UNSELECT IDLE NAMESPACE QUOTA ID XLIST CHILDREN X-GM-EXT-1 UIDPLUS COMPRESS=DEFLATE ENABLE MOVE CONDSTORE ESEARCH UTF8=ACCEPT LIST-EXTENDED LIST-STATUS LITERAL- SPECIAL-USE APPENDLIMIT=35651584
00:04:12 S: I2 OK Success
00:04:12 C: I3 ID ("name" "MailMate" "version" "r5671" "vendor" "Freron Software" "contact" "mm-imap-id@freron.com")
00:04:12 S: * ID ("name" "GImap" "vendor" "Google, Inc." "support-url" "https://support.google.com/mail" "version" "gmail_imap_200724.13_p0" "remote-host" "<snip>")
00:04:12 S: I3 OK Success
00:04:12 C: I4 LIST "z Archive" ""
00:04:12 S: * LIST (\Noselect) "/" "/"
00:04:12 S: I4 OK Success
00:04:12 C: I5 APPEND "z Archive/Testfolder/Sent" (\Seen) "15-Nov-2019 14:49:53 +0100" {1000+}
00:04:12 C:     charset=utf-8
00:04:12 C: From: foo@example.com
00:04:12 C: Mime-Version: 1.0 (1.0)
00:04:12 C: Date ...
00:04:12    <1000 bytes> 
00:04:12 C: ... 8yere kvote, i alle fall ut november og desember =
00:04:12 C: m=C3=A5ned.=20
00:04:12 C: 
00:04:12 C: --=20
00:04:12 C: Joachim
00:04:12 S: I5 BAD Invalid Arguments: Unable to parse message
00:04:12 Error: Server response: “I5 BAD Invalid Arguments: Unable to parse message”.
00:04:12 Error code: 1000
00:04:12 Failed action (1008). Reset observed read/write timeouts: 8/8

00:04:13 Handling reply
00:04:21 Terminating non-running connection...
00:06:21 Running action
00:06:21 Sending request (695)
00:06:21 Handling request
00:06:21 Trying to disconnect nicely (30)...
00:06:21 C: R6 LOGOUT
00:06:21 S: * BYE LOGOUT Requested
00:06:21 S: R6 OK 73 good day (Success)
00:06:21 Clearing connection to imap.gmail.com
00:06:21 Ready to run action (retry count: 0)
00:06:21 Disconnecting
00:06:21 Clearing connection to imap.gmail.com
00:06:21 Completed action (3). Observed read/write timeouts: 8/8

Full headers:

 charset=utf-8
From: foo@example.com
Mime-Version: 1.0 (1.0)
Date: Fri, 15 Nov 2019 14:49:53 +0100
Subject: <snip>
Message-Id: <snip>
Cc: <snip>
To: <snip>
Content-type: text/plain;
    charset="UTF-8"
Content-transfer-encoding: quoted-printable

<some text>
... h=C3=B8yere kvote, i alle fall ut november og desember =
m=C3=A5ned.=20

--=20
Joachim

Comments and changes to this ticket

  • Joachim Tingvold

    Joachim Tingvold August 12th, 2020 @ 06:01 PM

    Can confirm that removing charset=utf-8 from the first line of the .eml file fixes the issue (i.e. MM will not complain anymore).

    Out of ~3k email exported from Outlook, only 10 of them (all in the Sent folder) had this issue. It was consistent that the first line in the .eml contained charset=utf-8.

    Not sure why it's only present in so few of them, or why MM imports them just fine without complaining (it's only when it tries to upload/sync them that it fails).

Please Sign in or create a free account to add a new ticket.

With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.

New-ticket Create new ticket

Create your profile

Help contribute to this project by taking a few moments to create your personal profile. Create your profile ยป

Mac OS X email client.

Shared Ticket Bins

People watching this ticket

Pages