Hello,
thanks for your answers.
As MJ suggested, I will concentrate on the web interface first.
I'm using the nightly == development builds and just made an update of all packages, but the problem still exists.
Here's an update on my installed packages:
- python-samba 2:4.3.11+dfsg-0ubuntu0.16.04.11 amd64 Python bindings for Samba
- samba 2:4.3.11+dfsg-0ubuntu0.16.04.11 amd64 SMB/CIFS file, print, and login server for Unix
- samba-common 2:4.3.11+dfsg-0ubuntu0.16.04.11 all common files used by both the Samba server and client
- samba-common-bin 2:4.3.11+dfsg-0ubuntu0.16.04.11 amd64 Samba common files used by both the server and the client
- samba-dev 2:4.3.11+dfsg-0ubuntu0.16.04.11 amd64 tools for extending Samba
- samba-dsdb-modules 2:4.3.11+dfsg-0ubuntu0.16.04.11 amd64 Samba Directory Services Database
- samba-libs:amd64 2:4.3.11+dfsg-0ubuntu0.16.04.11 amd64 Samba core libraries
- samba-vfs-modules 2:4.3.11+dfsg-0ubuntu0.16.04.11 amd64 Samba Virtual FileSystem plugins
- samba 2:4.3.11+dfsg-0ubuntu0.16.04.11 amd64 SMB/CIFS file, print, and login server for Unix
- samba-common 2:4.3.11+dfsg-0ubuntu0.16.04.11 all common files used by both the Samba server and client
- samba-common-bin 2:4.3.11+dfsg-0ubuntu0.16.04.11 amd64 Samba common files used by both the server and the client
- samba-dev 2:4.3.11+dfsg-0ubuntu0.16.04.11 amd64 tools for extending Samba
- samba-dsdb-modules 2:4.3.11+dfsg-0ubuntu0.16.04.11 amd64 Samba Directory Services Database
- samba-libs:amd64 2:4.3.11+dfsg-0ubuntu0.16.04.11 amd64 Samba core libraries
- samba-vfs-modules 2:4.3.11+dfsg-0ubuntu0.16.04.11 amd64 Samba Virtual FileSystem plugins
- postfix 3.1.0-3 amd64 High-performance mail transport agent
- postfix-ldap 3.1.0-3 amd64 LDAP map support for Postfix
- postfix-ldap 3.1.0-3 amd64 LDAP map support for Postfix
- dovecot-core 1:2.2.22-1ubuntu2.4 amd64 secure POP3/IMAP server - core files
- dovecot-imapd 1:2.2.22-1ubuntu2.4 amd64 secure POP3/IMAP server - IMAP daemon
- dovecot-ldap 1:2.2.22-1ubuntu2.4 amd64 secure POP3/IMAP server - LDAP support
- dovecot-managesieved 1:2.2.22-1ubuntu2.4 amd64 secure POP3/IMAP server - ManageSieve server
- dovecot-pop3d 1:2.2.22-1ubuntu2.4 amd64 secure POP3/IMAP server - POP3 daemon
- dovecot-sieve 1:2.2.22-1ubuntu2.4 amd64 secure POP3/IMAP server - Sieve filters support
- sogo:amd64 2.3.22.20171004-1 amd64 a modern and scalable groupware
- sogo-common 2.2.17a-1.1build1 all Scalable groupware server - common files
- dovecot-imapd 1:2.2.22-1ubuntu2.4 amd64 secure POP3/IMAP server - IMAP daemon
- dovecot-ldap 1:2.2.22-1ubuntu2.4 amd64 secure POP3/IMAP server - LDAP support
- dovecot-managesieved 1:2.2.22-1ubuntu2.4 amd64 secure POP3/IMAP server - ManageSieve server
- dovecot-pop3d 1:2.2.22-1ubuntu2.4 amd64 secure POP3/IMAP server - POP3 daemon
- dovecot-sieve 1:2.2.22-1ubuntu2.4 amd64 secure POP3/IMAP server - Sieve filters support
- sogo:amd64 2.3.22.20171004-1 amd64 a modern and scalable groupware
- sogo-common 2.2.17a-1.1build1 all Scalable groupware server - common files
- libmysqlclient20:amd64 5.7.19-0ubuntu0.16.04.1 amd64 MySQL database client library
- mysql-client-5.7 5.7.19-0ubuntu0.16.04.1 amd64 MySQL database client binaries
- mysql-client-core-5.7 5.7.19-0ubuntu0.16.04.1 amd64 MySQL database core client binaries
- mysql-common 5.7.19-0ubuntu0.16.04.1 all MySQL database common files, e.g. /etc/mysql/my.cnf
- mysql-server 5.7.19-0ubuntu0.16.04.1 all MySQL database server (metapackage depending on the latest version)
- mysql-server-5.7 5.7.19-0ubuntu0.16.04.1 amd64 MySQL database server binaries and system database setup
- mysql-server-core-5.7 5.7.19-0ubuntu0.16.04.1 amd64 MySQL database server binaries
- python-mysqldb 1.3.7-1build2 amd64 Python interface to MySQL
- sope4.9-gdl1-mysql 4.9.r1664.20170721 amd64 MySQL connector for SOPE's fork of the GNUstep database environment
- sope4.9-libxmlsaxdriver 4.9.r1664.20170721 amd64 XML Parser for SOPE's SAX engine
- mysql-client-5.7 5.7.19-0ubuntu0.16.04.1 amd64 MySQL database client binaries
- mysql-client-core-5.7 5.7.19-0ubuntu0.16.04.1 amd64 MySQL database core client binaries
- mysql-common 5.7.19-0ubuntu0.16.04.1 all MySQL database common files, e.g. /etc/mysql/my.cnf
- mysql-server 5.7.19-0ubuntu0.16.04.1 all MySQL database server (metapackage depending on the latest version)
- mysql-server-5.7 5.7.19-0ubuntu0.16.04.1 amd64 MySQL database server binaries and system database setup
- mysql-server-core-5.7 5.7.19-0ubuntu0.16.04.1 amd64 MySQL database server binaries
- python-mysqldb 1.3.7-1build2 amd64 Python interface to MySQL
- sope4.9-gdl1-mysql 4.9.r1664.20170721 amd64 MySQL connector for SOPE's fork of the GNUstep database environment
- sope4.9-libxmlsaxdriver 4.9.r1664.20170721 amd64 XML Parser for SOPE's SAX engine
- libsope-appserver4.9 4.9.r1664.20170721 amd64 SOPE application server libraries
- libsope-core4.9 4.9.r1664.20170721 amd64 Core libraries of the SOPE application server
- libsope-gdl1-4.9 4.9.r1664.20170721 amd64 GNUstep database libraries for SOPE
- libsope-ldap4.9 4.9.r1664.20170721 amd64 SOPE libraries for LDAP access
- libsope-mime4.9 4.9.r1664.20170721 amd64 SOPE libraries for MIME processing
- libsope-xml4.9 4.9.r1664.20170721 amd64 SOPE libraries for XML processing
- libsope-core4.9 4.9.r1664.20170721 amd64 Core libraries of the SOPE application server
- libsope-gdl1-4.9 4.9.r1664.20170721 amd64 GNUstep database libraries for SOPE
- libsope-ldap4.9 4.9.r1664.20170721 amd64 SOPE libraries for LDAP access
- libsope-mime4.9 4.9.r1664.20170721 amd64 SOPE libraries for MIME processing
- libsope-xml4.9 4.9.r1664.20170721 amd64 SOPE libraries for XML processing
And here is my apache sogo.conf:
Alias /SOGo.woa/WebServerResources/ \
/usr/lib/GNUstep/SOGo/WebServerResources/
Alias /SOGo/WebServerResources/ \
/usr/lib/GNUstep/SOGo/WebServerResources/
<Directory /usr/lib/GNUstep/SOGo/>
Options -Indexes
AllowOverride None
Options -Indexes
AllowOverride None
<IfVersion < 2.4>
Order deny,allow
Allow from all
</IfVersion>
<IfVersion >= 2.4>
Require all granted
</IfVersion>
Order deny,allow
Allow from all
</IfVersion>
<IfVersion >= 2.4>
Require all granted
</IfVersion>
<IfModule expires_module>
ExpiresActive On
ExpiresDefault "access plus 1 year"
</IfModule>
</Directory>
ExpiresActive On
ExpiresDefault "access plus 1 year"
</IfModule>
</Directory>
ProxyRequests Off
SetEnv proxy-nokeepalive 1
ProxyPreserveHost On
SetEnv proxy-nokeepalive 1
ProxyPreserveHost On
ProxyPass /SOGo http://127.0.0.1:20000/SOGo retry=0
<Proxy http://127.0.0.1:20000/SOGo>
<IfModule headers_module>
RequestHeader set "x-webobjects-server-port" "443"
RequestHeader set "x-webobjects-server-name" "%{HTTP_HOST}e" env=HTTP_HOST
RequestHeader set "x-webobjects-server-url" "https://%{HTTP_HOST}e" env=HTTP_HOST
RequestHeader unset "x-webobjects-remote-user"
RequestHeader set "x-webobjects-server-protocol" "HTTP/1.0"
</IfModule>
<IfModule headers_module>
RequestHeader set "x-webobjects-server-port" "443"
RequestHeader set "x-webobjects-server-name" "%{HTTP_HOST}e" env=HTTP_HOST
RequestHeader set "x-webobjects-server-url" "https://%{HTTP_HOST}e" env=HTTP_HOST
RequestHeader unset "x-webobjects-remote-user"
RequestHeader set "x-webobjects-server-protocol" "HTTP/1.0"
</IfModule>
AddDefaultCharset UTF-8
Order allow,deny
Allow from all
</Proxy>
Allow from all
</Proxy>
# For Apple autoconfiguration
<IfModule rewrite_module>
RewriteEngine On
RewriteRule ^/.well-known/caldav/?$ /SOGo/dav [R=301]
RewriteRule ^/.well-known/carddav/?$ /SOGo/dav [R=301]
</IfModule>
<IfModule rewrite_module>
RewriteEngine On
RewriteRule ^/.well-known/caldav/?$ /SOGo/dav [R=301]
RewriteRule ^/.well-known/carddav/?$ /SOGo/dav [R=301]
</IfModule>
These modules are loaded:
lrwxrwxrwx 1 root root 36 Okt 4 11:21 access_compat.load -> ../mods-available/access_compat.load
lrwxrwxrwx 1 root root 28 Okt 4 11:21 alias.conf -> ../mods-available/alias.conf
lrwxrwxrwx 1 root root 28 Okt 4 11:21 alias.load -> ../mods-available/alias.load
lrwxrwxrwx 1 root root 33 Okt 4 11:21 auth_basic.load -> ../mods-available/auth_basic.load
lrwxrwxrwx 1 root root 33 Okt 4 11:21 authn_core.load -> ../mods-available/authn_core.load
lrwxrwxrwx 1 root root 33 Okt 4 11:21 authn_file.load -> ../mods-available/authn_file.load
lrwxrwxrwx 1 root root 33 Okt 4 11:21 authz_core.load -> ../mods-available/authz_core.load
lrwxrwxrwx 1 root root 33 Okt 4 11:21 authz_host.load -> ../mods-available/authz_host.load
lrwxrwxrwx 1 root root 33 Okt 4 11:21 authz_user.load -> ../mods-available/authz_user.load
lrwxrwxrwx 1 root root 32 Okt 4 11:21 autoindex.conf -> ../mods-available/autoindex.conf
lrwxrwxrwx 1 root root 32 Okt 4 11:21 autoindex.load -> ../mods-available/autoindex.load
lrwxrwxrwx 1 root root 30 Okt 4 11:21 deflate.conf -> ../mods-available/deflate.conf
lrwxrwxrwx 1 root root 30 Okt 4 11:21 deflate.load -> ../mods-available/deflate.load
lrwxrwxrwx 1 root root 26 Okt 4 11:21 dir.conf -> ../mods-available/dir.conf
lrwxrwxrwx 1 root root 26 Okt 4 11:21 dir.load -> ../mods-available/dir.load
lrwxrwxrwx 1 root root 26 Okt 4 11:21 env.load -> ../mods-available/env.load
lrwxrwxrwx 1 root root 29 Okt 4 11:21 filter.load -> ../mods-available/filter.load
lrwxrwxrwx 1 root root 30 Okt 4 14:49 headers.load -> ../mods-available/headers.load
lrwxrwxrwx 1 root root 27 Okt 4 11:21 mime.conf -> ../mods-available/mime.conf
lrwxrwxrwx 1 root root 27 Okt 4 11:21 mime.load -> ../mods-available/mime.load
lrwxrwxrwx 1 root root 32 Okt 4 11:21 mpm_event.conf -> ../mods-available/mpm_event.conf
lrwxrwxrwx 1 root root 32 Okt 4 11:21 mpm_event.load -> ../mods-available/mpm_event.load
lrwxrwxrwx 1 root root 34 Okt 4 11:21 negotiation.conf -> ../mods-available/negotiation.conf
lrwxrwxrwx 1 root root 34 Okt 4 11:21 negotiation.load -> ../mods-available/negotiation.load
lrwxrwxrwx 1 root root 28 Okt 4 14:49 proxy.conf -> ../mods-available/proxy.conf
lrwxrwxrwx 1 root root 33 Okt 4 14:49 proxy_http.load -> ../mods-available/proxy_http.load
lrwxrwxrwx 1 root root 28 Okt 4 14:49 proxy.load -> ../mods-available/proxy.load
lrwxrwxrwx 1 root root 30 Okt 4 14:49 rewrite.load -> ../mods-available/rewrite.load
lrwxrwxrwx 1 root root 31 Okt 4 11:21 setenvif.conf -> ../mods-available/setenvif.conf
lrwxrwxrwx 1 root root 31 Okt 4 11:21 setenvif.load -> ../mods-available/setenvif.load
lrwxrwxrwx 1 root root 36 Okt 4 14:50 socache_shmcb.load -> ../mods-available/socache_shmcb.load
lrwxrwxrwx 1 root root 26 Okt 4 14:50 ssl.conf -> ../mods-available/ssl.conf
lrwxrwxrwx 1 root root 26 Okt 4 14:50 ssl.load -> ../mods-available/ssl.load
lrwxrwxrwx 1 root root 29 Okt 4 11:21 status.conf -> ../mods-available/status.conf
lrwxrwxrwx 1 root root 29 Okt 4 11:21 status.load -> ../mods-available/status.load
Did I forget to install anything or is there a wrong configuration?
How can I check the subsequent imap login?
Greetings
Marc
Marc
Gesendet: Mittwoch, 04. Oktober 2017 um 15:52 Uhr
Von: "\"lists\" (li...@merit.unu.edu)" <users@sogo.nu>
An: users@sogo.nu
Betreff: Re: [SOGo] Problems logging on to the server with Outlook 2010/2013
Von: "\"lists\" (li...@merit.unu.edu)" <users@sogo.nu>
An: users@sogo.nu
Betreff: Re: [SOGo] Problems logging on to the server with Outlook 2010/2013
Hi,
No expert here, but this can have many reasons, I guess.
Perhaps the actual ldap authentication succeeded ("successful login")
but the subsequent imap login fails?
Or something wrong with the sogo apache2/proxy configuration?
But you need to stop looking at outlook 2010/2013 access at this stage.
First make sure that the regular /SOGo webinterface works. Then proceed
to outlook/ActiveSync.
MJ
On 4-10-2017 15:09, init (26196...@web.de) wrote:
> 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\" (li...@merit.unu.edu)" <users@sogo.nu>
> *An:* users@sogo.nu
> *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 (26196...@web.de) 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\" (li...@merit.unu.edu)" <users@sogo.nu>
> > *An:* users@sogo.nu
> > *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 (26196...@web.de) 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\" (26196...@web.de)" <users@sogo.nu>
> > > *An:* users@sogo.nu
> > > *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\" (rpenny241...@gmail.com)" <users@sogo.nu>
> > > *An:* users@sogo.nu
> > > *Betreff:* Re: [SOGo] Problems logging on to the server with Outlook
> > > 2010/2013
> > > On Sat, 30 Sep 2017 17:03:13 +0200
> > > "init" (26196...@web.de) <users@sogo.nu> 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 postmas...@fritz.box-Serversettings", 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:postmas...@example.com"
> > > >
> > > > 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
> > > --
> > > users@sogo.nu
> > > https://inverse.ca/sogo/lists
> > > --
> > > users@sogo.nu
> > > https://inverse.ca/sogo/lists
> > > --
> > > users@sogo.nu
> > > https://inverse.ca/sogo/lists
> > --
> > users@sogo.nu
> > https://inverse.ca/sogo/lists
> > --
> > users@sogo.nu
> > https://inverse.ca/sogo/lists
> --
> users@sogo.nu
> https://inverse.ca/sogo/lists
> --
> users@sogo.nu
> https://inverse.ca/sogo/lists
--
users@sogo.nu
https://inverse.ca/sogo/lists
No expert here, but this can have many reasons, I guess.
Perhaps the actual ldap authentication succeeded ("successful login")
but the subsequent imap login fails?
Or something wrong with the sogo apache2/proxy configuration?
But you need to stop looking at outlook 2010/2013 access at this stage.
First make sure that the regular /SOGo webinterface works. Then proceed
to outlook/ActiveSync.
MJ
On 4-10-2017 15:09, init (26196...@web.de) wrote:
> 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\" (li...@merit.unu.edu)" <users@sogo.nu>
> *An:* users@sogo.nu
> *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 (26196...@web.de) 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\" (li...@merit.unu.edu)" <users@sogo.nu>
> > *An:* users@sogo.nu
> > *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 (26196...@web.de) 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\" (26196...@web.de)" <users@sogo.nu>
> > > *An:* users@sogo.nu
> > > *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\" (rpenny241...@gmail.com)" <users@sogo.nu>
> > > *An:* users@sogo.nu
> > > *Betreff:* Re: [SOGo] Problems logging on to the server with Outlook
> > > 2010/2013
> > > On Sat, 30 Sep 2017 17:03:13 +0200
> > > "init" (26196...@web.de) <users@sogo.nu> 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 postmas...@fritz.box-Serversettings", 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:postmas...@example.com"
> > > >
> > > > 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
> > > --
> > > users@sogo.nu
> > > https://inverse.ca/sogo/lists
> > > --
> > > users@sogo.nu
> > > https://inverse.ca/sogo/lists
> > > --
> > > users@sogo.nu
> > > https://inverse.ca/sogo/lists
> > --
> > users@sogo.nu
> > https://inverse.ca/sogo/lists
> > --
> > users@sogo.nu
> > https://inverse.ca/sogo/lists
> --
> users@sogo.nu
> https://inverse.ca/sogo/lists
> --
> users@sogo.nu
> https://inverse.ca/sogo/lists
--
users@sogo.nu
https://inverse.ca/sogo/lists
--
users@sogo.nu
https://inverse.ca/sogo/lists
users@sogo.nu
https://inverse.ca/sogo/lists
