Hi, according to your earlier mail, it seems that you have sogo from 20170926 but sope from 20170721. When you use nightly == development builds, update both sogo and sope at the same time.
Cheers -- Slávek Dne st 4. října 2017 init napsal(a): > Hi, > > in this scenario ldap works for me fine, but I can't login to the SOGo > webinterface. Although I use valid credentials, I stay on the login > page and don't get into my mailbox. > This can also be seen in the sogo.log: > Oct 04 16:06:19 sogod [1310]: version 2.3.22 (build @shiva.inverse > 201710040510) -- starting Oct 04 16:06:20 sogod [1310]: vmem size check > enabled: shutting down app when vmem > 384 MB. Currently at 225 MB Oct > 04 16:06:20 sogod [1310]: <0x0x91e441c640[SOGoProductLoader]> SOGo > products loaded from '/usr/lib/GNUstep/SOGo': Oct 04 16:06:20 sogod > [1310]: <0x0x91e441c640[SOGoProductLoader]> Mailer.SOGo, > MailPartViewers.SOGo, Contacts.SOGo, MainUI.SOGo, > AdministrationUI.SOGo, MailerUI.SOGo, SchedulerUI.SOGo, CommonUI.SOGo, > ContactsUI.SOGo, PreferencesUI.SOGo, Appointments.SOGo Oct 04 16:06:22 > sogod [1310]: All products loaded - current memory usage at 272 MB Oct > 04 16:06:22 sogod [1310]: <0x0x91e4560290[WOWatchDog]> listening on > 127.0.0.1:20000 Oct 04 16:06:22 sogod [1310]: > <0x0x91e4560290[WOWatchDog]> watchdog process pid: 1310 Oct 04 16:06:22 > sogod [1310]: <0x0x7f9d327e1100[WOWatchDogChild]> watchdog request > timeout set to 10 minutes Oct 04 16:06:22 sogod [1310]: > <0x0x91e4560290[WOWatchDog]> preparing 3 children Oct 04 16:06:22 sogod > [1310]: <0x0x91e4560290[WOWatchDog]> child spawned with pid 1363 Oct 04 > 16:06:22 sogod [1310]: <0x0x91e4560290[WOWatchDog]> child spawned with > pid 1364 Oct 04 16:06:22 sogod [1310]: <0x0x91e4560290[WOWatchDog]> > child spawned with pid 1365 Oct 04 16:06:22 sogod [1363]: > <0x0x91e458ff40[WOHttpAdaptor]> notified the watchdog that we are ready > Oct 04 16:06:22 sogod [1364]: <0x0x91e458ff40[WOHttpAdaptor]> notified > the watchdog that we are ready Oct 04 16:06:22 sogod [1365]: > <0x0x91e458ff40[WOHttpAdaptor]> notified the watchdog that we are ready > Oct 04 14:49:41 sogod [1365]: <0x0x91e42a1160[SOGoCache]> Cache cleanup > interval set every 300.000000 seconds Oct 04 14:49:41 sogod [1365]: > <0x0x91e42a1160[SOGoCache]> Using host(s) 'localhost' as server(s) Oct > 04 14:49:41 sogod [1365]: [WARN] <0x0x7f9d32802cc0[WOxElemBuilder]> > could not locate builders: WOxExtElemBuilder,WOxExtElemBuilder Oct 04 > 14:49:41 sogod [1365]: 192.168.146.50 "GET /SOGo/ HTTP/1.1" 200 4505/0 > 0.536 12606 64% 3M Oct 04 14:52:14 sogod [1365]: 192.168.146.50 "GET > /SOGo/ HTTP/1.1" 200 4505/0 0.015 12606 64% 0 Oct 04 14:53:44 sogod > [1365]: 192.168.146.50 "GET /SOGo/ HTTP/1.1" 200 4505/0 0.021 12606 64% > 0 Oct 04 14:54:07 sogod [1365]: SOGoRootPage successful login from > '192.168.146.50' for user 'Administrator' - expire = -1 grace = -1 Oct > 04 14:54:07 sogod [1365]: 192.168.146.50 "POST /SOGo/connect HTTP/1.1" > 200 27/68 0.398 - - 1M Oct 04 14:54:07 sogod [1365]: 192.168.146.50 > "GET /SOGo/Administrator HTTP/1.1" 200 4505/0 0.209 12606 64% 420K > The only thing I see in the log is a warning message, which I haven't > gotten fixed yet. Anybody have any idea what my problem is? > > Greetings > Marc > > Gesendet: Mittwoch, 04. Oktober 2017 um 13:43 Uhr > Von: "\"lists\" ([email protected])" <[email protected]> > An: [email protected] > Betreff: Re: [SOGo] Problems logging on to the server with Outlook > 2010/2013 Ah I'm afraid I have been unclear: > > we ARE using on samba4, but only for the ldap functions > (authentication and ldap address book) > > We are *not* using OpenChange for native outlook compatibility. > > MJ > > On 4-10-2017 13:15, init ([email protected]) wrote: > > Hi, > > do you use openLdap instead of samba4 or an external Ldap-Server? > > Greetings > > Marc > > *Gesendet:* Mittwoch, 04. Oktober 2017 um 12:54 Uhr > > *Von:* "\"lists\" ([email protected])" <[email protected]> > > *An:* [email protected] > > *Betreff:* Re: [SOGo] Problems logging on to the server with Outlook > > 2010/2013 > > Hi, > > > > I can only tell you what we do: > > > > SOGo (v2) + Postfix + Dovecot, with ActiveSync. > > > > no samba4. > > > > MJ > > > > On 4-10-2017 11:55, init ([email protected]) wrote: > > > Hello, > > > can somebody answer my question below? > > > I'd really appreciate it, because somehow I'm going in circles. > > > Thanks in advance > > > Marc > > > *Gesendet:* Samstag, 30. September 2017 um 19:27 Uhr > > > *Von:* "\"init\" ([email protected])" <[email protected]> > > > *An:* [email protected] > > > *Betreff:* Aw: [SOGo] Problems logging on to the server with > > > Outlook 2010/2013 > > > Thanks for the answer. > > > So now only ActiveSync is supported or does the "normal" Outlook > > > connection work without openChange? > > > What's your recommendation? > > > SOGo + Samba4 + Postfix + Dovecot? > > > Many greetings > > > Marc > > > *Gesendet:* Samstag, 30. September 2017 um 18:52 Uhr > > > *Von:* "\"Rowland Penny\" ([email protected])" > > > <[email protected]> *An:* [email protected] > > > *Betreff:* Re: [SOGo] Problems logging on to the server with > > > Outlook 2010/2013 > > > On Sat, 30 Sep 2017 17:03:13 +0200 > > > > > > "init" ([email protected]) <[email protected]> wrote: > > > > Hello, everyone. > > > > > > > > I have now made a new installation and use a public domain with > > > > a trusted certificate and a working Autodiscover for the public > > > > Domain which refers to my server mail.example.com > > > > > > > > Here's my environmental data: > > > > > > > > Interne "Domain/Workgroup" = example.intern > > > > Interner Server Name = sogo.example.intern > > > > Interner Server IP = 192.168.146.6 > > > > Mail Domain = example.com > > > > Web Domain = mail.example.com > > > > > > > > When using the Outlook wizard I get NO warnings about > > > > certificates. At the first point "Establish network connection" > > > > I get a green tick. If I use a valid email address of the domain > > > > at the second point "Search for > > > > [email protected]", then I get a green tick > > > > and come to the next point. If I use an invalid email address of > > > > the domain, then I get a red cross at point 2. At the 3rd point > > > > "Logging on to the server" I get a red cross with the message > > > > "The action cannot be completed. No connection to Microsoft > > > > Exchange is available. Outlook must be in online mode or > > > > connected to complete this process." (German --> Die Aktion kann > > > > nicht abgeschlossen werden. Es steht keine Verbindung mit > > > > Microsoft Exchange zur Verfügung. Outlook muss im Onlinemodus > > > > oder verbunden sein, um diesen Vorgang abzuschließen) > > > > > > > > After that I get a popup where I have to fill the fields > > > > "Microsoft Exchange Server" and "Mailbox". These fields have the > > > > following default values: Microsoft Exchange Server = > > > > "mail.example.com" Mailbox = "=SMTP:[email protected]" > > > > > > > > Here is my smb.conf > > > > # Global parameters > > > > [global] > > > > workgroup = EXAMPLE > > > > realm = EXAMPLE.INTERN > > > > netbios name = SOGO > > > > server role = active directory domain controller > > > > dns forwarder = 192.168.146.1 > > > > #server services = dns > > > > #server services = -dns -winbindd +winbind > > > > > > > > #disable default strong auth > > > > ldap server require strong auth = No > > > > > > > > ### Configuration required by OpenChange server ### > > > > dsdb:schema update allowed = true > > > > dcerpc endpoint servers = epmapper, mapiproxy, dnsserver > > > > dcerpc_mapiproxy:server = true > > > > dcerpc_mapiproxy:interfaces = exchange_emsmdb, exchange_nsp, > > > > exchange_ds_rfr ### Configuration required by OpenChange server > > > > ### > > > > > > > > mapistore:namedproperties = mysql > > > > namedproperties:mysql_user = openchange-user > > > > namedproperties:mysql_pass = pwd > > > > namedproperties:mysql_host = localhost > > > > namedproperties:mysql_db = openchange > > > > > > > > mapistore:indexing_backend = > > > > mysql://openchange-user:pwd@localhost/openchange > > > > mapiproxy:openchangedb = > > > > mysql://openchange-user:pwd@localhost/openchange [netlogon] > > > > > > I cannot really comment about the Sogo aspects of this, but I can > > > assure you of this, Openchange is a dead project, it is not > > > maintained and I am surprised that you have managed to get it > > > working with The version of Samba that comes with Ubuntu 16.04, > > > that is if it is working. > > > > > > To put it another way, try starting again, but this time, do not > > > bother with Openchange. > > > > > > Rowland Penny > > > Samba team member > > > -- > > > [email protected] > > > https://inverse.ca/sogo/lists > > > -- > > > [email protected] > > > https://inverse.ca/sogo/lists > > > -- > > > [email protected] > > > https://inverse.ca/sogo/lists > > > > -- > > [email protected] > > https://inverse.ca/sogo/lists > > -- > > [email protected] > > https://inverse.ca/sogo/lists > > -- > [email protected] > https://inverse.ca/sogo/lists -- [email protected] https://inverse.ca/sogo/lists
