eM Client POP Errors

I’m already sick and tired of this total BS v8!!!

I keep getting POP errors on all of my emails regardless of the email domain.
I never got these error messages on v7 (I unfortunately switched a few days ago) with the exact same POP and SMTP settings.

The error is always the same for all the email addresses. An example here:

MailClient.Accounts.SocketException: Connection failed due to the following reason:
“Unable to read data from the transport connection: An invalid argument was supplied…”
at MailClient.Protocols.Pop3.Pop3ReceiveCommand.Connect(WorkerStatus status)
at MailClient.Protocols.Pop3.Pop3ReceiveCommand.Execute(WorkerStatus status)
at MailClient.Commands.Command.Process(WorkerStatus status)
EnqueuedStackTrace =
at MailClient.Protocols.Common.AccountBase.RunIfOnline(Action actionIfOnline, Action actionIfOffline)
at MailClient.Protocols.Pop3.Pop3Account.ReceiveAsync(Action1 receivedItem, Action1 completed, CancellationToken cancellationToken)
at MailClient.Accounts.BindingAccountBase.Receive()
at MailClient.Accounts.AccountManager.ReceiveAllInternal()
at MailClient.Accounts.AccountManager.SendAndReceiveAll()
at MailClient.Accounts.AccountManager.timerSendAndReceive_Tick(Object sender, EventArgs e)
at System.Windows.Forms.Timer.OnTick(EventArgs e)
at System.Windows.Forms.Timer.TimerNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.DebuggableCallback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
at System.Windows.Forms.UnsafeNativeMethods.DispatchMessageW(MSG& msg)
at System.Windows.Forms.Application.ComponentManager.System.Windows.Forms.UnsafeNativeMethods.IMsoComponentManager.FPushMessageLoop(IntPtr dwComponentID, Int32 reason, Int32 pvLoopData)
at System.Windows.Forms.Application.ThreadContext.RunMessageLoopInner(Int32 reason, ApplicationContext context)
at System.Windows.Forms.Application.ThreadContext.RunMessageLoop(Int32 reason, ApplicationContext context)
at System.Windows.Forms.Application.Run(ApplicationContext context)
at MailClient.Program.<>c.b__161_1()
at System.RuntimeMethodHandle.InvokeMethod(Object target, Object[] arguments, Signature sig, Boolean constructor, Boolean wrapExceptions)
at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)
at System.Delegate.DynamicInvokeImpl(Object[] args)
at System.Delegate.DynamicInvoke(Object[] args)
at System.Windows.Forms.Control.InvokeMarshaledCallbackDo(ThreadMethodEntry tme)
at System.Windows.Forms.Control.InvokeMarshaledCallbackHelper(Object obj)
at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
at System.Windows.Forms.Control.InvokeMarshaledCallback(ThreadMethodEntry tme)
at System.Windows.Forms.Control.InvokeMarshaledCallbacks()
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ScrollableControl.WndProc(Message& m)
at System.Windows.Forms.ContainerControl.WndProc(Message& m)
at System.Windows.Forms.Form.WndProc(Message& m)
at MailClient.Common.UI.Forms.BaseForm.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.DebuggableCallback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
at Xilium.CefGlue.Interop.libcef.run_message_loop()
at MailClient.Program.Main(String[] args)

I put this here as the support is full of total incompetent idiots whose job is only to try to convince the customer that it is OUR fault and never theirs!

On TrustPilot, I saw quite a few of reviews talking about these POP errors on v8 so it’s not just me.
Anyone has any idea how to stop these errors pls?

You can try stopping your AV and see if that has any effect.

Thank you for trying to help, I mean it, however that’s what you tell absolutely everyone for any kind of issues!!! If I get hemorrhoids, should I try to disable my AV? :slight_smile:

This is not an AV issue.

As a first shot at the problem related to connection issues, I usually ask them to give it a try. It has resolved an awful lot of issues. It’s not a cure all, for sure, because if it works then eM Client still has a major issue.

In the end, it is your choice…

Again, thank you for your help, but it’s an AV issue.