Since eM Client 7, we have created a completely new database structure for more efficient data storage, so the data cannot be just loaded from the old database as was possible in the past.

To migrate your data manually please use the Menu > File > Import.. > Import from eM Client 6 option.

If you upgraded from eM Client 7, the database should be upgraded automatically, since eM Client 8 keeps to the same model and can upgrade these files automatically, no migration is needed.

In this case, the issue might be with your storage location - make sure that the storage folder in Menu > Settings > General > Storage is pointing to the correct location where your eM Client 7 database was stored.

• Turn off Conversations (Menu > View > Conversations > Disable Conversations)
• Close eM Client
• Open RUN function from the Start menu
• Run the command "C:\Program Files (x86)\eM Client\MailClient.exe" /dbrepair
• (For MS Store version of eM Client the command is eMClientStore.exe /dbrepair )
• Wait until the database check is completed
• Turn eM Client on
• You should then be able to set any Conversations setting you prefer.

For IMAP and Exchange accounts only:

• If that doesn't help, please right-click on the folder that the messages are in, select Properties > Repair and click the Repair button.
• This will prompt the resynchronization of this folder from the server and should reset its data.
• You can also try removing your account from eM Client and then adding it again in Menu > Accounts.

Please note that all locally stored data will be lost, but if you have your data on the server, that shouldn't be of concern.

You can make a backup just to be on the safe side through Menu > Backup.

• go to Menu > Tools > Settings > General > General
• Scroll to Operations window
• uncheck the option to Show window when an error occurs

Last update on this post has been made on May 12th, 2017

That is why the subfolders created in eM Client can disappear after synchronizing with the Yahoo server. The server will clear them out.

We suggest only using top-level folders in Yahoo to make sure no messages get lost.

We, unfortunately, do not support export to PST files and it is not a feature our developers plan to implement in the future since the file is specific for Outlook only.

Instead, we export messages into EML files which is a widely accepted standard file format for email messages. Export your messages using the Menu > File > Export option.

You can find converters from EML to PST online.

In eM Client 8.1 we added a workaround in the Menu > Accounts section under the IMAP tab.

Under the Tag section you will find the Show Important tags option and you can select to either show it based on Gmail's settings, Always show it or to Never show it. 

LEGACY OPTIONS

In older versions, you need to go to your Gmail settings in your web browser and create a filter that will remove the Important label automatically from each message.

To achieve this, go to Gmail webmail, open Settings > Filters and Blocked addresses. Create a new filter where all messages received by your email address will never be marked as Important.

Screenshots of such filter setting can be found below:

Note: You can either apply the filter directly to all previous conversations or open the Important folder/label and manually select all messages to remove the Important label

So when you try to activate the license after the eM Client trial, you will encounter an error message instead, because the request sent from Windows XP, unfortunately, doesn't arrive at our licensing system.

A problem has occurred when contacting the licensing server:

The underlying connection was closed:  an unexpected error occurred on a send.

We have created a compatibility version for XP which allows the connection, but please be aware that this version will not be updated in the future.
Please send us a message to info@emclient.com if you are interested in this version.

Copy it into the eM Client folder in C:\Program Files (x86).

This config file should then enable the program to detect the needed credentials for your proxy.

However, this solution only works for eM Client up to version 7.2, not for the newly released eM Client 8.

If you are using a different proxy solution or newer version, you need to either arrange for eM Client to get the credentials using a 3rd party program (e.g.Proxifier) or add eM Client to exceptions.

[IMAP] Cannot open folder ... ([Clientbug] Select additional arguments found after last expected argument)

[IMAP] Cannot open folder ... (unrecognized extra arguments to SELECT command)

We have analyzed the issue in detail, including IMAP logs provided by some of our users and our developers concluded that it's a server issue that can't be fixed on our side, unfortunately.

It seems that the BT updated the feature on their back-end servers but didn't adapt the proxy servers which report the errors. It seems that BT is continuously changing the settings and that's why sometimes the account reset helps but later on the issue reappears.

Some tweaks to the settings seem to help though, these are solutions provided by our users:

"A bit of research reveals that BT uses two versions of mail - BT email and BT Yahoo email. See here

http://bt.custhelp.com/app/answers/detail/a_id/57483/~/im-not-sure-if-ive-got-bt-mail-or-bt-yahoo!-mail

By logging into the desktop version of BT email you can see which version you have got. It transpires I have BT Yahoo mail. I have set the email up using BT Yahoo settings and it is now working again. Something must have changed on BT's side. So if you get this query again this should be the solution."

Another tip that seems to help is filling in the manual option for credentials under the IMAP tab in Menu > Accounts. Open this section and open the IMAP tab for your BT account. Insert your credentials into "these credentials" fields and save the settings.

Also, if your username is set anywhere as just the user part, make sure to change it to full address - ie. if the full email address is example@btinternet.com make sure the user name is set to "example@btinternet.com", not just "example".

We have seen this often happen with Avast, Kaspersky and AVG, though others could cause the same problem.

Adding eM Client to exceptions in these apps and disabling any mail shields should resolve the issue.

We also recommend reporting this to the provider of your security app, so they can update their records and not block eM Client in the future.

To do this click on the down arrow v on the right side of the search bar and deselect Use server search if available. Also, while you’re in this search menu, double check that you’ve selected the correct search parameters, such as searching in All folders and searching for your keyword in the Subject, Sender, Recipients, Body and Attachments fields.

Read more in our blog: Search Like a Pro in eM Client

Alternatively, you can run the eM Client application with a disabled indexer by pressing the Windows key and R key at the same time and entering the following command:

"C:\Program Files (x86)\eM Client\MailClient.exe" --disable-attachment-indexer

(Unfortunately, there's not currently a similar workaround for Mac OS)

We’re also working hard on fixing the speed issue and bringing you better performance with future updates.

When you disable them, the native notifications for the eM Client Application take over and are more reliable.

[Google Contacts]Uploading item(s) to folder 'account@gmail.com/Contacts' failed due to the following error: Execution of request failed: https://www.google.com/m8/feeds/contacts/default/full (Invalid request.)

The first thing you should know is that most of the "folders" of Google's mail, contacts, tasks, calendar, etc. are just a complex Tag system that's pretending to be folders.
When objects (messages, events, contact entries etc.) are without a Tag to sort them somewhere, strange things and errors start to happen. Understanding that will help you understand the rest of the explanation and the solution.

It seems that if you click the orange + New > Contact button then it will typically default to the root /Contacts folder, which is what's causing your error. If you're creating a new contact using that method, you must either select a Tag to apply to the folder or select a subfolder.

The way to change the default is to select any of the subfolders before clicking the orange + New > Contact button. Then it will automatically apply a tag to the contact and it won't trigger the error.

To fix the rest of your contacts that have this "No Tag" error, the easiest thing to do would be to go to the Contacts folder and sort all of your contacts by Tag in ascending order. This will cause all your "unsorted" contacts to appear at the top. Drag all of the unsorted contacts into any of your subfolders and this will apply a tag to them and stop the error. It could also be helpful to click the "select" option so that you can easily select multiple entries at once.

Uploaded Public Key not Verified

Public Key John Doe for email address example@yahoo.com was uploaded to eM Keybook, but has not been verified yet. Should eM Client keep monitoring for incoming verification emails?

This occurs when you have not yet checked your email to confirm that you would like to upload your Public PGP Key to eM Client. The message you should be looking for is called "Verification email from eM Keybook" and it will be sent from keybook@emclient.com.

Furthermore, some email accounts (such as @seznam.cz, @yahoo.com, or @aol.com) have a problem if checking the message through normal means does not trigger the confirmation.

The workaround for this problem is as follows:

1. Right-click on the "Verification email from eM Keybook" message in your list of emails in your inbox and select "Save as" and then save the email as a .eml file.
2. With this .eml file you exported, go to your file explorer in Windows where you've saved it on your computer and open the file with eM Client.
3. When the .eml file is open click Menu > Message > Copy to Folder
4. Choose where you want to save a copy of the message in eM Client.
5. Navigate to where you saved the file within eM Client, and it should be displaying/working correctly and the verification will trigger.

[Google Contacts] Synchronizing folder 'xxx@gmail.com/Contacts' failed due to the following error: Execution of request failed:

(Contacts API is being deprecated. Migrate to People API to retain programmatic access to Google Contacts. See https://developers.goog.ecom/people/contacts-api-migration.)

We have switched to the current People API in eM Client 8.2, so if you are running any of the older versions, you need to either install the update (if your license is valid for eM Client 8) or upgrade your license and then install it.

You can of course keep using the older version if you prefer, but you will not be able to synchronize your Google contacts anymore, they will only be stored locally as they are.

To avoid the error pop-up, you can work around this situation by copying the contacts to Local Folders and switch off the Google Contacts service in Accounts settings.

On September 24th, 2021 Microsft made some changes on their mail servers, which disabled OAuth login for the IMAP protocol on their accounts. Unfortunately, this affected all outlook.com, hotmail.com, live.com, msn.com and other free Microsoft account domains in our program, since we used this secure login method as default.
You can tell if your account is affected by a red triangle shown next to your account name. This account also cannot receive any new messages.

The workaround at this time is to set up the account anew manually either as Exchange or as Other (IMAP) to avoid usage of the IMAP-XOAUTH2 login.

Note: If you use 2-factor verification, you might need to create and use an App password for eM Client.

Manual IMAP setup (Other):

• Go to Menu > Accounts.
• Click the '+Add account' button.
• In the New Account window select Mail > Other.
• Insert your Microsoft account address
• Select IMAP.
• Insert these settings for Incoming server: imap-mail.outlook.com
• Outgoing server: smtp-mail.outlook.com
• Finish the rest of the setup
• Delete or disable your previous IMAP setup

Exchange setup:

• Download the attached registry file in this article.
• Run it while eM Client is still closed and confirm the changes it will make.

If you'd like to add the needed registry key manually instead of using our provided file:

• Run Regedit
• Go to Computer\HKEY_CURRENT_USER\Software\eM Client
• Add the DWORD item AllowExchangeOnlineOAuth and set its value to 0
• Then run eM Client 

To set up the actual account:

• Go to Menu > Accounts.
• Click the '+Add account' button.
• In the New Account window select Mail > Exchange.
• Use your Microsoft mail address for both the Email and Username fields. 
• Finish the rest of the setup
• Delete or disable your previous IMAP setup. 

Known Microsoft Exchange server error "User is authenticated but not connected" has been encountered on IMAP connection. This issue is temporary and should be automatically resolved by the server. If not, please contact your mail provider.

This error means that the authentication process for your account was succesfull, but for some reason the mail server is not giving eM Client access to the account data, so it cannot synchronize your messages into the app.

This can have a few different causes - sometimes it's a temporary issue that will go away on its own, but lately we had this issue reported with brand new outlook.com accounts that do not have IMAP protocol allowed.

• Sign in to your Outlook account via the webmail (https://outlook.live.com/)
• Go to Settings > Mail > Forwarding and IMAP > Login > enter your credentials again
• Enable Allow devices and applications to use POP and Allow devices and applications to use IMAP
• Save your settings and click the Refresh button.

If you already have IMAP allowed and the issue does not clear on its own, reach out to your admin or provider of the email account so they can fix the issue.

If this is happening with an email account that is set up using an Alias and not the Primary email address, try setting up the account anew using the primary email address to see if that resolves the problem.

Communication with the previous instance failed. The other instance has to be ended in order to start the application.

This happens if you run eM Client in administrator mode, which is not compatible with Windows notifications. To avoid this issue, make sure to run eM Client as a regular user instead of 'as admin'.

"Cannot determine the frame size or a corrupted frame was received."

[SMTP] MailClient.Accounts.AuthenticationAbortedException: Authentication aborted.

This issue is caused by a new problem on Microsoft's modern OAuth login method, settings up the account with an older version of the OAuth authentication in the meantime will work.

For the workaround, follow these steps:

Windows

• Close eM Client.
• Revoke permission for eM Client in your Outlook.com account: https://account.live.com/consent/Manage
• Download and run the registry file in this article - useoldoutlookcomflow.reg
  (this file can be downloaded at the bottom of this article, in the Attachments section)
• Open eM Client and log in using the OAuth window that pops up.

macOS

• Close eM Client.
• Revoke permission for eM Client in your Outlook.com account: https://account.live.com/consent/Manage
• Open Terminal and run this command: defaults write com.emclient.mail.client UseOldOutlookComFlow -bool TRUE
• Open eM Client and log in using the OAuth window that pops up.

Once Microsoft fixes this issue, you can either keep the older OAuth or remove the workaround with these steps, which are just the reverse of the previous ones:

Windows

• Close eM Client.
• Revoke permission for eM Client in your Outlook.com account: https://account.live.com/consent/Manage
• Download and run the other registry file in this article- removeoldoutlookcomflow.reg
• Open eM Client and log in using the OAuth window that pops up.

macOS

• Close eM Client.
• Revoke permission for eM Client in your Outlook.com account: https://account.live.com/consent/Manage
• Open Terminal and run this command: defaults delete com.emclient.mail.client UseOldOutlookComFlow
• Open eM Client and log in using the OAuth window that pops up.

Unfortunately, this means we'll also need to rework how this functions in eM Client. The possibility to display the Birthday calendar is set to be reintroduced in eM Client 11.

While AirSync does not suffer from the authentication issue at this time, Microsoft does not let it use ALL sending features - namely, any alias will revert to your primary email and send the email from primary address instead of your desired alias.
This, of course, does not affect users who don't need alias for these specific accounts, but if you need the alias feature to work correctly, you'll have to manually switch to SMTP.

Follow the steps below:

Windows

• Close eM Client.
• Open Start menu and type in REGEDIT and press Enter to open Windows Registry
• Go to Computer\HKEY_CURRENT_USER\Software\eM Client
• Right-click inside this section and create New > DWORD
• Name it UseAirSyncSendMail and save - this should set it to 0

macOS

• Close eM Client.
• Open Terminal and run this command: defaults write com.emclient.mail.client UseAirSyncSendMail -bool FALSE

On Windows, trusted certificate authorities (CAs) are managed through the system certificate store. Outlook and some other applications can trigger Windows to fetch missing certificates from trusted CAs when needed. eM Client, however, only uses certificates already present in the Windows store. If an intermediate certificate is missing, it does not try to download it via AIA or force Windows to update its trusted root list (which is normally updated periodically through Windows Update).

This behavior is designed to prevent a type of privacy attack: a malicious sender could include a URL in the AIA field of their certificate pointing to their own server. If your mail client automatically contacts that URL to retrieve a certificate, the sender would immediately know you opened their email.

To avoid issues, make sure to import certificates with their complete chain (including intermediate certificates) into the Windows certificate store in advance.

Go to your web browser and open your Google Calendar settings. Scroll down to Event settings > Guest permissions and change it to Add invitations to my calendar "From everyone."

If any other setting is used, Google rejects the events added from eM Client, but does not show any errors or warnings. During synchronization, it seems that the server confirms that all is synchronized correctly, so unfortunately, there is little we can do on our end to avoid this issue.

However, other factors can also cause accepted events not to sync, so if adjusting this setting doesn’t resolve your issue, please contact our support team for further assistance.

• VersionNotSupported
• The input string '' was not in a correct format.
• Invalid namespace Meeting Response

If you want to keep using version 9, you can switch the sending protocol from AirSync to SMTP.

On Windows:

Close eM Client. Download and run this configuration file to update the Windows registry.

You can also change it manually if you prefer:

• Run REGEDIT in Windows Start menu
• Navigate to HKEY_CURRENT_USER\Software\eM Client
• Right-click > New > DWORD and name it UseAirSyncSendMail

On macOS:

Close eM Client. Open Terminal and run this command:

defaults write com.emclient.mail.client UseAirSyncSendMail -bool FALSE

After switching to SMTP, open Menu > Accounts (or eM Client > Accounts on macOS) and disable AirSync under Services. This stops the errors, but Outlook calendar and contacts will no longer work. You can use the local calendar and contacts or add these services from another provider.

If throttling continues for an extended period of time even with these precautions, there might be additional issues on your email provider's side. In that case, please report this to the Google support team so they can look into it or reconsider these limitations. 

How can you tell if your account is being throttled?

Throttling is usually visible in the IMAP diagnostic logs. A snippet of what it looks like in the logs:

01: A3 OK Success [THROTTLED]

01: A4 NAMESPACE

01: * NAMESPACE (("" "/")) NIL NIL

01: A4 OK Success [THROTTLED]

01: Detected server type: Gmail

01: A5 ENABLE CONDSTORE

01: * ENABLED CONDSTORE

01: A5 OK Success [THROTTLED]