Dear Péter (and list),
I fully agree with your opinion on Outlook. But it doesn't seem to be in
our power to break its dominance in business environments so we sadly
have to deal with it.
I followed your hint an configured the permissions for the shared
calendar with the web interface. It works fine there, I can read an
write the shared calendars. But still it doesn't work in Outlook.
I tried around and found that Outlook doesn't authenticate correctly
against ocsmanager. As (if I recall right - correct me if I'm wrong)
openchange handles shared calendars via ews and thus via ocsmanager that
looks as it could be related to the problem. This is from the apache
(ssl) log:
192.168.16.97 - - [14/Aug/2013:17:53:15 +0200] "POST /ews/as HTTP/1.1"
401 5317 "-" "Microsoft Office/14.0 (Windows NT 6.1; Microsoft Outlook
14.0.6129; Pro)"
192.168.16.97 - - [14/Aug/2013:17:53:15 +0200] "POST /ews/as HTTP/1.1"
401 634 "-" "Microsoft Office/14.0 (Windows NT 6.1; Microsoft Outlook
14.0.6129; Pro)"
192.168.16.97 - - [14/Aug/2013:17:53:15 +0200] "POST /ews/as HTTP/1.1"
200 3146 "-" "Microsoft Office/14.0 (Windows NT 6.1; Microsoft Outlook
14.0.6129; Pro)"
192.168.16.97 - - [14/Aug/2013:17:53:18 +0200] "HEAD /ews/oab.xml
HTTP/1.1" 401 5264 "-" "Microsoft BITS/7.5"
192.168.16.97 - - [14/Aug/2013:17:53:20 +0200] "HEAD /ews/oab.xml
HTTP/1.1" 401 325 "-" "Microsoft BITS/7.5"
192.168.16.97 - - [14/Aug/2013:17:53:22 +0200] "HEAD /ews/oab.xml
HTTP/1.1" 401 325 "-" "Microsoft BITS/7.5"
192.168.16.97 - - [14/Aug/2013:17:53:22 +0200] "HEAD /ews/oab.xml
HTTP/1.1" 401 581 "-" "Microsoft BITS/7.5"
192.168.16.97 - - [14/Aug/2013:17:53:22 +0200] "HEAD /ews/oab.xml
HTTP/1.1" 404 261 "-" "Microsoft BITS/7.5"
192.168.16.97 - - [14/Aug/2013:17:53:24 +0200] "POST
/autodiscover/autodiscover.xml HTTP/1.1" 401 5317 "-" "Microsoft
Office/14.0 (Windows NT 6.1; Microsoft Outlook 14.0.6129; Pro)"
192.168.16.97 - - [14/Aug/2013:17:53:24 +0200] "POST
/autodiscover/autodiscover.xml HTTP/1.1" 401 634 "-" "Microsoft
Office/14.0 (Windows NT 6.1; Microsoft Outlook 14.0.6129; Pro)"
192.168.16.97 - - [14/Aug/2013:17:53:24 +0200] "POST
/autodiscover/autodiscover.xml HTTP/1.1" 200 1514 "-" "Microsoft
Office/14.0 (Windows NT 6.1; Microsoft Outlook 14.0.6129; Pro)"
192.168.16.97 - - [14/Aug/2013:17:54:04 +0200] "POST /ews/oof HTTP/1.1"
401 5317 "-" "Microsoft Office/14.0 (Windows NT 6.1; Microsoft Outlook
14.0.6129; Pro)"
192.168.16.97 - - [14/Aug/2013:17:54:04 +0200] "POST /ews/oof HTTP/1.1"
401 634 "-" "Microsoft Office/14.0 (Windows NT 6.1; Microsoft Outlook
14.0.6129; Pro)"
192.168.16.97 - - [14/Aug/2013:17:54:04 +0200] "POST /ews/oof HTTP/1.1"
404 362 "-" "Microsoft Office/14.0 (Windows NT 6.1; Microsoft Outlook
14.0.6129; Pro)"
192.168.16.97 - - [14/Aug/2013:17:54:04 +0200] "POST /ews/oof HTTP/1.1"
401 5317 "-" "Microsoft Office/14.0 (Windows NT 6.1; Microsoft Outlook
14.0.6129; Pro)"
192.168.16.97 - - [14/Aug/2013:17:54:04 +0200] "POST /ews/oof HTTP/1.1"
401 634 "-" "Microsoft Office/14.0 (Windows NT 6.1; Microsoft Outlook
14.0.6129; Pro)"
192.168.16.97 - - [14/Aug/2013:17:54:04 +0200] "POST /ews/oof HTTP/1.1"
404 362 "-" "Microsoft Office/14.0 (Windows NT 6.1; Microsoft Outlook
14.0.6129; Pro)"
192.168.16.97 - - [14/Aug/2013:17:54:26 +0200] "HEAD /ews/oab.xml
HTTP/1.1" 401 5264 "-" "Microsoft BITS/7.5"
192.168.16.97 - - [14/Aug/2013:17:54:28 +0200] "HEAD /ews/oab.xml
HTTP/1.1" 401 325 "-" "Microsoft BITS/7.5"
192.168.16.97 - - [14/Aug/2013:17:54:30 +0200] "HEAD /ews/oab.xml
HTTP/1.1" 401 325 "-" "Microsoft BITS/7.5"
192.168.16.97 - - [14/Aug/2013:17:54:30 +0200] "HEAD /ews/oab.xml
HTTP/1.1" 401 581 "-" "Microsoft BITS/7.5"
192.168.16.97 - - [14/Aug/2013:17:54:30 +0200] "HEAD /ews/oab.xml
HTTP/1.1" 404 261 "-" "Microsoft BITS/7.5"
192.168.16.97 - - [14/Aug/2013:17:54:32 +0200] "POST
/autodiscover/autodiscover.xml HTTP/1.1" 401 5573 "-" "Microsoft
Office/14.0 (Windows NT 6.1; Microsoft Outlook 14.0.6129; Pro)"
192.168.16.97 - - [14/Aug/2013:17:54:32 +0200] "POST
/autodiscover/autodiscover.xml HTTP/1.1" 200 1514 "-" "Microsoft
Office/14.0 (Windows NT 6.1; Microsoft Outlook 14.0.6129; Pro)"
This is from the ocsmanager log:
2013-08-14 17:53:15,769 INFO [openchange.web.auth.NTLMAuthHandler]
[worker 9] client did not pass auth cookie
2013-08-14 17:53:15,793 INFO [openchange.web.auth.NTLMAuthHandler]
[worker 0] client did not pass auth cookie
2013-08-14 17:53:15,793 INFO [openchange.web.auth.NTLMAuthHandler]
[worker 0] acquiring lock /var/cache/ntlmauthhandler/ntlm-127.0.0.1.lock
(1053)
2013-08-14 17:53:15,846 INFO [openchange.web.auth.NTLMAuthHandler]
[worker 1] acquiring lock /var/cache/ntlmauthhandler/ntlm-127.0.0.1.lock
(1053)
2013-08-14 17:53:18,191 INFO [openchange.web.auth.NTLMAuthHandler]
[worker 3] client did not pass auth cookie
2013-08-14 17:53:20,680 INFO [openchange.web.auth.NTLMAuthHandler]
[worker 5] client did not pass auth cookie
2013-08-14 17:53:22,700 INFO [openchange.web.auth.NTLMAuthHandler]
[worker 4] client did not pass auth cookie
2013-08-14 17:53:22,704 INFO [openchange.web.auth.NTLMAuthHandler]
[worker 6] client did not pass auth cookie
2013-08-14 17:53:22,704 INFO [openchange.web.auth.NTLMAuthHandler]
[worker 6] acquiring lock /var/cache/ntlmauthhandler/ntlm-127.0.0.1.lock
(1053)
2013-08-14 17:53:22,710 INFO [openchange.web.auth.NTLMAuthHandler]
[worker 7] acquiring lock /var/cache/ntlmauthhandler/ntlm-127.0.0.1.lock
(1053)
2013-08-14 17:53:24,732 INFO [openchange.web.auth.NTLMAuthHandler]
[worker 2] client did not pass auth cookie
2013-08-14 17:53:24,735 INFO [openchange.web.auth.NTLMAuthHandler]
[worker 8] client did not pass auth cookie
2013-08-14 17:53:24,736 INFO [openchange.web.auth.NTLMAuthHandler]
[worker 8] acquiring lock /var/cache/ntlmauthhandler/ntlm-127.0.0.1.lock
(1053)
2013-08-14 17:53:24,743 INFO [openchange.web.auth.NTLMAuthHandler]
[worker 9] acquiring lock /var/cache/ntlmauthhandler/ntlm-127.0.0.1.lock
(1053)
2013-08-14 17:54:04,746 INFO [openchange.web.auth.NTLMAuthHandler]
[worker 0] client did not pass auth cookie
2013-08-14 17:54:04,779 INFO [openchange.web.auth.NTLMAuthHandler]
[worker 1] client did not pass auth cookie
2013-08-14 17:54:04,779 INFO [openchange.web.auth.NTLMAuthHandler]
[worker 1] acquiring lock /var/cache/ntlmauthhandler/ntlm-127.0.0.1.lock
(1053)
2013-08-14 17:54:04,814 INFO [openchange.web.auth.NTLMAuthHandler]
[worker 3] acquiring lock /var/cache/ntlmauthhandler/ntlm-127.0.0.1.lock
(1053)
2013-08-14 17:54:04,881 INFO [openchange.web.auth.NTLMAuthHandler]
[worker 5] client did not pass auth cookie
2013-08-14 17:54:04,906 INFO [openchange.web.auth.NTLMAuthHandler]
[worker 4] client did not pass auth cookie
2013-08-14 17:54:04,907 INFO [openchange.web.auth.NTLMAuthHandler]
[worker 4] acquiring lock /var/cache/ntlmauthhandler/ntlm-127.0.0.1.lock
(1053)
2013-08-14 17:54:04,913 INFO [openchange.web.auth.NTLMAuthHandler]
[worker 6] acquiring lock /var/cache/ntlmauthhandler/ntlm-127.0.0.1.lock
(1053)
2013-08-14 17:54:26,229 INFO [openchange.web.auth.NTLMAuthHandler]
[worker 7] client did not pass auth cookie
2013-08-14 17:54:28,735 INFO [openchange.web.auth.NTLMAuthHandler]
[worker 2] client did not pass auth cookie
2013-08-14 17:54:30,751 INFO [openchange.web.auth.NTLMAuthHandler]
[worker 8] client did not pass auth cookie
2013-08-14 17:54:30,757 INFO [openchange.web.auth.NTLMAuthHandler]
[worker 9] client did not pass auth cookie
2013-08-14 17:54:30,758 INFO [openchange.web.auth.NTLMAuthHandler]
[worker 9] acquiring lock /var/cache/ntlmauthhandler/ntlm-127.0.0.1.lock
(1053)
2013-08-14 17:54:30,764 INFO [openchange.web.auth.NTLMAuthHandler]
[worker 0] acquiring lock /var/cache/ntlmauthhandler/ntlm-127.0.0.1.lock
(1053)
2013-08-14 17:54:32,771 INFO [openchange.web.auth.NTLMAuthHandler]
[worker 1] client did not pass auth cookie
2013-08-14 17:54:32,771 INFO [openchange.web.auth.NTLMAuthHandler]
[worker 1] acquiring lock /var/cache/ntlmauthhandler/ntlm-127.0.0.1.lock
(1053)
2013-08-14 17:54:32,778 INFO [openchange.web.auth.NTLMAuthHandler]
[worker 3] acquiring lock /var/cache/ntlmauthhandler/ntlm-127.0.0.1.lock
For me it looks like Outlook never sends the right authentication and
because of that ocsmanager just sends the free/busy information but no
other details back to Outlook. I can't dig deeper today, but I will
tomorrow. Maybe somebody has an idea? I found that my
/etc/ocsmanager/ocsmanager.ini (http://pastebin.com/Qcs0vriS) is pretty
raw, was I supposed to configure it? I never came across it.
Sorry for this unreflected mail - just some last minute thoughts before
knock off. But am I right that my calendar problem could be related to
ocsmanager or is this normal behaviour? I also saw that even when I tell
Outlook to connect via http there is very little activity with apache
oder ocsmanager but very much witch samba so it seems to me that it
connects directly via rpc after all.
Best regards
Michael
Am 14.08.2013 17:05, schrieb Szládovics Péter:
Dear Michael,
Just a hint from me, but it maybe (I hope) helps you.
The outlook not the best choice (IMHO the worst), but on commercial
environment it's the default (a Hungarian slang: the necessary evil).
So. Workaround, but working fine:
Share all of needed resources under the web (SOGo interface), and use
them in Outlook.
One thing won't works: shared folders. But contacts and calendars ;)
You will need same method about out of office settings and server side
mail rules.
As far as I excperienced - Thunderbird the one and only MUA for using
the most features (with lot of extensions), but neither the sharing
resources.
So, the web client will your best friend ever :)
--
users@sogo.nu
https://inverse.ca/sogo/lists
