Stuck in "Syncing your Mail" forever #158
Comments
|
I'm encounter the same problem on Windows 10 Pro, Mailspring versions 1.0.0, 1.0.1, 1.0.2, 1.0.3, 1.0.4, and 8 accounts (2 * GMAIL, 2 * YAHOO, 2 * OUTLOOK, 2 * IMAP). |
|
Having the same issue on Arch Linux. I have two email accounts set up. One was synced with no issues (outlook) and another (SMTP) always getting "Encountered an error while syncing". |
|
Same as well. |
|
I also encountered this issue. Arch linux + Mailspring 1.0.4 with 1 GSuite Account 200k+ emails |
|
I occasionally had reset the mail cache and kill the sync client because of this. On the other hand, there is nothing useful related to this on the mailsync logs. |
|
I get this as well, and had it with Nylas as well, but with Mailspring I get the added errors as above, the red "Encountered error while syncing". |
|
@bengotow are you aware of this issue ? |
|
Upgrading to 1.0.5 fix this issue for me |
|
I have the same issue. Arch Linux, Mailspring 1.0.5. I have an Office 365 account and the syncing is always stuck at the drafts folder of this account (that is, only the drafts is blinking after expanding the syncing status) and CPU usage is high. The log for this account is like this:
|
|
I think both of you are right:
|
|
I still have it on my outlook account on 1.0.5 |
|
Have same problem on one of gmail accounts. It was working OK until 1.0.5. Syncing forever, and sometimes drops Error syncing. KDE Neon. |
|
Hey folks - I'm pushing a fix for the "Unable to fetch body for message "Deleting..." (Drafts UID 0). Error ErrorFetch" issue, and that may resolve this in some scenarios. For other accounts that are syncing forever, could you look in the mailsync logs (in ~/.config/Mailspring/mailsync-***.log on Linux, ~/Library/Application Support/Mailspring on macOS) and see if you're seeing It looks like there's a scenario where if a folder can't be fetched consistently, it'd just stay in "syncing..." state forever. It'd be really useful to know what your IMAP server is responding with (eg: |
|
@bengotow seems like I have this problem |
|
I am getting this error in log: 3526 [2017-10-19 15:05:56.252] [foreground] [info] Idling on folder [Gmail]/All Mail *** A C++ exception occurred during program execution: 3526 [2017-10-19 15:05:56.777] [background] [critical] *** Stack trace (line numbers are approximate): |
|
31482 [2017-10-19 19:55:25.464] [metadataExpiration] [info] Scanning for expired metadata *** A C++ exception occurred during program execution: 31482 [2017-10-19 19:55:38.162] [background] [critical] *** Stack trace (line numbers are approximate): |
|
Not sure if this will help much, no errors reported, but it just keeps looping the same few emails: More of the same: https://pastebin.com/pNfLUxud edit found better log info from the log file: (FYI: I've removed/replaced some text like email Subject) |
The o365 account gets stuck syncing Drafts (same as other users above). High CPU usage. The rest of my folders are solid green on this account and my GMail accounts. Here's a chunk of what's in the relevant log file: |
|
Still have the problem with 1.0.6 @bengotow are you aware ? |
|
Syncing my mailbox with 1.0.6 is endless forever too :-) FEDORA 26 Thank you so much! David |
|
Just to confirm, 1.0.6 solved the "Unable to fetch body for message 'Deleting...' (Drafts UID 0). Error ErrorFetch" issue for me. Thanks bengotow. |
|
In my case, it was not solved at first, but I reset my local cache and since then I had a few successful synchronisations after restarts or shutdowns . |
|
Same here, Fedora 26, GNOME Shell 3.24.3 , Mailspring Both accounts sync successfully after resetting the mailcache. After a restart of Mailspring the sync gets stuck and hangs on The only error I get in the mailsync logs after: This is how it looks before failing:
Could it be that folder with the |
|
v1.0.6 has seemed to have solved it!!! It took a while, and I saw the error I had previously a few times: "Encountered error while syncing". But after a few close/reopens, and time past, the "Syncing your Mailbox" has gone! Amazing work, and amazing fixes done to this amazing email client! |
|
I still have this on 1.0.7 |
|
me too, I remember Nylas Mail was indexing my email for at least 8 hours, but it finished eventually. Mailspring however promps an error after a minute or two of indexing |
|
To be completely honest, I found Mailspring to be the best option for me, especially if you don't like the other such as Thunderbird, Evolution or Geary. |
|
Mailspring seems great but if I cant get my mail then it is of no use as a mail reader. |
|
Hey folks—this issue should be largely resolved in 1.0.9 which will ship tomorrow. Basically, Mailspring would get stuck "syncing your mail" indefinitely if one or more of the recent messages in your account were permanently "corrupt" or otherwise un-retrievable. (Mailspring pre-fetches the contents of the last three months of your email to build an offline search index.) It turns out, this happens occasionally, even for large providers like Gmail. Starting in 1.0.9, Mailspring will make one attempt to fetch the body of a message for indexing, and if it fails, it will wait until you click that message to try to fetch it again. This means that any rouge messages your mailserver cannot provide or badly corrupted messages that crash the sync worker won't stop the app from completing its pass through your mailbox. There are a handful of other ways "syncing your mail" can get stuck forever but I expect this is the biggest one by a good margin. Stay tuned— |
|
I have the same problem on macOS. It get stuck on "syncing your email" with ~20% CPU usage (which is a lot). Reloading the app via the developer tab seems to solve this. The log seems to indicate that the syncing loop completed but I still see "syncing your email" on the bottom left of the app. 19611 [2017-12-13 10:37:58.329] [background] [info] Syncing folder list... |
|
Restarting in dev mode will start over and do a fresh sync. |
|
It looks like that sync still get some problems， I still get lots of log info like And some actions such as P.S my mail service is a coremail based service. |
|
Cannot sync my gsuite account. Here is my mailsync log: *** A C++ exception occurred during program execution: 1003 [2018-05-22 11:10:56.564] [metadata] [critical] *** A C++ exception occurred during program execution: 1003 [2018-05-22 11:10:56.564] [background] [info] Fetching XOAuth2 access token from Gmail for fcdf4968 |
|
Howzit guys, I had the same problem and literally rebuilt the cache about 10 times. It finally started working... This is with Google Business Suite so I'm not sure if that had any effect on why it was always stuck on 14%. I'm using Ubuntu 18.04 and |
|
I tried caching a few times. It kept saying 'Scanning messages'. However, every time it got stuck on different folders. I have Mailspring 1.4.2 installed via snap on Ubuntu 16.04 Below a selection of the log-file after some time of scanning messages, when warnings appear: As far as I could find there are 2 errors:
@bengotow, please let me know if I need to try out anything else or if you need more information. |
|
Hello! I have this log on macOS: Thanks a lot! |
Thanks, I had the same experience. |
|
Same issue here, I had the scanning messages info forever and CPU usage is high. From the logs: Turns out, I had created invalid directories on the mail server while experimenting with procmail filters. Deleting these directories solved the problem for me, no more CPU usage when idle. Edit: the directories were invalid because they had the format |
|
I have the same problem. This is the log that keeps repeating every 2 minutes: It's pretty weird because judging by the log it doesn't try to sync the non-existent folder continuously. However in the GUI it says that this exact folder is being synced and CPU usage is very high: 20 - 30% which makes the program unusable. |
|
This same thing happens to me too. Ubuntu
It appears, however, that all new emails are being received, and all sent emails are arriving at the correct users inbox. |
|
I am on Mint 19.2, and I installed Mailspring 1.7.2 two days ago. I have four O365 accounts. Three sync perfectly fine, the other does not. The one that does not does receive new mail, but it eats up CPU trying to get the other folders synced up. I've checked that I have no folders with dots in the name, and I've also gone into OWA and emptied deleted items, etc. I have tried to rebuild cache several times and I've deleted and re-added as an IMAP account all to no avail. Here is a current log snippet:
|
|
I ran into the same issue. After checking the logs, I found that Gmail OAuth Tokens were revoked for some security reasons. So MailSpring didn't throw any error or didn't ask to reauthenticate. Reauthenticating the accounts worked for me. |
|
I had the same problem of tokens being revoked. I had to re-authenticate and then rebuild the cache to get it working. |
|
Just hit the same issue. It would be good if Mailspring would notify the user about that |
|
I'm hitting this issue with an insanely long inbox name: |
|
I am also getting syncing your mailbox indefinitely. And this ticket has been open for about 4 years now. When will we see a fix? |
|
Honestly, the issue never reappeared for me since February. Looks like the main problem (processing OAuth errors from GMail and other providers) has been fixed since then. So, probably, you better check the logs, and maybe raise a new, more focused issue about the actual underlying problem? |
|
This issue has been mentioned on Mailspring Community. There might be relevant details there: https://community.getmailspring.com/t/mail-getting-stuck-in-outbox/60/2 |
|
It's difficult to know whether this issue is still active because of the same causes, or new ones. If you're experiencing this, please open a bug report on our new Discourse community (https://community.getmailspring.com) or upvote an existing bug report there. We're closing and locking the issue here as part of this migration. We hope to see you on Discourse soon! -The Mailspring Team |
and others
What operating system are you using?
Arch Linux
...
What version of Mailspring are you using?
1.0.4
...
Bug?
Is the issue related to a specific email provider (Gmail, Exchange, etc.)?
ALL
...
Is the issue reproducible with a particular attachment, message, signature, etc?
...
--
Note :
#91 This issue seems to be related. But I don't have high memory usage. So I opened new issue.
The text was updated successfully, but these errors were encountered: