
This article might shed some light on this: The Importance of Content-Type HTML Character Encoding in Email The emails that got this error had Norwegian characters, without setting a charset in the Content-Type header. I suspect the non-utf8 content without charset specification error might have something to do with the Content-Type header. Error: non-utf8 content without charset specification I just left them, as they were not important. These emails were all left on my previous IMAP mail server, since the sync failed. To folder INBOX: 4259 NO mime: duplicate parameter name Hm, so since it stopped at message 175, maybe I should try batches of 150.Įrr 4/18: - msg INBOX/4223 could not append ( Subject:, Date:, Size:, Flags: ) I sent an email to ProtonMail support, and after about a day and a half I got a reply Ĭan you try importing the messages in smaller batches (folder by folder or set a specific import date) and let us know if it will work? The ProtonMail import tool just stopped at message 175

And annoyingly those 175 messages were now duplicated on my ProtonMail account. Same thing, it got a bit further, but not a lot. I waited for about 15 minutes before figuring out that it wasn’t going to keep going. It looked good at first, then it just stopped - on message 175 of 9602. Everything was looking good, then I started the sync. I logged in with my ProtonMail account, clicked “Import from account” and signed in to my previous IMAP mail server. Since there is, currently, no Linux version, I installed it on my virtual Windows 10 machine. Naturally I went and downloaded the import/export tool. Update, more errors migrating my wife’s email.Error: non-utf8 content without charset specification.Time to import my decade of emails into my ProtonMail account… After giving the free account a quick look, I upgraded to a paid account and moved two custom domains over. I recently signed up with ProtonMail - I wanted something secure, able to handle PGP encryption and with a nice webmail interface and Android app.
