As I mentioned, when it was happening, both computers with v9 failing, but my phone was still getting emails, also another computer with Thunderbird was working fine. Also, the 4 other people who are different people to me, different mail servers etc etc. All after upgrading to v9.
Don’t worry about this, as obviously nobody is taking a v9 fault seriously. I can add that after the email sent to myself on each computer, there have been no further issues.
Haven’t had that issue myself. Suggest you create a new post, and someone may help.
Hi Grant. Just for the record, the topic says: " Almost total failure after update to v9". For me a force closure after the upgrade belongs to this thread, even though it says “almost…”, that said, whatever that makes you happy. I will consider reporsting it somewhere else.
I to am having problems with V9. Some read emails have disappeared. Also, my signature which I was able to add using CTRL 1 is gone. I can’t seem to locate where to rebuild it. This is very frustrating.
Hi Gary, it just happened for a short time, and then went away. There is quite a bit in the log in the seconds around when the failure happened, but the following seems to show the error.
09:50:29.729|027| 01: A217 OK Fetch completed.
09:50:29.729|027| >>> FetchPreviewsAsync(): New messages need preview, fetching…
09:50:29.730|027| 01: A218 UID FETCH 68458,68464:68465 (BODY.PEEK[TEXT]<0.1024>)
09:50:29.730|027| 01: A219 UID FETCH 68455:68456 (BODY.PEEK[1.1]<0.1024>)
09:50:29.730|027| 01: A220 UID FETCH 68459:68461,68469 (BODY.PEEK[TEXT]<0.4096>)
09:50:29.730|027| 01: A221 UID FETCH 68457 (BODY.PEEK[1]<0.4096>)
09:50:29.862|027| 01: * 3857 FETCH (UID 68458 BODY[TEXT]<0> {76}
09:50:29.863|027| 01: )
09:50:29.864|027| 01: * 3863 FETCH (UID 68464 BODY[TEXT]<0> {71}
09:50:29.864|027| 01: )
09:50:29.866|027| 01: * 3864 FETCH (UID 68465 BODY[TEXT]<0> {68}
09:50:29.866|027| 01: )
09:50:29.866|027| 01: * 3854 FETCH (UID 68455 BODY[1.1.MIME] {93}
09:50:29.866|027| 01: BODY[1.HEADER] {0}
09:50:29.868|027| 01: RECEIVE EXCEPTION: System.ArgumentOutOfRangeException: Specified argument was out of the range of valid values. (Parameter ‘start’)
09:50:29.868|027| at MailClient.Imap.Base.Extensions.GetString(ReadOnlySequence1& buffer, Encoding encoding) 09:50:29.868|027| at MailClient.Imap.Base.Extensions.GetUtf8String(ReadOnlySequence1& buffer)
09:50:29.868|027| at MailClient.Imap.Base.LineSequence.ToString()
09:50:29.868|027| at MailClient.Imap.Base.Connection.ReceiveAsync()
09:50:29.868|027|
09:50:29.868|027| 01: — RECEIVE: CLOSED
09:50:29.868|027| 01: — CLOSE: PRIMARY START
09:50:29.868|027| 01: A222 LOGOUT
09:50:30.175|027| 01: — CMD LOGOUT WAS CANCELLED
09:50:30.175|027| 01: — CLOSE: LOGOUT TIMED-OUT !!!
09:50:30.175|027| 01: — CMD A218 UID FETCH FAILED: A task was canceled.
09:50:30.175|027| 01: — CMD A219 UID FETCH FAILED: A task was canceled.
09:50:30.175|027| 01: — CMD A221 UID FETCH FAILED: A task was canceled.
09:50:30.175|027| 01: — CMD A220 UID FETCH FAILED: A task was canceled.
09:50:30.175|027| 01: — CLOSE: PRIMARY FINISHED
09:50:30.175|027| 01: Connection 1 was closed, deliberate = False, folder = /Inbox [Inbox], activated = True
09:50:30.175|027| >>> ResynchronizeFolder(folder: /Inbox [Inbox]): connection died
09:50:30.175|027| >>> FetchNewMessagesAsync(): End
09:50:30.176|027| >>> COMMAND CONNECTION EXCEPTION (retry: True): Connection was closed
09:50:30.176|027| >>> SynchronizeMessagesAsync(folder: /Inbox [Inbox], fast: False): executing
09:50:30.176|027| 02: A45 SELECT “INBOX” (CONDSTORE)
09:50:30.236|027| 02: * OK [CLOSED] Previous mailbox closed.
09:50:30.236|027| 02: * FLAGS (\Answered \Flagged \Deleted \Seen \Draft $Forwarded $MDNSent $label3 NonJunk $label1 $label2 $label4 $label5)
09:50:30.236|027| 02: * OK [PERMANENTFLAGS (\Answered \Flagged \Deleted \Seen \Draft $Forwarded $MDNSent $label3 NonJunk $label1 $label2 $label4 $label5 *)] Flags permitted.
09:50:30.237|027| 02: * 3871 EXISTS
09:50:30.237|027| 02: * 0 RECENT
09:50:30.237|027| 02: * OK [UNSEEN 9] First unseen.
09:50:30.237|027| 02: * OK [UIDVALIDITY 1568118540] UIDs valid
09:50:30.237|027| 02: * OK [UIDNEXT 68477] Predicted next UID
09:50:30.237|027| 02: * OK [HIGHESTMODSEQ 142346] Highest
09:50:30.237|027| 02: A45 OK [READ-WRITE] Select completed.
09:50:30.247|027| >>> SynchronizeMessagesAsync(folder: /Inbox [Inbox]): Starting initial synchronization, number of existing messages = 3848, minUID = 28066, max UID = 68475, highest MODSEQ = 142341, temp MODSEQ = 142273
09:50:30.247|027| >>> SynchronizeMessagesAsync(folder: /Inbox [Inbox]): Fetching new messages up to UidNext = 68477
09:50:30.247|027| >>> FetchNewMessagesAsync(idSet: 68475:68477, estimate: 2): Start
09:50:30.248|027| 02: A46 UID FETCH 68475:68477 (UID RFC822.SIZE FLAGS INTERNALDATE BODYSTRUCTURE ENVELOPE BODY.PEEK[HEADER.FIELDS (importance x-priority references document-reference content-type)] MODSEQ)
09:50:30.348|027| 02: * 3870 FETCH (UID 68475 RFC822.SIZE 45070 FLAGS () INTERNALDATE “11-May-2022 09:34:54 +1200” MODSEQ (142341) BODYSTRUCTURE (((“text” “plain” (“charset” “us-ascii”) NIL NIL “quoted-printable” 234 6 NIL NIL NIL NIL)(“text” “html” (“charset” “us-ascii”) NIL NIL “quoted-printable” 444 11 NIL NIL NIL NIL) “alternative” (“differences” “Content-Type” “boundary” “edecd79f-a6dc-432a-97b6-79f0b20c1965”) NIL NIL NIL)(“message” “delivery-status” NIL NIL NIL “7bit” 464 NIL NIL NIL NIL)(“text” “rfc822-headers” (“charset” “us-ascii”) NIL NIL “7bit” 35399 506 NIL NIL NIL NIL) “report” (“report-type” “delivery-status” “boundary” “defcf73c-f6b2-4121-bcaf-e7f7f17e27ab”) NIL (“en-US”) NIL) ENVELOPE (“Tue, 10 May 2022 21:34:34 +0000” “Delivered: Re[2]: Redpath Pacific Ltd Websale tracking for order” ((NIL NIL “postmaster” “redpath.co.nz”)) ((NIL NIL “postmaster” “redpath.co.nz”)) ((NIL NIL “postmaster” “redpath.co.nz”)) ((NIL NIL “grant” “ctas.co.nz”)) NIL NIL “[email protected]” “11c72054-4f16-432d-aeac-887819503516@MEYPR01MB7886.ausprd01.prod.outlook.com”) BODY[HEADER.FIELDS (IMPORTANCE X-PRIORITY REFERENCES DOCUMENT-REFERENCE CONTENT-TYPE)] {488}
09:50:30.348|027| 02: )
09:50:30.349|027| 02: * 3871 FETCH (UID 68476 RFC822.SIZE 2961936 FLAGS () INTERNALDATE “11-May-2022 09:44:13 +1200” MODSEQ (142346) BODYSTRUCTURE (((“text” “plain” (“charset” “utf-8”) NIL NIL “base64” 7402 95 NIL NIL NIL NIL)(“text” “html” (“charset” “utf-8”) NIL NIL “base64” 36636 470 NIL NIL NIL NIL) “alternative” (“boundary” “000_SYBPR01MB7979C045F9641F04F0F2E293EDC99SYBPR01MB7979ausp”) NIL NIL NIL)(“image” “png” (“name” “image005.png”) “[email protected]” “image005.png” “base64” 839490 NIL (“inline” (“filename” “image005.png” “size” “613471” “creation-date” “Tue, 10 May 2022 21:43:46 GMT” “modification-date” “Tue, 10 May 2022 21:43:48 GMT”)) NIL NIL)(“image” “jpeg” (“name” “image006.jpg”) “[email protected]” “image006.jpg” “base64” 2358 NIL (“inline” (“filename” “image006.jpg” “size” “1720” “creation-date” “Tue, 10 May 2022 21:43:48 GMT” “modification-date” “Tue, 10 May 2022 21:43:48 GMT”)) NIL NIL)(“image” “png” (“name” “image007.png”) “[email protected]” “image007.png” “base64” 822864 NIL (“inline” (“filename” “image007.png” “size” “601323” “creation-date” “Tue, 10 May 2022 21:43:48 GMT” “modification-date” “Tue, 10 May 2022 21:43:49 GMT”)) NIL NIL)(“image” “png” (“name” “image008.png”) “[email protected]” “image008.png” “base64” 743850 NIL (“inline” (“filename” “image008.png” “size” “543581” “creation-date” “Tue, 10 May 2022 21:43:49 GMT” “modification-date” “Tue, 10 May 2022 21:43:50 GMT”)) NIL NIL)(“image” “png” (“name” “image009.png”) “[email protected]” “image009.png” “base64” 494460 NIL (“inline” (“filename” “image009.png” “size” “361334” “creation-date” “Tue, 10 May 2022 21:43:50 GMT” “modification-date” “Tue, 10 May 2022 21:43:51 GMT”)) NIL NIL) “related” (“boundary” “008_SYBPR01MB7979C045F9641F04F0F2E293EDC99SYBPR01MB7979ausp” “type” “multipart/alternative”) NIL (“en-US”) NIL) ENVELOPE (“Tue, 10 May 2022 21:43:51 +0000” “RE: Re[2]: Redpath Pacific Ltd Websale tracking for order” ((“Mark Donnelly” NIL “markd” “redpath.co.nz”)) ((“Mark Donnelly” NIL “markd” “redpath.co.nz”)) ((“Mark Donnelly” NIL “markd” “redpath.co.nz”)) ((“Grant Collingwood” NIL “grant” “ctas.co.nz”)) ((“Donna Vanderbyl” NIL “RedPathCustomerService” “redpath.co.nz”)) NIL “[email protected]” “SYBPR01MB7979C045F9641F04F0F2E293EDC99@SYBPR01MB7979.ausprd01.prod.outlook.com”) BODY[HEADER.FIELDS (IMPORTANCE X-PRIORITY REFERENCES DOCUMENT-REFERENCE CONTENT-TYPE)] {517}
09:50:30.349|027| 02: )
09:50:30.349|027| 02: A46 OK Fetch completed.
09:50:30.349|027| >>> SynchronizeMessagesAsync(): Message 68475 ignored - this message is already in DB
09:50:30.349|027| >>> FetchPreviewsAsync(): New message needs preview, fetching…
09:50:30.349|027| 02: A47 UID FETCH 68476 (BODY.PEEK[1.1]<0.1024>)
09:50:30.421|027| 02: * 3871 FETCH (UID 68476 BODY[1.1]<0> {1024}
09:50:30.421|027| 02: )
09:50:30.421|027| 02: A47 OK Fetch completed.
It is unbelievable that after several days of complains from multiple people with clear examples of cases where the server were working, there is still the blame to others instead of recognizing the issue with the infamous release 9, and fixing it!
Red Triangle is back. Following is from Log
11:32:27 am Grant IMAP Synchronizing folder ‘/Inbox’
11:32:28 am Grant [IMAP] MailClient.Accounts.ConnectionException: Synchronizing folder ‘Grant/Inbox’ failed due to the following error: Connection was closed
—> MailClient.Imap.Base.ByeException: Connection was closed
—> System.Threading.Tasks.TaskCanceledException: A task was canceled.
at MailClient.Imap.Base.Connection.RunCommandAsync(Command command, Func3 notificationCallback) --- End of inner exception stack trace --- at MailClient.Imap.Base.Connection.RunCommandAsync(Command command, Func3 notificationCallback)
at MailClient.Protocols.Imap.ConnectionExtensions.RunCommandAsync(ConnectionContext context, Command command)
at MailClient.Protocols.Imap.ImapMailSynchronizer.<>c__DisplayClass106_1.<g__AsyncPath|48>d.MoveNext()
— End of stack trace from previous location —
at MailClient.Protocols.Imap.ImapMailSynchronizer.<>c__DisplayClass106_1.<g__ProcessPriorityUpdatesSlow2Async|29>d.MoveNext()
— End of stack trace from previous location —
at MailClient.Protocols.Imap.ImapMailSynchronizer.<>c__DisplayClass106_1.<g__FetchNewMessagesAsync|3>d.MoveNext()
— End of stack trace from previous location —
at MailClient.Protocols.Imap.ImapMailSynchronizer.<>c__DisplayClass106_1.<g__FillHoles|1>d.MoveNext()
— End of stack trace from previous location —
at MailClient.Protocols.Imap.ImapMailSynchronizer.SynchronizeMessagesAsync(IItemSynchronizeContext1 synchronizeContext, Folder folder, Boolean fast, CancellationToken cancellationToken) at MailClient.Protocols.Imap.ImapMailSynchronizer.SynchronizeMessagesAsync(IItemSynchronizeContext1 synchronizeContext, Folder folder, Boolean fast, CancellationToken cancellationToken)
at MailClient.Protocols.Imap.ImapMailSynchronizer.Synchronize(IItemSynchronizeContext1 synchronizeContext, Folder folder, CancellationToken cancellationToken) at MailClient.Protocols.Common.ItemSynchronizer2.<>c__DisplayClass37_2.b__6(WorkerStatus status, CancellationToken ct)
at MailClient.Protocols.Imap.ImapActionCommand.<>c__DisplayClass11_0.<.ctor>b__0(WorkerStatus ws, CancellationToken ct)
at MailClient.Protocols.Imap.ImapActionCommand.ExecuteInternalSync(WorkerStatus status)
— End of inner exception stack trace —
at MailClient.Protocols.Imap.ImapActionCommand.ExecuteInternalSync(WorkerStatus status)
at MailClient.Protocols.Imap.ImapActionCommand.Execute(WorkerStatus status)
at MailClient.Commands.Command.Process(WorkerStatus status)
IMAP_SERVER_TYPE = Other
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.Folder.Synchronize(SynchronizationPriority priority, Boolean fromUI)
at MailClient.Storage.Application.Folder.Synchronize(Boolean forced, Boolean fromUI)
at MailClient.UI.Forms.formMain.MailFolderSelectHandler.FolderSelectInternal(ControlFoldersBase sender, FolderChangeEventArgs e)
at MailClient.UI.Forms.formMain.FolderSelectHandler.FolderSelect(ControlFoldersBase sender, FolderChangeEventArgs e)
at MailClient.UI.Forms.formMain.ControlFolders_FolderSelect(Object sender, FolderChangeEventArgs e)
at System.EventHandler`1.Invoke(Object sender, TEventArgs e)
at MailClient.UI.Controls.Folders.ControlFoldersBase.OnFolderSelect(FolderChangeEventArgs e)
at MailClient.UI.Controls.Folders.controlMailUserFolders.OnFolderSelectChanged(Boolean selectedByMouse, Boolean& focusAfterSelect)
at MailClient.UI.Controls.Folders.ControlFoldersBase.treeView_NodeSelected(Object sender, TreeViewNodeSelectedEventArgs e)
at MailClient.Common.UI.Controls.ControlTreeView.ControlTreeView.OnNodeSelected(TreeViewNodeSelectedEventArgs e)
at MailClient.Common.UI.Controls.ControlTreeView.ControlTreeView.selectSingleNode(TreeNode newSelectedNode, TreeViewAction selectAction, Boolean ensureVisible, Boolean expandParents)
at MailClient.Common.UI.Controls.ControlTreeView.ControlTreeView.OnMouseDown(MouseEventArgs e)
at System.Windows.Forms.Control.WmMouseDown(Message& m, MouseButtons button, Int32 clicks)
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.UserControl.WndProc(Message& m)
at MailClient.Common.UI.Controls.AutomationViewUserControl.WndProc(Message& m)
at MailClient.Common.UI.Controls.TouchScrollUserControl.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.Callback(IntPtr hWnd, WM msg, IntPtr wparam, IntPtr lparam)
at Interop.User32.DispatchMessageW(MSG& msg)
at System.Windows.Forms.Application.ComponentManager.Interop.Mso.IMsoComponentManager.FPushMessageLoop(UIntPtr dwComponentID, msoloop uReason, Void* pvLoopData)
at System.Windows.Forms.Application.ThreadContext.RunMessageLoopInner(msoloop reason, ApplicationContext context)
at System.Windows.Forms.Application.ThreadContext.RunMessageLoop(msoloop reason, ApplicationContext context)
at System.Windows.Forms.Application.Run(ApplicationContext context)
at MailClient.Program.<>c.b__171_2()
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.Callback(IntPtr hWnd, WM msg, IntPtr wparam, IntPtr lparam)
at Xilium.CefGlue.Interop.libcef.run_message_loop()
at MailClient.Program.Main(String[] args)
GUIStatus_Exception_Reported = True
ByeException
TaskCanceledException
Before anyone from emClient tries to blame our mail server, THERE IS NOTHING WRONG WITH THE SERVER. I can still send and receive emails from my phone. ( Lucky that doesn’t use emClient )
Also, I have loaded v8 onto another computer and it is working fine. ( No Red Triangle on v8. Two comuters with v9, and both have Red Triangle. )
Any update or do we have to go back to Version 8 to achieve stability?
I have supplied logs and evidence, and Version 8 does not have these connection problems.
My main computer is totally faulty today with Red Triangle but laptops on Version 8 and Version 9 are working fine.
My main computer is totally faulty today with Red Triangle but laptops on Version 8 and Version 9 are working fine
Interesting your laptops with V8 and V9 are working fine, but not your main computer with presumably the same eM Client versions & settings.
What’s different on your main computer ? as if you run the same eM Client versions as your laptops it also should be working.
Do you run any different optional software on your main computer like eg: optional firewall / security programs, optional antivirus programs, VPNs etc.
Also does the main computer run via the same modem router wired or wireless.
Main computer and Laptop are sitting hear in office, on same OS (Windows 11), same internet, same AVG and no VPN or any special security. The only thing different is that the desktop also connects to one of our clients Microsoft Exchange email server. That doesn’t seem to be faulty. However, since v9, the laptop has been faulty as well, it is only today, that the laptop is exhibiting a difference to the main computer.
Since it had totally stopped today, I need my email working. I recovered the complete emClient Program folder and Roaming folder database from our offsite backups, and so am back on Version 8. It is working perfectly like that.
I recovered the complete emClient Program folder and Roaming folder database from our offsite backups, and so am back on Version 8. It is working perfectly like that
Sounds like then you might be best atm sticking with V8 as that works for you ok till you get feedback on your logs.
Well yes, and it would be great if I even knew they are looking at my logs. So far communications are totally pointing away from anything at emClient v9, even though I and many other people have proven that v9 is problematic.
Yet many of us does not have any of these problems with v9, and the problems reported seems to be different. Though there’s some reports on connectivity/authentication issues, it’s different protocols (IMAP, POP3, SMTP) so they’d need to dig down and figure out what’s going on in different cases. My guess is the devs are working on it. If all these is indeed related, my guess would be that there’s been some change in TLS/ciphers etc, giving olders servers trouble. Yet that would not explain problems that come and go … So, I just wish the devs best of luck. 
This update is horrible, and almost makes eM Client useless. Will there be a patch update to fix all the issues. I can count to 10 before an email sends now.
I just found out that after the last update, Avast Antivirus is blocking emClient and need to be stopped to allow communication (get the red triangle and “no connection with server” message). I have two other email clients without a problem with the antivirus, so there is something odd with emClient that is triggering Avast to block.
So there is something odd with emClient that is triggering Avast to block
Avast is known to block alot of mail clients and you need to disable the mail scanning part (Core Mailshield) to allow eM Client to work.
Yes, seen the same with Avast and Thunderbird upgrades previously.
Do as cyberzork recommends … 
We have been working with emClient last couple of days, and others have found similar, that there is a conflict with AVG/Avast. I found a process at AVG that exports a certificate, which you then import into emClient. Am testing this today. If ok, I will update with the process.
No I don’t.
