--- Original Message ---
On Monday, January 31st, 2022 at 06:24, Aki Tuomi
wrote:
> Markus
Hi Laura, did you try this? Did it work?
Aki
Hi Aki
Sorry, your mail got caught in spam.
Tried it, it didn't work. So I just ended up using "-o imapc_ssl_verify=no".
> On 26/01/2022 11:19 Markus Winkler wrote:
>
>
> Hi Laura,
>
> On Wed, 26 Jan 2022 at 12:09:04AM +, Laura Smith wrote:
> >‐‐‐ Original Message ‐‐‐
> >>
> >> I thought that
> >>
> >> ssl_ca = >>
> >> is worth a try.
> >
> >
> >Does ssl_ca even apply to dsync/imapc ?
>
> as I wrot
Hi Laura,
On Wed, 26 Jan 2022 at 12:09:04AM +, Laura Smith wrote:
‐‐‐ Original Message ‐‐‐
I thought that
ssl_ca =
Does ssl_ca even apply to dsync/imapc ?
as I wrote: I cannot test your scenario and the link to the documentation I
sent was only a rough idea.
Looking at the
‐‐‐ Original Message ‐‐‐
>
> I thought that
>
> ssl_ca =
> is worth a try.
Does ssl_ca even apply to dsync/imapc ?
Looking at the docs its all about client certificate authentication ? Something
which does not apply to my environment, and even if it did, it would not apply
to dsync/
Hi Laura,
On 25.01.22 11:48, Laura Smith wrote:
Thanks for your suggestion, I have a couple of questions about it though. > First, my understanding from the docs was that ssl_client_ca_* were
override parameters and that in the absence of the parameters, Dovecot
would default to using OpenSSL d
For the benefit of list, I've decided to work-around the problem using:
imapc_ssl_verify = no
Obviously I still welcome suggestions as to how I can get dsync working with
Let's Encrypt certificates and when OpenSSL validates "ok" but Dovecot does not
(despite Dovecot supposedly falling-back to
> just an idea, but maybe that's the problem?:
>
> https://doc.dovecot.org/configuration_manual/authentication/proxies/
>
> "Note
>
> ssl_client_ca_dir or ssl_client_ca_file aren’t currently used for verifying
> the
>
> remote certificate, although ideally they will be in a future Dovecot
> ver
Hi Laura,
On Mon, 24 Jan 2022 at 08:25:12PM +, Laura Smith wrote:
I'm having a frustrating problem trying to use "doveadm sync" to pull
mails off a server for migration purposes.
# 2.3.17.1 (476cd46418): /etc/dovecot/dovecot.conf
# Pigeonhole version 0.5.17.1 (a1a0b892)
# OS: Linux 5.10.0-1
Hi Zakaria
Thank you for your suggestion.
I don't think an out of date ca trust is the issue with me. I'm running Debian
Bullseye (i.e. latest Debian release) and its fully up to date with all patches.
I will look into your suggestion though.
Laura
‐‐‐ Original Message ‐‐‐
On Monday,
I'm having a frustrating problem trying to use "doveadm sync" to pull mails off
a server for migration purposes.
# 2.3.17.1 (476cd46418): /etc/dovecot/dovecot.conf
# Pigeonhole version 0.5.17.1 (a1a0b892)
# OS: Linux 5.10.0-11-amd64 x86_64 Debian 11.2
I have tried both explicit "ssl_client_ca_di
Hi, after updating from dovecot.x86_64 2:2.3.16-2 to 2:2.3.17.1-1 on
AlmaLinux 8 my dovecot replication stopped working.
Log is full of
Error: doveadm server disconnected before handshake: Received invalid
SSL certificate: unable to get certificate CRL: /CN=my.domain.redacted
(check ssl_client_ca_
Hi,
I have updated dovecot from 2.3.16 (working flawless ) to 2.3.17 (
both Centos8 - community repo ) . Now dsync does not work anymore,
logs shows:
dovecot[30398]: doveadm(vmail): Error: Disconnected from remote:
Received invalid SSL certificate: unable to get certificate CRL:
/CN
12 matches
Mail list logo
