On 10/23/2015 4:13 PM, Steve Ankeny wrote:
On 10/23/2015 09:32 AM, Chris Coleman wrote:
And this tip:
"If you face strange issues from Microsoft Outlook, you might want to
remove any data associated with the user from the SOGo server and
recreate a Microsoft Outlook profile. To remove any data associated
to a user, use the openchange_cleanup.py script distributed with
sogo. The script can be found in |/usr/share/doc/sogo/|
(|/usr/share/sogo-VERSION/| on |RHEL|). To reset a user, run the
script as root: |python openchange_cleanup.py username|. See the
usage output for additional options."
Chris . . .
What is meant by "strange issues?" Can you give examples?
For instance, I'm receiving, "The name cannot be resolved. The
requested operation failed because no search criteria were given to
the Microsoft Exchange Address Book." -- with errors in
'/ocsmanager.log' --
Starting server in PID 1885.
serving on http://127.0.0.1:5000
2015-10-17 07:44:28,313 INFO [openchange.web.auth.NTLMAuthHandler]
[worker 0] client did not pass auth cookie
2015-10-17 07:44:28,321 INFO [openchange.web.auth.NTLMAuthHandler]
[worker 1] client did not pass auth cookie
2015-10-17 07:44:28,358 INFO [openchange.web.auth.NTLMAuthHandler]
[worker 1] acquiring lock
/var/cache/ntlmauthhandler/ntlm-127.0.0.1.lock (1885)
2015-10-17 07:44:29,019 INFO [openchange.web.auth.NTLMAuthHandler]
[worker 2] acquiring lock
/var/cache/ntlmauthhandler/ntlm-127.0.0.1.lock (1885)
Would clearing out any existing data and recreating an Outlook profile
benefit my users?
Steve,
* That quote ("If you face strange issues from Microsoft Outlook, you
might want to [...] run the script as root: openchange_cleanup.py
username See the usage output for additional options.") comes from
openchange 2.0 release notes at this URL:
http://www.openchange.org/developers/relnotes/2.0-quadrant.html
in the section "Known Issues from SOGo backend".
You can and certainly should try it out, clear out and recreate an
Outlook profile.
I'd test it first. Make new Outlook user profile, send it some email,
then use that command line to clear it out (openchange_cleanup.py
username), see what that does. Recreate the user profile it if the user
profile for that username was truly removed completely. Just to be
totally sure that script works properly, before trying to run the script
on your real user profile.
* Here is another quote from the same 2.0 release notes, explaining
exactly how openchange and sogo interoperate.
"Benefits of SOGo collaboration
OpenChange server and SOGo ( http://www.sogo.nu ) are both groupware
servers sharing mutual interest in collaborating for the greatest
benefits of end users. The cement of this cooperation lies in a backend
developed by Inverse Inc on top of OpenChange API that plugs SOGo
storage to OpenChange server through SOGo libraries. From a general
perspective, it can be described as:
* *OpenChange uses SOGo libraries to store Outlook data*
* *SOGo uses OpenChange to serve Outlook clients*
In practice, it means that users primarily interested in an Exchange
compatible server interoperable with Microsoft Outlook clients don't
need anything but Samba4 and OpenChange. There is no need to run SOGo
server.
In the meanwhile, as soon as users are looking for Webmail access,
synchronization with Mozilla Thunderbird/Lighning, Apple iPhone or
Blackberry, then SOGo server is needed."
* Here is yet another page well worth reading because it explains in
more detail how OpenChange uses SOGo to store the user's Outlook (MAPI)
information in what it calls a "MAPIStore".
http://www.openchange.org/documentation/programming/mapistore_python/concepts.html
* I highly suggest having a good read of this series of pages because
they provide a more in depth look at how OpenChange and SOGo talk to one
another.
** Did you know the "realm", which you provide in the configuration,
(for example: mycompany.local which is 15 characters in length ) must be
14 characters or less in length, to satisfy a Microsoft realm name
length limit, otherwise strange and/or unpredictable results may occur?
I didn't know that. And it's undocumented in the SOGo documentation for
Native Outlook aka OpenChange,
http://www.sogo.nu/files/docs/SOGo%20Native%20Microsoft%20Outlook%20Configuration.pdf
. Now I know, after having read this openchange "docs" and "cookbook"!
Here is the reference explaining this (it's in the first section):
http://www.openchange.org/cookbook/configuring.html
"For the purpose of this documentation, arbitrary domain (|OC|) and
realm (|OC.LOCAL|) and passwords (|adminpass| and |user password|) have
been chosen. Feel free to adjust values to match your requirements.
However, when configuring the domain name during OS installation, it is
very important *NOT* to choose a realm which length is more or equal to
15 characters. This is a limit on Windows domain side which may result
in connectivity issues."
This limit should be right in the "SOGo Native Microsoft Outlook
Configuration.pdf" document, and a glaringly obvious comment in the
config file.
** http://www.openchange.org/cookbook/ocsmanager.html
** http://www.openchange.org/cookbook/backends/index.html
** http://www.openchange.org/cookbook/backends/sogo/index.html (slightly
outdated it's for 12.04 LTS ubuntu and the version of sogo used is not
mentioned)
** http://www.openchange.org/cookbook/backends/sogo/webui.html
** http://www.openchange.org/cookbook/backends/sogo/dovecot.html
** http://www.openchange.org/cookbook/backends/sogo/postfix.html
According do these pages, if you have done all these steps in order
properly, then you should have it fully configured and working, and the
steps in "Testing messasging services" should succeed exactly as described.
Let us know your results Steve, and others !
-Chris
--
[email protected]
https://inverse.ca/sogo/lists
