[SOGo] BTS activities for Wednesday, August 05 2020
Title: BTS activities for Wednesday, August 05 2020 BTS Activities Home page: https://sogo.nu/bugs Project: SOGo For the period covering: Wednesday, August 05 2020 idlast updatestatus (resolution)categorysummary 5111 2020-08-05 17:25:57 updated (open) Web Mail the TO fields and the email should be displayed on the same line. 5078 2020-08-05 15:22:11 resolved (fixed) Backend Mail Does the latest nightly build support STARTTLS and SSL for SMTP service? 5079 2020-08-05 15:22:32 resolved (wont fix) Backend Mail How to disable SSL cert verification for SMTP (auth) connection? -- users@sogo.nuhttps://inverse.ca/sogo/lists
Re: [SOGo] Certificate validation failed
Hi Christian, I'll have to go back and look then, as I was told our recently purchased cert was a wildcard, and https:// on staff verifies this: *.prioritycolo.com Issued by: COMODO RSA Domain Validation Secure Server CA I take it updating the cert for apache doesn't mean that SOGO and sieve are happy? My only guess at the moment is that this cert wasn't updated? But that is also confusing as I was told this was working as it was (e.g. I didn't make any changes to the config), but can't verify. Thanks, Jonathan Davis - Priority Colo Inc. jonat...@prioritycolo.com - https://www.prioritycolo.com 1-888-AS-30176 (1-888-273-0176) x304 On 2020-08-05 3:50 a.m., Christian Mack (christian.m...@uni-konstanz.de) wrote: Hello Am 04.08.20 um 19:48 schrieb Jonathan Davis (jonat...@prioritycolo.com): Hi Christian, Trying the staff.prioritycolo.com fails without much detail, but I am also not able to telnet to staff on port 4190. I did try with a different hostname (ending in .prioritycolo.com) for that box, one that I am able to telnet on port 4190 and get a connection up, but receive the same error that the certificate validation failed. My next steps is to check to see if we installed the certs correctly? https:// on staff is happy. Problem is, that in the certificate staff.prioritycolo.com is set as cn. Therefore accessing with a different hostname will fail. You need to either get mangae-sieve working with staff.prioritycolo.com, or add your different hostname as alternateName in your certificate. Kind regards, Christian Mack Jonathan Davis - Priority Colo Inc. jonat...@prioritycolo.com - https://www.prioritycolo.com 1-888-AS-30176 (1-888-273-0176) x304 On 2020-08-04 11:15 a.m., Christian Mack (christian.m...@uni-konstanz.de) wrote: Hello Am 27.07.20 um 16:39 schrieb Jonathan Davis (jonat...@prioritycolo.com): I gave it a go, and ended up with an error that was not very descriptive: Jul 27 10:00:29 sogod [9679]: 2607:fea8:4a0:1e8b:807f:f6f2:baa3:7a12 "POST /SOGo/so/jonat...@prioritycolo.com/Mail/0/folderINBOX/view HTTP/1.1" 200 31884/48 0.617 - - 15M - 15 Jul 27 10:00:29 sogod [9679]: 2607:fea8:4a0:1e8b:807f:f6f2:baa3:7a12 "POST /SOGo/so/jonat...@prioritycolo.com/Mail/unseenCount HTTP/1.1" 200 21/31 0.323 - - 0 - 14) Jul 27 10:00:32 sogod [9680]: [ERROR] <0x0x561a54ed0d50[SOGoSieveManager]> Sieve connection failed on sieve://staff.prioritycolo.com:4190/?tls=YES < cut > Does your manage-sieve (sieve://) listen on your outside IP for staff.prioritycolo.com? Giving DNS name will query your DNS and get the outside IPs back per default. In order to prevent that you must change your /etc/hosts file for the FQDN set to your loop back IPs. Or enable manage-sieve for your external IPs. Kind regards, Christian Mack -- users@sogo.nu https://inverse.ca/sogo/lists
Re: [SOGo] Unable to run SOGo on Ubuntu
I installed the nightly build from a few days ago
Sent using the free mail.com iPhone App
On 2020-08-04 at 13:41, "\"Christian Mack\" (christian.m...@uni-konstanz.de)"
wrote:
> Hello
>
> Am 03.08.20 um 22:35 schrieb m...@earthling.net:
> > I installed successfully on Ubuntu but when I try to logon using an LDAP
> > user after saying authenticated the logon screen reappears but the user is
> > in the URL when I check the log file there’s an error about
> > SOGoWebDAVAclManager entry ‘{DAV:}write’ already exist in DAV permission
> > table
> > The follows a post to /SGOo/connect and get /SOGo/so/bimbo both with 200
> > http status 200 (bimbo is the logged on user)
> > Sent using the free mail.com iPhone App
> >
>
> That is not an error, just an info.
>
> Which version of SOGo are you using?
>
>
> Kind regards,
> Christian Mack
>
> --
> Christian Mack
> Universität Konstanz
> Kommunikations-, Informations-, Medienzentrum (KIM)
> Abteilung IT-Dienste Forschung und Lehre
> 78457 Konstanz
> +49 7531 88-4416
>
>
--
users@sogo.nu
https://inverse.ca/sogo/lists
Re: [SOGo] Certificate validation failed
Hello Am 04.08.20 um 19:48 schrieb Jonathan Davis (jonat...@prioritycolo.com): > Hi Christian, > > Trying the staff.prioritycolo.com fails without much detail, but I am > also not able to telnet to staff on port 4190. > > I did try with a different hostname (ending in .prioritycolo.com) for > that box, one that I am able to telnet on port 4190 and get a connection > up, but receive the same error that the certificate validation failed. > > My next steps is to check to see if we installed the certs correctly? > https:// on staff is happy. > Problem is, that in the certificate staff.prioritycolo.com is set as cn. Therefore accessing with a different hostname will fail. You need to either get mangae-sieve working with staff.prioritycolo.com, or add your different hostname as alternateName in your certificate. Kind regards, Christian Mack > Jonathan Davis - Priority Colo Inc. > jonat...@prioritycolo.com - https://www.prioritycolo.com > 1-888-AS-30176 (1-888-273-0176) x304 > > On 2020-08-04 11:15 a.m., Christian Mack > (christian.m...@uni-konstanz.de) wrote: >> Hello >> >> Am 27.07.20 um 16:39 schrieb Jonathan Davis (jonat...@prioritycolo.com): >>> I gave it a go, and ended up with an error that was not very >>> descriptive: >>> >>> Jul 27 10:00:29 sogod [9679]: 2607:fea8:4a0:1e8b:807f:f6f2:baa3:7a12 >>> "POST /SOGo/so/jonat...@prioritycolo.com/Mail/0/folderINBOX/view >>> HTTP/1.1" 200 31884/48 0.617 - - 15M - 15 >>> Jul 27 10:00:29 sogod [9679]: 2607:fea8:4a0:1e8b:807f:f6f2:baa3:7a12 >>> "POST /SOGo/so/jonat...@prioritycolo.com/Mail/unseenCount HTTP/1.1" 200 >>> 21/31 0.323 - - 0 - 14) >>> Jul 27 10:00:32 sogod [9680]: [ERROR] >>> <0x0x561a54ed0d50[SOGoSieveManager]> Sieve connection failed on >>> sieve://staff.prioritycolo.com:4190/?tls=YES >>> >> < cut > >> Does your manage-sieve (sieve://) listen on your outside IP for >> staff.prioritycolo.com? >> Giving DNS name will query your DNS and get the outside IPs back per >> default. >> In order to prevent that you must change your /etc/hosts file for the >> FQDN set to your loop back IPs. >> Or enable manage-sieve for your external IPs. >> >> >> Kind regards, >> Christian Mack >> -- Christian Mack Universität Konstanz Kommunikations-, Informations-, Medienzentrum (KIM) Abteilung IT-Dienste Forschung und Lehre 78457 Konstanz +49 7531 88-4416 smime.p7s Description: S/MIME Cryptographic Signature
