The workaround still needs to be accepted by the people responsible for maintaining libetpan though, and will require that MailCore2 integrates this new version of libetpan and in turn requires email client authors to update their MailCore2 to that version. This workaround should provide a temporary reolsution of the issue until Apple fixes it on their side. In the mean while, I implemented a workaround in libetpan, which is used by MailCore2 to communicate with IMAP servers. I've opened an issue with Apple to this end but their track record responding to these is not great. The issue is on Apple's side and should ideally be fixed by them. This in turn results in some clients crashing or getting stuck in the synchronization process because they keep retrying the UID FETCH and it keeps faling. This causes the parser to fault and the fetch command to fail.

In short, some messages in iCloud's IMAP reply to an UID FETCH request contain ENVELOPE's that have a Message-ID containing unescaped double quotes.

(I don't just add it as an iCloud account because I want to specify a different outgoing server and address, Apple unfortunately. I use IMAP (.com) to access my iCloud account using Mail on an iPhone, Mail on a Mac and Thunderbird on a PC. Hi all, I would like to inform the devs that I discovered an iCloud server issue that affects many email clients (including all currently using MailCore2) and causes them to crash or not synchronize properly when used with iCloud IMAP accounts.įor an example of this issue in a client utilizing MailCore2, see The Eternal Sync Bug As I said, I changed the password using, but the IMAP server is not updated.

Icloud imap server