eM client crashes after connecting to my Courier IMAP server

Crash exception:
System.IndexOutOfRangeException: Index was outside the bounds of the array.
at MailClient.Imap.Base.NamespaceNotification.NamespaceListFromImapList(ListParameter list)
at MailClient.Imap.Base.NamespaceNotification…ctor(String namespaceLine, UnbufferedTextReader reader)
at MailClient.Imap.Base.Notification.FromUntaggedResponse(String line, UnbufferedTextReader reader)
at MailClient.Imap.Base.Connection.ParseUntagged(String line)
at MailClient.Imap.Base.Connection.ParseReply(String line)
at MailClient.Imap.Base.Connection.ReceiveWorker()
at System.Threading.ThreadHelper.ThreadStart_Context(Object state)

Connection dump:
* OK [CAPABILITY IMAP4rev1 UIDPLUS CHILDREN NAMESPACE THREAD=ORDEREDSUBJECT THREAD=REFERENCES SORT QUOTA IDLE ACL ACL2=UNION STARTTLS] Courier-IMAP ready. Copyright 1998-2004 Double Precision, Inc. See COPYING for distribution information.
A0 CAPABILITY
* CAPABILITY IMAP4rev1 UIDPLUS CHILDREN NAMESPACE THREAD=ORDEREDSUBJECT THREAD=REFERENCES SORT QUOTA IDLE ACL ACL2=UNION STARTTLS
A0 OK CAPABILITY completed
A1 LOGIN “XXX” “XXX”
A1 OK LOGIN Ok.
A2 NAMESPACE
* NAMESPACE ((“INBOX.” “.”)) NIL (("#shared." “”)(“shared.” “.”))
A2 OK NAMESPACE completed.

It is a bug in the Courier server, where the path delimiter in the NAMESPACE response is empty. The correct response from the server should be

* NAMESPACE ((“INBOX.” “.”)) NIL (("#shared." NIL)(“shared.” “.”))

We are adding a workaround for this to eM Client 3.5. Beta version should be available within few days.

Thanks!