Can someone describe more specifically how to implement the VCF solution?
How do you locate just emails with VCF attachments?
Do you just delete them client side or do you have to delete them server side as well?
Thank you – I’d like to rescue my lifetime licenses.
UPDATE: I deleted the attachments on the server and client and now problem resolved, just like everyone else…
Like everyone has said, no other email client has this sync issue. Only emClient.
It seems Gary cannot figure out why this is happening, so just points the finger at the server, despite no other client having a problem.
While the solution may be beyond Gary’s capabilities, he could create a simple workaround – prevent emClient from handling any email with a .vcf attachment.
If he can’t figure out why this is happening to emClient -but no other email program, at least a workaround would permit people to avoid the problem
UPDATE: I deleted the attachments on the server and client and now problem resolved, just like everyone else…
As @Gary advised further up this thread Quote:- “Sure you can delete the server data, and then there won’t be any server error. But a better solution is to ask your email provider to fix the error on their server so you don’t need to delete your data”.
I agree with Gary that this issue “does sounds mailbox server related” and the server tech staff should find out why this is happening and fix it their end without you having to delete your data.
While the solution may be beyond Gary’s capabilities, he could create a simple workaround – prevent emClient from handling any email with a .vcf attachment.
Gary carn’t write that “as is also an end user” and not the developer but is very knowledgeable with eM Client and many mail server systems.
So if you believe this is an eM Client issue and also have a suggestion for a fix, then if you have an active Paid Pro or Personal version, go to the following VIP support page and login and lodge a support ticket who can then investigate that problem with you. They will then get you to send logs etc to check out and will get back to you.
Gary is the sole developer/employee of eMClient.
An analogy…
My state has yearly emission tests for cars.
Let’s say you take a Ford, Chevy, Chrysler, Mercedes, BMW, Porsche, Lexus, Toyota, and Honda to the emission testing facility.
All test fine, except for the Ford. The Ford’s onboard computer says “testing machine fault.”
Kinda suggests that something is wrong with the way the Ford is connecting to the machine, right?
But Ford keeps saying, “No, its the machine’s fault! Our car is fine!”
Sorta the situation here.
It’s too bad that emClient can’t figure out why its client reports an error when no other client does.
Sorry but I don’t think that is true. You can find a number of employees online, for example.
Then that’s even worse. I was giving the benefit of the doubt thinking this was a one-man show.
Blaming the server when no other email client has a problem is beyond silly.
As I advised then send that on a ticket to official support who will then investigate it with you.
Been there, done that.
Got the exact same response as has been posted here: “It’s a server problem, not our problem. We can’t fix a server”
And like everyone else here, when I contact the ISP, they say, “if every other email client works and webmail works, then it’s clearly an issue with the one client that’s having the problem”
Which make perfect sense. Except to emClient support!
I contact the ISP, they say, “if every other email client works and webmail works, then it’s clearly an issue with the one client that’s having the problem”.
Just because your other mail clients work doesn’t mean there isn’t a server related problem. Other mailers could be eg: authenticating “with some other / different method”. All Mail clients are not programmed the same way. So your mail server tech support need to see why it’s not working for you their end from their eg: mail server logs etc.
If this was an eM Client issue, no Exchange customers would connect at all. But the fact is, most users of eM Client Exchange connections work fine and “it’s only a very small amount of users who have this issue”, which then points to a mail server related problem & not eM Client.
No one is saying that. If you read this thread (and the many other threads like it) you will see that eM Client has an issue when doing a sync that includes an attachment with a files of certain type. The connection and the rest of the transfer is fine.
Only some users have this issue because only some are attempting a sync with the file type that eM Client does not handle properly with the server. All other email programs are able to handle a sync with the specified attachment (.vcf gets mentioned a lot).
So you can say that all Exchange servers need to be modified across the planet or you can figure out why this one email client can’t handle this when all other email clients can.
I have been following this thread. I sign in today to add my voice to those who have posted earlier that it is just silly to not fix this issue. I had to switch to Thunderbird, which I don’t like, but it doesn’t throw a “server error” like emclient. I don’t care how many employees there are. Whether it is one or a hundred, they should take responsibility to their PAYING customers and fix this problem that no other email program has.
Hello,
in version 10.3 we’ve added several workarounds for such errors that Exchange server returns (and yes Internal server error is primarily always an error on the server). @RonScott Do you experience these issues with version 10.3 as well? Problem is also, that our QA has never been able to reproduce it on our testing Exchange servers. @RonScott Can you send us EWS logs with your current problem, as it is the same as this thread was all about or it is something different?
We’ve tested again and in v 10.3 at least sync is not stopped, only the problematic file is replaced with error.txt. Please try it with v. 10.3. We will also try to find out what part of VCF attachments Exchange is unable to handle. But at least it should be usable now with 10.3.
@JohnnyCakes & @RonScott apart from what @Michal_Burger already advised to try above in his posts with the updated 10.3 version, do you use Microsoft Direct Exchange servers or Alternative Non Microsoft Exchange servers ?
As I’m wondering if this attachment issue is with any specific Exchange Server or Server version.
With version 10.3, the sync will work normally, just the vcf attachments will be unreadable, because Exchange converts them to his internal format and then fires internal server error. It really is primarily a server issue, but we now investigating how we can workaround it even further to make vcf attachments readable in eM Client somehow. I (as CEO of eM Client) apologize it took so long to come up with some solution. It is somehow hard to make workarounds for all the bugs of big players, but I fully understand users just want it to work and we have to put the effort into it, which is exactly what we are now doing at last. I am sorry for the Gary’s approach and reactions. He is no longer with us exactly for that reason.
While looking for a solution to a Calendar related problem I came across this thread. Watching Gary’s responses to people here made me severely doubt if I wanted to continue with eM Client.
@Michal_Burger thank you for the feedback you have given, as someone who has only been going through this thread from the sidelines I think you made the right decision to send Gary away.
I am still getting MS Server errors on 10.3 but it is happening much less than earlier versions.
Can you post here the error you get in 10.3?
So we deep dived in the issue and we were able to come up with workaround that finally resolves the issue. We now use a different way how to sync VCF attachments from the server to bypass the server bug. It can be downloaded here:
Windows
https://www.emclient.com/dist/v10.3.1720/setup.msi
Mac
https://www.emclient.com/dist/v10.3.1720_Mac/setup.pkg
Once again sorry it took so long. I believe this issue is now resolved for good.
This are two of them. I will see how v10.3.1720 goes.
3:14:29 PM [email protected] [AirSync] MailClient.Accounts.ConnectionException: An error occurred while sending the request.
—> System.Net.Http.HttpRequestException: An error occurred while sending the request.
—> System.IO.IOException: Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host…
—> System.Net.Sockets.SocketException (10054): An existing connection was forcibly closed by the remote host.
— End of inner exception stack trace —
at System.Net.Sockets.Socket.AwaitableSocketAsyncEventArgs.ThrowException(SocketError error, CancellationToken cancellationToken)
at System.Net.Sockets.Socket.AwaitableSocketAsyncEventArgs.System.Threading.Tasks.Sources.IValueTaskSource<System.Int32>.GetResult(Int16 token)
at System.Net.Security.SslStream.EnsureFullTlsFrameAsync[TIOAdapter](CancellationToken cancellationToken, Int32 estimatedSize)
at System.Runtime.CompilerServices.PoolingAsyncValueTaskMethodBuilder1.StateMachineBox1.System.Threading.Tasks.Sources.IValueTaskSource.GetResult(Int16 token)
at System.Net.Security.SslStream.ReadAsyncInternal[TIOAdapter](Memory1 buffer, CancellationToken cancellationToken) at System.Runtime.CompilerServices.PoolingAsyncValueTaskMethodBuilder1.StateMachineBox1.System.Threading.Tasks.Sources.IValueTaskSource<TResult>.GetResult(Int16 token) at System.Net.Http.HttpConnection.SendAsync(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken) --- End of inner exception stack trace --- at System.Net.Http.HttpConnection.SendAsync(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken) at System.Net.Http.AuthenticationHelper.SendWithNtAuthAsync(HttpRequestMessage request, Uri authUri, Boolean async, ICredentials credentials, Boolean isProxyAuth, HttpConnection connection, HttpConnectionPool connectionPool, CancellationToken cancellationToken) at System.Net.Http.HttpConnectionPool.SendWithVersionDetectionAndRetryAsync(HttpRequestMessage request, Boolean async, Boolean doRequestAuth, CancellationToken cancellationToken) at System.Net.Http.AuthenticationHelper.SendWithAuthAsync(HttpRequestMessage request, Uri authUri, Boolean async, ICredentials credentials, Boolean preAuthenticate, Boolean isProxyAuth, Boolean doRequestAuth, HttpConnectionPool pool, CancellationToken cancellationToken) at System.Net.Http.DecompressionHandler.SendAsync(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken) at MailClient.Protocols.InteractionController.HttpClientCertificationValidationMessageHandler.SendAsync(HttpRequestMessage request, CancellationToken cancellationToken) at MailClient.Protocols.Common.HttpClientHandlers.HttpClientBackoffHandler.SendAsync(HttpRequestMessage request, CancellationToken cancellationToken) at System.Net.Http.HttpClient.<SendAsync>g__Core|83_0(HttpRequestMessage request, HttpCompletionOption completionOption, CancellationTokenSource cts, Boolean disposeCts, CancellationTokenSource pendingRequestsCts, CancellationToken originalCancellationToken) at MailClient.Protocols.AirSync.Protocol.ActiveSyncCommandRequest.GetResponse(CancellationToken cancellationToken) at MailClient.Protocols.AirSync.AirSyncItemSynchronizer2.Synchronize(IItemSynchronizeContext1 synchronizeContext, Folder folder, CancellationToken cancellationToken) at MailClient.Protocols.Common.ItemSynchronizer2.<>c__DisplayClass37_2.b__6(WorkerStatus status, CancellationToken ct)
at MailClient.Protocols.AirSync.AirSyncGenericCommand.Execute(WorkerStatus status)
— End of inner exception stack trace —
at MailClient.Protocols.AirSync.AirSyncGenericCommand.Execute(WorkerStatus status)
at MailClient.Commands.Command.Process(WorkerStatus status)
AccountId = 3140da67-fbd8-4bf8-b4b9-830ac37706b8
AccountName = [email protected]
RunInPlace = False
EnqueuedStackTrace =
at MailClient.Protocols.Common.ItemSynchronizer2.<>c__DisplayClass37_1.<EnqueueSynchronize>g__RunSynchronize|2() at MailClient.Protocols.Common.ItemSynchronizer2.<>c__DisplayClass37_0.b__0()
at MailClient.Protocols.Common.AccountBase.RunIfOnline(Action actionIfOnline, Action actionIfOffline)
at MailClient.Protocols.Common.ItemSynchronizer2.EnqueueSynchronize(Folder folder, Boolean fast, CancellationToken cancellationToken, Action1 completed)
at MailClient.Protocols.Common.ItemSynchronizer2.Synchronize(Folder folder, SynchronizationPriority priority, Action1 completed)
at MailClient.Storage.Application.ItemCollection2.Synchronize(SynchronizationPriority priority, Action1 completed, Boolean fromUI)
at MailClient.Storage.Application.ItemCollection`2.SynchronizeAsync(Boolean forced, Boolean fromUI)
at MailClient.Storage.Application.Folder.SynchronizeAsync(Boolean forced, Boolean fromUI)
at MailClient.Protocols.AirSync.AirSyncAccount.<>c__DisplayClass22_0.b__2(CompletionEventArgs e)
at MailClient.Protocols.Common.FolderSynchronizer.<>c__DisplayClass20_0.b__0(CompletionEventArgs completionEventArgs)
at MailClient.Protocols.Common.FolderSynchronizer.<>c__DisplayClass21_0.b__1(CompletionEventArgs completionEventArgs)
at MailClient.Protocols.Common.RequestIssuer.<>c__DisplayClass12_0.b__0(Object sender, CompletionEventArgs e)
at MailClient.Commands.Command.Complete()
at MailClient.Commands.Command.Process(WorkerStatus status)
at MailClient.Commands.DefaultSynchronizationQueue.ThreadWorker(Object threadData)
at System.Threading.Thread.StartHelper.Callback(Object state)
at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state)
at System.Threading.Thread.StartCallback()
GUIStatus_Exception_Reported = True
3:13:15 PM [email protected] [AirSync] MailClient.Storage.Application.OperationException: Synchronization error (InvalidSynchronizationKey)
at MailClient.Protocols.AirSync.AirSyncItemSynchronizer2.Synchronize(IItemSynchronizeContext1 synchronizeContext, Folder folder, CancellationToken cancellationToken)
at MailClient.Protocols.Common.ItemSynchronizer2.<>c__DisplayClass37_2.<EnqueueSynchronize>b__6(WorkerStatus status, CancellationToken ct) at MailClient.Protocols.AirSync.AirSyncGenericCommand.Execute(WorkerStatus status) at MailClient.Commands.Command.Process(WorkerStatus status) AccountId = null AccountName = null RunInPlace = False EnqueuedStackTrace = at MailClient.Protocols.Common.ItemSynchronizer2.<>c__DisplayClass37_0.b__0()
at MailClient.Protocols.Common.AccountBase.RunIfOnline(Action actionIfOnline, Action actionIfOffline)
at MailClient.Protocols.Common.ItemSynchronizer2.Synchronize(Folder folder, SynchronizationPriority priority, Action1 completed)
at MailClient.Storage.Application.ItemCollection2.Synchronize(SynchronizationPriority priority, Action1 completed, Boolean fromUI)
at MailClient.Storage.Application.ItemCollection`2.SynchronizeAsync(Boolean forced, Boolean fromUI)
at MailClient.Storage.Application.Folder.SynchronizeAsync(Boolean forced, Boolean fromUI)
at MailClient.Protocols.AirSync.AirSyncAccount.<>c__DisplayClass22_0.b__2(CompletionEventArgs e)
at MailClient.Protocols.Common.FolderSynchronizer.<>c__DisplayClass20_0.b__0(CompletionEventArgs completionEventArgs)
at MailClient.Protocols.Common.RequestIssuer.<>c__DisplayClass12_0.b__0(Object sender, CompletionEventArgs e)
at MailClient.Commands.Command.Complete()
at MailClient.Commands.Command.Process(WorkerStatus status)
at MailClient.Commands.DefaultSynchronizationQueue.ThreadWorker(Object threadData)
at System.Threading.Thread.StartHelper.Callback(Object state)
at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state)
at System.Threading.Thread.StartCallback()
GUIStatus_Exception_Reported = True