Comments in-line.
Am 16.02.16 um 18:30 schrieb Christian Mack:
hello
Am 16.02.2016 um 17:16 schrieb m.plo...@berlin.de:
Heya,
When trying to connect to a SOGo installation with Outlook 2016, these errors
appear in my log.
Feb 16 09:38:45 sogod [30243]: [ERROR] <0x0x5633db73fbd8[WOHttpTransaction]>
client disconnected during delivery of response for
<WORequest[0x0x5633dba094e8]: method=POST uri=/SOGo/Microsoft-Server-
ActiveSync?
Cmd=Sync&User=u...@domain.tld&DeviceId=DEVICEID&DeviceType=WindowsOutlook15
app=SOGo rqKey=Microsoft-Server-ActiveSync rqPath=(null)> (len=0): the socket
was shutdown
Feb 16 09:38:45 sogod [30243]: localhost "POST /SOGo/Microsoft-Server-
ActiveSync?
Cmd=Sync&User=u...@domain.tld&DeviceId=DEVICEID&DeviceType=WindowsOutlook15
HTTP/1.0" 503 0/16812 303.853 - - 334M
The connection then fails. SOGo is part of an iRedMail installation, I already
checked with the developer, but he can't help me with this issue.
There is a similar case here on the mailing list, but the user was having a
faulty rewrite rule. That doesn't seem to be the case here. Also, Outlook for
Android and Outlook for Windows Phone seems to be unaffected and work without
issues (probably due to a different prtocoll being used)
Any ideas?
1) Outlook for Android and Outlook for Windows Phone only share the same
name with Outlook 20XX on PCs. They have completely different codebases,
are developed from completely different development teams, which were
not even part of Microsoft, when they wrote those first two.
I see. I could talk to the product teams, fortunately my mobile clients
work.
2) There are no different protocols used, you always seem to use
ActiveSync for synchronizing.
At least that is what your error messages suggest.
From what I recall, SOGo isn't supporting EWS anyway. So EAS is the
only protocol available, right?
3) The error message says, that the connection was closed from the
client, before the complete response could be delivered from SOGo.
That can mean, that the Proxy server closed the connection, but it can
also happen, because Outlook did close the connection or the network did
fail.
There is no Proxy between the client and the SOGo service. There is
however a firewall. I'll check for the logs. The sogo.log says the
socket was shutdown. Has it been shut down because of a lack of activity
from the client or because of an internal error within SOGo?
Perhaps your sogo.conf parameters for ActiveSync are bogus
I checked the sogo.conf. What should I look for? I've enabled
SOGoEASDebugEnabled = YES for now.
Perhaps your settings for the ProxyPass directive in Apache is bogus.
I'm using nginx. This is from my conf
location ^~ /SOGo {
proxy_pass http://127.0.0.1:20000;
proxy_set_header x-webobjects-server-protocol HTTP/1.0;
proxy_connect_timeout 600;
proxy_send_timeout 600;
proxy_read_timeout 600;
}
location ^~ /Microsoft-Server-ActiveSync {
proxy_pass http://127.0.0.1:20000/SOGo/Microsoft-Server-ActiveSync;
proxy_redirect http://127.0.0.1:20000/Microsoft-Server-ActiveSync /;
}
location ^~ /SOGo/Microsoft-Server-ActiveSync {
proxy_pass http://127.0.0.1:20000/SOGo/Microsoft-Server-ActiveSync;
proxy_redirect
http://127.0.0.1:20000/SOGo/Microsoft-Server-ActiveSync /;
}
location /SOGo.woa/WebServerResources/ {
alias /usr/lib/GNUstep/SOGo/WebServerResources/;
}
location /SOGo/WebServerResources/ {
alias /usr/lib/GNUstep/SOGo/WebServerResources/;
}
location ^/SOGo/so/ControlPanel/Products/([^/]*)/Resources/(.*)$ {
alias /usr/lib/GNUstep/SOGo/$1.SOGo/Resources/$2;
}
Perhaps your network is unstable.
Perhaps your Outlook doesn't like something in your setup.
4) Please give us a hint, which version of sogo you use.
marc@mail:~$ dpkg -s sogo
...
Architecture: amd64
Multi-Arch: same
Version: 2.3.8-1
Kind regards,
Christian Mack
Thanks for your help,
Marc Plogas
--
users@sogo.nu
https://inverse.ca/sogo/lists
