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.