Actually, I did provide the analyzer with valid login information. Maybe I should not pay too much attention to that 401 error. ActiveSync does work on any other device, also on Android with other clients (such as "nine").
Could it be, that Let's Encrypt certificates do not work on Android with the standard mail client? They do work in browsers. > Am 22.02.2016 um 15:18 schrieb Christian Mack > <christian.m...@uni-konstanz.de>: > > Hello > > Am 22.02.2016 um 14:00 schrieb elagil: >> Hello! >> >> I am using SOGo on my Debian 8 Server with Apache 2.4. >> >> Everything is working, except for ActiveSync on the native Android Mail >> client. Other clients, also on Android, do work. I get the following error >> message on the Android device: "Cannot connect to server". >> >> I am using Let's Encrypt certificates, which also work fine. However, if I >> enably trusting any certificate, Android will connect to the server. I do not >> want that, though. >> >> When using the Microsoft Connectivity Analyzer, I get: >> >> A 401 error was received from the server, but no authentication methods are >> supported. >> HTTP Response Headers: >> Keep-Alive: timeout=5, max=100 >> Connection: Keep-Alive >> Content-Length: 0 >> Content-Type: text/plain; charset=UTF-8 >> Date: Mon, 22 Feb 2016 12:29:41 GMT >> Server: Apache >> WWW-Authenticate: basic realm="SOGo" >> Elapsed Time: 760 ms. >> >> Any ideas on this? >> > > Error 401 means, that you try to access a web site, which need > authentication, but you did not provide username and password. > It (the App or Connectivity Analyzer) should ask you for username and > password, when receiving that. > > > Kind regards, > Christian Mack > > > > -- > Christian Mack > Universität Konstanz > Kommunikations-, Informations-, Medienzentrum (KIM) > Abteilung Basisdienste > 78457 Konstanz > +49 7531 88-4416
smime.p7s
Description: S/MIME cryptographic signature
