search for: hilltopgroup

Hi, I have two servers (HA configuration) on which I'm attempting to get replication working over SSL.? They're at two different sites, but connected via a site-site VPN. Everything seems to be fine, except that the certificates are not validating as I'm using IP addresses for the sync, as opposed to the public hostnames for which the certificates are valid, and so I get the

I guess what I don't understand is why the IP address approach is more attractive to you, and why you think the "public Internet" path is less good. Best regards, A -- Please excuse my clumbsy thums ---------- On December 21, 2017 12:47:47 AM Joseph Ward <jbwlists at hilltopgroup.com> wrote: > Hi, > > I have two servers (HA configuration) on which I'm attempting to get > replication working over SSL.? They're at two different sites, but > connected via a site-site VPN. > > Everything seems to be fine, except that the certificates are not &gt...

Joseph Ward writes: > I'm aware of at least a couple of fallback options: > ??? -have a self-signed cert for replication and use the Let's Encrypt > one for IMAP/POP > ??? - create firewall rules allowing them to connect to each other over > the public internet so that it can validate the proper cert > ? > These are both much less palatable than simply disabling the

I'd considered doing it at the internal DNS server level which I wasn't a fan of because it's a separate server's config that I'd have to rely on to make sure this server was working.? The thought of the local hosts file slipped my mind.? That is a good idea; it meets my needs, and keeps everything in the same "create mail server" ansible file. Thank you! -Joseph

I'm looking for a way to indicate which listener a connection came in via in the logs. For instance, I have IMAPS connections coming in via 993 as well as 1993, and would like some way to differentiate in the logging. Is there a way to do this? Thanks in advance, Joseph