Re: Dovecot eBook

[Chris Bennett via dovecot]

On Sat, Jul 20, 2019 at 02:32:34AM -0600, LuKreme via dovecot wrote:
> On Jul 19, 2019, at 19:29, Peter Fraser via dovecot  
> wrote:
> > I have a strange question. I bought the Dovecot Book off Amazon. I can 
> > easily prove it with a picture and/or my receipt off Amazon. I still have 
> > it o my library but I don’t like to travel around with it. Is there a way 
> > for me to get a PDF copy? I just checked Amazon and there is still no PDF 
> > version available there.
> 
> Tedious, but scan the book. I have done this with my iPhone and it resulted 
> in a very good copy that was fully OCRed
> 
> 

I will double check, but there is software in OpenBSD (Linux too), that
can quickly change ebook to pdf. No hassle and you can boot OpenBSD off
of a usb stick.

Chris Bennett

RE: Dovecot eBook

[Michael Slusarz via dovecot]

 
 
  
   You need to talk to Peer and/or the publisher.  We are not affiliated with that book.
   
  
  
   
  
  
   michael
   
  
  
   
  
  
   

   
   

   One can easily find some PDFs on the net. But all of them looks outdated.
   
   http://gen.lib.rus.ec/book/index.php?md5=AB28964F8CB3CC8BC319BBDE25C8B41A
   
   * Do not forget to support writers by buying their books.
   
   
   
On July 21, 2019 12:09:24 AM GMT+03:00, Peter Fraser via dovecot  wrote:

 
  Well, if there’s no other way, I guess I will have to.
  
  Thanks.
  
  Sent from Mail for Windows 10
  
  
   From: LuKreme via dovecotSent: Saturday, July 20, 2019 3:33 AMTo: Peter Fraser via dovecotSubject: Re: Dovecot eBook
  
  
  On Jul 19, 2019, at 19:29, Peter Fraser via dovecot  wrote:
  
   

 I have a strange question. I bought the Dovecot Book off Amazon. I can easily prove it with a picture and/or my receipt off Amazon. I still have it o my library but I don’t like to travel around with it. Is there a way for me to get a PDF copy? I just checked Amazon and there is still no PDF version available there.

   
  
  
   
  
  Tedious, but scan the book. I have done this with my iPhone and it resulted in a very good copy that was fully OCRed
  
   
  
  
  
 

   
   Eugene Bright
   IT-engineer
   Tel.: +7 925 728 96 22
   
   
 

Re: Dovecot with MySQL over SSL.

[Reio Remma via dovecot]

On 20.07.2019 22:37, Aki Tuomi via dovecot wrote:



On 20/07/2019 21:07 Reio Remma via dovecot  wrote:


On 20.07.2019 18:03, Aki Tuomi via dovecot wrote:


On 20/07/2019 13:12 Reio Remma via dovecot < dovecot@dovecot.org 
> wrote:



On 19.07.2019 0:24, Reio Remma via dovecot wrote:

I'm attempting to get Dovecot working with MySQL user database on
another machine. I can connect to the MySQL (5.7.26) instance with 
SSL

enabled:
mysql -h db.mrst.ee --ssl-ca=/etc/dovecot/ca.pem
--ssl-cert=/etc/dovecot/client-cert.pem
--ssl-key=/etc/dovecot/client-key.pem --ssl-cipher=DHE-RSA-AES256-SHA
-u vmail -p
However if I use the same values in dovecot-sql.conf.ext, I get the
following error:
Jul 19 00:20:18 turin dovecot: auth-worker(82996): Error:
mysql(db.mrst.ee): Connect failed to database (vmail): SSL connection
error: protocol version mismatch - waiting for 1 seconds before retry
Jul 19 00:20:19 turin dovecot: auth-worker(82996): Error:
mysql(db.mrst.ee): Connect failed to database (vmail): Connections
using insecure transport are prohibited while
--require_secure_transport=ON. - waiting for 5 seconds before retry
Database connection string:
connect = host=db.mrst.ee dbname=vmail user=vmail password=stuff \
    ssl_ca=/etc/dovecot/ca.pem \
    ssl_cert=/etc/dovecot/client-cert.pem \
    ssl_key=/etc/dovecot/client-key.pem \
    ssl_cipher=DHE-RSA-AES256-SHA
Update: I got it to connect successfully now after downgrading the 
MySQL

server tls-version from TLSv1.1 to TLSv1.

Is there a reason why Dovecot MySQL doesn't support TLSv1.1?

Thanks!
Reio


Dovecot mysql uses libmysqlclient. We do not enforce any particular 
tls protocol version. If it requires you to downgrade I suggest you 
review your client my.cnf for any restrictions.

---
Aki Tuomi


Thanks Aki! I'm looking at it now and despite identical MySQL 5.7.26 
versions on both systems, it seems Dovecot is using libmysqlclient 
5.6.37.


Dovecot seems to be using the older libmysqlclient.so.18.1.0 (5.6.37) 
from mysql-community-libs-compat 5.7.26 instead of the newer 
libmysqlclient.so.20.3.13 (5.7.26) from mysql-community-libs 5.7.26.


If I try to remove the libs-compat, yum also insists on removing 
dovecot-mysql, so it depends on the older libmysqlclient and ignores 
the newer one.


I don't suspect I can do anything on my end to force the Dovecot 
CentOS package to use the non-compat libmysqlclient?


Thanks,
Reio 


What repo are you using?
---
Aki Tuomi


Installed Packages
dovecot-mysql.x86_64 2:2.3.7-8 @dovecot-2.3-latest
mysql-community-libs.x86_64 5.7.26-1.el7 @mysql57-community

Both are from official repos.

Thanks,
Reio

RE: Dovecot eBook

[Eugene Bright via dovecot]

One can easily find some PDFs on the net. But all of them looks outdated.
http://gen.lib.rus.ec/book/index.php?md5=AB28964F8CB3CC8BC319BBDE25C8B41A

* Do not forget to support writers by buying their books.

On July 21, 2019 12:09:24 AM GMT+03:00, Peter Fraser via dovecot 
 wrote:
>Well, if there’s no other way, I guess I will have to.
>
>Thanks.
>
>Sent from Mail for Windows 10
>
>From: LuKreme via dovecot
>Sent: Saturday, July 20, 2019 3:33 AM
>To: Peter Fraser via dovecot
>Subject: Re: Dovecot eBook
>
>On Jul 19, 2019, at 19:29, Peter Fraser via dovecot
> wrote:
>
>I have a strange question. I bought the Dovecot Book off Amazon. I can
>easily prove it with a picture and/or my receipt off Amazon. I still
>have it o my library but I don’t like to travel around with it. Is
>there a way for me to get a PDF copy? I just checked Amazon and there
>is still no PDF version available there.
>
>Tedious, but scan the book. I have done this with my iPhone and it
>resulted in a very good copy that was fully OCRed

---
Eugene Bright
IT-engineer
Tel.: +7 925 728 96 22

RE: Dovecot eBook

[Peter Fraser via dovecot]

Well, if there’s no other way, I guess I will have to.

Thanks.

Sent from Mail for Windows 10

From: LuKreme via dovecot
Sent: Saturday, July 20, 2019 3:33 AM
To: Peter Fraser via dovecot
Subject: Re: Dovecot eBook

On Jul 19, 2019, at 19:29, Peter Fraser via dovecot  wrote:

I have a strange question. I bought the Dovecot Book off Amazon. I can easily 
prove it with a picture and/or my receipt off Amazon. I still have it o my 
library but I don’t like to travel around with it. Is there a way for me to get 
a PDF copy? I just checked Amazon and there is still no PDF version available 
there.

Tedious, but scan the book. I have done this with my iPhone and it resulted in 
a very good copy that was fully OCRed

Re: Dovecot with MySQL over SSL.

[Aki Tuomi via dovecot]

 
 
  
   
  
  
   
On 20/07/2019 21:07 Reio Remma via dovecot  wrote:
   
   

   
   

   
   
On 20.07.2019 18:03, Aki Tuomi via dovecot wrote:

   
   

 


 
  On 20/07/2019 13:12 Reio Remma via dovecot < 
  dovecot@dovecot.org> wrote:
 
 
  
 
 
  
 
 
  On 19.07.2019 0:24, Reio Remma via dovecot wrote:
 
 
  
   I'm attempting to get Dovecot working with MySQL user database on
  
  
   another machine. I can connect to the MySQL (5.7.26) instance with SSL
  
  
   enabled:
  
 
 
  
   mysql -h db.mrst.ee --ssl-ca=/etc/dovecot/ca.pem
  
  
   --ssl-cert=/etc/dovecot/client-cert.pem
  
  
   --ssl-key=/etc/dovecot/client-key.pem --ssl-cipher=DHE-RSA-AES256-SHA
  
  
   -u vmail -p
  
 
 
  
   However if I use the same values in dovecot-sql.conf.ext, I get the
  
  
   following error:
  
 
 
  
   Jul 19 00:20:18 turin dovecot: auth-worker(82996): Error:
  
  
   mysql(db.mrst.ee): Connect failed to database (vmail): SSL connection
  
  
   error: protocol version mismatch - waiting for 1 seconds before retry
  
  
   Jul 19 00:20:19 turin dovecot: auth-worker(82996): Error:
  
  
   mysql(db.mrst.ee): Connect failed to database (vmail): Connections
  
  
   using insecure transport are prohibited while
  
  
   --require_secure_transport=ON. - waiting for 5 seconds before retry
  
 
 
  
   Database connection string:
  
 
 
  
   connect = host=db.mrst.ee dbname=vmail user=vmail password=stuff \
  
  
       ssl_ca=/etc/dovecot/ca.pem \
  
  
       ssl_cert=/etc/dovecot/client-cert.pem \
  
  
       ssl_key=/etc/dovecot/client-key.pem \
  
  
       ssl_cipher=DHE-RSA-AES256-SHA
  
 
 
  Update: I got it to connect successfully now after downgrading the MySQL
 
 
  server tls-version from TLSv1.1 to TLSv1.
 
 
  
 
 
  Is there a reason why Dovecot MySQL doesn't support TLSv1.1?
 
 
  
 
 
  Thanks!
 
 
  Reio
 


 


 Dovecot mysql uses libmysqlclient. We do not enforce any particular tls protocol version. If it requires you to downgrade I suggest you review your client my.cnf for any restrictions.


 ---
Aki Tuomi

   
   Thanks Aki! I'm looking at it now and despite identical MySQL 5.7.26 versions on both systems, it seems Dovecot is using libmysqlclient 5.6.37.
   
   Dovecot seems to be using the older libmysqlclient.so.18.1.0 (5.6.37) from mysql-community-libs-compat 5.7.26 instead of the newer libmysqlclient.so.20.3.13 (5.7.26) from mysql-community-libs 5.7.26.
   
   If I try to remove the libs-compat, yum also insists on removing dovecot-mysql, so it depends on the older libmysqlclient and ignores the newer one.
   
   I don't suspect I can do anything on my end to force the Dovecot CentOS package to use the non-compat libmysqlclient?
   
   Thanks,
   Reio
  
  
   
  
  
   What repo are you using?
  
  
   ---
Aki Tuomi
   
 

Re: Dovecot with MySQL over SSL.

[Reio Remma via dovecot]

On 20.07.2019 18:03, Aki Tuomi via dovecot wrote:


On 20/07/2019 13:12 Reio Remma via dovecot < dovecot@dovecot.org 
> wrote:



On 19.07.2019 0:24, Reio Remma via dovecot wrote:

I'm attempting to get Dovecot working with MySQL user database on
another machine. I can connect to the MySQL (5.7.26) instance with SSL
enabled:
mysql -h db.mrst.ee --ssl-ca=/etc/dovecot/ca.pem
--ssl-cert=/etc/dovecot/client-cert.pem
--ssl-key=/etc/dovecot/client-key.pem --ssl-cipher=DHE-RSA-AES256-SHA
-u vmail -p
However if I use the same values in dovecot-sql.conf.ext, I get the
following error:
Jul 19 00:20:18 turin dovecot: auth-worker(82996): Error:
mysql(db.mrst.ee): Connect failed to database (vmail): SSL connection
error: protocol version mismatch - waiting for 1 seconds before retry
Jul 19 00:20:19 turin dovecot: auth-worker(82996): Error:
mysql(db.mrst.ee): Connect failed to database (vmail): Connections
using insecure transport are prohibited while
--require_secure_transport=ON. - waiting for 5 seconds before retry
Database connection string:
connect = host=db.mrst.ee dbname=vmail user=vmail password=stuff \
    ssl_ca=/etc/dovecot/ca.pem \
    ssl_cert=/etc/dovecot/client-cert.pem \
    ssl_key=/etc/dovecot/client-key.pem \
    ssl_cipher=DHE-RSA-AES256-SHA

Update: I got it to connect successfully now after downgrading the MySQL
server tls-version from TLSv1.1 to TLSv1.

Is there a reason why Dovecot MySQL doesn't support TLSv1.1?

Thanks!
Reio


Dovecot mysql uses libmysqlclient. We do not enforce any particular 
tls protocol version. If it requires you to downgrade I suggest you 
review your client my.cnf for any restrictions.

---
Aki Tuomi


Thanks Aki! I'm looking at it now and despite identical MySQL 5.7.26 
versions on both systems, it seems Dovecot is using libmysqlclient 5.6.37.


Dovecot seems to be using the older libmysqlclient.so.18.1.0 (5.6.37) 
from mysql-community-libs-compat 5.7.26 instead of the newer 
libmysqlclient.so.20.3.13 (5.7.26) from mysql-community-libs 5.7.26.


If I try to remove the libs-compat, yum also insists on removing 
dovecot-mysql, so it depends on the older libmysqlclient and ignores the 
newer one.


I don't suspect I can do anything on my end to force the Dovecot CentOS 
package to use the non-compat libmysqlclient?


Thanks,
Reio

Re: Dovecot with MySQL over SSL.

[Reio Remma via dovecot]

On 20.07.2019 17:52, John Fawcett via dovecot wrote:

On 18/07/2019 23:24, Reio Remma via dovecot wrote:

Hello!

I'm attempting to get Dovecot working with MySQL user database on
another machine. I can connect to the MySQL (5.7.26) instance with SSL
enabled:

  mysql -h db.mrst.ee --ssl-ca=/etc/dovecot/ca.pem
--ssl-cert=/etc/dovecot/client-cert.pem
--ssl-key=/etc/dovecot/client-key.pem --ssl-cipher=DHE-RSA-AES256-SHA
-u vmail -p

However if I use the same values in dovecot-sql.conf.ext, I get the
following error:

Jul 19 00:20:18 turin dovecot: master: Dovecot v2.3.7 (494d20bdc)
starting up for imap, lmtp, sieve (core dumps disabled)
Jul 19 00:20:18 turin dovecot: auth-worker(82996): Error:
mysql(db.mrst.ee): Connect failed to database (vmail): SSL connection
error: protocol version mismatch - waiting for 1 seconds before retry
Jul 19 00:20:18 turin dovecot: auth-worker(82996): Error:
mysql(db.mrst.ee): Connect failed to database (vmail): SSL connection
error: protocol version mismatch - waiting for 1 seconds before retry
Jul 19 00:20:19 turin dovecot: auth-worker(82996): Error:
mysql(db.mrst.ee): Connect failed to database (vmail): Connections
using insecure transport are prohibited while
--require_secure_transport=ON. - waiting for 5 seconds before retry
Jul 19 00:20:19 turin dovecot: auth-worker(82996): Error:
mysql(db.mrst.ee): Connect failed to database (vmail): Connections
using insecure transport are prohibited while
--require_secure_transport=ON. - waiting for 5 seconds before retry

Database connection string:

connect = host=db.mrst.ee dbname=vmail user=vmail password=stuff \
     ssl_ca=/etc/dovecot/ca.pem \
     ssl_cert=/etc/dovecot/client-cert.pem \
     ssl_key=/etc/dovecot/client-key.pem \
     ssl_cipher=DHE-RSA-AES256-SHA

If I leave the ssl_cipher unset, I get:

Jul 19 00:23:41 turin dovecot: auth-worker(83069): Error:
mysql(db.mrst.ee): Connect failed to database (vmail): SSL connection
error: Failed to set ciphers to use - waiting for 1 seconds before retry

Any ideas?

Thanks!
Reio

One difference between your testing manually with mysql client and the
same configuration in dovecot is the "ssl_verify_server_cert" parameter.
Dovecot is setting it if it is not specified. So to make the tests the
same you should either specify the --ssl_verify_server_cert parameter to
mysql or set it to no in the dovecot configuration.

John


This works as well:

mysql -h db.mrst.ee --ssl-ca=/etc/dovecot/ca.pem 
--ssl-cert=/etc/dovecot/client-cert.pem 
--ssl-key=/etc/dovecot/client-key.pem --ssl-cipher=DHE-RSA-AES256-SHA 
--ssl-mode=VERIFY_IDENTITY -u vmail -p


Protocol mismatch persists when I set ssl_verify_server_cert=no for 
Dovecot MySQL connection.


Thanks,
Reio

Re: Dovecot with MySQL over SSL.

[Aki Tuomi via dovecot]

 
 
  
   
  
  
   
On 20/07/2019 13:12 Reio Remma via dovecot <
dovecot@dovecot.org> wrote:
   
   

   
   

   
   
On 19.07.2019 0:24, Reio Remma via dovecot wrote:
   
   

 I'm attempting to get Dovecot working with MySQL user database on


 another machine. I can connect to the MySQL (5.7.26) instance with SSL


 enabled:

   
   

 mysql -h db.mrst.ee --ssl-ca=/etc/dovecot/ca.pem


 --ssl-cert=/etc/dovecot/client-cert.pem


 --ssl-key=/etc/dovecot/client-key.pem --ssl-cipher=DHE-RSA-AES256-SHA


 -u vmail -p

   
   

 However if I use the same values in dovecot-sql.conf.ext, I get the


 following error:

   
   

 Jul 19 00:20:18 turin dovecot: auth-worker(82996): Error:


 mysql(db.mrst.ee): Connect failed to database (vmail): SSL connection


 error: protocol version mismatch - waiting for 1 seconds before retry


 Jul 19 00:20:19 turin dovecot: auth-worker(82996): Error:


 mysql(db.mrst.ee): Connect failed to database (vmail): Connections


 using insecure transport are prohibited while


 --require_secure_transport=ON. - waiting for 5 seconds before retry

   
   

 Database connection string:

   
   

 connect = host=db.mrst.ee dbname=vmail user=vmail password=stuff \


     ssl_ca=/etc/dovecot/ca.pem \


     ssl_cert=/etc/dovecot/client-cert.pem \


     ssl_key=/etc/dovecot/client-key.pem \


     ssl_cipher=DHE-RSA-AES256-SHA

   
   
Update: I got it to connect successfully now after downgrading the MySQL
   
   
server tls-version from TLSv1.1 to TLSv1.
   
   

   
   
Is there a reason why Dovecot MySQL doesn't support TLSv1.1?
   
   

   
   
Thanks!
   
   
Reio
   
  
  
   
  
  
   Dovecot mysql uses libmysqlclient. We do not enforce any particular tls protocol version. If it requires you to downgrade I suggest you review your client my.cnf for any restrictions.
  
  
   ---
Aki Tuomi
   
 

Re: Dovecot with MySQL over SSL.

[John Fawcett via dovecot]

On 18/07/2019 23:24, Reio Remma via dovecot wrote:
> Hello!
>
> I'm attempting to get Dovecot working with MySQL user database on
> another machine. I can connect to the MySQL (5.7.26) instance with SSL
> enabled:
>
>  mysql -h db.mrst.ee --ssl-ca=/etc/dovecot/ca.pem
> --ssl-cert=/etc/dovecot/client-cert.pem
> --ssl-key=/etc/dovecot/client-key.pem --ssl-cipher=DHE-RSA-AES256-SHA
> -u vmail -p
>
> However if I use the same values in dovecot-sql.conf.ext, I get the
> following error:
>
> Jul 19 00:20:18 turin dovecot: master: Dovecot v2.3.7 (494d20bdc)
> starting up for imap, lmtp, sieve (core dumps disabled)
> Jul 19 00:20:18 turin dovecot: auth-worker(82996): Error:
> mysql(db.mrst.ee): Connect failed to database (vmail): SSL connection
> error: protocol version mismatch - waiting for 1 seconds before retry
> Jul 19 00:20:18 turin dovecot: auth-worker(82996): Error:
> mysql(db.mrst.ee): Connect failed to database (vmail): SSL connection
> error: protocol version mismatch - waiting for 1 seconds before retry
> Jul 19 00:20:19 turin dovecot: auth-worker(82996): Error:
> mysql(db.mrst.ee): Connect failed to database (vmail): Connections
> using insecure transport are prohibited while
> --require_secure_transport=ON. - waiting for 5 seconds before retry
> Jul 19 00:20:19 turin dovecot: auth-worker(82996): Error:
> mysql(db.mrst.ee): Connect failed to database (vmail): Connections
> using insecure transport are prohibited while
> --require_secure_transport=ON. - waiting for 5 seconds before retry
>
> Database connection string:
>
> connect = host=db.mrst.ee dbname=vmail user=vmail password=stuff \
>     ssl_ca=/etc/dovecot/ca.pem \
>     ssl_cert=/etc/dovecot/client-cert.pem \
>     ssl_key=/etc/dovecot/client-key.pem \
>     ssl_cipher=DHE-RSA-AES256-SHA
>
> If I leave the ssl_cipher unset, I get:
>
> Jul 19 00:23:41 turin dovecot: auth-worker(83069): Error:
> mysql(db.mrst.ee): Connect failed to database (vmail): SSL connection
> error: Failed to set ciphers to use - waiting for 1 seconds before retry
>
> Any ideas?
>
> Thanks!
> Reio

One difference between your testing manually with mysql client and the
same configuration in dovecot is the "ssl_verify_server_cert" parameter.
Dovecot is setting it if it is not specified. So to make the tests the
same you should either specify the --ssl_verify_server_cert parameter to
mysql or set it to no in the dovecot configuration.

John

Re: Replication issue 2.3.7

[Stuart Henderson via dovecot]

On 2019-07-16, Stuart Henderson via dovecot  wrote:
> On 2019/07/16 19:46, Aki Tuomi wrote:
>> 
>> > On 16/07/2019 18:40 Stuart Henderson via dovecot  
>> > wrote:
>> > 
>> >  
>> > On 2019-07-13, Reio Remma via dovecot  wrote:
>> > > Hello!
>> > >
>> > > I noticed these in the logs since upgrading from 2.3.6. to 2.3.7:
>> > >
>> > > Jul 13 11:52:10 turin dovecot: doveadm: Error: 
>> > > dsync-remote(r...@mrstuudio.ee): Error: 
>> > > Exporting mailbox INBOX failed: Mailbox attribute 
>> > > vendor/vendor.dovecot/pvt/server/sieve/files/MR lookup failed: Mailbox 
>> > > attributes not enabled
>> > > Jul 13 11:52:11 turin dovecot: doveadm: Error: 
>> > > dsync-remote(r...@mrstuudio.ee): Error: 
>> > > Exporting mailbox INBOX failed: Mailbox attribute 
>> > > vendor/vendor.dovecot/pvt/server/sieve/files/MR lookup failed: Mailbox 
>> > > attributes not enabled
>> > 
>> > Same here (in my case: on OpenBSD -current, mdbox, pigeonhole 0.5.7).
>> > I have backed out to 2.3.6 + pigeonhole 0.5.6 and it's happy again.
>> 
>> Instead of downgrading, you could've attempted
>> 
>> mail_attribute_dict = file:%h/dovecot-attributes
>> 
>> to enable mailbox attributes. This should fix sieve script replication too.
>> 
>> Aki
>
> Perhaps, but when dealing with mailboxes out of sync between the two
> replicated machines the first thought is to backout the change that
> triggered the problem, rather than guess things that might help,
> especially when they aren't mentioned in the release notes (actually
> the only thing I find in either NEWS or ChangeLog relating to
> attributes/metadata at all since the last release is adding methods
> to access this via lua API?).
>
>

So after adding "mail_attribute_dict = file:%h/dovecot-attributes"
(alone, I have not configured to use the METADATA extension and the
file is not being created) and going back to 2.3.7, syncs are now
working and I see no more "lookup failed: Mailbox attributes not
enabled".

Prior to adding mail_attribute_dict, with a two server dsync setup,
new mail was syncing from A->B ok but new mail arriving on B didn't
sync to A.

I'm happy that things are now functioning ok on this setup but given
the limited information about what's happening and no information about
config changes needed for 2.3.6->2.3.7 I'm a bit twitchy about 2.3.7
in OS packages (I reverted it to 2.3.6 in OpenBSD after running into
the problem) so it would be nice to know a little more about what's
going on here.

Re: Dovecot with MySQL over SSL.

[Reio Remma via dovecot]

On 19.07.2019 0:24, Reio Remma via dovecot wrote:
I'm attempting to get Dovecot working with MySQL user database on 
another machine. I can connect to the MySQL (5.7.26) instance with SSL 
enabled:


mysql -h db.mrst.ee --ssl-ca=/etc/dovecot/ca.pem 
--ssl-cert=/etc/dovecot/client-cert.pem 
--ssl-key=/etc/dovecot/client-key.pem --ssl-cipher=DHE-RSA-AES256-SHA 
-u vmail -p


However if I use the same values in dovecot-sql.conf.ext, I get the 
following error:


Jul 19 00:20:18 turin dovecot: auth-worker(82996): Error: 
mysql(db.mrst.ee): Connect failed to database (vmail): SSL connection 
error: protocol version mismatch - waiting for 1 seconds before retry
Jul 19 00:20:19 turin dovecot: auth-worker(82996): Error: 
mysql(db.mrst.ee): Connect failed to database (vmail): Connections 
using insecure transport are prohibited while 
--require_secure_transport=ON. - waiting for 5 seconds before retry


Database connection string:

connect = host=db.mrst.ee dbname=vmail user=vmail password=stuff \
    ssl_ca=/etc/dovecot/ca.pem \
    ssl_cert=/etc/dovecot/client-cert.pem \
    ssl_key=/etc/dovecot/client-key.pem \
    ssl_cipher=DHE-RSA-AES256-SHA


Update: I got it to connect successfully now after downgrading the MySQL 
server tls-version from TLSv1.1 to TLSv1.


Is there a reason why Dovecot MySQL doesn't support TLSv1.1?

Thanks!
Reio

Re: Dovecot eBook

[LuKreme via dovecot]

On Jul 19, 2019, at 19:29, Peter Fraser via dovecot  wrote:
> I have a strange question. I bought the Dovecot Book off Amazon. I can easily 
> prove it with a picture and/or my receipt off Amazon. I still have it o my 
> library but I don’t like to travel around with it. Is there a way for me to 
> get a PDF copy? I just checked Amazon and there is still no PDF version 
> available there.

Tedious, but scan the book. I have done this with my iPhone and it resulted in 
a very good copy that was fully OCRed