On 05/08/15 17:05, Andreas Hainke wrote: > Hi Daniel
Hi, Andreas. > Have a look at /etc/default/sogo, PREFORK=xyz overrides the setting of > WOWorkersCount. But this setting is only relevant if sogo logs messages like > Aug 05 08:00:38 sogod [720]: [ERROR] <0x0x7f1ce01f7000[WOWatchDog]> No > child available to handle incoming request! Thanks for the observation. Just today I've noticed a lot of lines of this type when sync with Android and ActiveSync (few minutes ago I sent an email with some tests I made with Android without any problem). In Debian the PREFORK line (PREFORK=3) was commented. So I added a line with PREFORK=20. After that, so far I have not seen lines with "No child available to handle incoming request!" >> What strikes me is that I don't see on /var/log/apache2/access.log any >> access to /Microsoft-Server-ActiveSync from the virtual machine where >> I'm doing tests with Windows. Do you see any entry in your Apache from >> the Outlook IP to access /Microsoft-Server-ActiveSync? > Yes I have quite a lot of entries in the access log like this: > > 10.10.10.190 - - [05/Aug/2015:10:52:41 +0200] "POST > /Microsoft-Server-ActiveSync?Cmd=Ping&User=te...@piraten.lan&DeviceId=C199A908AC31425381AA3BCA7BDA590E&Dev > iceType=WindowsOutlook15 HTTP/1.1" 502 793 "-" "Outlook/15.0 > (15.0.4737.1000; C2R; x86)" Perfect! Thank you for the confirmation! >> I also see that the documentation says on page 50: "Outlook 2013 does >> not search the GAL. One possible alternative solution is to configure >> Outlook to use LDAP server (over SSL) with authentication". >> >> Are you using Outlook with LDAP? Currently I'm using a MySQL database >> for authenticating the users of SOGo, not LDAP. Nor am I using Apache >> SSL connections. Could this affect the connection issue? Anyway, I guess >> I would have to see at least some entry on the Apache log. > I'm using LDAP, but only for SOGo user authentication. I haven't changed > anything for the global address list. GAL is not available in my setup. Good. Thank you for the confirmation. > I traced it down, like you suggested, not using SSL could be the > problem. I tried to setup Outlook 2013 with plain http and get an error > while account configuration dialog. I captured the traffic with > wireshark. Outlook 2013 only tries to connect to port 443 in my case > even if I supply the server address including port. That seems to be the > problem. Try to enable SSL. > > Surprisingly using Windows Mail (shipped with Windows 10) and ActiveSync > works with plain http. Interesting. With this I can say that I see some light at the end of the tunnel :-) I also appreciate that you've taken the time to make a Wireshark capture. It was something that today crossed my mind (I was running out my choices). I'll do a test configuring the access to SOGo with https and I'll let you know the results. Have you had any problems in Outlook using self-signed certificates? Thank you very much for your time. Best regards, Daniel
signature.asc
Description: OpenPGP digital signature
