I use the sogo client with a Microsoft Exchange Server, it has self-signed certificates, some solution for this problem
Hello
Version 5 has more robust certificate checking. Make sure your imap ssl certificate is valid for the domain you are using to access it from the sogo server.
On 12/09/20 2:25 am, Yaisel Cruz Zuñiga ([email protected]) wrote:
hello list, upgrade to version 5 and now it does not connect to mail server
Sep 11 10:16:09 sogod [3458]: [ERROR] <0x0x557f24278750[NGImap4ConnectionManager]> IMAP4 login failed:
host=correo.ucf.edu.cu, user=ycruz, pwd=yes
url="">
base=(null)
base-class=(null))
= <0x0x557f23da5000[NGImap4Client]: login=ycruz(pwd) socket=<NGActiveSocket[0x0x557f23d99d80]: mode=rw address=<0x0x557f24163300[NGInternetSocketAddress]: host=10.14.2.201 port=35418> connectedTo=<0x0x557f240fb130[NGInternetSocketAddress]: host=correo.ucf.edu.cu port=143>>>
Sep 11 10:16:09 sogod [3458]: [ERROR] <0x557f243b8c80[SOGoMailAccount]:0> Could not connect IMAP4
Sep 11 10:16:09 sogod [3458]: |SOGo| request took 0.018597 seconds to execute
Sep 11 10:16:09 sogod [3458]: 10.15.20.2 "POST /SOGo/so/ycruz/Mail/unseenCount HTTP/1.1" 200 21/31 0.020 - - 0 - 21
I have the SOGo client installed separately from the server, in version 4 it worked perfectly.
Universidad de Cienfuegos “Carlos Rafael Rodríguez”
40 años Inspirando Innovación y Progreso
Universidad de Cienfuegos “Carlos Rafael Rodríguez”
40 años Inspirando Innovación y Progreso
Universidad de Cienfuegos “Carlos Rafael Rodríguez”
40 años Inspirando Innovación y Progreso
<<attachment: ycruz.vcf>>
