Fresh email very slow to download/sync

New email in the AM, or any time of day takes 5 to 10 min to hit my eMClient inbox. It shows up in ATT/Yahoo wembail near immediately. Once I see it in inbox, it’s another 2-3-4 min before the body of the email fills in with content. I do have slow internet at 7meg, but it did not used to download this slow. This is new in the last 2-3 months. I’m on eMClient v7.xxxx latest rev.

Could this be a function of how my large number of email messages and IMAP folders?

I have base account “A” with sub account “B”. A forwards all email to B. A is never used since the folder struct is corrupted and ATT/Yahoo won’t fix it, so “B” is my daily acct.

A has 21,600 emails since it’s too tedious to delete them by clicking boxes with webmail, and B has 6,600 messages (I’m a hoarder). B also has probably 75+ IMAP folders and 200 local folders.

Is there a known upper limit on the IMAP message/folder count before it slows down syncing of incoming email? Or is this even the problem?

Thanks for any thoughts.

PS: I know I could clean up the old A inbox with the added dexterity of eMC vs webmail, but the free v7 only allows two accounts at one time. 1) my main B account and 2) the cardav/caldav acct for Apple contacts and calendar syncing. I do have a 3rd disabled acct. for A and might enable that, disable B and do some housekeeping, but for massive deletes eMC takes forever and I’m never sure it it’s working or got lost and hung up.

7.2.xxxx means which version? 7.2.38732 was released about a week back. Check in the Release History to download it if that is not what you have. If you are just using eM Client for home use, you might also consider trying out the version 8 beta that is listed there as there are huge improvements in the new version.

But one possibility that might help without installing anything new is to remove the Yahoo! account from eM Client, then add it again. That will give a fresh cache of the account folders and may make a difference.

OK, I’m on 7.2. 34711.0. I assumed I was on latest since I’m used to update reminders and have not seen any. I will update. Also, been trimming back the Inbox substantially, and emptied Inbox for the primary account that “feeds” the sub-account I use daily (the one that’s slow). Then, in no improvement I will remove/re-install the Yahoo acct as you advise.

A question on archiving to free up IMAP space. My archive folder is in the main IMAP account, so when I archive to it, the data is still on the server, right? How’s that reduce the IMAP footprint?  Is it better to manually “move” email to a local archive folder of my creation? I’ve done this in the past, then just delete the email from Inbox.

Thanks for the fast reply!

There is a difference between archiving as defined by an email provider, and Automatic Archiving as implemented by eM Client. Normally archiving with the provider simply moves messages from one folder to another, so that they are separated from the main body of messages. Automatic Archiving as implemented by eM Client moves messages from the server to a local folder thus reducing storage on the server.

OK, but then why is the archive folder under my account name and not below under  local folders? When I click “properties” Move and Delete are grayed out indicating it’s an eMC generated system folder. Local has no archive folder.  Or is a “special” folder treated as local under the hood.

I did a bunch of clean up mentioned, but can’t tell if it’s helped yet. Jury is still out.


Like I said, there are two types of archiving in eM Client. If you use the archiving by right-click Move to Archive (Ctrl + Shift + A) that will move the message to the Archive folder within your account folders. This is a server side archive. You cannot delete or move this folder as it is a server system folder just like Inbox or Sent.

If you use eM Client’s Automatic Archiving, this will move the messages to a Local Folder Archive and remove them from the server. You also cannot delete or move this folder as it is a system folder created by em Client. It will only be visible after the first Automatic Archive has been performed.