Re: Virtual folder auto creation

On 21/11/2019 10:59, Sami Ketola via dovecot wrote: > Return the virtual folder settings from userdb for only the selected users. > Or return hidden = yes variable for those that you wish not to see it. Could you give more details how to do this? > Virtual folder really does not exist. It is m

virtual folder index logs

A virtual folder is just really a saved search, but index log files are created. dovecot.list.index.log for the virtual folder itself and dovecot.index.log for all subfolders. Is it correct? Is it possible to disable index logs for virtual folder or it will only make dovecot worse? -- sergio.

Virtual folder auto creation

After switching on Virtual Plugin and configuring it as specified on https://doc.dovecot.org/configuration_manual/virtual_plugin/ the virtual folder is created for each user. Is it possible do not creater virtual folder automatically, only manually, for specific users? lda_mailbox_autocreate s

Re: Junk virtual forder

Sorry, I've missed the rfc3501. The right answer is just "KEYWORD Junk" without a backslash. Aleksander, thank you! -- sergio.

Re: Junk virtual forder

Aki, sorry for poor question. >> Is it possible to create a virtual folder that selects all mails with >> imap Junk flag (set by pigeonhole imap4flags' setflag "Junk")? > Yes, see https://doc.dovecot.org/configuration_manual/virtual_plugin/ Yes, I'm talking exactly about virtual_plugin. While it

Junk virtual forder

Is it possible to create a virtual folder that selects all mails with imap Junk flag (set by pigeonhole imap4flags' setflag "Junk")? -- sergio.

limits in high-security mode with ssl

Hello. I'm using dovecot in high-security mode: service_count = 1 for imap-login service starttls is requires, so the maximum number of active connections is process_limit (which is set to 1024) for the same imap-login service. But with this setup I got: doveconf: Warning: service auth { clie

Secure Client-Initiated Renegotiation

Hello. I've just tested my system that runs dovecot 2.3.4.1 on debian buster with testssl.sh (https://testssl.sh/) and is says: Secure Renegotiation (CVE-2009-3555)not vulnerable (OK) Secure Client-Initiated Renegotiation VULNERABLE (NOT ok), potential DoS threat Is this a configurati

Fwd: segfault in libdovecot-storage at unknown circumstances

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925961 Forwarded Message Subject: segfault in libdovecot-storage at unknown circumstances Date: Fri, 29 Mar 2019 16:34:15 +0300 From: sergio To: Debian Bug Tracking System Package: dovecot-core Version: 1:2.3.4.1-1~bpo9+1 Sev

Re: ssl_dh

On 16/03/2019 17:07, Aki Tuomi via dovecot wrote: ssl_dh is required from 2.3.0-2.3.2. From 2.3.3 onwards its optional. You can rm the ssl-parameters.dat file to get rid of that warning. Should wiki be updated? -- sergio.

Re: ssl_dh

On 16/03/2019 23:25, Kostya Vasilyev via dovecot wrote: Did you check /var/lib/dovecot Sorry, no! Works fine now, thank you (: -- sergio.

Re: ssl_dh

I'm subscribed, please reply to list directly. ssl_dh is required from 2.3.0-2.3.2. From 2.3.3 onwards its optional. You can rm the ssl-parameters.dat file to get rid of that warning. I have no ssl-parameters.dat file. -- sergio.

ssl_dh

https://wiki.dovecot.org/SSL/DovecotConfiguration says: "Since v2.3.3+ Diffie-Hellman parameters have been made optional, and you are encouraged to disable non-ECC DH algorithms completely." and a bit later: "From version 2.3, you must specify path to DH parameters file using ssl_dh= So.