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.
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-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
