Hi Nocholas
> I'm happy this works! Would be great to help others not to fall into
> the same trap.
>
> Certainly, I think this needs to be handled properly by the exception
> handling. However, I am no expert in objc in this. Maybe file a bug
> report.
>
Yeah, will do.
Cheers
Lars
--
---
HI Lars,
Everything is working fine now in the production-system clone. I will
have to play through the whole update process again, to make sure that
works flawlessly but you helped me clarifiying the config very much,
indeed. Maybe this could be clarified in the documentation as well(?). I
Hello Nicholas,
thank you very much!
> imaps://localhost:993/?tlsVerifyMode=allowInsecureLocalhost
was the way I actually wanted it to be.
Everything is working fine now in the production-system clone. I will
have to play through the whole update process again, to make sure that
works
Hi Lars,
ERROR(-[NGImap4Client _processUnknownCommandParserException:]): catched
non-IMAP4 parsing exception NGSocketException: NGActiveSocket is not open
Nov 04 12:25:43 sogod [85659]: [ERROR]
<0x0x8123bd708[NGImap4ConnectionManager]> IMAP4 login failed:
> host=localhost, user=ry86,
Hello Nicholas,
took me some time, but I have found more information, while I was
setting up a FreeBSD-Environment in a box in which I could build SOGo
and SOPE in explicit versions and have all the connnected services like
ldap/AD, postfix and dovecot configured.
The problem seems to be in
Hi Lars,
Any ideas on that?
It is no problem running 5.0.0 for us for now, I just wanted to share
this, as it might be helpful. Or should I run SOGo 5.0.1 with SOPE
5.0.0 on commit 099e8b0ec8251dbddeff337fe728d9398ba744b2?
This Log is not really helpful (at least not to me), unfortunately.
Hi Nicholas ,
SOGo 5.0.0 with SOPE 5.0.0 updated to commit
099e8b0ec8251dbddeff337fe728d9398ba744b2 (don't leak fds) worked. So
after that I saw that SOGo 5.0.1 and SOPE 5.0.1 were released. So I
tried combining both. But then I again get a blank page after Login,
with errors in the Log like:
>
