General discussion on installation and configuration of SOGo

Text archives Help


Aw: [SOGo] Problems logging on to the server with Outlook 2010/2013


Chronological Thread 
  • From: "init" ( ) < >
  • To:
  • Subject: Aw: [SOGo] Problems logging on to the server with Outlook 2010/2013
  • Date: Sat, 30 Sep 2017 17:03:13 +0200
  • Dmarc-filter: OpenDMARC Filter v1.2.0 mail.inverse.ca 37E6CFAB8E8
  • Importance: normal
  • Sensitivity: Normal

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 -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: "

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]
   path = /var/lib/samba/sysvol/EXAMPLE.intern/scripts
   read _only_ = No
  
  [sysvol]
   path = /var/lib/samba/sysvol
   read _only_ = No
   
Here is my ocsmanager.ini
  [DEFAULT]
  debug = true
  email_to =
  smtp_server = localhost
  error_email_from =
  
  [main]
  auth = ldap
  mapistore_root = /var/lib/samba/private
  mapistore_data = /var/lib/samba/private/mapistore
  
  debug = yes
  
  [auth:file]
  
  [auth:ldap]
  host = ldap://192.168.146.6
  port = 389
  bind_dn = cn=administrator,cn=users,dc=EXAMPLE,dc=intern
  bind_pw = pwd
  basedn = cn=users,dc=example,dc=intern
  
  [auth:single]
  username = openchange
  password = {SSHA}I6Hy5Wv0wuxyXvMBFWFQDVVN12_CLaX9
  
  [server:main]
  use = egg:Paste#http
  host = 127.0.0.1
  port = 5000
  protocol_version = HTTP/1.1
  
  [app:main]
  use = egg:ocsmanager
  full_stack = true
  static_files = true
  cache_dir = %(here)s/data
  beaker.session.key = ocsmanager
  beaker.session.secret = SDyKK3dKyDgW0mlpqttTMGU1f
  app_instance_uuid = {ee533ebc-f266-49d1-ae10-d017ee6aa98c}
  NTLMAUTHHANDLER_WORKDIR = /var/cache/ntlmauthhandler
  SAMBA_HOST = 127.0.0.1
  
  [rpcproxy:ldap]
  host = localhost
  port = 389
  basedn = cn=users,dc=example,dc=intern
  
  
  set debug = true
  
  [autodiscover]
  
  [autodiscover:rpcproxy]
  enabled = true
  
  [outofoffice]
  
  [outofoffice:file]
  sieve_script_path = /var/vmail/$domain/$user/sieve-script
  sieve_script_path_mkdir = false
  
  [outofoffice:managesieve]
  secret = secret
  
  [loggers]
  keys = root
  
  [handlers]
  keys = console
  
  [formatters]
  keys = generic
  
  [logger_root]
  level = INFO
  handlers = console
  
  [handler_console]
  class = StreamHandler
  args = (sys.stderr,)
  level = NOTSET
  formatter = generic
  
  [formatter_generic]
  format = %(asctime)s %(levelname)-5.5s [%(name)s] [%(threadName)s] %(message)s
  
I found errors in the /var/log/samba/log.wb-EXAMPLE:
  [2017/09/30 16:47:57.028294,  0] ../source3/winbindd/winbindd_cm.c:1840(wb_open_internal_pipe)
    open_internal_pipe: Could not connect to lsarpc pipe: NT_STATUS_UNSUCCESSFUL
  [2017/09/30 16:52:57.029398,  0] ../source3/winbindd/winbindd_cm.c:1840(wb_open_internal_pipe)
    open_internal_pipe: Could not connect to dssetup pipe: NT_STATUS_UNSUCCESSFUL
  [2017/09/30 16:52:57.029941,  0] ../source3/winbindd/winbindd_cm.c:1840(wb_open_internal_pipe)
    open_internal_pipe: Could not connect to lsarpc pipe: NT_STATUS_UNSUCCESSFUL
  [2017/09/30 16:52:57.030351,  0] ../source3/winbindd/winbindd_cm.c:1840(wb_open_internal_pipe)
    open_internal_pipe: Could not connect to lsarpc pipe: NT_STATUS_UNSUCCESSFUL

Other errors in the logs I can't find.

For me it looks like the email address is found correctly in the server, but the internal assignment of email addresses to users does not work.

Has nobody any idea what I can check or what my problem is?

I spend several days with the installation and after numerous installations I just can't get any further.

I would be very happy about your support.

Many greetings
Marc

 
Gesendet: Donnerstag, 28. September 2017 um 18:12 Uhr
Von: "\"init\" ( )" < >
An: 
Betreff: Aw: [SOGo] Problems logging on to the server with Outlook 2010/2013
Hello Christian,
 
thanks for the answer!
 
What would this mean in my environment?
 
Here's my environmental data:
 
Interne "Domain/Workgroup" = fritz.box
Interner Server Name = sogo.fritz.box
Interner Server IP = 192.168.146.127
Mail Domain = example.com
Web Domain = mail.example.com
 
Do I need an official certificate for mail.example.com? For example from letsencrypt.org?
 
What should my hosts entry look like, because I have problems with autodiscover at Strato?
1) 192.168.146.127 example.com autodiscover.example.com
2) 192.168.146.127 mail.example.com autodiscover.example.com
3) 192.168.146.127 sogo.fritz.box autodiscover.example.com
 
Thank you for your help.
 
Greetings
Marc
 
Gesendet: Donnerstag, 28. September 2017 um 16:18 Uhr
Von: "\"Christian Mack\" ( )" < >
An: 
Betreff: Re: [SOGo] Problems logging on to the server with Outlook 2010/2013
Hello

Outlook only supports access to sites with a valid signed certificate,
which means no self signed ones.

Kind regards,
Christian Mack

Am 28.09.2017 um 10:30 schrieb init ( ):
> Hello, everyone.
>
> I have installed SOGo V2 under Ubuntu 16.04.
>
> I used the script from https://www.onlinedemo.hu/71-zeg-install-script and
> adapted it to the current version.
>
> The following software components are used here:
> Ubuntu 16.04
> - postfix 3.1.0-3
> amd64 High-performance mail transport agent
> - 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
>
> - 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
>
> - sogo:amd64 2.3.22.20170926-1
> amd64 a modern and scalable groupware
> - sogo-activesync 2.3.22.20170926-1
> amd64 a modern and scalable groupware - ActiveSync module
> - sogo-openchange:amd64 2.3.22.20170926-1
> amd64 a modern and scalable groupware - OpenChange backend
> - openchange-ocsmanager 4:2.4-zentyal22
> all Working instance of python-ocsmanager
> - openchange-rpcproxy 4:2.4-zentyal22
> all A RPC-over-HTTP implementation for Samba, using wsgi
> - openchangeproxy 4:2.4-zentyal22
> amd64 Experimental MAPI (Exchange/Outlook) proxy
> - openchangeserver 4:2.4-zentyal22
> amd64 Experimental MAPI (Exchange/Outlook) server
> - sogo-openchange:amd64 2.3.22.20170926-1
> amd64 a modern and scalable groupware - OpenChange backend
>
> - 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
>
>
> Connecting Outlook 2013 using ActiveSync works fine.
>
> To simulate autodiscover, I've adapted my hosts:
> 192.168.146.127 sogotest.fritz.box autodiscover.fritz.box
>
> When using the Outlook wizard I get warnings about certificates.
> At the first point "Establish network connection" I get a green tick.
> At the second point "Search for -Serversettings
> <mailto: -Serversettings>" I get a green tick.
> 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 = "autodiscover.fritz.box"
> Mailbox = "=SMTP: "
>
> In Apache, I get no errors and in the ssl_access.log the following:
> "POST /autodiscover/autodiscover.xml HTTP/1.1" 200 1769 "-" "Microsoft
> Office/14.0 (Windows NT 10.0; Microsoft Outlook 14.0.7182; Pro)"
>
> In the sogo.log I do not receive any messages.
>
> When I call URL "https://sogotest.fritz.box/autodiscover/autodiscover.xml" in
> the browser and log in with "Administrator","postmaster" or
> " <mailto: >", I get the following XML:
> <Autodiscover>
> <Response>
> <Error Id="6834840294878632642" Time="22:13:10.788261">
> <ErrorCode>600</ErrorCode>
> <Message>Invalid request</Message>
> <DebugData/>
> </Error>
> </Response>
> </Autodiscover>
>
> When I log in to the web interface "http://sogotest.fritz.box/SOGo/", only the
> user "Administrator" works. It is important to know that the email address of
> the administrator is <mailto: >
>
> Does anyone have any idea what I can check or what might be the cause of the
> problem?
>
> Many thanks in advance for your help.
>
> Many greetings
> Marc
>
> --
>
> https://inverse.ca/sogo/lists
>


--
Christian Mack
Universität Konstanz
Kommunikations-, Informations-, Medienzentrum (KIM)
Abteilung Basisdienste
78457 Konstanz
+49 7531 88-4416
 
--

https://inverse.ca/sogo/lists



Archive powered by MHonArc 2.6.18.

Top of page