- dovecot - dovecot.org

How to correctly use readonly=yes with the sqlite driver?
by oddlama 24 Jul '22

24 Jul '22

Hi! I want to use a sqlite database in readonly mode, which I found mentionend in the docs [1]. Unfortunately no examples were given, so I tried to infer the usage by inspecting core/driver-sqlite.c. If I interpret it correctly, this should have worked: /etc/dovecot/dovecot-sql.conf.ext: driver = sqlite connect = readonly=yes /var/vmail/virtual.sqlite user_query = #... Unfortunately, dovecot tries to open a file named "readonly=yes /var/vmail/virtual.sqlite" instead. I have no idea why the option is not parsed. Is this a bug or am I using the feature incorrectly? Best regards, oddlama [1]: https://doc.dovecot.org/settings/plugin/sql-sqlite/

2 1

Dovecot sync stopped working since 2.3.18-r1 when .maildir has 700 permissions
by Martin Kuchta 23 Jul '22

23 Jul '22

Hello, Since upgrading to dovecot 2.3.18-r1 my sync setup using replicator plugin stopped working. It seems there is a problem accessing a .maildir with 700 permissions, only accessible by the owner. Everything worked fine prior to this version and I made no configuration changes. # 2.3.19.1 (9b53102964): /etc/dovecot/dovecot.conf # Pigeonhole version 0.5.19 (4eae2f79) # OS: Linux 5.10.74-gentoo x86_64 Gentoo Base System release 2.8 # Hostname: www.example.com auth_mechanisms = plain login auth_username_format = %Ln doveadm_password = # hidden, use -P to show it hostname = www.example.xom listen = * login_greeting = Dovecot ready. mail_location = maildir:~/.maildir mail_plugins = notify replication managesieve_notify_capability = mailto managesieve_sieve_capability = fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date index ihave duplicate mime foreverypart extracttext imapflags notify vnd.dovecot.pipe namespace inbox { inbox = yes location = mailbox Drafts { special_use = \Drafts } mailbox Junk { special_use = \Junk } mailbox Sent { special_use = \Sent } mailbox "Sent Messages" { special_use = \Sent } mailbox Trash { special_use = \Trash } prefix = } passdb { args = * driver = pam } plugin { mail_replica = tcps:www.example.com:8000 sieve = file:~/sieve;active=~/.dovecot.sieve sieve_extensions = +notify +imapflags +vnd.dovecot.pipe sieve_pipe_bin_dir = /usr/lib/dovecot/sieve-pipe sieve_plugins = sieve_extprograms } postmaster_address = postmaster(a)example.com protocols = imap lmtp sieve service aggregator { fifo_listener replication-notify-fifo { mode = 0666 } unix_listener replication-notify { mode = 0666 } } service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0666 user = postfix } } service doveadm { inet_listener { port = 8000 ssl = yes } } service lmtp { unix_listener /var/spool/postfix/private/dovecot-lmtp { group = postfix mode = 0600 user = postfix } } service replicator { process_min_avail = 1 unix_listener replicator-doveadm { mode = 0600 } } ssl_cert = </etc/letsencrypt/live/example.com/fullchain.pem ssl_cipher_list = ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-AES256-GCM-SHA384:DHE-RSA-AES128-GCM-SHA256:DHE-DSS-AES128-GCM-SHA256:kEDH+AESGCM:ECDHE-RSA-AES128-SHA256:ECDHE-ECDSA-AES128-SHA256:ECDHE-RSA-AES128-SHA:ECDHE-ECDSA-AES128-SHA:ECDHE-RSA-AES256-SHA384:ECDHE-ECDSA-AES256-SHA384:ECDHE-RSA-AES256-SHA:ECDHE-ECDSA-AES256-SHA:DHE-RSA-AES128-SHA256:DHE-RSA-AES128-SHA:DHE-DSS-AES128-SHA256:DHE-RSA-AES256-SHA256:DHE-DSS-AES256-SHA:DHE-RSA-AES256-SHA:AES128-GCM-SHA256:AES256-GCM-SHA384:AES128-SHA256:AES256-SHA256:AES128-SHA:AES256-SHA:AES:CAMELLIA:DES-CBC3-SHA:!aNULL:!eNULL:!EXPORT:!DES:!RC4:!MD5:!PSK:!aECDH:!EDH-DSS-DES-CBC3-SHA:!EDH-RSA-DES-CBC3-SHA:!KRB5-DES-CBC3-SHA ssl_client_ca_dir = /etc/ssl/certs ssl_dh = # hidden, use -P to show it ssl_key = # hidden, use -P to show it userdb { driver = passwd } protocol lmtp { mail_plugins = notify replication sieve postmaster_address = postmaster(a)example.com } protocol lda { mail_plugins = notify replication sieve } local_name mail.example.com { ssl_cert = </etc/letsencrypt/live/example.com/fullchain.pem ssl_key = # hidden, use -P to show it } local_name example.com { ssl_cert = </etc/letsencrypt/live/example.com/fullchain.pem ssl_key = # hidden, use -P to show it } -- roughgrain.com - Mastering Mentoring +447780565902

1 1

Tools to get a report of which folders have new mail?
by Steve Litt 20 Jul '22

20 Jul '22

Hi all, I use a Dovecot IMAP server on my Linux desktop computer, and I'm pretty good at writing shellscripts. Is there any way I could use doveadm or other tools to create a report that shows all my folders in a hierarchy? Also, is there a way to show only those with new mail? Thanks, SteveT Steve Litt Summer 2022 featured book: Thriving in Tough Times http://www.troubleshooters.com/bookstore/thrive.htm

7 10

Tracing Sieve actions
by Doug Hardie 20 Jul '22

20 Jul '22

I encountered an interesting problem that one originator was being dumped into the Deleted file directly by my sieve. The sieve file was quite large and it was not obvious which entry was causing the issue. I recall there was a way to get sieve-test to show what is going on and which lines it used, but I could not replicate it tonight for anything. I ended up having to change all the deliver to the Deleted files to something else and test one at a time to find the offending entry. It took a long time. How do you get sieve-test to show the actual path it took through the file? -- Doug

3 4

Re: dovecot Digest, Vol 231, Issue 31
by Joseph Tam 20 Jul '22

20 Jul '22

> > doveadm -fjson mailbox status -u user unseen "*" > > Very nice Aki! I can pass that JSON to a Python program I make to parse > JSON, and then just report the ones not having "unseen":"0" . Thank Or use format "-ftab" and grep non-zero entries. Simpler than parsing JSON. Joseph Tam <jtam.home(a)gmail.com>

1 0

verify dovecot 2.3.19.1 + fts_tika + tika-server 2.4.1 attachment scanning?
by PGNet Dev 19 Jul '22

19 Jul '22

debugging a reproducible tika-server fail with fts_tika has proved a bit challenging, upstream 1st Q: can anyone _here_ verify successful (no error/fail) PDF attachment scanning using dovecot 2.3.19.1 + fts_tika, with tika-server 2.4.1 ? i'm seeing issues with any/all PDF attachments. this one, from smallpdf.com, "Get_Started_With_Smallpdf.pdf" DL @: https://ufile.io/dkew7k0u is the/a sample that reproduces the problem

2 6

Interfacing mutt with Dovecott
by Steve Litt 19 Jul '22

19 Jul '22

Hi all, All my email for the past 20 years is held on a Dovecot IMAP server (version 2.3.19.1 (9b53102964)) on my desktop. I've been using Claws-Mail but want to switch to Mutt. In the past I've tried this, but Mutt was unreliable in reading folders from my local Dovecot server. It didn't see a lot of the folders. I know some people have been very successful running Mutt to access an IMAP server, so it appears to be possible. How should I run Mutt to access my Dovecot? Also, in the past I've used Claws-Mail to admin my Dovecot folders (make new folders, move folders, etc). I've heard there are one or more Dovecot provided tools to do this kind of admin. What are the names of those tools? Thanks, SteveT Steve Litt Summer 2022 featured book: Thriving in Tough Times http://www.troubleshooters.com/bookstore/thrive.htm

2 1

Deleting "folders only" folder doesn't actually delete
by Alex 19 Jul '22

19 Jul '22

Hi, I'm using dovecot-2.3.17.1-1.fc34.x86_64 on fedora34 and Thunderbird 91 on fedora35. When creating a folder of type "folders only" in Thunderbird, then trying to delete it, it doesn't actually delete it from the filesystem. Is this a permissions problem? Or perhaps a Thunderbird problem? I don't see any messages in the logs that would indicate some type of failed attempt to delete. How do I troubleshoot this? Thanks, Alex

2 3

Re: Trouble configuring managesive plugin for roundcube
by Austin Witmer 16 Jul '22

16 Jul '22

So, here is my dovecot configuration. /etc/dovecot/dovecot.conf ## Dovecot configuration file # Enable installed protocols !include_try /usr/share/dovecot/protocols.d/*.protocol dict { #quota = mysql:/etc/dovecot/dovecot-dict-sql.conf.ext #expire = sqlite:/etc/dovecot/dovecot-dict-sql.conf.ext } !include conf.d/*.conf !include_try local.conf !include_try /usr/share/dovecot/protocols.d/*.protocol listen = * disable_plaintext_auth = yes mail_privileged_group = mail passdb { args = /etc/dovecot/dovecot-sql.conf driver = sql } protocols = imap lmtp pop3 namespace inbox { inbox = yes mailbox Trash { auto = subscribe # autocreate and autosubscribe the Trash mailbox special_use = \Trash } mailbox Sent { auto = subscribe # autocreate and autosubscribe the Sent mailbox special_use = \Sent } mailbox Spam { auto = subscribe # autocreate and autosubscribe the Spam mailbox } } service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0660 user = postfix } } service imap-login { inet_listener imap { port = 0 } inet_listener imaps { port = 993 } } service lmtp { unix_listener /var/spool/postfix/private/dovecot-lmtp { group = postfix mode = 0600 user = postfix } } protocol lmtp { postmaster_address=postmaster(a)mydomain.com hostname=mail.mydomain.com } ssl = required # Enable installed protocols !include_try /usr/share/dovecot/protocols.d/*.protocol listen = * disable_plaintext_auth = yes mail_privileged_group = mail passdb { args = /etc/dovecot/dovecot-sql.conf driver = sql } namespace inbox { inbox = yes mailbox Trash { auto = subscribe # autocreate and autosubscribe the Trash mailbox special_use = \Trash } mailbox Sent { auto = subscribe # autocreate and autosubscribe the Sent mailbox special_use = \Sent } } service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0660 user = postfix } } service imap-login { inet_listener imap { port = 0 } inet_listener imaps { port = 993 } } service lmtp { unix_listener /var/spool/postfix/private/dovecot-lmtp { group = postfix mode = 0600 user = postfix } } protocol lmtp { postmaster_address=postmaster(a)mydomain.com hostname=mail.mydomain.com } ssl = required ssl_cert = </etc/letsencrypt/live/mail.mydomain.com/fullchain.pem ssl_cipher_list = AES128+EECDH:AES128+EDH ssl_key = </etc/letsencrypt/live/mail.mydomain.com/privkey.pem ssl_prefer_server_ciphers = yes userdb { driver = prefetch } userdb { driver = sql args = /etc/dovecot/dovecot-sql.conf } ssl_cert = </etc/letsencrypt/live/mail.mydomain.com/fullchain.pem ssl_cipher_list = AES128+EECDH:AES128+EDH #ssl_dh_parameters_length = 4096 ssl_key = </etc/letsencrypt/live/mail.mydomain.com/privkey.pem ssl_prefer_server_ciphers = yes #ssl_protocols = !SSLv3 userdb { driver = prefetch } userdb { driver = sql args = /etc/dovecot/dovecot-sql.conf } And here is the /etc/dovecot/conf.d/20-managesieve.conf file. I tried enabling ssl = yes in the config below but it still didn’t work. ## ## ManageSieve specific settings ## # Uncomment to enable managesieve protocol: protocols = $protocols sieve # Service definitions service managesieve-login { inet_listener sieve { port = 4190 # ssl = yes } #inet_listener sieve_deprecated { # port = 2000 #} # Number of connections to handle before starting a new process. Typically # the only useful values are 0 (unlimited) or 1. 1 is more secure, but 0 # is faster. <doc/wiki/LoginProcess.txt> #service_count = 1 # Number of processes to always keep waiting for more connections. #process_min_avail = 0 # If you set service_count=0, you probably need to grow this. #vsz_limit = 64M } #service managesieve { # Max. number of ManageSieve processes (connections) #process_limit = 1024 #} # Service configuration protocol sieve { # Maximum ManageSieve command line length in bytes. ManageSieve usually does # not involve overly long command lines, so this setting will not normally # need adjustment #managesieve_max_line_length = 65536 # Maximum number of ManageSieve connections allowed for a user from each IP # address. # NOTE: The username is compared case-sensitively. #mail_max_userip_connections = 10 # Space separated list of plugins to load (none known to be useful so far). # Do NOT try to load IMAP plugins here. #mail_plugins = # MANAGESIEVE logout format string: # %i - total number of bytes read from client # %o - total number of bytes sent to client # %{put_bytes} - Number of bytes saved using PUTSCRIPT command # %{put_count} - Number of scripts saved using PUTSCRIPT command # %{get_bytes} - Number of bytes read using GETCRIPT command # %{get_count} - Number of scripts read using GETSCRIPT command # %{get_bytes} - Number of bytes processed using CHECKSCRIPT command # %{get_count} - Number of scripts checked using CHECKSCRIPT command # %{deleted_count} - Number of scripts deleted using DELETESCRIPT command # %{renamed_count} - Number of scripts renamed using RENAMESCRIPT command #managesieve_logout_format = bytes=%i/%o # To fool ManageSieve clients that are focused on CMU's timesieved you can # specify the IMPLEMENTATION capability that Dovecot reports to clients. # For example: 'Cyrus timsieved v2.2.13' #managesieve_implementation_string = Dovecot Pigeonhole # Explicitly specify the SIEVE and NOTIFY capability reported by the server # before login. If left unassigned these will be reported dynamically # according to what the Sieve interpreter supports by default (after login # this may differ depending on the user). #managesieve_sieve_capability = #managesieve_notify_capability = # The maximum number of compile errors that are returned to the client upon # script upload or script verification. #managesieve_max_compile_errors = 5 # Refer to 90-sieve.conf for script quota configuration and configuration of # Sieve execution limits. } Here is the output of testing with openssl from the roundcube server. I ran this: openssl s_client -connect 10.116.0.2:4190 </dev/null And got this: CONNECTED(00000003) 139804327073088:error:1408F10B:SSL routines:ssl3_get_record:wrong version number:../ssl/record/ssl3_record.c:331: --- no peer certificate available --- No client certificate CA names sent --- SSL handshake has read 5 bytes and written 283 bytes Verification: OK --- New, (NONE), Cipher is (NONE) Secure Renegotiation IS NOT supported Compression: NONE Expansion: NONE No ALPN negotiated Early data was not sent Verify return code: 0 (ok) — Is the second line in the output above the problem? Thanks to all of you for your help so far! Austin Witmer > On Jul 10, 2022, at 2:17 AM, Tomas Habarta <lists+dovecot(a)tocc.cz> wrote: > > I can't see your dovecot conf, but anyway -- roundcube side has to be aligned with dovecot's, i.e. if you use ssl on roundcube side, make sure you have it enabled on dovecot side too, something like: > > service managesieve-login { > inet_listener sieve { > port = 4190 > ssl = yes > } > > or just use tls, i.e. no "ssl=yes" in dovecot conf, but tls://10.116.0.2 in roundcube conf > This seems to be the same case: https://github.com/roundcube/roundcubemail/issues/7127 > > Tomas > > > On Sat, Jul 09, 2022 at 10:31:04PM -0600, Austin Witmer wrote: >> Hello all! >> I’ve got a bit of a problem that I would like some help with. So, I have >> two servers, one is my mail server running postfix, dovecot etc. I have a >> second server setup as my roundcube server. Both servers are running on >> the same LAN network. >> I have sieve scripts setup in dovecot in my mail server and they are >> working great! My trouble is that I can’t seem to make my roundcube talk >> correctly to managesieve on my mail server. >> Here is the mail.log file from the mail server when I try to create a >> sievescript from roundcube webmail: >> Jul 10 04:11:45 mail dovecot: managesieve-login: Disconnected: Too many >> invalid commands. (no auth attempts in 0 secs): user=<>, rip=10.116.0.3, >> lip=10.116.0.2, session=<cZMzomvjyNgKdAAD> >> And here is my managesieve configuration from my roundcube server. >> /var/www/roundcube/plugins/managesieve/config.inc.php >> <?php >> $config['managesieve_port'] = 4190; >> $config['managesieve_host'] = '[1]ssl://10.116.0.2'; >> $config['managesieve_auth_type'] = null; >> $config['managesieve_auth_cid'] = null; >> $config['managesieve_auth_pw'] = null; >> $config['managesieve_usetls'] = false; >> $config['managesieve_conn_options'] = array( >> 'ssl' => array( >> 'verify_peer' => false, >> 'allow_self_signed' => true, >> ), >> ); >> $config['managesieve_default'] = 'var/lib/dovecot/sieve/default.sieve'; >> $config['managesieve_script_name'] = 'default.sieve'; >> $config['managesieve_mbox_encoding'] = 'UTF-8'; >> $config['managesieve_replace_delimiter'] = ''; >> $config['managesieve_disabled_extensions'] = []; >> $config['managesieve_debug'] = true; >> $config['managesieve_kolab_master'] = false; >> $config['managesieve_filename_extension'] = '.sieve'; >> $config['managesieve_filename_exceptions'] = []; >> $config['managesieve_domains'] = []; >> $config['managesieve_default_headers'] = ['Subject', 'From', 'To']; >> $config['managesieve_vacation'] = 0; >> $config['managesieve_forward'] = 0; >> $config['managesieve_vacation_interval'] = 0; >> $config['managesieve_vacation_addresses_init'] = false; >> $config['managesieve_vacation_from_init'] = false; >> $config['managesieve_notify_methods'] = ['mailto']; >> $config['managesieve_raw_editor'] = true; >> $config['managesieve_disabled_actions'] = []; >> $config['managesieve_allowed_hosts'] = null; >> Does anybody have any clue why roundcube isn’t able to login in to >> managesieve on my mail server? >> Are there more logs/configs you would like to see? >> Thanks in advance for your help and suggestions! >> Austin Witmer >> >> References >> >> Visible links >> 1. file:///tmp/ssl:/10.116.0.2

3 13

dovecot 2.3.19.1 + tika-server 2.4.1 failed attachment scanning -- ERROR: 'corrupt stream'?
by PGNet Dev 15 Jul '22

15 Jul '22

i'm running dovecot 2.3.19.1 + fts_tika for attachment scanning, with tika-server 2.4.1 submitting a PDF attachment DIRECTLY to tika, via curl, there's no issue -- scan's OK on mail receipt in dovecot, the attachment is submitted to tika via fts, but scanning fails with a 'corrupt stream' ERROR. i've posted the issue, with details here, @ tika ML, https://lists.apache.org/thread/pztsq8tb8xqz3s4kmjpnt9p3zt07y05k where it's suggested the message may be getting truncated since direct-via-curl doesn't truncate, it seems that the submission process -- via fts plugin -- is a possiblity. can anyone confirm PDF attachment scan in a similar config, with latest versions? or suggest what diagnostic to use to dig for further, relevant troubleshooting info in dovecot+fts?

1 0