it doesn’t need a specific thing to reproduce this issue. I have tried to mannualy create the MailSpring folder like you said in #769, but I think 126 & 163 mail server do not support adding a subfolder in the mail folders, and that’s what’s causing the sync process to crush.
6942 [2019-07-13 16:25:22.036] [main] [info] Identity created at 1562964813 - using ID Schema 1
6942 [2019-07-13 16:25:22.038] [main] [info] ------------- Starting Sync (salamandernewt@126.com) ---------------
6942 [2019-07-13 16:25:22.043] [background] [info] Marking all folders as `busy`
6942 [2019-07-13 16:25:22.044] [metadata] [info] Metadata delta stream starting...
6942 [2019-07-13 16:25:22.045] [background] [info] Syncing folder list...
6942 [2019-07-13 16:25:22.346] [background] [error] Could not create Mailspring container folder: Mailspring. ErrorNonExistantFolder
6942 [2019-07-13 16:25:22.384] [background] [error] Could not create required Mailspring folder: Mailspring/Snoozed. ErrorNonExistantFolder
6942 [2019-07-13 16:25:22.386] [background] [info] Syncing folder list...
6942 [2019-07-13 16:25:22.457] [background] [error] Could not create Mailspring container folder: Mailspring. ErrorNonExistantFolder
6942 [2019-07-13 16:25:22.493] [background] [error] Could not create required Mailspring folder: Mailspring/Snoozed. ErrorNonExistantFolder
6942 [2019-07-13 16:25:22.538] [background] [info] syncFolderUIDRange for INBOX, UIDs: 1 - 4294967296, Heavy: false
6942 [2019-07-13 16:25:22.582] [background] [critical]
***
*** Mailspring GenericException occurred during program execution:
*** {"debuginfo":"syncFolderUIDRange - fetchMessagesByUID","key":"ErrorNonExistantFolder","retryable":false,"what":"std::exception"}
***
6942 [2019-07-13 16:25:22.583] [background] [critical] *** Stack trace:
*** SyncWorker::syncFolderUIDRange(Folder&, mailcore::Range, bool, vector*)
*** SyncWorker::syncNow()
*** runBackgroundSyncWorker()
*** clone
***
Server address and port number are set according to the guidance provided by mail.163.com/
This line of sentences were shown after setting up the account.
“Mailspring encountered errors syncing this account. Crash reports have been sent to the Mailspring team and we’ll work to fix these errors in the next release. Try Reconnecting.”
Error Log
7667 [2018-03-19 20:21:06.255] [main] [info] ------------- Starting Sync (**************@163.com) ---------------
7667 [2018-03-19 20:21:06.258] [metadata] [info] Metadata delta stream starting…
7667 [2018-03-19 20:21:06.258] [background] [info] Marking all folders as busy
7667 [2018-03-19 20:21:06.259] [background] [info] Syncing folder list…
7667 [2018-03-19 20:21:07.302] [background] [error] Could not create Mailspring container folder: Mailspring. ErrorNonExistantFolder
7667 [2018-03-19 20:21:07.493] [background] [error] Could not create required Mailspring folder: Mailspring/Snoozed. ErrorNonExistantFolder
7667 [2018-03-19 20:21:07.494] [background] [info] Syncing folder list…
7667 [2018-03-19 20:21:07.710] [background] [error] Could not create Mailspring container folder: Mailspring. ErrorNonExistantFolder
7667 [2018-03-19 20:21:07.720] [background] [error] Could not create required Mailspring folder: Mailspring/Snoozed. ErrorNonExistantFolder
7667 [2018-03-19 20:21:07.910] [background] [info] syncFolderUIDRange for INBOX, UIDs: 1 - 4294967296, Heavy: false
7667 [2018-03-19 20:21:07.931] [foreground] [info] Connection does not support idling. Locking until more to do…
7667 [2018-03-19 20:21:07.940] [background] [critical]
*** Mailspring GenericException occurred during program execution:
*** {“debuginfo”:“syncFolderUIDRange - fetchMessagesByUID”,“key”:“ErrorNonExistantFolder”,“retryable”:false,“what”:“std::exception”}
The problem seems to be that nested folder is not supported by 126/163 email, but mailspring are trying to create such subfolder. Is there any way that user can specify the snoozed folder in settings?
Encountering the same problem in email.qq.com. Nested folders are not supported. I cannot create the folder manually. This brokes not only the snoozing feature but also the whole syncing process of the account.