subject:"Re\: \[SOGo\] SOGo 5.0.0 Login Problem"

Re: [SOGo] SOGo 5.0.0 Login Problem -> SOGo 5.0.1

2020-11-06 Thread Lars Liedtke

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

-- 
---
punkt.de GmbH
Lars Liedtke
.infrastructure

Kaiserallee 13a 
76133 Karlsruhe

Tel. +49 721 9109 500
https://infrastructure.punkt.de
i...@punkt.de

AG Mannheim 108285
Geschäftsführer: Jürgen Egeling, Daniel Lienert, Fabian Stein

-- 
users@sogo.nu
https://inverse.ca/sogo/lists

Re: [SOGo] SOGo 5.0.0 Login Problem -> SOGo 5.0.1

2020-11-05 Thread nico...@hoeft.de


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
would be willing to do that with providing a pull request, in a couple
of days.


I'm happy this works! Would be great to help others not to fall into the 
same trap.




The only thing that bugs me a bit, is that the WebUI simply goes blank,
when there are certain configuration errors. Do you see a way to improve
this?


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.



best regards,

Nicolas

--
users@sogo.nu
https://inverse.ca/sogo/lists

Re: [SOGo] SOGo 5.0.0 Login Problem -> SOGo 5.0.1

2020-11-05 Thread Lars Liedtke

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 flawlessly but you helped me clarifiying the config very much,
indeed. Maybe this could be clarified in the documentation as well(?). I
would be willing to do that with providing a pull request, in a couple
of days.

The only thing that bugs me a bit, is that the WebUI simply goes blank,
when there are certain configuration errors. Do you see a way to improve
this?

Cheers and thanks again

Lars

Am 04.11.20 um 18:58 schrieb Nicolas Höft (nico...@hoeft.de):
> 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, pwd=yes
>>   >
>> url=imaps://ry86@localhost:993/?tls=YES=allowInsecureLocalhost
>>
>>   > base=(null)
>>   > base-class=(null))
>>   > = <0x0x80c3c7028[NGImap4Client]: login=ry86(pwd)
>> socket=
>> address=<0x0x80caeb758[NGInternetSocketAddress]: host=localhost
>> port=42967>>>
>
> Please do not combine imaps (imap over TLS, default port 993) and IMAP
> with STARTTLS (port 143, and the TLS connection is established on the
> same socket after the handshake).
>
> What you probably wanted was one of these:
>
> * imaps://localhost:993/?tlsVerifyMode=allowInsecureLocalhost
>
> or
>
> * imap://localhost:143/?tls=YES=allowInsecureLocalhost
>
> Cheers,
>
> Nicolas
>
-- 
---
punkt.de GmbH
Lars Liedtke
.infrastructure

Kaiserallee 13a 
76133 Karlsruhe

Tel. +49 721 9109 500
https://infrastructure.punkt.de
i...@punkt.de

AG Mannheim 108285
Geschäftsführer: Jürgen Egeling, Daniel Lienert, Fabian Stein


-- 
users@sogo.nu
https://inverse.ca/sogo/lists

Re: [SOGo] SOGo 5.0.0 Login Problem -> SOGo 5.0.1

2020-11-04 Thread nico...@hoeft.de


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, pwd=yes
  >
url=imaps://ry86@localhost:993/?tls=YES=allowInsecureLocalhost
  > base=(null)
  > base-class=(null))
  > = <0x0x80c3c7028[NGImap4Client]: login=ry86(pwd)
socket=
address=<0x0x80caeb758[NGInternetSocketAddress]: host=localhost
port=42967>>>


Please do not combine imaps (imap over TLS, default port 993) and IMAP 
with STARTTLS (port 143, and the TLS connection is established on the 
same socket after the handshake).


What you probably wanted was one of these:

* imaps://localhost:993/?tlsVerifyMode=allowInsecureLocalhost

or

* imap://localhost:143/?tls=YES=allowInsecureLocalhost

Cheers,

Nicolas

--
users@sogo.nu
https://inverse.ca/sogo/lists

Re: [SOGo] SOGo 5.0.0 Login Problem -> SOGo 5.0.1

2020-11-04 Thread Lars Liedtke

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 conjunction with requests made to other
services: If the imap or ldap connections fail, for example because ldap
is not reachable or the imap configuration is wrong. Then the WebUI
simply won't finish to load. What I can see is about 70% that the
SOGo-Backend delivers to Angular in the Frontend and then stops. This
causes the UI to go blank seemingly without any error displayed. But not
totally. While clicking around in the Browser I rather randomly went to
the browser's Java Script-Console and this shows a Proxy-Error after
about a minute, which seems to be a timeout. In the apache log I see
this ProxyError

> [Wed Nov 04 12:12:42.956664 2020] [proxy_http:error] [pid 18011:tid
34399326720] (70007)The timeout specified has expired: [client
2a00:b580:a000:c800::100d:35790] AH01102: error reading status line from
remote server 127.0.0.1:2, referer:
https://vpro0214.proserver.punkt.de/SOGo/so/ry86/Mail/view
> [Wed Nov 04 12:12:42.956774 2020] [proxy:error] [pid 18011:tid
34399326720] [client 2a00:b580:a000:c800::100d:35790] AH00898: Error
reading from remote server returned by
/SOGo/so/ry86/Mail/0/folderINBOX/view, referer:
https://vpro0214.proserver.punkt.de/SOGo/so/ry86/Mail/view

and in the maillog Dovecot writes the following:

> Nov  4 12:24:43 vpro0214 dovecot: imap-login: Disconnected: Inactivity
(no auth attempts in 180 secs): user=<>, rip=127.0.0.1, lip=127.0.0.1,
TLS handshaking, session=

When restarting sogod I the many log entries with activated Debug logs I
can see this:

> Nov 04 12:25:43 sogod [85659]: <0x0x80c3c7028[NGImap4Client]>
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, pwd=yes
 >
url=imaps://ry86@localhost:993/?tls=YES=allowInsecureLocalhost
 > base=(null)
 > base-class=(null))
 > = <0x0x80c3c7028[NGImap4Client]: login=ry86(pwd)
socket=
address=<0x0x80caeb758[NGInternetSocketAddress]: host=localhost
port=42967>>>

So I started playing around with the imap configurations I made:

> domains =
>    {
>   punkt.de =
>    {
>    /* Mail */
>    SOGoDraftsFolderName = "Entwürfe";
>    SOGoSentFolderName = "Gesendet";
>    SOGoTrashFolderName = "Mülleimer";
>    SOGoJunkFolderName = "Junk";
>    SOGoIMAPServer =
"imap://localhost:993/?tls=YES=allowInsecureLocalhost";
>    SOGoSieveServer =
"sieve://localhost:4190/?tls=YES=allowInsecureLocalhost";
>    SOGoSMTPServer =
"smtp://localhost:465/?tls=YES=allowInsecureLocalhost";
>    SOGoMailDomain = punkt.de;
>    SOGoMailingMechanism = smtp;

When I turn TLS off for imap and switch to port 143, everything works fine.

> SOGoIMAPServer = "imap://localhost:143/";

So there has to be some kind of problem between SOGo and Dovecot when
communicationg over TLS. But I was not able to figure out what the exact
Problem is. For the moment it would be ok switching to imap nistead of
imaps. But before trying this in our production system I will replay the
whole upgrade process from 4 to 5 with changing to imap in a clone of
our production system for testing.

Maybe you are able to make out something from this mail to find the
underlying problem in the SOGo Code.

Cheers

Lars


Am 12.10.20 um 15:55 schrieb Nicolas Höft (nico...@hoeft.de):
> 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. If
> you have time and want to figure out what commit is causing this, I'd
> suggest to start with 5.0.0 both SOGo and SOPE and then upgrade SOPE
> to 5.0.1 and then if it still works try to bisect which SOGo commit is
> causing the login problems.
>
>
> cheers,
>
> Nicolas
>
>
>
-- 
---
punkt.de GmbH
Lars Liedtke
.infrastructure

Kaiserallee 13a 
76133 Karlsruhe

Tel. +49 721 9109 500
https://infrastructure.punkt.de
i...@punkt.de

AG Mannheim 108285
Geschäftsführer: Jürgen Egeling, Daniel Lienert, Fabian Stein


-- 
users@sogo.nu
https://inverse.ca/sogo/lists

Re: [SOGo] SOGo 5.0.0 Login Problem -> SOGo 5.0.1

2020-10-12 Thread nico...@hoeft.de


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. If 
you have time and want to figure out what commit is causing this, I'd 
suggest to start with 5.0.0 both SOGo and SOPE and then upgrade SOPE to 
5.0.1 and then if it still works try to bisect which SOGo commit is 
causing the login problems.



cheers,

Nicolas



--
users@sogo.nu
https://inverse.ca/sogo/lists

Re: [SOGo] SOGo 5.0.0 Login Problem -> SOGo 5.0.1

2020-10-12 Thread Lars Liedtke

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:

> Oct 09 15:17:31 sogod [38523]: |SOGo|   using root-url from context:
> /SOGo/so/
> Oct 09 15:17:31 sogod [38523]: |SOGo| ROOT baseURL(no container,
> name=(null)):
>   own: /SOGo/so/
> Oct 09 15:17:31 sogod [38523]: <0x8127dc208[SOGoUserFolder]:ry86>
> baseURL: name=ry86 (container=SOGo)
>   container: /SOGo --
> https://mail.integration.punkt.hosting/SOGo/so/ry86/Calendar/view
>   own: /SOGo/so/ry86
> Oct 09 15:17:31 sogod [38523]: |SOGo|   using root-url from context:
> /SOGo/so/
> Oct 09 15:17:31 sogod [38523]: |SOGo| ROOT baseURL(no container,
> name=(null)):
>   own: /SOGo/so/
> Oct 09 15:17:31 sogod [38523]: <0x8127dc208[SOGoUserFolder]:ry86>
> baseURL: name=ry86 (container=SOGo)
>   container: /SOGo --
> https://mail.integration.punkt.hosting/SOGo/so/ry86/Calendar/view
>   own: /SOGo/so/ry86
> Oct 09 15:17:31 sogod [38523]:
> <0x80c2a8408[SOGoAppointmentFolders]:Calendar> baseURL: name=Calendar
> (container=SOGoUserFolder)
>   container: /SOGo/so/ry86/
>   own: /SOGo/so/ry86/Calendar
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?

Cheers

Lars

Am 05.10.20 um 14:53 schrieb Lars Liedtke (lied...@punkt.de):
>
> Hi Nicholas,
>
> thank you, indeed I was building SOGo 5 with the latest SOPE Port in
> FreeBSD, which is still on 4.x.
>
> So I will have to try to update the sope4 Port to as well and try with
> that.
>
> Cheers
>
> Lars
>
> Am 04.10.20 um 16:10 schrieb Nicolas Höft (nico...@hoeft.de):
>>
>> Hi,
>>
>> this error:
>>
>> > 2020-10-01 17:35:39.988 sogod[14915:101031] EXCEPTION: > > 0x80c39b878> NAME:NSInvalidArgumentException REASON:-[NSURL 
>> > queryComponents]: 
>> > unrecognized selector sent to instance 0x80c39b7e8 INFO:(null)
>>
>>
>> Indicates your SOPE version is not up-to-date. Make sure you are building 
>> with at least SOPE 5.0.0 (tagged as `SOPE-5.0.0` in git).
>> Also if you're using starttls for smtp or imap, better use the latest HEAD, 
>> otherwise you're going to suffer from leaking file descriptors.
>>
>> Cheers,
>> Nicolas
>> -- 
>> users@sogo.nu
>> https://inverse.ca/sogo/lists
> -- 
> ---
> punkt.de GmbH
> Lars Liedtke
> .infrastructure
>
> Kaiserallee 13a   
> 76133 Karlsruhe
>
> Tel. +49 721 9109 500
> https://infrastructure.punkt.de
> i...@punkt.de
>
> AG Mannheim 108285
> Geschäftsführer: Jürgen Egeling, Daniel Lienert, Fabian Stein
> -- 
> users@sogo.nu
> https://inverse.ca/sogo/lists

-- 
---
punkt.de GmbH
Lars Liedtke
.infrastructure

Kaiserallee 13a 
76133 Karlsruhe

Tel. +49 721 9109 500
https://infrastructure.punkt.de
i...@punkt.de

AG Mannheim 108285
Geschäftsführer: Jürgen Egeling, Daniel Lienert, Fabian Stein

-- 
users@sogo.nu
https://inverse.ca/sogo/lists

Re: [SOGo] SOGo 5.0.0 Login Problem

2020-10-02 Thread Lars Liedtke

Hi Odhiambo,

of course. I was facing the same "problem" as you, so at first I tried
copying the sogo4-Port and updating the Makefile. After I ran into some
problems I opened a bug in the FreeBSD-Bugtracker
(https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=249370) but
unfortunately neither the port maintainer nor someone else responded. So
I tried fixing the port specific patch problems I had with the help of a
long expirienced colleague and succeeded. So I have got a sogo5 port
draft and a pkg package built by poudriere, which installs fine. If
you'd like I am happy to share. Of course I cannot give any guarantees,
but if you'd like to try yourself and eventually help with my problem,
be my guest:

* https://github.com/punktDe/port-www_sogo5/tree/master

*
https://pkg.proserver.punkt.de/packages/113-2020Q3-mariadb104/All/sogo5-5.0.0.txz

Cheers

Lars

Am 01.10.20 um 20:06 schrieb Odhiambo Washington (odhia...@gmail.com):
> Hi Lars,
>
> Might you be able to share HOW you manually install it on FreeBSD?
> I usually rely on installing using the FreeBSD port and since v5
> hasn't been ported to FreeBSD, I am stuck on v4.3.2.
>
> -- 
>
> users@sogo.nu 
> https://inverse.ca/sogo/lists
>
>
>
> -- 
> Best regards,
> Odhiambo WASHINGTON,
> Nairobi,KE
> +254 7 3200 0004/+254 7 2274 3223
> "Oh, the cruft.", grep ^[^#] :-)
> -- 
> users@sogo.nu
> https://inverse.ca/sogo/lists

-- 
---
punkt.de GmbH
Lars Liedtke
.infrastructure

Kaiserallee 13a 
76133 Karlsruhe

Tel. +49 721 9109 500
https://infrastructure.punkt.de
i...@punkt.de

AG Mannheim 108285
Geschäftsführer: Jürgen Egeling, Daniel Lienert, Fabian Stein

-- 
users@sogo.nu
https://inverse.ca/sogo/lists

Re: [SOGo] SOGo 5.0.0 Login Problem

2020-10-01 Thread Odhiambo Washington

Hi Lars,

Might you be able to share HOW you manually install it on FreeBSD?
I usually rely on installing using the FreeBSD port and since v5 hasn't
been ported to FreeBSD, I am stuck on v4.3.2.


On Thu, 1 Oct 2020 at 20:13, Lars Liedtke  wrote:

> Hi *,
>
> So I tried installing SOGo5 on FreeBSD. Got it working so far, and set it
> up the same way I did with did with Sogo 4.3.2 (Ansible). But I cannot
> log in on my vagrant box neither over LDAP/AD nor over a "normal" Database
> connection.
>
> I can see an error in the logs, but I don't know what it means.
>
> Oct 01 17:35:39 sogod [14915]: |SOGo| starting method 'GET' on uri 
> '/SOGo/so/ry86/Mail/view'
> Oct 01 17:35:39 sogod [14915]: <0x0x80d24df68[SOGoCache]> Cache cleanup 
> interval set every 300.00 seconds
> Oct 01 17:35:39 sogod [14915]: <0x0x80d24df68[SOGoCache]> Using host(s) 
> 'localhost' as server(s)
> 2020-10-01 17:35:39.408 sogod[14915:101031]  connection=0x0x80d365a00> SQL: BEGIN;
> 2020-10-01 17:35:39.408 sogod[14915:101031]  connection=0x0x80d365a00>   query has no results.
> 2020-10-01 17:35:39.409 sogod[14915:101031]  connection=0x0x80d365a00> SQL: SELECT t1.c_creationdate, t1.c_id, 
> t1.c_lastseen, t1.c_value FROM  sogo_sessions_folder t1 WHERE 
> t1.c_id='lTB3MdkwTh+gJnR2n7EWSA==';
> 2020-10-01 17:35:39.410 sogod[14915:101031]  connection=0x0x80d365a00>   query has results, entering fetch-mode.
> 2020-10-01 17:35:39.411 sogod[14915:101031]  connection=0x0x80d365a00> SQL: ROLLBACK;
> 2020-10-01 17:35:39.411 sogod[14915:101031]  connection=0x0x80d365a00>   query has no results.
> 2020-10-01 17:35:39.414 sogod[14915:101031] MySQL4 connection established 
> 0x0x80d367300
> 2020-10-01 17:35:39.414 sogod[14915:101031] MySQL4 channel 0x0x80cfbe1e8 
> opened (connection=0x0x80d367300,sogo)
> 2020-10-01 17:35:39.414 sogod[14915:101031]  connection=0x0x80d367300> SQL: BEGIN;
> 2020-10-01 17:35:39.414 sogod[14915:101031]  connection=0x0x80d367300>   query has no results.
> 2020-10-01 17:35:39.414 sogod[14915:101031]  connection=0x0x80d367300> SQL: SELECT t1.c_creationdate, t1.c_id, 
> t1.c_lastseen, t1.c_value FROM  sogo_sessions_folder t1 WHERE 
> t1.c_id='lTB3MdkwTh+gJnR2n7EWSA==';
> 2020-10-01 17:35:39.414 sogod[14915:101031]  connection=0x0x80d367300>   query has results, entering fetch-mode.
> 2020-10-01 17:35:39.414 sogod[14915:101031]  connection=0x0x80d367300> SQL: ROLLBACK;
> 2020-10-01 17:35:39.415 sogod[14915:101031]  connection=0x0x80d367300>   query has no results.
> 2020-10-01 17:35:39.415 sogod[14915:101031]  connection=0x0x80d365a00> SQL: BEGIN;
> 2020-10-01 17:35:39.415 sogod[14915:101031]  connection=0x0x80d365a00>   query has no results.
> 2020-10-01 17:35:39.415 sogod[14915:101031]  connection=0x0x80d365a00> SQL: UPDATE sogo_sessions_folder SET c_lastseen = 
> 1601566539, c_creationdate = 1601565510, c_value = 
> 'U9DH9V/gAYHaYIayZFpnBicSJLIyP9kBsvyiHmvub5wtw6K7I6eZ/UI7IAZ2ds3gKrP5sIjXn7456T5IjjOt2Y3XTUSG9Aly8jFI2gqVBipPThJDYPUhO5cfmMIIJX+w8Y4OjcYz24YnIurshFOfIL6XeEHcU+pJaUmKgomWS57xxBdnLt6lP2nw0u47eIabFyuro+uJKwH0YI4U7wsgWg==',
>  c_id = 'lTB3MdkwTh+gJnR2n7EWSA==' WHERE c_id='lTB3MdkwTh+gJnR2n7EWSA==';
> 2020-10-01 17:35:39.416 sogod[14915:101031]  connection=0x0x80d365a00>   query has no results.
> 2020-10-01 17:35:39.416 sogod[14915:101031]  connection=0x0x80d365a00> SQL: COMMIT;
> 2020-10-01 17:35:39.418 sogod[14915:101031]  connection=0x0x80d365a00>   query has no results.
> 2020-10-01 17:35:39.422 sogod[14915:101031] MySQL4 connection established 
> 0x0x80d367800
> 2020-10-01 17:35:39.422 sogod[14915:101031] MySQL4 channel 0x0x80cfbef68 
> opened (connection=0x0x80d367800,sogo)
> 2020-10-01 17:35:39.422 sogod[14915:101031]  connection=0x0x80d367800> SQL: SELECT c_password FROM resources WHERE c_uid = 
> 'ry86';
> 2020-10-01 17:35:39.424 sogod[14915:101031]  connection=0x0x80d367800>   query has results, entering fetch-mode.
> Oct 01 17:35:39 sogod [14915]: <0x0x80d31ada8[NGLdapConnection]> Using 
> ldap_initialize for LDAP URL: ldap://127.0.0.1:389
> Oct 01 17:35:39 sogod [14915]: <0x0x80d31ae98[NGLdapConnection]> Using 
> ldap_initialize for LDAP URL: ldap://127.0.0.1:389
> 2020-10-01 17:35:39.505 sogod[14915:101031] -[NGLdapConnection 
> _searchAtBaseDN:qualifier:attributes:scope:]: search at base '' filter 
> '(objectClass=*)' for attrs 'subschemaSubentry'
> 2020-10-01 17:35:39.519 sogod[14915:101031] -[NGLdapConnection 
> _searchAtBaseDN:qualifier:attributes:scope:]: search at base '' 
> filter '(objectClass=*)' for attrs 'objectclasses'
> 2020-10-01 17:35:39.591 sogod[14915:101031] -[NGLdapConnection 
> _searchAtBaseDN:qualifier:attributes:scope:]: search at base '' 
> filter '' for attrs 'dn'
> 2020-10-01 17:35:39.687 sogod[14915:101031]  connection=0x0x80d367800> SQL: SELECT * FROM resources WHERE (c_uid = 'ry86') 
> OR (mail = 'ry86');
> 2020-10-01 17:35:39.687 sogod[14915:101031]  connection=0x0x80d367800>   query has results, entering fetch-mode.
> Oct 01 17:35:39 sogod [14915]:

Re: [SOGo] SOGo 5.0.0 Login Problem -> SOGo 5.0.1

Re: [SOGo] SOGo 5.0.0 Login Problem -> SOGo 5.0.1

Re: [SOGo] SOGo 5.0.0 Login Problem -> SOGo 5.0.1

Re: [SOGo] SOGo 5.0.0 Login Problem -> SOGo 5.0.1

Re: [SOGo] SOGo 5.0.0 Login Problem -> SOGo 5.0.1

Re: [SOGo] SOGo 5.0.0 Login Problem -> SOGo 5.0.1

Re: [SOGo] SOGo 5.0.0 Login Problem -> SOGo 5.0.1

Re: [SOGo] SOGo 5.0.0 Login Problem

Re: [SOGo] SOGo 5.0.0 Login Problem

9 matches

Site Navigation

Mail list logo

Footer information