Re: changing cipher for imap clients

2019-10-28 Thread @lbutlr via dovecot
On 28 Oct 2019, at 08:45, Fourhundred Thecat <400the...@gmx.ch> wrote: > setting ssl_prefer_server_ciphers=yes did the trick. Now my imap client > uses ECDHE-RSA-AES256-SHA Now go turn off TLSv1 -- At night when the bars close down Brandy walks through a silent town And loves a man who's not

Re: changing cipher for imap clients

2019-10-28 Thread lists via dovecot
The funny thing is AES128 may be harder to break than AES256. https://www.schneier.com/blog/archives/2009/07/another_new_aes.html It had been a decade, so it would be interesting if Bruce Schneier has the same opinion. I just use the defaults.   Original Message   From:

Re: changing cipher for imap clients

2019-10-28 Thread Fourhundred Thecat via dovecot
> On 2019-10-28 15:36, Aki Tuomi wrote: > Also, you could try the *default* cipher list (unset ssl_cipher_list), which > is reasonable. Also make sure you have 'ssl_prefer_server_ciphers=yes', so > that the server-side priority list is used. setting ssl_prefer_server_ciphers=yes did the trick.

Re: changing cipher for imap clients

2019-10-28 Thread Aki Tuomi via dovecot
> On 28/10/2019 16:12 Fourhundred Thecat via dovecot > wrote: > > > When my client connects, I see this in my log: > > dovecot: imap-login: TLSv1 with cipher ECDHE-RSA-AES128-SHA (128/128 > bits) > > Whereas, when client connects to my postfix server, I see: > > Anonymous TLS

changing cipher for imap clients

2019-10-28 Thread Fourhundred Thecat via dovecot
When my client connects, I see this in my log: dovecot: imap-login: TLSv1 with cipher ECDHE-RSA-AES128-SHA (128/128 bits) Whereas, when client connects to my postfix server, I see: Anonymous TLS connection established from * TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits) how can I

Re: Dovecot and MySQL aborted connections.

2019-10-28 Thread Reio Remma via dovecot
On 28/10/2019 11:28, Gerald Galster via dovecot wrote: Hi, Is anyone else using Dovecot (2.3.8) with MySQL (5.7) seeing a lot of these in MySQL logs? 2019-10-28T11:08:20.384428+02:00 58378 [Note] Aborted connection 58378 to db: 'vmail' user: 'vmail' host: 'localhost' (Got an error reading

Re: Dovecot and MySQL aborted connections.

2019-10-28 Thread Christian Kivalo via dovecot
On October 28, 2019 10:15:34 AM GMT+01:00, Reio Remma via dovecot wrote: >Is anyone else using Dovecot (2.3.8) with MySQL (5.7) seeing a lot of >these in MySQL logs? > >2019-10-28T11:08:20.384428+02:00 58378 [Note] Aborted connection 58378 >to db: 'vmail' user: 'vmail' host: 'localhost'

Re: Dovecot and MySQL aborted connections.

2019-10-28 Thread Gerald Galster via dovecot
Hi, > Is anyone else using Dovecot (2.3.8) with MySQL (5.7) seeing a lot of these > in MySQL logs? > > 2019-10-28T11:08:20.384428+02:00 58378 [Note] Aborted connection 58378 to db: > 'vmail' user: 'vmail' host: 'localhost' (Got an error reading communication > packets) >

Dovecot list breaks DKIM.

2019-10-28 Thread Reio Remma via dovecot
Hello again, I noticed mails from the Dovecot list break DKIM signatures. Perhaps it's something to look at? Most lists I'm on manage to pass messages with DKIM intact. Authentication-Results: abc.abc.abc; dkim=fail (rsa verify failed) header.d=mrstuudio.ee header.s=mr

Dovecot and MySQL aborted connections.

2019-10-28 Thread Reio Remma via dovecot
Is anyone else using Dovecot (2.3.8) with MySQL (5.7) seeing a lot of these in MySQL logs? 2019-10-28T11:08:20.384428+02:00 58378 [Note] Aborted connection 58378 to db: 'vmail' user: 'vmail' host: 'localhost' (Got an error reading communication packets) 2019-10-28T11:10:09.821171+02:00 58420

Re: SQL iterate_query

2019-10-28 Thread James via dovecot
On 25/10/2019 00:00, Daniel Miller via dovecot wrote: So, given that the complete address is used as the username I now use: iterate_query = SELECT username FROM mailbox https://doc.dovecot.org/configuration_manual/authentication/sql/#user-iteration ...says that iterate_query has two