- dovecot - dovecot.org

Error since Dovecot v2.3.7
by Paul Hecker 15 Jul '19

15 Jul '19

Hi, since upgrading to Dovecot 2.3.7 I get the following new errors: 2019-07-15 09:10:52 mail dovecot: imap(paul(a)iwascoding.com)<32484><goWh8rKNSNZfqJ9R>: Error: file_lock_free(): Unexpectedly failed to retry locking /var/spool/mail/iwascoding/paul/mdbox/mailboxes/INBOX/dbox-Mails/dovecot-vsize.lock: fcntl(/var/spool/mail/iwascoding/paul/mdbox/mailboxes/INBOX/dbox-Mails/dovecot-vsize.lock, write-lock, F_SETLK) locking failed: No such file or directory It seems that this is related to moving or deleting mails (IMAP). The file at least sometimes exists, the folder exists. You find my doveconf below. Thanks, Paul # 2.3.7 (494d20bdc): /etc/dovecot/dovecot.conf # Pigeonhole version 0.5.7 (5a4e63b5) # OS: Linux 4.9.0-9-amd64 x86_64 Debian 9.9 # Hostname: mail.iwascoding.com auth_cache_size = 10 M auth_cache_ttl = 2 hours auth_mechanisms = plain login default_vsz_limit = 1 G first_valid_gid = 8 first_valid_uid = 8 hostname = mail.iwascoding.com imap_capability = +SPECIAL-USE last_valid_gid = 8 last_valid_uid = 8 lda_mailbox_autocreate = yes lda_mailbox_autosubscribe = yes mail_attachment_detection_options = add-flags-on-save mail_attribute_dict = file:/var/mail/iwascoding/%n/dovecot-attributes mail_gid = 8 mail_home = /var/mail/iwascoding/%n mail_location = mdbox:~/mdbox mail_plugins = quota listescape fts fts_xapian mail_prefetch_count = 200 mail_uid = 8 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 spamtest spamtestplus mdbox_rotate_size = 16 M namespace inbox { inbox = yes location = mailbox "Sent Messages" { auto = no special_use = \Sent } mailbox archive { auto = no special_use = \Archive } mailbox drafts { auto = no special_use = \Drafts } mailbox junk { auto = no special_use = \Junk } mailbox sent { auto = no special_use = \Sent } mailbox trash { auto = no special_use = \Trash } prefix = separator = / } passdb { args = /etc/dovecot/dovecot-sql.conf.ext driver = sql } plugin { fts = xapian fts_autoindex = yes fts_autoindex_exclude = \Junk fts_autoindex_exclude2 = \Trash fts_autoindex_exclude3 = \Drafts fts_enforced = yes fts_xapian = partial=2 full=20 plugin = fts fts_xapian quota = count:User quota quota_grace = 10%% quota_rule = *:storage=200M quota_vsizes = yes recipient_delimiter = + sieve = /var/mail/iwascoding/%n/.dovecot.sieve sieve_default = /var/lib/dovecot/sieve/default.sieve sieve_dir = /var/mail/iwascoding/%n/sieve sieve_extensions = +spamtest +spamtestplus sieve_global_dir = /var/lib/dovecot/sieve/global sieve_spamtest_max_value = 200 sieve_spamtest_status_header = X-Spam-Score-Int sieve_spamtest_status_type = score } postmaster_address = postmaster(a)iwascoding.com protocols = imap pop3 lmtp sieve submission quota_full_tempfail = yes service auth { unix_listener auth-client { mode = 0600 user = Debian-exim } unix_listener auth-userdb { user = mail } vsz_limit = 4 G } service imap-login { inet_listener imap { port = 0 } } service indexer-worker { vsz_limit = 2 G } service lmtp { user = mail } service managesieve-login { inet_listener sieve { port = 4190 } } service pop3-login { inet_listener pop3 { port = 0 } } service stats { unix_listener stats-writer { user = mail } } service submission-login { inet_listener submission_ssl { port = 465 ssl = yes } } ssl = required ssl_alt_cert = </usr/local/acme/var/iwascoding.com/fullchain.cer ssl_alt_key = # hidden, use -P to show it ssl_cert = </usr/local/acme/var/iwascoding.com_ecc/fullchain.cer ssl_cipher_list = ALL:HIGH:!SSLv2:!SSLv3:!kRSA:!MEDIUM:!LOW:!EXP:!RC4:!MD5:!aNULL:!eNULL:!EXPORT:!DES:!3DES:!PSK:!SRP:!DSS:!SEED:@STRENGTH ssl_client_ca_dir = /etc/ssl/certs ssl_client_ca_file = /etc/ssl/certs/ca-certificates.crt ssl_dh = # hidden, use -P to show it ssl_key = # hidden, use -P to show it ssl_min_protocol = TLSv1.2 ssl_prefer_server_ciphers = yes submission_client_workarounds = whitespace-before-path submission_max_mail_size = 50 M submission_relay_host = mail.iwascoding.com submission_relay_port = 10025 submission_relay_ssl = smtps userdb { args = /etc/dovecot/dovecot-sql.conf.ext driver = sql } protocol lmtp { mail_fsync = optimized mail_plugins = quota listescape fts fts_xapian sieve } protocol !indexer-worker { mail_vsize_bg_after_count = 100 } protocol lda { mail_fsync = optimized mail_plugins = quota listescape fts fts_xapian sieve } protocol imap { imap_metadata = yes mail_max_userip_connections = 40 mail_plugins = quota listescape fts fts_xapian imap_quota imap_zlib } protocol pop3 { mail_max_userip_connections = 30 }

2 2

broken mdboxes
by Mike 15 Jul '19

15 Jul '19

Hello, I was forced to do an emergency server migration with about 3000 mailboxes and I botched it somewhat. Hoping to find some help here. My symptoms are, users showing apparently deleted mail messages, some replicated mail, and a time period of mail that is just 'missing'. The source server is centos 6.10 with dovecot 2.2.5, and the destination is ubuntu 16 / dovecot 2.2.22. User mailboxes are mdbox format and I did an rsync from the old to the new. My screw up however was that my rsync was not --delete files, and had to be run multiple times over the course of a few weeks due to to bandwidth disparities and the sheer size of the mail spool approaching 700GB (source server had 10mbps. Should have used sneakernet instead). The bottom line however is that I wound up having many extra m.* files in each user storage dir that were not actually present on the source when the final, final sync was made and I went live with the migration server. I know this is my fsckup but now I have to deal with it. I first tried to fix the symptoms with a force-resync on the boxes not realizing the above, and that seemed to make things worse by only showing new mail as of the server migration date. Ugh. New mail is being delivered and this does appear in user mail boxes. But as I said, there seems to be some users with a problem with old mail presumably deleted on the prior server suddenly re-appearing (probbly due to the extraneous m.* mdbox files present). A more pressing problem is that there is simply a time period of mail that is in user mailboxes (on the old server) from before the migration, which is not displaying now for these users on the new server. I have investigated this and hacked on "mdbox-recover.pl" somewhat so that it iterates over all mdbox files for a user and I can extract ALL messages, and see that, yes, the mail really is present in the mdbox files, but pop/imap never shows it. This is puzzling to me. I have a test user that when I check imap, it shows only 21 message in inbox and 1 in sent. But if I extract the messages from the mdbox files, then I actually have 1117 messages. I know I can't just rsync the source server again with the right --delete flag, there has been lots of mail deliveries to the migrated boxes and so I don't want to lose all of that and create yet more problems. But I need to find some way to make these present mail messages appear for my users again. Im thinking it's got to be a flag of some kind since the data is there it's just ignored. Wondering what you would reccomend? Thanks. Mike-

2 3

Unable to send the mail but able to receive them
by necktwi 15 Jul '19

15 Jul '19

From my mac mail client I've connected to remote exim+dovecot server. Since few weeks back I was not able to send mail but able to receive. exim in /var/log/messages says: Jul 14 15:22:15 RPi3B exim[3576]: 2019-07-14 20:52:15 dovecot_plain authenticator failed for ([xx.xx.xx.xx]) [yy.yy.yy.yy]: 535 Incorrect authentication data (set_id=necktwi) dovecot in /var/log/dovecot.log says: Jul 14 19:40:27 auth: Debug: client in: AUTH 1 LOGIN service=smtp rip=yy.yy.yy.yy lip=xx.xx.xx.xx nologin resp= (previous base64 data may contain sensitive data) Jul 14 19:40:27 auth: Debug: client passdb out: CONT 1 VXNlcm5hbWU6 Jul 14 19:40:27 auth: Debug: auth client connected (pid=0) Jul 14 19:40:27 auth: Debug: client in: AUTH 1 PLAIN service=smtp secured rip=xx.xx.xx.xx lip=yy.yy.yy.yy nologin resp=aeVja333aQeuZWerdHdpAeRecmezaG9lcw== (previous base64 data may contain sensitive data) Jul 14 19:40:27 auth: Debug: policy(necktwi,xx.xx.xx.xx): Policy check action is continue Jul 14 19:40:27 auth-worker(11866): Debug: pam(necktwi,xx.xx.xx.xx): lookup service=smtp Jul 14 19:40:27 auth-worker(11866): Info: pam(necktwi,xx.xx.xx.xx): pam_authenticate() failed: Authentication failure (Password mismatch?) (given password: xxxxxxx) (log is obfuscated) Is it the problem with dovecot or exim? Should exim contact dovecot prior to sending the mail? I have also tried windows mail client with same error. auth-system.conf.ext: passdb { driver = pam args = %s } userdb { driver = passwd args = blocking=no } ... Necktwi

1 0

Sent messages disappear and don't arrive. (Receiving is ok)
by John 15 Jul '19

15 Jul '19

Hi List, I'm running an email server (Postfix, Dovecot, MySQL) on an RPi. I set it up using this 'howto' https://pestmeester.nl/index.html#11.0. It seemed to work but now sent emails just disappear and are not received. Inward emails are ok. I'm a Linux and Postfix Dovecot learner so please treat me as not being very knowledgeable. I'm not even sure if this is a Postfix or Dovecot issue so I've posted to both. (Nothing from Postfix so far!) I've tried to include what relevant info I thought a helper might need but if I've missed something please let me know. I'll appreciate any help. TIA, John

3 2

Purpose of stats-writer and why doveadm try to open it to dump stats ?
by Jean-Daniel 15 Jul '19

15 Jul '19

Hello, I want to monitor dovecot stats, and so I have an exporter process that run with limited rights. The monitoring user has only access to /var/run/dovecot/stats-reader and it works fine. Doveadm stats dump returns the list of all stats as expected. But each time I run doveadm stats dump, it logs the following error: Error: net_connect_unix(/var/run/dovecot/stats-writer) failed: Permission denied So what is the purpose of the stats-writer socket, and why doveadm try to open it to simply dump stats ? Is it really something it needs and I should update my user permissions or is it a doveadm bug ?

2 1

Re: Purpose of stats-writer and why doveadm try to open it to dump stats ?
by Jean-Daniel 14 Jul '19

14 Jul '19

> Le 14 juil. 2019 à 11:58, Reio Remma <reio(a)mrstuudio.ee> a écrit : > > On 14.07.2019 10:10, Jean-Daniel via dovecot wrote: >> Hello, >> >> I want to monitor dovecot stats, and so I have an exporter process that run with limited rights. >> The monitoring user has only access to /var/run/dovecot/stats-reader and it works fine. >> Doveadm stats dump returns the list of all stats as expected. >> >> But each time I run doveadm stats dump, it logs the following error: >> >> Error: net_connect_unix(/var/run/dovecot/stats-writer) failed: Permission denied >> >> So what is the purpose of the stats-writer socket, and why doveadm try to open it to simply dump stats ? >> Is it really something it needs and I should update my user permissions or is it a doveadm bug ? >> > > Hello! > > Depending on the system you're running on, there may be SELinux etc. doing its work. > I know why stats-writer is not accessible, this is on purpose (doveadm run with a uid that explicitly don’t have access to stats-writer). What I want to know is why does doveadm even try to open it to simply dump the stats.

1 0

Getting SSL certificate/key from database
by Yevgeny Kosarzhevsky 14 Jul '19

14 Jul '19

Hello, I am not finding how to read SSL keys/certificates from database. Is this possible? Or only file reads allowed? -- Regards, Yevgeny

2 1

Pigeonhole-0.5.7 fails to build from sources
by Lefteris Tsintjelis 13 Jul '19

13 Jul '19

Latest update fails to build from sources in FreeBSD 12-STABLE --- lda-sieve-plugin.lo --- lda-sieve-plugin.c:82:27: error: variable has incomplete type 'struct smtp_submit_input' struct smtp_submit_input submit_input; ^ lda-sieve-plugin.c:82:9: note: forward declaration of 'struct smtp_submit_input' struct smtp_submit_input submit_input; ^ 1 error generated. *** [lda-sieve-plugin.lo] Error code 1 make[6]: stopped in /usr/ports/mail/dovecot-pigeonhole/work/dovecot-2.3-pigeonhole-0.5.7/src/plugins/lda-sieve --- lda-sieve-log.lo --- mv -f .deps/lda-sieve-log.Tpo .deps/lda-sieve-log.Plo 1 error make[6]: stopped in /usr/ports/mail/dovecot-pigeonhole/work/dovecot-2.3-pigeonhole-0.5.7/src/plugins/lda-sieve *** [all-recursive] Error code 1 make[5]: stopped in /usr/ports/mail/dovecot-pigeonhole/work/dovecot-2.3-pigeonhole-0.5.7/src/plugins 1 error make[5]: stopped in /usr/ports/mail/dovecot-pigeonhole/work/dovecot-2.3-pigeonhole-0.5.7/src/plugins *** [all-recursive] Error code 1 make[4]: stopped in /usr/ports/mail/dovecot-pigeonhole/work/dovecot-2.3-pigeonhole-0.5.7/src 1 error make[4]: stopped in /usr/ports/mail/dovecot-pigeonhole/work/dovecot-2.3-pigeonhole-0.5.7/src *** [all-recursive] Error code 1 make[3]: stopped in /usr/ports/mail/dovecot-pigeonhole/work/dovecot-2.3-pigeonhole-0.5.7 1 error make[3]: stopped in /usr/ports/mail/dovecot-pigeonhole/work/dovecot-2.3-pigeonhole-0.5.7 *** [all] Error code 2 make[2]: stopped in /usr/ports/mail/dovecot-pigeonhole/work/dovecot-2.3-pigeonhole-0.5.7 1 error make[2]: stopped in /usr/ports/mail/dovecot-pigeonhole/work/dovecot-2.3-pigeonhole-0.5.7 ===> Compilation failed unexpectedly. Ensure that dovecot-pigeonhole's GSSAPI backend is the same as dovecot2 (make config). Try to set MAKE_JOBS_UNSAFE=yes and rebuild before reporting the failure to the maintainer. *** Error code 1 Stop. make[1]: stopped in /usr/ports/mail/dovecot-pigeonhole *** Error code 1 Stop. make: stopped in /usr/ports/mail/dovecot-pigeonhole

2 3

Re: Applying Dovecot for a large / deep folder-hierarchy archive - BUG REPORTS!
by Adam D. Barratt 13 Jul '19

13 Jul '19

On Wed, 2019-07-10 at 12:26 +0100, Arnold Opio Oree wrote: > Understood Adam, > > My thinking is that this is a package released with Debian 10. And so > has everything to do with the release. For clarity here - debian-release is neither a support forum nor a discussion list, nor a means of reporting issues in software contained within a Debian release. Debian has support fora and a bug tracking system to handle such reports and issues, as per https://www.debian.org /support . Having a single list that discusses any issue in any piece of software shipped by Debian cannot possibly scale. Rather, this list is the contact point and team alias for the Release Team, who oversee and manage the release process. It is up to individual package maintainers to triage and deal with issues reported against their packages and then to liaise with us if required. Regards, Adam

2 1

Error: file_ostream.net_set_tcp_nodelay
by Lefteris Tsintjelis 13 Jul '19

13 Jul '19

After upgrading to 2.3.7_1 I get those errors every now and then. Running FreeBSD 12-RELEASE. Any idea what they may be? Jul 13 08:07:11 pop3-login: Error: file_ostream.net_set_tcp_nodelay(, FALSE) failed: Connection reset by peer Jul 13 08:19:10 imap-login: Error: file_ostream.net_set_tcp_nodelay(, TRUE) failed: Connection reset by peer Jul 13 08:24:09 imap-login: Error: file_ostream.net_set_tcp_nodelay(, TRUE) failed: Connection reset by peer Jul 13 08:34:53 imap-login: Error: file_ostream.net_set_tcp_nodelay(, TRUE) failed: Connection reset by peer Lefteris

1 0

Pigeonhole release v0.5.7
by Aki Tuomi 12 Jul '19

12 Jul '19

Hi! We are pleased to release Pigeonhole release v0.5.7. Tarball is available at https://pigeonhole.dovecot.org/releases/2.3/dovecot-2.3-pigeonhole-0.5.7.ta… https://pigeonhole.dovecot.org/releases/2.3/dovecot-2.3-pigeonhole-0.5.7.ta… Binary packages are available at https://repo.dovecot.org/ Changes ------- + vacation: Made the subject for the automatic response message produced by the Sieve vacation action configurable. Both the default subject (if the script defines none) and the subject template (e.g. used to add a subject prefix) can be configured. - dsync: dsync-replication does not synchronize Sieve scripts. - imap_sieve_filter: Reduce FILTER=SIEVE verbosity over IMAP connection. - testsuite: Pigeonhole testsuite segfaulted if it was compiled with GCC 9 --- Aki Tuomi Open-Xchange oy

3 4

2.3.7/FreeBSD: Seeing lots of stats-writer errors.
by Larry Rosenman 12 Jul '19

12 Jul '19

A user reported this to me, and I'm seeing it too: Hi all :) After mail/dovecot upgrade to v2.3.7 it seems something went wrong with stat-writer... IMAP and POP3 logs: Jul 12 19:45:34 mail dovecot: imap-login: Error: file_ostream.net_set_tcp_nodelay((conn:unix:/var/run/dovecot/stats-writer), TRUE) failed: Invalid argument Jul 12 19:45:34 mail dovecot: imap-login: Error: file_ostream.net_set_tcp_nodelay((conn:unix:login), TRUE) failed: Invalid argument Jul 12 19:45:35 mail dovecot: imap: Error: file_ostream.net_set_tcp_nodelay((conn:unix:/var/run/dovecot/stats-writer), TRUE) failed: Invalid argument Jul 12 19:45:35 mail dovecot: imap: Error: file_ostream.net_set_tcp_nodelay((conn:unix:/var/run/dovecot/auth-master), TRUE) failed: Invalid argument Jul 12 19:45:35 mail dovecot: imap-login: Login: user=<someone(a)domain.tld>, method=PLAIN, rip=192.168.0.28, lip=192.168.0.1, mpid=47811, TLS, session=<aelAen+NKpDAqAAc> Jul 12 19:45:41 mail dovecot: imap(someone(a)domain.tld)<47811><aelAen+NKpDAqAAc>: Connection closed (UID SEARCH finished 6.727 secs ago) in=128 out=2015 deleted=0 expunged=0 trashed=0 hdr_count=0 hdr_bytes=0 body_count=0 body_bytes=0 Jul 12 19:51:21 mail dovecot: pop3-login: Error: file_ostream.net_set_tcp_nodelay((conn:unix:/var/run/dovecot/stats-writer), TRUE) failed: Invalid argument Jul 12 19:51:21 mail dovecot: auth: Error: file_ostream.net_set_tcp_nodelay((conn:unix:/var/run/dovecot/stats-writer), TRUE) failed: Invalid argument Jul 12 19:51:21 mail dovecot: pop3-login: Error: file_ostream.net_set_tcp_nodelay((conn:unix:login), TRUE) failed: Invalid argument Jul 12 19:51:21 mail dovecot: pop3: Error: file_ostream.net_set_tcp_nodelay((conn:unix:/var/run/dovecot/stats-writer), TRUE) failed: Invalid argument Jul 12 19:51:21 mail dovecot: pop3: Error: file_ostream.net_set_tcp_nodelay((conn:unix:/var/run/dovecot/auth-master), TRUE) failed: Invalid argument Jul 12 19:51:21 mail dovecot: pop3-login: Login: user=<someone(a)domain.tld>, method=PLAIN, rip=192.168.0.33, lip=192.168.0.1, mpid=47877, TLS, session=<h+3jjn+NcPrAqAAh> Jul 12 19:51:21 mail dovecot: pop3(someone(a)domain.tld)<47877><h+3jjn+NcPrAqAAh>: Disconnected: Logged out top=0/0, retr=0/0, del=0/0, size=0 Ideas? -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 214-642-9640 (c) E-Mail: larryrtx(a)gmail.com US Mail: 5708 Sabbia Dr, Round Rock, TX 78665-2106

2 1

new dovecot, selinux Problem ?
by Günther J. Niederwimmer 12 Jul '19

12 Jul '19

Hello List, after the last update I have a selinux "Problem" with dovecot. My system is a centos 7. After a new start from dovecot selinux block a connection. Jul 12 16:24:24 mx01 systemd: Starting Dovecot IMAP/POP3 email server... Jul 12 16:24:54 mx01 systemd: Started Dovecot IMAP/POP3 email server. Jul 12 16:24:54 mx01 dovecot: Warning: Corrected permissions for login directory /var/run/dovecot/token-login Jul 12 16:24:54 mx01 dbus[3008]: [system] Activating service name='org.fedoraproject.Setroubleshootd' (using servicehelper) Jul 12 16:24:55 mx01 dbus[3008]: [system] Successfully activated service 'org.fedoraproject.Setroubleshootd' Jul 12 16:24:55 mx01 setroubleshoot: SELinux is preventing dovecot from getattr access on the file /proc/sys/fs/suid_dumpable. For complete SELinux messages run: sealert -l c46ae6a7-64c4-49a7-9e3d-477547fb6da8 Jul 12 16:24:55 mx01 python: SELinux is preventing dovecot from getattr access on the file /proc/sys/fs/suid_dumpable.#012#012***** Plugin catchall (100. confidence) suggests **************************#012#012If you believe that dovecot should be allowed getattr access on the suid_dumpable file by default.#012Then you should report this as a bug.#012You can generate a local policy module to allow this access.#012Do#012allow this access for now by executing:#012# ausearch -c 'dovecot' --raw | audit2allow -M my-dovecot#012# semodule -i my-dovecot.pp#012 is this a bad Error? When I install this local Policy i have a Problem with selinux wrong policy. sealert -a /var/log/audit/audit.log 13% donetype=AVC msg=audit(1562936830.462:61868): avc: denied { getattr } for pid=31288 comm="dovecot" path="/proc/sys/fs/suid_dumpable" dev="proc" ino=35734 scontext=system_u:system_r:dovecot_t:s0 tcontext=system_u:object_r:proc_security_t:s0 tclass=file permissive=0 **** Invalid AVC allowed in current policy *** 100% done found 0 alerts in /var/log/audit/audit.log Can any tell / help me for a correct installation? -- mit freundliche Grüßen / best regards, Günther J. Niederwimmer

1 0

[bug] success field never emited in auth_request_finished event
by Jean-Daniel Dupas 12 Jul '19

12 Jul '19

Hi, I'm playing with the new events, and encounter some issues: First the 'auth_request_finished' event is documented as having a 'successful' field, but in the code, the field is defined as 'success' (e->add_str("success", "yes")). But more important, in the function "auth_request_success_continue()" (auth/auth-request.c:288), "auth_request_log_finished(request)" is call (line 303) before updating the request status: "request->successful = TRUE" (line 312) So the log function never set the success field to "yes" as at this point request->successful is still false. Jean-Daniel

2 3

Getting login stats
by Jean-Daniel Dupas 12 Jul '19

12 Jul '19

Hello, I'm trying to get some IMAP auth stats on a Dovecot 2.3.6 instance, but whatever I declare in metric, it always show 0. What I want basically is how many IMAP auth attempts there was on the server, and optional a way to filter on the auth attempt status (successful or failed). My server uses a simple auth (with LDAP backend) and supports only "auth_mechanisms = plain login" I tried using the following metrics: -------------------------------- metric auth_request_finished { event_name = auth_request_finished } metric auth_passdb_request_finished { event_name = auth_passdb_request_finished } metric auth_userdb_request_finished { event_name = auth_userdb_request_finished } metric auth_client_request_started { event_name = auth_client_request_started } metric auth_client_userdb_lookup_started { event_name = auth_client_userdb_lookup_started } metric auth_client_passdb_lookup_started { event_name = auth_client_passdb_lookup_started } metric auth_client_cache_flush_started { event_name = auth_client_cache_flush_started } metric imap_command_finished { event_name = imap_command_finished filter { name = LOGIN } } -------------------------------- But even after many successful logins, doveadm reports 0 for all events: metric_name field count sum min max avg median stddev %95 auth_request_finished duration 0 0 0 0 0.00 0 0.00 0 auth_passdb_request_finished duration 0 0 0 0 0.00 0 0.00 0 auth_userdb_request_finished duration 0 0 0 0 0.00 0 0.00 0 auth_client_request_started duration 0 0 0 0 0.00 0 0.00 0 auth_client_userdb_lookup_started duration 0 0 0 0 0.00 0 0.00 0 auth_client_passdb_lookup_started duration 0 0 0 0 0.00 0 0.00 0 auth_client_cache_flush_started duration 0 0 0 0 0.00 0 0.00 0 imap_command_finished duration 0 0 0 0 0.00 0 0.00 0

2 2

dovecot 2.3.6 on FreeBSD 12.0-RELEASE inside a JAIL does not see dovecot/replication-notify-fifo
by Lars Schotte 12 Jul '19

12 Jul '19

Hi, I see dovecot[47939]: imap(gustik(a)gustik.eu)<48079><XVTMe3qNFpQqAchEJAsZAoGuBtbxcZmK>: Error: open(/var/run/dovecot/replication-notify-fifo) failed: No such file or directory even though, right after: Jul 12 13:54:41 madarka dovecot[47939]: aggregator: Error: Client sent invalid input when I send echo 1 > /var/run/dovecot/replication-notify-fifo and yes, of course prw-rw-rw- 1 dovecot vmail 0B Jul 12 13:57 /var/run/dovecot/replication-notify-fifo exists. FreeBSD madarka.gustik.eu 12.0-RELEASE FreeBSD 12.0-RELEASE r342152 GENERIC amd64 Dovecot running inside a jail with a version of 2.3.6 just recently compiled from ports! I ve allowed raw sockets and sysvipc for this jail but it did not help. Also making explicit imap mail plugins notify and replicator did not help. Any ideas? -- Lars Schotte Mudroňova 13 92101 Piešťany

1 0

Confused about dovecot ACL
by HTMLServices.it 12 Jul '19

12 Jul '19

Hello everyone sorry i'm not very experienced and also my english I installed a centos 7 server with ispconfig postfix dovecot 2.2.36 and roundcube, this server is only a mail archive, so my need is that ALL the mailboxes are read-only on roundcube/imap and any user must NOT delete the messages. ... so I configured dovecot's ALC following the guide "https://wiki2.dovecot.org/ACL" I think I did everything correctly and I don't get errors but entering the webmail roundcube I CAN DELETE MESSAGES ..... it seems that the acl have no effect .... added to the dovecot configuration file /etc/dovecot/dovecot.conf ______________________________________ .... plugin { acl = vfile: / etc / dovecot / dovecot-acl } ..... protocol imap { mail_plugins = $ mail_plugins imap_acl } mail_plugins = acl ..... ______________________________________ created the "global" file /etc/dovecot/dovecot-acl and inserted that the test user has only lookup and reading rights (lr): * user=test(a)test.com lr ______________________________________ my dovecot.conf ********************************* listen = *,[::] protocols = imap pop3 auth_mechanisms = plain login disable_plaintext_auth = no log_timestamp = "%Y-%m-%d %H:%M:%S " mail_privileged_group = vmail ssl_cert = </etc/postfix/smtpd.cert ssl_key = </etc/postfix/smtpd.key ssl_protocols = !SSLv3 passdb { args = /etc/dovecot-sql.conf driver = sql } userdb { driver = prefetch } userdb { args = /etc/dovecot-sql.conf driver = sql } plugin { acl = vfile:/etc/dovecot/dovecot-acl quota = dict:user::file:/var/vmail/%d/%n/.quotausage sieve=/var/vmail/%d/%n/.sieve } service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0660 user = postfix } unix_listener auth-userdb { group = vmail mode = 0600 user = vmail } user = root } service lmtp { unix_listener /var/spool/postfix/private/dovecot-lmtp { group = postfix mode = 0600 user = postfix } } service imap-login { client_limit = 1000 process_limit = 500 } protocol imap { mail_plugins = $mail_plugins imap_acl mail_plugins = quota imap_quota } protocol pop3 { pop3_uidl_format = %08Xu%08Xv mail_plugins = quota } protocol lda { mail_plugins = sieve quota postmaster_address = root@localhost } protocol lmtp { postmaster_address = admin(a)htmlservices.it mail_plugins = quota sieve } mail_plugins = $mail_plugins quota mail_plugins = acl ********************************* my dovecot-acl ********************************* * user=test(a)test.com lr ********************************* "debug" ********************************* [root@archivio ~]# doveadm -Dv acl debug -u test(a)test.com INBOX Debug: Loading modules from directory: /usr/lib64/dovecot Debug: Module loaded: /usr/lib64/dovecot/lib01_acl_plugin.so Debug: Loading modules from directory: /usr/lib64/dovecot/doveadm Debug: Module loaded: /usr/lib64/dovecot/doveadm/lib10_doveadm_acl_plugin.so Debug: Skipping module doveadm_expire_plugin, because dlopen() failed: /usr/lib64/dovecot/doveadm/lib10_doveadm_expire_plugin.so: undefined symbol: expire_set_deinit (this is usually intentional, so just ignore this message) Debug: Skipping module doveadm_quota_plugin, because dlopen() failed: /usr/lib64/dovecot/doveadm/lib10_doveadm_quota_plugin.so: undefined symbol: quota_user_module (this is usually intentional, so just ignore this message) Debug: Module loaded: /usr/lib64/dovecot/doveadm/lib10_doveadm_sieve_plugin.so Debug: Skipping module doveadm_fts_lucene_plugin, because dlopen() failed: /usr/lib64/dovecot/doveadm/lib20_doveadm_fts_lucene_plugin.so: undefined symbol: lucene_index_iter_deinit (this is usually intentional, so just ignore this message) Debug: Skipping module doveadm_fts_plugin, because dlopen() failed: /usr/lib64/dovecot/doveadm/lib20_doveadm_fts_plugin.so: undefined symbol: fts_user_get_language_list (this is usually intentional, so just ignore this message) Debug: Skipping module doveadm_mail_crypt_plugin, because dlopen() failed: /usr/lib64/dovecot/doveadm/libdoveadm_mail_crypt_plugin.so: undefined symbol: mail_crypt_box_get_pvt_digests (this is usually intentional, so just ignore this message) doveadm(test(a)test.com): Debug: Added userdb setting: mail=maildir:/var/vmail/test.com/test/Maildir doveadm(test(a)test.com): Debug: Added userdb setting: plugin/quota_rule=*:storage=0B doveadm(test(a)test.com): Debug: Added userdb setting: plugin/sieve=/var/vmail/test.com/test/.sieve doveadm(test(a)test.com): Debug: Effective uid=5000, gid=5000, home=/var/vmail/test.com/test doveadm(test(a)test.com): Debug: acl: No acl_shared_dict setting - shared mailbox listing is disabled doveadm(test(a)test.com): Debug: maildir++: root=/var/vmail/test.com/test/Maildir, index=, indexpvt=, control=, inbox=/var/vmail/test.com/test/Maildir, alt= doveadm(test(a)test.com): Debug: acl: initializing backend with data: vfile:/etc/dovecot/dovecot-acl doveadm(test(a)test.com): Debug: acl: acl username = test(a)test.com doveadm(test(a)test.com): Debug: acl: owner = 1 doveadm(test(a)test.com): Debug: acl vfile: Global ACL file: /etc/dovecot/dovecot-acl doveadm(test(a)test.com): Info: Mailbox 'INBOX' is in namespace '' doveadm(test(a)test.com): Info: Mailbox path: /var/vmail/test.com/test/Maildir doveadm(test(a)test.com): Info: All message flags are shared across users in mailbox doveadm(test(a)test.com): Debug: Mailbox 'INBOX' matches global ACL pattern '*' doveadm(test(a)test.com): Debug: Mailbox 'INBOX' matches global ACL pattern '*' doveadm(test(a)test.com): Debug: Mailbox 'INBOX' matches global ACL pattern '*' doveadm(test(a)test.com): Debug: acl vfile: file /var/vmail/test.com/test/Maildir/dovecot-acl not found doveadm(test(a)test.com): Info: User test(a)test.com has rights: lookup read doveadm(test(a)test.com): Info: Mailbox in user's private namespace doveadm(test(a)test.com): Info: Mailbox INBOX is visible in LIST [root@archivio ~]# ********************************* if I see the line "Info: User test(a)test.com has rights: lookup read" it seems that the ACL (lookup and read) are correctly applied, but as I was saying above, entering the user test(a)test.com on the webmail, I can do everything I want to also delete the e-mails ..... these are days I try to understand but I don't understand what I'm wrong and how to solve .... thank you all in advance

2 1

Re: Best mail encryption solution for per-user
by Aki Tuomi 12 Jul '19

12 Jul '19

On 27.05.2018 21:16, mail(a)sjemm.net wrote: > May 27, 2018 8:52 AM, "Aki Tuomi" <aki.tuomi(a)dovecot.fi> wrote: >>> On 26 May 2018 at 10:36 mail(a)sjemm.net wrote: >>> >>> May 23, 2018 10:10 AM, mail(a)sjemm.net wrote: >>> May 23, 2018 9:46 AM, "Aki Tuomi" <aki.tuomi(a)dovecot.fi> wrote: >>> >>> On 23.05.2018 10:15, mail(a)sjemm.net wrote: >>> >>> May 23, 2018 8:31 AM, "Aki Tuomi" <aki.tuomi(a)dovecot.fi> wrote: >>> >>> On 23.05.2018 09:13, mail(a)sjemm.net wrote: >>> May 20, 2018 8:01 PM, mail(a)sjemm.net wrote: >>> May 20, 2018 2:47 PM, "Aki Tuomi" <aki.tuomi(a)dovecot.fi> wrote: >>> On 19 May 2018 at 16:40 mail(a)sjemm.net wrote: >>> >>> May 18, 2018 10:01 PM, "Aki Tuomi" <aki.tuomi(a)dovecot.fi> wrote: >>> On 18 May 2018 at 21:44 mail(a)sjemm.net wrote: >>> >>> May 18, 2018 4:43 PM, "Aki Tuomi" <aki.tuomi(a)dovecot.fi> wrote: >>> On 18 May 2018 at 17:38 mail(a)sjemm.net wrote: >>> >>> May 18, 2018 4:05 PM, "Aki Tuomi" <aki.tuomi(a)dovecot.fi> wrote: >>> On 18 May 2018 at 16:43 mail(a)sjemm.net wrote: >>> >>> Hi Tai74 and Aki, >>> I followed your conversation with interest on how to setup per user encryption in dovecot. >>> I have setup my dovecot with the following in a conf file: >>> >>> ============== >>> >>> mail_attribute_dict = file:%h/Maildir/dovecot-attributes >>> mail_plugins = $mail_plugins mail_crypt >>> plugin { >>> >>> mail_crypt_curve = secp521r1 >>> >>> mail_crypt_save_version = 2 >>> >>> } >>> >>> ============== >>> >>> This works nice, all emails are being encrypted and every user/folder has keys. >>> But as I understood from your conversation these keys are not protected. And I want them to be >>> protected by the users password used by imap. >>> >>> Those passwords are stored in a mysql DB file. ( I used a guide from workaround [dot] org to set up >>> the DB and postfix/dovecot) >>> >>> but how would i set it so, that the users password from the DB is used to encrypt the keys? >>> >>> should i use mail_crypt_private_password = ? >>> how do i point it to the mysql db then? >>> im unsure about this >>> >>> Do you have any hints on this? >>> >>> Kind regards, >>> Zjemm >>> >>> The passwords in your MySQL database are, hopefully, not in plaintext. If you want to secure your >>> user's keys using user's login password, you must have a TOOL that manages this. >>> >>> You can use mail_crypt_private_password = %w in (mysql) passdb fields to provide the user's login >>> password as private password. You might want to run it thru some hash, so %{sha1:password} might be >>> a good option. >>> >>> You can change the key password using 'doveadm mailbox cryptokey', this needs to be done every time >>> user changes his password. >>> >>> Also note that if you go down this road, and the user forgets his password, you will not be able to >>> recover the emails without backup copy of the private key. >>> >>> Aki >>> >>> Hi Aki >>> >>> I used the following command: >>> dovecot pw -s SHA256-CRYPT >>> >>> the output on the chosen password looks like: {SHA256-CRYPT}$5$Rokc06a7In4SF3bO$OQpGQWqg........ >>> >>> This output is used to store in the password fields in the database. So no plain text passwords no >>> :) >>> >>> You can use mail_crypt_private_password = %w in (mysql) passdb fields to provide the user's login >>> password as private password. >>> >>> can you explain this a bit more for me? >>> >>> for now i have in the 10-auth.conf file the following: >>> ============== >>> passdb { >>> driver = sql >>> >>> # Path for SQL configuration file, see example-config/dovecot-sql.conf.ext >>> args = /etc/dovecot/dovecot-sql.conf.ext >>> } >>> >>> and: >>> >>> userdb { >>> driver = static >>> args = uid=vmail gid=vmail home=/var/vmail/%d/%n >>> } >>> ============== >>> >>> then i have in dovecot-sql.conf.ext >>> ============== >>> driver = mysql >>> connect = host=x.x.x.x dbname=mailserver user=mailuser password=mailpasswordexample >>> default_pass_scheme = SHA256-CRYPT >>> password_query = SELECT email as user, password FROM virtual_users WHERE email='%u'; >>> ============== >>> Where do i need to set : mail_crypt_private_password = %w ? >>> >>> password as private password. You might want to run it thru some hash, so %{sha1:password} might be >>> a good option. >>> >>> the passwords are allready hashed in the DB using: dovecot pw -s SHA256-CRYPT to genereate the has. >>> so this step isnt nesesary anymore am i right? >>> >>> Thank you for your quick response, very helpfull >>> >>> Zjemm >>> >>> You misunderstood a bit. The idea is to use the *plaintext* password as the password for the >>> private key. Otherwise anyone could just decrypt it by looking at your database where the hashed >>> password is.. >>> >>> So: >>> >>> password_query = SELECT email as user, password, '%w' AS userdb_mail_crypt_private_password FROM >>> virtual_users WHERE email='%u' >>> >>> Aki >>> >>> Hi Aki, >>> >>> Thank you very much for your help, i realy appreciate that. >>> >>> Ok so if i understand it correctly i'll have to use: >>> >>> password_query = SELECT email as user, password, '%w' AS userdb_mail_crypt_private_password FROM >>> virtual_users WHERE email='%u' >>> >>> in my dovecot-sql.conf.ext file >>> >>> This query selects the user, the password, and %w >>> >>> if i run a little query myself: >>> MariaDB [mailserver]> SELECT email as user, password, '%w' AS userdb_mail_crypt_private_password >>> FROM virtual_users; >>> +------------------+----------------------------------+------------------------------------+ >>> | user | password | userdb_mail_crypt_private_password | >>> +------------------+----------------------------------+------------------------------------+ >>> | john(a)example.org | {SHA256-CRYPT}$5$M/GWzmtjsLroRWI | %w | >>> +------------------+----------------------------------+------------------------------------+ >>> >>> %w is a dovecot variable, and stands for the plaintext password, but the password is not stored as >>> plaintext in the DB, %w get filled with the actual plaintext password by dovecot upon the user that >>> is typing in the password when authenticating. >>> >>> is this correct? >>> >>> yes. >>> >>> so then i have the username the hashed password en the plaintext password as a result of the query. >>> >>> yes >>> >>> now userdb_mail_crypt_private_password = the plaintext password >>> do i need to reference it somewhere? or is userdb_mail_crypt_private_password autmatically used by >>> the dovecot mail_crypt plugin to encrypt the keys? or should it be mail_crypt_private_password? >>> >>> It gets injected into the mail process as 'mail_crypt_private_password', as if it was set in plugin >>> {} section. >>> >>> if i have this setup working i'm going to write a blog post on this topic to share this knowledge >>> >>> Thanks again and have a great weekend. >>> >>> Zjemm >>> >>> Aki >>> >>> Hi Aki, >>> >>> Cool i'm testing it right now. >>> I have set up a new mailserver (life is great with lxc containers :) ) >>> >>> postfix and dovecot are working like normal >>> >>> next i enable mail_crypt >>> >>> i did create a file: /etc/dovecot/conf.d/10-mailcrypt.conf >>> ========================== >>> mail_attribute_dict = file:%h/Maildir/dovecot-attributes >>> >>> mail_plugins = $mail_plugins mail_crypt >>> >>> plugin { >>> mail_crypt_curve = secp521r1 >>> mail_crypt_save_version = 2 >>> } >>> ========================== >>> >>> and then i changed the file: /etc/dovecot/dovecot-sql.conf.ext >>> >>> so the query is now the new query: >>> password_query = SELECT email as user, password, '%w' AS userdb_mail_crypt_private_password FROM >>> virtual_users WHERE email='%u'; >>> >>> then i restarted dovecot and postfix and send a test email to the one and only testuser that is in >>> there. >>> >>> when i open the mailbox with the tool mutt, i can see the new email, and when openening the email >>> the mutt client drops the connection. >>> >>> in the log i can see: >>> >>> May 19 13:34:48 mailserver1.example.local dovecot[600]: imap-login: Login: user=<john(a)example.org>, >>> method=PLAIN, rip=::1, lip=::1, mpid=713, TLS, session=<E3PnIY9sNM4AAAAAAAAAAAAAAAAAAAAB> >>> May 19 13:34:49 mailserver1.example.local dovecot[600]: imap(john(a)example.org): Error: read() >>> failed: >>> read(/var/vmail/example.org/john/Maildir/cur/1526736378.M161472P641.mailser…, >>> =571:2,) failed: Private key not available: Cannot decrypt key >>> bfc5bb25b1bf64290eea6dc14b516c6a0a25b64551b6e4f0f8677ba7274887cb: error:03070068:bignum >>> routines:BN_mpi2bn:encoding error (FETCH BODY[] for mailbox INBOX UID 8) >>> >>> i think i missed a step, but witch one? >>> >>> the userpassword hasnt been changed (that would be the next step in the testing process) >>> >>> should i've use doveadm first to encrypt the key with that userpassword? i thought it would do that >>> on the fly, because the initial keys where only just created when enabling the mail_crypt plugin >>> >>> please let me know your thougts >>> Zjemm >>> I noticed you replied directly to me, and not to the list, too... fixed that for you. >>> >>> mail_crypt_private_password is used when key is created, but if you have created it before using >>> password, you'll need to encrypt it before turning the setting on. >>> >>> Aki >>> Hi, Ok i'm sorry about that, thank you for fixing that. i'm a bit new to mailing lists :) >>> >>> are you a dovecot devoloper? or a enthusiastic user? >>> >>> anyway, i managed to get it working now with all your help :) >>> >>> to start fresh i did a: >>> rm -rf /var/vmail/example.org >>> >>> so all email is gone, and i assume all dovecot keys are gone that way. >>> >>> Then i tried to set a password first: >>> >>> root@mailserver1:/var/vmail# doveadm mailbox cryptokey password -u john(a)example.org -n summersun >>> result: Changed password for 0 key(s) >>> >>> (summersun = the password for this user) >>> >>> but then it says there are 0 keys, so then i send the test user an email and try to open the >>> mailbox, i'll get: >>> >>> imap(john(a)example.org): Error: read() failed: >>> read(/var/vmail/example.org/john/Maildir/cur/1526827992.M149712P883.mailser…, >>> =561:2,) failed: Private key not available: Cannot decrypt key >>> 71849013a70b0c631c06112077e7c2fe39b0b2737b4933b219793841209d4e7f: error:03070068:bignum >>> routines:BN_mpi2bn:encoding error >>> >>> but hey, now the key's are created, so i tried to set the password again: >>> >>> root@mailserver1:/var/vmail# doveadm mailbox cryptokey password -u john(a)example.org -n summersun >>> result: dcrypt_key_load_private(787701bd677dd69a26842547a3926cbaa625b0b5a91751f06678c3e9708343d9) >>> failed: password missing >>> ========= >>> >>> Lets start over again, i did a new: >>> rm -rf /var/vmail/example.org >>> >>> i disabled the mail_crypt_private_password in the sql query and send an email to the test user. >>> now again new keys are generated. >>> >>> then i did set the password via doveadm: >>> >>> root@mailserver1:/var/vmail# doveadm mailbox cryptokey password -u john(a)example.org -n summersun >>> result: Changed password for 1 key(s) >>> >>> i enabled the mail_crypt_private_password again in the sql query part and now it works :) >>> >>> YESSS!!! >>> >>> if i now change the password for the user, i cannot read the email anymore. that is what should >>> happen. >>> so now i changed the password for this user also with doveadm: >>> - doveadm mailbox cryptokey password -u john(a)example.org -n qwerty -o summersun >>> >>> and now i'm able to read the emails again. so it all works now as expected. >>> >>> i have now only one thing remaining. >>> >>> when i want to add a new user, i have to somehow: >>> - create the new user in the mysql DB >>> - start with dovecot not using mail_crypt_private_password (so disabled) >>> - send an initial email to let the users mailbox be created and generate the keys >>> - set the users password with doveadm >>> - restart dovecot again with mail_crypt_private_password (so enabled) >>> >>> but this would be disruptive to existing users, and i would have to script the whole thing as a >>> "add-new-user" script to make it usable i guess. >>> >>> do you know of a more easy way of acomplishing this? >>> could i use doveadm for all steps, and get around the mail_crypt_private_password disable part? >>> >>> or could i add a column in the mysql db called userdb_mail_crypt_private_password and fill that >>> column with %w for users that allready exist, and empty for new users. >>> when being empty, it might not set the mail_crypt_private_password for new users >>> >>> or is this the wrong way of thinking? >>> >>> let me know your thoughts on this. >>> >>> And last but not least, i really want to thank you for all your help. It is a really nice >>> experience. >>> Bless you! >>> >>> Zjemm >>> Hi Aki, >>> >>> You did fix the posting on the mail archive, i can see our conversation on there, all but the last >>> email i send to you. >>> Maybe you did not received the last email? >>> >>> would you be willing to take a look at my last question in the email See below: >>> Thank you very much. >>> >>> ================================ >>> i have now only one thing remaining. >>> >>> when i want to add a new user, i have to somehow: >>> - create the new user in the mysql DB >>> - start with dovecot not using mail_crypt_private_password (so disabled) >>> - send an initial email to let the users mailbox be created and generate the keys >>> - set the users password with doveadm >>> - restart dovecot again with mail_crypt_private_password (so enabled) >>> >>> but this would be disruptive to existing users, and i would have to script the whole thing as a >>> "add-new-user" script to make it usable i guess. >>> >>> do you know of a more easy way of acomplishing this? >>> could i use doveadm for all steps, and get around the mail_crypt_private_password disable part? >>> >>> or could i add a column in the mysql db called userdb_mail_crypt_private_password and fill that >>> column with %w for users that allready exist, and empty for new users. >>> when being empty, it might not set the mail_crypt_private_password for new users >>> >>> or is this the wrong way of thinking? >>> >>> let me know your thoughts on this. >>> >>> And last but not least, i really want to thank you for all your help. It is a really nice >>> experience. >>> Bless you! >>> >>> Zjemm >>> >>> If you have mail_crypt_private_password set *when* keys are generated, >>> dovecot should use that password to encrypt the user key. >>> >>> Aki >>> Hi Aki, >>> >>> well, if there is a new email user setup in the mysql DB, and no email has been send to that new >>> user. at that point there are no keys. >>> >>> So trying to set a password on those key's wont work. see: >>> root@mailserver1:/var/vmail/example.org# doveadm mailbox cryptokey password -u john2(a)example.org -n >>> qwerty >>> result: Changed password for 0 key(s) >>> >>> the keys need to be generated first. And that only happens when sending a mail to that new user. >>> Also, at the point of creating the keys, the mail_crypt_private_password should be disabled >>> otherwise the keys are generated and also encrypted with no user password, and then im unable to >>> set a new pasword for that key >>> >>> How can i set the password before the keys are generated? >>> or can i manually generate key's and then set the password? >>> >>> so at this point i have to do the following: >>> >>> You can use doveadm mailbox cryptokey generate -u user -U >>> >>> to generate a user key. >>> >>> Aki >>> >>> - create the new user in the mysql DB >>> - start with dovecot not using mail_crypt_private_password (so disabled) >>> - send an initial email to let the users mailbox be created and generate the keys >>> - set the users password with doveadm >>> - restart dovecot again with mail_crypt_private_password (so enabled) >>> can i somehow enable the mail_crypt_private_password per user? >>> because this mysql query always returns: %w >>> and thus allways sets: userdb_mail_crypt_private_password >>> SELECT email as user, password, '%w' AS userdb_mail_crypt_private_password FROM virtual_users; >>> >>> Hi Aki, >>> >>> You are correct >>> >>> doveadm mailbox cryptokey generate -u user -U generates the keys, but i have to first remove: >>> '%w' AS userdb_mail_crypt_private_password >>> from dovecot configuration and restart dovecot. >>> >>> if i don't do that, the keys are generated, but also somehow encrypted using: no >>> password/empty/something else (i don't know) >>> >>> here you can see that happening: >>> >>> root@mailserver1:/var/vmail/example.org# doveadm mailbox cryptokey generate -u john2(a)example.org -U >>> Folder Public ID >>> ✓ <userkey> 53004acf9886f887ca081c83d7392a5aa3fac4b5a20ce013db91a341fb4644c4 >>> root@mailserver1:/var/vmail/example.org# doveadm mailbox cryptokey password -u john2(a)example.org -n >>> qwerty >>> result: dcrypt_key_load_private(53004acf9886f887ca081c83d7392a5aa3fac4b5a20ce013db91a341fb4644c4) >>> failed: password missing >>> >>> it expects an old password wich is never set in my opinion. >>> >>> so the last part of this setup would be to figure out a way to disable '%w' AS >>> userdb_mail_crypt_private_password for new users without manually removing that part from the query >>> and restarting dovecot. As that would mean connection interruption while adding new users >>> >>> if we could add new users to the DB and somehow not give '%w' AS userdb_mail_crypt_private_password >>> for that new user in the query, we can add the password afterward, and then enable '%w' AS >>> userdb_mail_crypt_private_password in the query for this user >>> >>> could we add a column in the user db lets say called: encrypted (yes/no) >>> >>> and then change the existing query: SELECT email as user, password, '%w' AS >>> userdb_mail_crypt_private_password FROM virtual_users; >>> >>> to firrt check if encryption is set to 'yes', if so retrun: >>> SELECT email as user, password, '%w' AS userdb_mail_crypt_private_password FROM virtual_users; >>> >>> if not return: >>> SELECT email as user, password FROM virtual_users; >>> >>> but then in one mysql query so dovecot can work with it >>> >>> ? >>> >>> Hi Aki, >>> >>> would you be willing to respond to my last question i had send to you last week? >>> its this one: >>> ================================== >>> doveadm mailbox cryptokey generate -u user -U generates the keys, but i have to first remove: >>> '%w' AS userdb_mail_crypt_private_password >>> from dovecot configuration and restart dovecot. >>> >>> if i don't do that, the keys are generated, but also somehow encrypted using: no >>> password/empty/something else (i don't know) >>> >>> here you can see that happening: >>> >>> root@mailserver1:/var/vmail/example.org# doveadm mailbox cryptokey generate -u john2(a)example.org -U >>> Folder Public ID >>> ✓ <userkey> 53004acf9886f887ca081c83d7392a5aa3fac4b5a20ce013db91a341fb4644c4 >>> root@mailserver1:/var/vmail/example.org# doveadm mailbox cryptokey password -u john2(a)example.org -n >>> qwerty >>> result: dcrypt_key_load_private(53004acf9886f887ca081c83d7392a5aa3fac4b5a20ce013db91a341fb4644c4) >>> failed: password missing >>> >>> it expects an old password wich is never set in my opinion. >>> >>> could this be a bug? or am i doing it wrong? if needed i could send in a bug report? >>> >>> or might we need to enable the userdb_mail_crypt_private_password "per user" ? >>> >>> so the last part of this setup would be to figure out a way to disable '%w' AS >>> userdb_mail_crypt_private_password for new users without manually removing that part from the query >>> and restarting dovecot. As that would mean connection interruption while adding new users >>> >>> if we could add new users to the DB and somehow not give '%w' AS userdb_mail_crypt_private_password >>> for that new user in the query, we can add the password afterward, and then enable '%w' AS >>> userdb_mail_crypt_private_password in the query for this user >>> >>> could we add a column in the user db lets say called: encrypted (yes/no) >>> >>> and then change the existing query: SELECT email as user, password, '%w' AS >>> userdb_mail_crypt_private_password FROM virtual_users; >>> >>> to firrt check if encryption is set to 'yes', if so retrun: >>> SELECT email as user, password, '%w' AS userdb_mail_crypt_private_password FROM virtual_users; >>> >>> if not return: >>> SELECT email as user, password FROM virtual_users; >>> >>> but then in one mysql query so dovecot can work with it >>> >>> Please let me know your thougts, after this last thing im done :) >>> also let me know if i can support this project in some way, im willing to contribute >>> >>> Zjemm >> You can select it as userdb_mail_crypt_save_version=0 to disable encryption (it won't disable >> decryption). You can use value '2' for enabling encryption. DO NOT USE 1. >> >> Also I tried the SQL based thing, and if you had EMPTY mail_crypt_private_password, try these to >> change the password. If the one that works is the second one, let me know =) >> >> doveadm mailbox cryptokey password -u testuser -nnewpass -o "" >> >> doveadm mailbox cryptokey password -u testuser -nnewpass -o "yes" >> >> Aki > Hi Aki, > > Thanks for replying > > So if i understand you correctly i could enable encryption per user by using: userdb_mail_crypt_save_version= in the database as an extra column. the column would be called "userdb_mail_crypt_save_version" and the value is "0" or "2" > > if a user has: userdb_mail_crypt_save_version=0, encryption is disabled for that user > if a user has: userdb_mail_crypt_save_version=2, encryption is enabled for that user > > would this also override the setting: mail_crypt_save_version = 2 > in the mailcryp.conf file where that is a global setting? or should i delete it there and only use userdb_mail_crypt_save_version= from the database? > > for the password set command i hve testest some things: > > new user with no keys yet: > doveadm -o plugin/mail_crypt_private_password=password mailbox cryptokey generate -u john2(a)example.org -U > > i can set a password with: > new password: > doveadm mailbox cryptokey password -u john2(a)example.org -n newpass -o password > > > if i do not use new user doveadm: (doveadm -o plugin/mail_crypt_private_password=password mailbox cryptokey generate -u john2(a)example.org -U) > then use this: > doveadm mailbox cryptokey password -u john2(a)example.org -n newpass -o "yes" > > > so yes it is the second one > > Kind regards, > > Zjemm It's unfortunate problem with 2.2 that it defaults empty userdb variables into yes. This has been remedied in 2.3. Unfortunately there is no clean fix to this, they all resort to various levels of trickery. Variables set in passdb/userdb overwrite the ones in plugin {} section. Aki

2 2

Connection statistics per user and IP
by Lefteris Tsintjelis 12 Jul '19

12 Jul '19

Is it possible to enable statistics and keep track of the maximum number of connections per user and also per IP? Lefteris

3 2

Frequent Out of Memory for service(config)
by Root Kev 12 Jul '19

12 Jul '19

Hello Group, We have dovecot deployed as solely a Pop3 service that is used by our applications to pass mail from one application to another internally. We have roughly 4 applications that connect to the Pop3 service every 2 seconds, to check for new messages and pop them for processing if they are present. Depending on the site, we have between 1024-2048MB of memory set for default_vsz_limit. In all systems we see the Out of memory alert several times a day. We previously did not see this at all when running on CentOS6, with less memory. We have tried increasing the memory to the vsz_limit up to 2gb without success. We are running on CentOS 7 servers, running dovecot 2.3.6 (7eab80676) (from the dovecot repo). Can anyone advise any other settings that could be modified in order to correct these out of memory issues? # dovecot -n # 2.3.6 (7eab80676): /etc/dovecot/dovecot.conf # OS: Linux 3.10.0-957.5.1.el7.x86_64 x86_64 CentOS Linux release 7.6.1810 (Core) # Hostname: ****** #<modified for security> auth_cache_size = 10 M auth_verbose = yes default_vsz_limit = 1 G instance_name = Pop3 Mail Service listen = 10.*.*.* #<modified for security> log_path = /var/log/dovecot.log login_greeting = Pop3 Mail Service login_trusted_networks = 10.*.*.* 10.*.*.* 10.*.*.* 10.*.*.* 10.*.*.* #<modified for security> mail_location = maildir:~/Maildir 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 = cache_key=#hidden_use-P_to_show# driver = pam } protocols = pop3 ssl_cert = </etc/pki/dovecot/certs/dovecot.pem ssl_key = # hidden, use -P to show it userdb { driver = passwd } verbose_ssl = yes May 10 06:44:05 config: Fatal: pool_system_malloc(8192): Out of memory May 10 06:44:05 config: Fatal: master: service(config): child 27887 returned error 83 (Out of memory (service config { vsz_limit=1024 MB }, you may need to increase it) - set CORE_OUTOFMEM=1 environment to get core dump) May 10 14:56:31 config: Fatal: pool_system_malloc(8192): Out of memory May 10 14:56:31 config: Fatal: master: service(config): child 2495 returned error 83 (Out of memory (service config { vsz_limit=1024 MB }, you may need to increase it) - set CORE_OUTOFMEM=1 environment to get core dump) May 10 23:09:02 config: Fatal: pool_system_malloc(8192): Out of memory May 10 23:09:02 config: Fatal: master: service(config): child 10581 returned error 83 (Out of memory (service config { vsz_limit=1024 MB }, you may need to increase it) - set CORE_OUTOFMEM=1 environment to get core dump) May 11 10:18:43 config: Fatal: pool_system_malloc(8192): Out of memory May 11 10:18:43 config: Fatal: master: service(config): child 30511 returned error 83 (Out of memory (service config { vsz_limit=1024 MB }, you may need to increase it) - set CORE_OUTOFMEM=1 environment to get core dump) May 11 18:30:59 config: Fatal: pool_system_malloc(1608): Out of memory May 11 18:30:59 config: Fatal: master: service(config): child 12134 returned error 83 (Out of memory (service config { vsz_limit=1024 MB }, you may need to increase it) - set CORE_OUTOFMEM=1 environment to get core dump) May 12 02:57:28 config: Fatal: pool_system_malloc(8192): Out of memory May 12 02:57:28 config: Fatal: master: service(config): child 24940 returned error 83 (Out of memory (service config { vsz_limit=1024 MB }, you may need to increase it) - set CORE_OUTOFMEM=1 environment to get core dump) May 12 11:07:34 config: Fatal: pool_system_malloc(8192): Out of memory May 12 11:07:35 config: Fatal: master: service(config): child 8203 returned error 83 (Out of memory (service config { vsz_limit=1024 MB }, you may need to increase it) - set CORE_OUTOFMEM=1 environment to get core dump) May 12 19:17:52 config: Fatal: pool_system_malloc(8192): Out of memory May 12 19:17:52 config: Fatal: master: service(config): child 14623 returned error 83 (Out of memory (service config { vsz_limit=1024 MB }, you may need to increase it) - set CORE_OUTOFMEM=1 environment to get core dump) May 13 03:26:34 config: Fatal: pool_system_malloc(8192): Out of memory May 13 03:26:35 config: Fatal: master: service(config): child 21479 returned error 83 (Out of memory (service config { vsz_limit=1024 MB }, you may need to increase it) - set CORE_OUTOFMEM=1 environment to get core dump) May 13 11:35:42 config: Fatal: pool_system_malloc(8192): Out of memory May 13 11:35:43 config: Fatal: master: service(config): child 26900 returned error 83 (Out of memory (service config { vsz_limit=1024 MB }, you may need to increase it) - set CORE_OUTOFMEM=1 environment to get core dump) May 13 19:34:26 config: Fatal: pool_system_malloc(8192): Out of memory May 13 19:34:26 config: Fatal: master: service(config): child 32187 returned error 83 (Out of memory (service config { vsz_limit=1024 MB }, you may need to increase it) - set CORE_OUTOFMEM=1 environment to get core dump). Thanks, Kevin

4 6

Re: Segfault of doveconf
by Claudio Prono 11 Jul '19

11 Jul '19

On 9.7.2019 13.40, Aki Tuomi via dovecot wrote: On 9.7.2019 12.54, Claudio Prono wrote: On 4.7.2019 19.00, Claudio Prono via dovecot wrote: Sorry to bother again, but the problem persist. I have checked all the configurations of dovecot, and seems all ok, but randomly the segfault pops up again, without no apparently reason. My packages are: ii dovecot-core 1:2.2.22-1ubuntu2.10 amd64 secure POP3/IMAP server - core files ii dovecot-imapd 1:2.2.22-1ubuntu2.10 amd64 secure POP3/IMAP server - IMAP daemon ii dovecot-managesieved 1:2.2.22-1ubuntu2.10 amd64 secure POP3/IMAP server - ManageSieve server ii dovecot-mysql 1:2.2.22-1ubuntu2.10 amd64 secure POP3/IMAP server - MySQL support ii dovecot-pop3d 1:2.2.22-1ubuntu2.10 amd64 secure POP3/IMAP server - POP3 daemon ii dovecot-sieve 1:2.2.22-1ubuntu2.10 amd64 secure POP3/IMAP server - Sieve filters support Can be a temporarly solution to uninstall dovecot-managesieved ? Cordially, Claudio. On 5.7.2019 09:59 Aki via dovecot wrote: You should install dovecot-dbg, and follow https://www.dovecot.org/bugreport-mail, then we could figure out why it's crashing in the first place. Aki I have followed the instructions to debug the problem, and I have uploaded the crash log at this location: https://justpaste.it/5wlot Yesterday the system have got some I/O Errors on the hard disk (virtual system hosted from Seeweb). The problems on the disk now are solved by the provider, and the crash reported is before that. So, now my question is: the doveconf crash can be linked to the hardware problem ? Or something else? Thanks for your help. Cordially, Claudio Prono. I tried unpacking the crash file you pastebin, can you please send it as attachment to me? Aki It seems you are at least missing postmaster_address in your config. I was not able to actually make dovecot crash when I tested, so can you try adding this setting and see if it helps? Aki On 9.7.2019 09:59 Claudio Prono via dovecot wrote: I have added it to the configuration, and restarted dovecot. Now I wait and see if this error again. Thank you for your time. Cheers, Claudio. ---- Just a rapid update, the problem of the segmentation fault of doveconf was not occourred again in the past two days. I think the problem was somehow related to the hardware failure on the virtual disk where the system is hosted. Now, the hardware problem is resolved from the virtual system maintainer, and doveconf has stopped to crash. Anyway, thanks for the support. Claudio.

1 0

Dovecot 2.3.6 on Solaris10: build issues, segfaults
by Joseph Tam 11 Jul '19

11 Jul '19

Hopefully, there is some fix for issue 3 which is beyond my skill to fix. Issue 1) Need recent gcc version Building Dovecot versions <=2.2.x using gcc 3.4.4 worked, but this gcc version fails to build 2.3.x properly: symptoms include compile failures and executable crashes that depended on the amount of optimization used, which is usually a sign of compiler bugs. (It could also be issue 3 in disguise.) Either way, I updated to gcc 9.1.0. Issue 2) Cannot build with --enable-hardening Using gcc 9.1.0, "configure" step fails because fd passing was broken, but the real problem was a compilation failure when "--enable-hardening" is used. Demonstration: # echo 'int main(){char a[1]; strcpy(a,a);} ' | gcc -w -fstack-protector-strong -x c - Undefined first referenced symbol in file __stack_chk_guard /var/tmp//cc12L9zV.o (symbol scope specifies local binding) ld: fatal: symbol referencing errors. No output written to a.out collect2: error: ld returned 1 exit status I'm not sure if this is a Solaris10 fumble, but configuring "--disable-hardening" removes the "-fstack-protector-strong" compiler option, which resolves this issue. Issue 3) dovecot/doveconf segfaults on startup It crashes here while processing dovecot.conf, as does "doveconf" (settings-parser.c:1519 in setting_copy()) *dest_size = *src_size; It appears *src_size is not an 8-byte address aligned (0x5597c). It inherits this value from the calling routine as the sum of "set" (8-byte aligned) + "def->offset"=20 => misaligned address. (settings-parser.c:1597 in settings_dup_full()) src = CONST_PTR_OFFSET(set, def->offset); (gdb) p set $2 = (const void *) 0x55968 (gdb) p *def $3 = {type = SET_SIZE, key = 0x2d548 "submission_max_mail_size", offset = 20, list_info = 0x0} (gdb) bt full #0 0xff190690 in setting_copy (type=SET_SIZE, src=0x5798c, dest=0xf7ed4, pool=0xf29a0, keep_values=false) at settings-parser.c:1519 src_size = 0x5798c dest_size = 0xf7ed4 __func__ = "setting_copy" #1 0xff190bc4 in settings_dup_full (info=0x2d9ac <submission_setting_parser_info>, set=0x57978, pool=0xf29a0, keep_values=false) at settings-parser.c:1600 def = 0x2d7d4 <submission_setting_defines+80> src = 0x5798c dest_set = 0xf7ec0 dest = 0xf7ed4 children = 0x2c i = 1105688 count = 4279837964 #2 0xff192724 in settings_parser_dup (old_ctx=0x9ec08, new_pool=0xf29a0) at settings-parser.c:1946 new_ctx = 0x10def0 iter = 0x0 links = {_table = 0xa23c0, _key = 0xa23c0, _keyp = 0xa23c0, _const_key = 0xa23c0, _value = 0xa23c0, _valuep = 0xa23c0} new_link = 0x10b488 value = 0x0 key = 0x0 i = 0 parser_pool = 0x10ded8 keep_values = false __func__ = "settings_parser_dup" #3 0x0001fc0c in config_filter_parsers_get (ctx=0x657a8, pool=0xf29a0, modules=0x0, filter=0x583e8, parsers_r=0xffbff9c4, output_r=0xffbff9bc, error_r=0xffbffa44) at config-filter.c:372 src = 0xf29d8 dest = 0xf2a48 error = 0x0 error_p = 0x52cfc i = 26 count = 33 __func__ = "config_filter_parsers_get" #4 0x00021be4 in config_all_parsers_check (ctx=0xffbffac8, new_filter=0x657a8, error_r=0xffbffa44) at config-parser.c:441 parsers = 0x58180 tmp_parsers = 0x4 output = {specific_services = 0xf2a20, service_uses_local = false, service_uses_remote = false, used_local = false, used_remote = false, permission_denied = false} i = 0 count = 3 ssl_set = 0x4 <error: Cannot access memory at address 0x4> global_ssl_set = 0x32188 "" tmp_pool = 0xf29a0 ssl_warned = false ret = 0 __func__ = "config_all_parsers_check" #5 0x00022ec8 in config_parse_finish (ctx=0xffbffac8, error_r=0xffbffb98) at config-parser.c:747 new_filter = 0x657a8 error = 0x33c22 "/user=%s" ret = 0 #6 0x00024230 in config_parse_file (path=0x50468 "/local/dovecot/etc/dovecot/dovecot.conf", expand_values=false, modules=0x0, error_r=0xffbffb98) at config-parser.c:1064 root = {prev = 0x0, input = 0x0, path = 0x50468 "/local/dovecot/etc/dovecot/dovecot.conf", linenum = 400} ctx = {pool = 0x52b58, path = 0x50468 "/local/dovecot/etc/dovecot/dovecot.conf", , all_parsers = {arr = {buffer = 0x58160, element_size = 4}, v = 0x58160, v_modifiable = 0x58160}, root_parsers = 0x52b70, cur_section = 0x58388, cur_input = 0x0, str = 0x58458, pathlen = 0, section_counter = 6, error = 0x0, old = 0x58580, seen_settings = {_table = 0x0, _key = 0x0, _keyp = 0x0, _const_key = 0x0, _value = 0x0, _valuep = 0x0}, filter = 0x0, expand_values = false, hide_errors = false} i = 33 count = 33 key = 0x0 value = 0x0 full_line = 0x0 type = CONFIG_LINE_TYPE_SKIP line = 0x0 fd = -1 ret = 0 handled = false #7 0x000188dc in main (argc=1, argv=0xffbffc94) at doveconf.c:979 master_service_flags = (MASTER_SERVICE_FLAG_STANDALONE | MASTER_SERVICE_FLAG_NO_INIT_DATASTACK_FRAME | MASTER_SERVICE_FLAG_DONT_SEND_STATS) scope = CONFIG_DUMP_SCOPE_ALL orig_config_path = 0x46300 "/local/dovecot/etc/dovecot/dovecot.conf" config_path = 0x50468 "/local/dovecot/etc/dovecot/dovecot.conf" module = 0x1c00 <error: Cannot access memory at address 0x1c00> module_names = {arr = {buffer = 0x46338, element_size = 4}, v = 0x46338, v_modifiable = 0x46338} filter = {service = 0x0, local_name = 0x0, local_host = 0x0, remote_host = 0x0, local_net = {family = 0, u = {ip6 = {_S6_un = {_S6_u8 = '\000' <repeats 15 times>, _S6_u32 = {0, 0, 0, 0}, __S6_align = 0}}, ip4 = {S_un = {S_un_b = { s_b1 = 0 '\000', s_b2 = 0 '\000', s_b3 = 0 '\000', s_b4 = 0 '\000'}, S_un_w = { s_w1 = 0, s_w2 = 0}, S_addr = 0}}}}, remote_net = {family = 0, u = {ip6 = { _S6_un = {_S6_u8 = '\000' <repeats 15 times>, _S6_u32 = {0, 0, 0, 0}, __S6_align = 0}}, ip4 = {S_un = {S_un_b = {s_b1 = 0 '\000', s_b2 = 0 '\000', s_b3 = 0 '\000', s_b4 = 0 '\000'}, S_un_w = {s_w1 = 0, s_w2 = 0}, S_addr = 0}}}}, local_bits = 0, remote_bits = 0} wanted_modules = 0x0 error = 0xfef47940 <_uberdata> "" exec_args = 0x0 setting_name_filters = 0x0 i = 5 c = -1 ret = -4195172 ret2 = 4 config_path_specified = false expand_vars = false hide_key = false parse_full_config = false simple_output = false dump_defaults = false host_verify = false print_plugin_banner = true hide_passwords = true Joseph Tam <jtam.home(a)gmail.com>

4 6

Dovecot behind Load Balancer
by Paolo Daniele 10 Jul '19

10 Jul '19

Hi, i've a question for you. I've two dovecot imap/pop server behind a zen load balancer. Load balancing is made by lx4nat so the public ip address of my load balancer contact directly the dovecot servers. Since few months i've a message from thunderbird that i've reached the imap limit login for ip. I've triend to increase the max user ip parameter but sometimes i've the same problem. It's a strange things that actually i'm able to mitigate by reduce the number of cached connections in Thunderbird but it's not normal. What do you think about that? Maybe there's some tuning that you can suggest. Thank you, Paolo

5 10

solr
by Maciej Milaszewski IQ PL 10 Jul '19

10 Jul '19

Hi I have set up SOLR in accordance with documentation and it runs well. I use solr like: ....... fts = solr fts_solr = debug url=http://IP:8983/solr/ (solr in external machine) ...... Is replication of this system really essential ?? Due to my tests, rollback of the solr server on external machine lasts less than minute and it is nearly non-visible from client side. On the other hand solr replication is quite complicated process and rollback or master-slave switch in this case is non-trivial task, that may have result in whole dataset inconsistency. Do you have any experience in such cases ? Maby load-balance in HAProxy colud do the thing ? Something like: ......... server search1 192.168.1.1:8983 check port 8983 inter 20s fastinter 2 server search2 192.168.1.2:8983 backup ......... Best Regards

2 1

Some questions
by Jérôme Bardot 10 Jul '19

10 Jul '19

Hello, This is my first email here. I want to understand well how dovecot is integrate with ldap in a postfix/dovecot/ldap setup. I use a debian server. More specifically what dovecot need in ldap to work. I saw we can use several "mode" related to virtual domain, etc. For "start" i only need one domain with several address. I currently use fusiondirectory for manage my ldap users. i guess i can use that schema to auto create users email (name.firstname(a)domain.tld for ie) ? I also want to setup some aliases and share directory based on ldap group/role can i do it ? An other question is can we have two domain name for imap.domain.tld && smtp.domain.tld ? IF some questions are out of topic let me know. thx jerome

4 3

Re: Applying Dovecot for a large / deep folder-hierarchy archive - BUG REPORTS!
by Arnold Opio Oree 10 Jul '19

10 Jul '19

Hello Timo, I have scheduled some time to carry through the test requested by Aki. I will add responding to you as part of that process. Not sure if I have said or done anything to offend you, as your tone appears quite abrasive, even where you do not have an actual response to an observation. It is my view that it is a privilege to provide an open source platform, and therefore a responsibility wherever feasible not only to properly maintain and support it, but also to properly document it; both of which from my experience and findings to date, Dovecot have failed to do. Kind regards, Arnold Opio Oree Chief Executive Officer Parallax Digital Technologies arnoldoree(a)parallaxdt.com http://www.parallaxdt.com tel : +44 (0) 333 577 8587 fax : +44 (0) 20 8711 2477 Parallax Digital Technologies is a trading name of Parallax Global Limited. U.K. Co. No. 08836288 The contents of this e-mail are confidential. If you are not the intended recipient you are to delete this e-mail immediately, disregard its contents and disclose them to no other persons. -----Original Message----- From: Timo Sirainen via dovecot <dovecot(a)dovecot.org> Reply-To: Timo Sirainen <timo(a)sirainen.com> To: Arnold Opio Oree <arnold.oree(a)parallaxict.com> Cc: Dovecot Mailing List <dovecot(a)dovecot.org> Subject: Re: Applying Dovecot for a large / deep folder-hierarchy archive - BUG REPORTS! Date: Wed, 10 Jul 2019 11:09:57 +0300 On 7 Jul 2019, at 18.12, Arnold Opio Oree via dovecot < dovecot(a)dovecot.org> wrote: > > Dovecot Team, > > > > I'd like to report a number of bugs, that are to my view all > > critical. It would help to get your doveconf -n, example command lines causing the problems and the error messages it outputs or what the wrong behavior looks like in filesystem. It's now rather difficult to guess what exactly you tried and what happened. Also what kind of output does readpst make? I'm not sure why you're using DIRNAMEs here. > > doveadm-sync -1/general > > > > 1) If DIRNAMEs are not different between command line and > > mail_location doveadm sync will fail, saying that the source and > > destination directories are the same This sounds very strange. I'm not sure what exactly you did, and I couldn't reproduce with a small test. > > 2) The -n / -N flags do not work, and a sync will fail strangely if > > location is specified in the namespace definition Again, sounds strange. > > 3) Adds mbox to path name under mailbox directory (where syncing > from > > an mbox source) Probably with different parameters you could avoid it. > > 4) Not having the mailboxes at source named the same as those at > > destination causes errors and partial sync > > > > 5) Not having the target mailboxes formatted to receive the sync > > (/<mailboxroot>/DIRNAME/) will cause sync errors. I don't understand these. Target mailboxes are supposed to be empty initially, and after the initial sync they should be in the expected format. Why would they be different? > > doveadm-sync > > > > 1) With large synchronizations UIDs are corrupted where multiple > > syncs are executed and the program can no longer synchronize What exactly is the error message? > > dovecot > > > > 1) Panics and fails to expand ~ to user home: observed cases are > > where multiple namespaces are being used Panic message and more details would also help. > > With regards to the last error that I requested help on i.e. > > \Noselect. This has been resolved more-or-less by the workarounds > > that I have implemented for the bugs reported above. > > > > I have seen a number of threads whilst researching the \Noselect > > issue where people have been very confused. My finding was that > > \Noselect is a function of the IMAP specification server-side > > implementation RFC3501 ( > > https://tools.ietf.org/html/rfc3501#section-6.3.6) And for me the > > server was returning directories with \Noselect because the > mailboxes > > were malformed on account of dovadm-sync errors. In order to fix > this > > I formed a bash command to transverse the mailbox hierarchy and > > create the missing folders critical to the sdbox format, namely > > DIRNAME. Nowadays we have also an option to disable creation of \Noselect folders, because they confuse people. Using mail_location = ...:NO- NOSELECT - It won't affect existing folders immediately though. -----Original Message----- From: Arnold Opio Oree <arnoldoree(a)parallaxict.com> Reply-To: arnoldoree(a)parallaxict.com To: Aki Tuomi <aki.tuomi(a)open-xchange.com>, Dovecot Mailing List < dovecot(a)dovecot.org> Cc: debian-release(a)lists.debian.org Subject: Re: Applying Dovecot for a large / deep folder-hierarchy archive - BUG REPORTS! Date: Mon, 08 Jul 2019 13:21:51 +0100 Hello Aki, Thanks for looking into these. I will as requested attempt the relevant procedures under Dovecot 2.3.6. To make the test fair, I will need to fork the relevant production groupware stack (which is now stable and in operation, with our enterprise (email) data successfully migrated from Microsoft Exchange) to a new staging server; given that the current staging server is now of a materially different configuration to the production server (where the most controlled observations of these bugs were made). Kindly give me some time, as I have an urgent internal openstack deployment project to kick-off, that has been delayed by an overrun of this internal groupware stack deployment project. Best regards, Arnold Opio Oree Chief Executive Officer Parallax Digital Technologies arnoldoree(a)parallaxdt.com http://www.parallaxdt.com tel : +44 (0) 333 577 8587 fax : +44 (0) 20 8711 2477 Parallax Digital Technologies is a trading name of Parallax Global Limited. U.K. Co. No. 08836288 The contents of this e-mail are confidential. If you are not the intended recipient you are to delete this e-mail immediately, disregard its contents and disclose them to no other persons. -----Original Message----- From: Aki Tuomi via dovecot < dovecot(a)dovecot.org > Reply-To: Aki Tuomi < aki.tuomi(a)open-xchange.com > To: arnoldoree(a)parallaxict.com , Arnold Opio Oree < arnold.oree(a)parallaxict.com >, Arnold Opio Oree via dovecot < dovecot(a)dovecot.org > Cc: debian-release(a)lists.debian.org Subject: Re: Applying Dovecot for a large / deep folder-hierarchy archive - BUG REPORTS! Date: Mon, 8 Jul 2019 08:48:08 +0300 (EEST) Hi! Thank you for reporting these. We will look into them. In the mean time, can you see if any of these are fixed in 2.3.6? Aki > On 07/07/2019 18:12 Arnold Opio Oree via dovecot < > dovecot(a)dovecot.org > > > wrote: > > > Dovecot Team, > > I'd like to report a number of bugs, that are to my view all > critical. > > System: Replicated on multiple Debian 10 (Buster) systems > Dovecot Version(s): 2.3.4.1 > > doveadm-sync -1/general > > 1) If DIRNAMEs are not different between command line and > mail_location doveadm sync will fail, saying that the source and > destination directories are the same > > 2) The -n / -N flags do not work, and a sync will fail strangely if > location is specified in the namespace definition > > 3) Adds mbox to path name under mailbox directory (where syncing from > an mbox source) > > 4) Not having the mailboxes at source named the same as those at > destination causes errors and partial sync > > 5) Not having the target mailboxes formatted to receive the sync > (/<mailboxroot>/DIRNAME/) will cause sync errors. > > doveadm-sync > > 1) With large synchronizations UIDs are corrupted where multiple > syncs are executed and the program can no longer synchronize > > dovecot > > 1) Panics and fails to expand ~ to user home: observed cases are > where multiple namespaces are being used > > Please let me know if you need me to elaborate or to provide any > further information that you may need to replicate the bugs, or if I > can help in any other way. > > With regards to the last error that I requested help on i.e. > \Noselect. This has been resolved more-or-less by the workarounds > that I have implemented for the bugs reported above. > > I have seen a number of threads whilst researching the \Noselect > issue where people have been very confused. My finding was that > \Noselect is a function of the IMAP specification server-side > implementation RFC3501 ( > https://tools.ietf.org/html/rfc3501#section-6.3.6 > ). And for me the > server was returning directories with \Noselect because the mailboxes > were malformed on account of dovadm-sync errors. In order to fix this > I formed a bash command to transverse the mailbox hierarchy and > create the missing folders critical to the sdbox format, namely > DIRNAME. > > Kind regards, > > Arnold Opio Oree > Chief Executive Officer > Parallax Digital Technologies > > arnoldoree(a)parallaxdt.com > > > http://www.parallaxdt.com > > > tel : +44 (0) 333 577 8587 > fax : +44 (0) 20 8711 2477 > > Parallax Digital Technologies is a trading name of Parallax Global > Limited. U.K. Co. No. 08836288 > > The contents of this e-mail are confidential. If you are not the > intended recipient you are to delete this e-mail immediately, > disregard its contents and disclose them to no other persons. > > -----Original Message----- > From: Arnold Opio Oree via dovecot < > dovecot(a)dovecot.org > > > Reply-To: > arnoldoree(a)parallaxict.com > , Arnold Opio Oree < > arnold.oree(a)parallaxict.com > > > To: > dovecot(a)dovecot.org > > Cc: > rs(a)sys4.de > , > aki.tuomi(a)open-xchange.com > > Subject: Re: Applying Dovecot for a large / deep folder-hierarchy > archive. > Date: Thu, 04 Jul 2019 14:52:28 +0100 > > > Hi all, > > The guidance provided so far has been really helpful, and has helped > a great deal to bringing down wasted energy on finding and executing > a viable path. I am now at the final due action to complete our > Dovecot application to our use-case, but am stuck on an issue that I > cannot find any easily accessible documentation on. > > Generally this is what has been done: > > 1. Uploaded the enterprise data PST to the target groupware server. > 2. Prepared the server by changing the mailbox format to sdbox and > the the Dovecot mail location to > mail_location=/var/vmail/domain/user/mail/ > 3. Converted the pst (on-server) to a recursive mbox hierarchy using > readpst > 4. Executed doveadm-sync to convert mbox hierarchy data into sdbox > and to copy it into the enterprise archive user's mailboxes > 4.i. The biggest issue I faced at this point was doveadm-sync saying > that the source and destination pointed to the same location, whereas > they clearly did not. > 4.i.a. I resolved this by removing the location= setting from the > target namespace, and allowing it to default to mail_location = > setting, and then using a completely different DIRNAME for the import > doveadm-sync execution (which was the desired final DIRNAME); I then > once the sync had been successful, changed the mail_location DIRNAME > so that it pointed to the imported mail DIRNAME; and hence the > imported email data was in the live mailboxes > 4.i.b. doveadm-import failed several times, and was throwing quite > inexplicable errors, so I moved onto doveadm-sync > 4.i.c. I also had to make sure that the source and destination folder > names matched, otherwise doveadm-syc threw very many errors and only > partially imported the data > 4.i.d. An issue which I decided just to live with is that an mbox > DIRNAME was added to each mailbox as well as the DIRNAME specified so > the path to mail is mbox/dbox-Mails. My thought is that with the data > live on an IMAP server it will be possible to do a dysync through TCP > to correct this problem. > > The final issue that I am facing now, is that when readpst finds > empty folders in the source pst hierarchy, it does not create an mbox > file in the mbox hierarchy folder space. This causes doveadm-sync to > not create the target data required for its mailbox structure i.e. > DIRNAME sub-folder and index file (with our configuration). At this > point either doveadm-sync or the dovecot process makes these empty > folders not selectable. > > The question now is how would I go about making all of these folders > selectable, e.g. with an internal or external command line tool to > change flags / create necessary sdbox mailbox constituent data? > > Many thanks, > > Arnold Opio Oree > Chief Executive Officer > Parallax Digital Technologies > > arnoldoree(a)parallaxdt.com > > > http://www.parallaxdt.com > > > tel : +44 (0) 333 577 8587 > fax : +44 (0) 20 8711 2477 > > Parallax Digital Technologies is a trading name of Parallax Global > Limited. U.K. Co. No. 08836288 > > The contents of this e-mail are confidential. If you are not the > intended recipient you are to delete this e-mail immediately, > disregard its contents and disclose them to no other persons. > > -----Original Message----- > From: Arnold Opio Oree via dovecot < > dovecot(a)dovecot.org > > > Reply-To: > arnoldoree(a)parallaxict.com > , Arnold Opio Oree < > arnold.oree(a)parallaxict.com > > > To: Robert Schetterer < > rs(a)sys4.de > >, > dovecot(a)dovecot.org > > Subject: Re: Applying Dovecot for a large / deep folder-hierarchy > archive. > Date: Thu, 27 Jun 2019 12:05:35 +0100 > > > Also you may run into client limits.... i ve seen this with > > outlook, > > apple mail, thunderbird via imap in the past > > Thanks for this note Robert, it was not really an aspect that I was > considering. > > We are operating our groupware services user access through both > Evolution Groupware and KDE Kontact / KMail on Debian Linux > workstations. Hopefully if there is a client issue it should be local > to only one groupware client. > > I will be sure to study / investigate in this - client - area should > any issues that are not traceable to the server-side arise. > > Many thanks, > > Arnold Opio Oree > Chief Executive Officer > Parallax Digital Technologies > > arnoldoree(a)parallaxdt.com > > > > http://www.parallaxdt.com > > > > tel : +44 (0) 333 577 8587 > fax : +44 (0) 20 8711 2477 > > Parallax Digital Technologies is a trading name of Parallax Global > Limited. U.K. Co. No. 08836288 > > The contents of this e-mail are confidential. If you are not the > intended recipient you are to delete this e-mail immediately, > disregard > its contents and disclose them to no other persons. > > > -----Original Message----- > From: Robert Schetterer via dovecot < > dovecot(a)dovecot.org > > > Reply-To: Robert Schetterer < > rs(a)sys4.de > > > To: > dovecot(a)dovecot.org > > > Subject: Re: Applying Dovecot for a large / deep folder-hierarchy > archive. > Date: Thu, 27 Jun 2019 12:53:49 +0200 > > Am 27.06.2019 um 07:35 schrieb Aki Tuomi via dovecot: > > On 26.6.2019 22.12, Arnold Opio Oree via dovecot wrote: > > > Hello to you all, > > > > > > I'd like to ask about my intended application of Dovecot to > > > create > > > a folder-hierarchy for storing our enterprise emails, which are > > > treated as live data rather than archives for compliance or > > > occasional / reactive retrieval. > > > > > > The data is presently not that large (a few gigabytes), but it is > > > expected to grow rapidly. Up to this stage the data has been > > > contained > > > in a Microsoft Exchange mailbox (2013), and then in an offline > > > PST. > > > The move to the offline PST was by necessity, as the large number > > > of > > > folders, and depth of hierarchy to my best understanding caused > > > the > > > exchange server / outlook / evolution mail clients to begin to > > > malfunction. To cope with this the archive was broken up and the > > > bulk stored in the offline PST and the most active components > > > stored in > > > online Exchange mailboxes. > > > > > > I have some understanding of the fs mbox format, and also the > > > mitigations to be made for certain characters / strings. My main > > > concern is whether Dovecot is likely to be able to cope well with > > > a > > > large number of folders / depth of hierarcy. > > > > > > I will really appreciate any help / advice you can give. > > > > > > Best regards, > > > > > > Arnold Opio Oree > > > > > > > Hi! > > > > Dovecot 2.2.34/2.3 supports unlimited folder depth, the only > > limiting > > factor is that the total name may not exceed 4096 bytes. Also > > individual > > folder names may not exceed 255 bytes. > > > > Prior to that the limit is 255 per folder up to 16 levels. > > > > I can't recommend using 'mbox' storage format, please consider > > using > > maildir or sdbox instead. > > > > Aki > > > > > > > > > > --- Aki Tuomi

2 2

Re: Applying Dovecot for a large / deep folder-hierarchy archive - BUG REPORTS!
by Adam D. Barratt 10 Jul '19

10 Jul '19

On 2019-07-10 12:01, Arnold Opio Oree wrote: Please stop CCing this thread to the Debian Release Management mailing list. If there are issues with the Dovecot packages in Debian then they should be reported as bugs against the packages. Thanks. Adam (Debian Release Team member)

2 1

Error: last_login_dict: Failed to write value: dict-server returned failure: sql dict: commit failed: Field 'password' doesn't have a default value
by Lefteris Tsintjelis 10 Jul '19

10 Jul '19

Hi, after upgrading my database I kept on getting those errors. It seems like later versions of databases have strict mode enabled by default and it must either be disabled or change the dovecot database schema. Besides the password, would anyone know what other fields must be changed to the dovecot schema and have a default value? Is there any other dovecot schema for strict mode? Lefteris

1 0

Applying Dovecot for a large / deep folder-hierarchy archive.
by Arnold Opio Oree 10 Jul '19

10 Jul '19

Hello to you all, I'd like to ask about my intended application of Dovecot to create a folder-hierarchy for storing our enterprise emails, which are treated as live data rather than archives for compliance or occasional / reactive retrieval. The data is presently not that large (a few gigabytes), but it is expected to grow rapidly. Up to this stage the data has been containedin a Microsoft Exchange mailbox (2013), and then in an offline PST. The move to the offline PST was by necessity, as the large number offolders, and depth of hierarchy to my best understanding caused the exchange server / outlook / evolution mail clients to begin tomalfunction. To cope with this the archive was broken up and the bulk stored in the offline PST and the most active components stored inonline Exchange mailboxes. I have some understanding of the fs mbox format, and also the mitigations to be made for certain characters / strings. My main concern is whether Dovecot is likely to be able to cope well with a large number of folders / depth of hierarcy. I will really appreciate any help / advice you can give. Best regards, Arnold Opio OreeChief Executive OfficerParallax Digital Technologies arnoldoree(a)parallaxdt.com http://www.parallaxdt.com tel : +44 (0) 333 577 8587fax : +44 (0) 20 8711 2477 Parallax Digital Technologies78A Hatfeild MeadLondonSM4 5PF Parallax Digital Technologies is a trading name of Parallax GlobalLimited. U.K. Co. No. 08836288 The contents of this e-mail are confidential. If you are not theintended recipient you are to delete this e-mail immediately, disregardits contents and disclose them to no other persons.

5 11

10-ssl.conf
by Nicholas Chua 10 Jul '19

10 Jul '19

Hi, I am having an error, doveconf: Fatal: Error in configuration file /usr/local/dovecot/etc/dovecot/conf.d/10-ssl.conf line 6: Unknown setting: service { ssl I am on dovecot 2.3.6. My 10-ssl.conf as follows https://pastebin.com/sYXsmm5b Any idea what went wrong? Thanks nic

2 1

Segfault of doveconf
by Claudio Prono 09 Jul '19

09 Jul '19

Hi, I have some problems of segfault at doveconf: Jul 2 08:13:16 mail kernel: [1415540.297823] doveconf[7103]: segfault at 560cb801e000 ip 00007f861da742d0 sp 00007ffe2d671548 error 6 in libc-2.23.so[7f861d9e5000+1c0000] Jul 2 15:45:38 mail kernel: [1442682.919193] doveconf[11915]: segfault at 563b32420000 ip 00007fcb127ae2d0 sp 00007ffecfc7b598 error 6 in libc-2.23.so[7fcb1271f000+1c0000] Jul 2 20:27:37 mail kernel: [1459601.781407] doveconf[14680]: segfault at 55618f01b000 ip 00007f44137202d0 sp 00007ffcbb8d8628 error 6 in libc-2.23.so[7f4413691000+1c0000] Jul 2 21:35:36 mail kernel: [1463680.435538] doveconf[15090]: segfault at 55ea7521d000 ip 00007f0bfe79f2d0 sp 00007ffd272793b8 error 6 in libc-2.23.so[7f0bfe710000+1c0000] Jul 3 00:44:28 mail kernel: [1475013.132492] doveconf[16253]: segfault at 561feea20000 ip 00007f34be2be2d0 sp 00007ffe731ef4b8 error 6 in libc-2.23.so[7f34be22f000+1c0000] System configuration follows: lsb_release -d Description: Ubuntu 16.04.6 LTS doveconf -n # 2.2.22 (fe789d2): /etc/dovecot/dovecot.conf # Pigeonhole version 0.4.13 (7b14904) # OS: Linux 4.4.0-45-generic x86_64 Ubuntu 16.04.6 LTS disable_plaintext_auth = no first_valid_gid = 8 first_valid_uid = 150 last_valid_gid = 8 last_valid_uid = 150 mail_location = mbox:~/mail:INBOX=/var/mail/%u 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 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 = INBOX. } passdb { args = /etc/dovecot/dovecot-sql.conf.ext driver = sql } plugin { quota_warning = storage=95%% quota-warning 95 %u quota_warning2 = storage=80%% quota-warning 80 %u sieve = /var/vmail/%d/%u/.dovecot.sieve sieve_dir = /var/vmail/%d/%u/sieve sieve_global_dir = /var/lib/dovecot/sieve/ sieve_storage = /var/vmail/%d/%u/sieve } protocols = " imap sieve pop3" service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0660 user = postfix } unix_listener auth-userdb { group = mail mode = 0600 user = vmail } } service quota-warning { executable = script /usr/bin/quota-warning.sh unix_listener quota-warning { user = vmail } user = dovecot } ssl_ca = </etc/ssl/certs/SecureTrust_CA_mauri2.pem ssl_cert = </etc/ssl/certs/dovecot6.pem ssl_cipher_list = TLSv1+HIGH:!SSLv2:!RC4:!aNULL:!eNULL:!3DES:!IDEA:!SEED ssl_key = </etc/ssl/private/dovecot3.pem ssl_prefer_server_ciphers = yes userdb { args = /etc/dovecot/dovecot-sql.conf.ext driver = sql } protocol lda { mail_plugins = " sieve" } protocol pop3 { pop3_uidl_format = %Mf } dovecot --version 2.2.22 (fe789d2) apt-get update Hit:1 http://ubuntu.seeweb.it/ubuntu xenial InRelease Hit:2 http://ubuntu.seeweb.it/ubuntu xenial-updates InRelease Hit:3 http://ubuntu.seeweb.it/ubuntu xenial-backports InRelease Get:4 http://ubuntu.seeweb.it/ubuntu-security xenial-security InRelease [109 kB] Fetched 109 kB in 1s (99.1 kB/s) Reading package lists... Done apt-get upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. apt-get dist-upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. Any hint about it ? Sometimes, from my webmail I receive an error communicating with server, but no other errors. Cordially, Claudio Prono. -- ---------------------------------------------------------------------------- Claudio Prono OPST System Developer @Mediaservice.net Srl Tel: +39-011-07.49.338 Via Santorelli, 15 Fax: +39-011-32.46.497 10095 Grugliasco (TO) http://mediaservice.net/disclaimer ITALY ---------------------------------------------------------------------------- PGP Key - http://keys.mediaservice.net/c_prono.asc

2 7

Orphaned processes after doveadm log reopen
by Tom Sommer 09 Jul '19

09 Jul '19

I rotate logs every night on my Director, running "doveadm log reopen" I've noticed a problem with processes not closing correctly, they can be open for days and cause corrupt index files because they are connected to different backends (so it writes to the wrong server when the process disconnects) 23518 ? S 140:53 dovecot/anvil [4 connections] 23519 ? S 444:45 dovecot/log 23520 ? S 497:19 dovecot/imap-login [8 pre-login + 27 proxies] 23531 ? S 0:27 dovecot/config 26201 ? S 551:53 dovecot/imap-login [7 pre-login + 33 proxies] 22126 ? S 960:15 dovecot/pop3-login [28 pre-login + 396 proxies] 59515 ? S 218:32 dovecot/pop3-login [44 pre-login + 468 proxies] Is there any way to force these orphaned processes to terminate after a certain time? -- Tom

2 4

Re: Applying Dovecot for a large / deep folder-hierarchy archive - BUG REPORTS!
by Arnold Opio Oree 07 Jul '19

07 Jul '19

Dovecot Team, I'd like to report a number of bugs, that are to my view all critical. System: Replicated on multiple Debian 10 (Buster) systemsDovecot Version(s): 2.3.4.1 doveadm-sync -1/general 1) If DIRNAMEs are not different between command line and mail_location doveadm sync will fail, saying that the source and destination directories are the same 2) The -n / -N flags do not work, and a sync will fail strangely if location is specified in the namespace definition 3) Adds mbox to path name under mailbox directory (where syncing from an mbox source) 4) Not having the mailboxes at source named the same as those at destination causes errors and partial sync 5) Not having the target mailboxes formatted to receive the sync (/<mailboxroot>/DIRNAME/) will cause sync errors. doveadm-sync 1) With large synchronizations UIDs are corrupted where multiple syncs are executed and the program can no longer synchronize dovecot 1) Panics and fails to expand ~ to user home: observed cases are where multiple namespaces are being used Please let me know if you need me to elaborate or to provide any further information that you may need to replicate the bugs, or if I can help in any other way. With regards to the last error that I requested help on i.e. \Noselect. This has been resolved more-or-less by the workarounds that I have implemented for the bugs reported above. I have seen a number of threads whilst researching the \Noselect issue where people have been very confused. My finding was that \Noselect is a function of the IMAP specification server-side implementation RFC3501 (https://tools.ietf.org/html/rfc3501#section-6.3.6) And for me the server was returning directories with \Noselect because the mailboxes were malformed on account of dovadm-sync errors. In order to fix this I formed a bash command to transverse the mailbox hierarchy and create the missing folders critical to the sdbox format, namely DIRNAME. Kind regards, Arnold Opio Oree -----Original Message-----From: Arnold Opio Oree via dovecot < dovecot(a)dovecot.org>Reply-To: arnoldoree(a)parallaxict.com, Arnold Opio Oree <arnold.oree(a)parallaxict.com>To: dovecot(a)dovecot.orgCc: rs(a)sys4.de , aki.tuomi(a)open-xchange.comSubject: Re: Applying Dovecot for a large / deep folder-hierarchy archive.Date: Thu, 04 Jul 2019 14:52:28 +0100 Hi all, The guidance provided so far has been really helpful, and has helped a great deal to bringing down wasted energy on finding and executing a viable path. I am now at the final due action to complete our Dovecot application to our use-case, but am stuck on an issue that I cannot find any easily accessible documentation on. Generally this is what has been done: 1. Uploaded the enterprise data PST to the target groupware server.2. Prepared the server by changing the mailbox format to sdbox and the the Dovecot mail location to mail_location=/var/vmail/domain/user/mail/3. Converted the pst (on-server) to a recursive mbox hierarchy using readpst4. Executed doveadm-sync to convert mbox hierarchy data into sdbox and to copy it into the enterprise archive user's mailboxes4.i. The biggest issue I faced at this point was doveadm-sync saying that the source and destination pointed to the same location, whereas they clearly did not. 4.i.a. I resolved this by removing the location= setting from the target namespace, and allowing it to default to mail_location = setting, and then using a completely different DIRNAME for the import doveadm-sync execution (which was the desired final DIRNAME); I then once the sync had been successful, changed the mail_location DIRNAME so that it pointed to the imported mail DIRNAME; and hence the imported email data was in the live mailboxes4.i.b. doveadm-import failed several times, and was throwing quite inexplicable errors, so I moved onto doveadm-sync4.i.c. I also had to make sure that the source and destination folder names matched, otherwise doveadm-syc threw very many errors and only partially imported the data4.i.d. An issue which I decided just to live with is that an mbox DIRNAME was added to each mailbox as well as the DIRNAME specified so the path to mail is mbox/dbox-Mails. My thought is that with the data live on an IMAP server it will be possible to do a dysync through TCP to correct this problem. The final issue that I am facing now, is that when readpst finds empty folders in the source pst hierarchy, it does not create an mbox file in the mbox hierarchy folder space. This causes doveadm-sync to not create the target data required for its mailbox structure i.e. DIRNAME sub- folder and index file (with our configuration). At this point either doveadm-sync or the dovecot process makes these empty folders not selectable. The question now is how would I go about making all of these folders selectable, e.g. with an internal or external command line tool to change flags / create necessary sdbox mailbox constituent data? Many thanks, Arnold Opio Oree Chief Executive Officer Parallax Digital Technologies arnoldoree(a)parallaxdt.com http://www.parallaxdt.com tel : +44 (0) 333 577 8587 fax : +44 (0) 20 8711 2477 Parallax Digital Technologies is a trading name of Parallax Global Limited. U.K. Co. No. 08836288 The contents of this e-mail are confidential. If you are not the intended recipient you are to delete this e-mail immediately, disregard its contents and disclose them to no other persons. -----Original Message-----From: Arnold Opio Oree via dovecot < dovecot(a)dovecot.org>Reply-To: arnoldoree(a)parallaxict.com, Arnold Opio Oree <arnold.oree(a)parallaxict.com>To: Robert Schetterer <rs(a)sys4.de>, dovecot(a)dovecot.orgSubject: Re: Applying Dovecot for a large / deep folder-hierarchy archive.Date: Thu, 27 Jun 2019 12:05:35 +0100 > Also you may run into client limits.... i ve seen this with outlook, > apple mail, thunderbird via imap in the past Thanks for this note Robert, it was not really an aspect that I wasconsidering. We are operating our groupware services user access through bothEvolution Groupware and KDE Kontact / KMail on Debian Linuxworkstations. Hopefully if there is a client issue it should be localto only one groupware client. I will be sure to study / investigate in this - client - area should any issues that are not traceable to the server-side arise. Many thanks, Arnold Opio OreeChief Executive OfficerParallax Digital Technologies arnoldoree(a)parallaxdt.com http://www.parallaxdt.com tel : +44 (0) 333 577 8587fax : +44 (0) 20 8711 2477 Parallax Digital Technologies is a trading name of Parallax GlobalLimited. U.K. Co. No. 08836288 The contents of this e-mail are confidential. If you are not theintended recipient you are to delete this e-mail immediately, disregardits contents and disclose them to no other persons. -----Original Message-----From: Robert Schetterer via dovecot < dovecot(a)dovecot.org>Reply-To: Robert Schetterer <rs(a)sys4.de>To: dovecot(a)dovecot.org Subject: Re: Applying Dovecot for a large / deep folder- hierarchyarchive.Date: Thu, 27 Jun 2019 12:53:49 +0200 Am 27.06.2019 um 07:35 schrieb Aki Tuomi via dovecot: > On 26.6.2019 22.12, Arnold Opio Oree via dovecot wrote: > > Hello to you all, > > > > I'd like to ask about my intended application of Dovecot to create > > a folder-hierarchy for storing our enterprise emails, which are > > treated as live data rather than archives for compliance or > > occasional / reactive retrieval. > > > > The data is presently not that large (a few gigabytes), but it is > > expected to grow rapidly. Up to this stage the data has been > > contained > > in a Microsoft Exchange mailbox (2013), and then in an offline PST. > > The move to the offline PST was by necessity, as the large number > > of > > folders, and depth of hierarchy to my best understanding caused the > > exchange server / outlook / evolution mail clients to begin to > > malfunction. To cope with this the archive was broken up and the > > bulk stored in the offline PST and the most active components > > stored in > > online Exchange mailboxes. > > > > I have some understanding of the fs mbox format, and also the > > mitigations to be made for certain characters / strings. My main > > concern is whether Dovecot is likely to be able to cope well with a > > large number of folders / depth of hierarcy. > > > > I will really appreciate any help / advice you can give. > > > > Best regards, > > > > Arnold Opio Oree > > > > Hi! > > Dovecot 2.2.34/2.3 supports unlimited folder depth, the only limiting > factor is that the total name may not exceed 4096 bytes. Also > individual > folder names may not exceed 255 bytes. > > Prior to that the limit is 255 per folder up to 16 levels. > > I can't recommend using 'mbox' storage format, please consider using > maildir or sdbox instead. > > Aki > Chief Executive Officer Parallax Digital Technologies arnoldoree(a)parallaxdt.com http://www.parallaxdt.com tel : +44 (0) 333 577 8587 fax : +44 (0) 20 8711 2477 Parallax Digital Technologies is a trading name of Parallax Global Limited. U.K. Co. No. 08836288 The contents of this e-mail are confidential. If you are not the intended recipient you are to delete this e-mail immediately, disregard its contents and disclose them to no other persons.

1 0

Dovecot 2.3.0 TLS
by Hauke Fath 07 Jul '19

07 Jul '19

All, our dovecot installation provides a bundle of intermedia CA certificates using the ssl_ca option. 2.3.0 does not supply the bundle, resulting in various clients either complaining about an unverifiable server cert, or quietly not connecting. The log has Jan 5 17:01:46 Bounce dovecot: imap-login: Disconnected (no auth attempts in 0 secs): user=<>, rip=XXX, lip=YYY, TLS handshaking: SSL_accept() failed: error:14094416:SSL routines:SSL3_READ_BYTES:sslv3 alert certificate unknown: SSL alert number 46, session=<uKK/kAlia+GCUyU5> We fixed the issue by downgrading to 2.2.33.2. Cheerio, hauke -- The ASCII Ribbon Campaign Hauke Fath () No HTML/RTF in email Institut für Nachrichtentechnik /\ No Word docs in email TU Darmstadt Respect for open standards Ruf +49-6151-16-21344

11 22

Repository / builds for Debian "buster"?
by Kostya Vasilyev 07 Jul '19

07 Jul '19

Speaking of repositories... Debian "buster" (future version 10) has for some time been "stage 1 frozen" (if I have the terminology right) and quite usable. Perhaps it's starting to make sense to make a repo / start producing builds? -- Kostya Vasilyev kman(a)fastmail.com

2 2

Reprocess mail through sieve?
by ＠lbutlr 06 Jul '19

06 Jul '19

is there a way to process a mailbox through an existing sieve script as it the mail was being delivered anew? I’ve cleaned up a lot of my list-sorting scripts and I would like to process a bunch of mail again so it gets sorted properly. If I can do this could I also do it for a specific date range? For example, let’s say io want to reprocess all the messages that are in “Archive” from between 20190501 and 20190630? -- Think of how stupid the average person is, and realize half of them are stupider than that.

2 1

dovecot/imap [blocking on log write]
by alpha_one_x86 06 Jul '19

06 Jul '19

Hi, My dovecot process seam blocked on dovecot/imap [blocking on log write], only restart fix it. How solve that's? Cheers, -- alpha_one_x86/BRULE Herman <alpha_one_x86(a)first-world.info> Main developer of Supercopier/Ultracopier/CatchChallenger, Esourcing and server management IT, OS, technologies, research & development, security and business department

4 4

Dovecot and Solr on the same server or on different
by Götz Reinicke 06 Jul '19

06 Jul '19

Hi. what would you suggest? What are the pros and cons for having dovecot and Solr on the same or different hots? I have about 800 accounts, some millions of mails and about 2 TB of zipped mails. From the recent experiences regarding maintenance I’d prefer different hosts for each. Thanks for suggestions and feedback . Götz

5 12

solr vs fts
by Maciej Milaszewski IQ PL 06 Jul '19

06 Jul '19

Hi I have a question about tunning dovecot-2.2.36.x Mail was stared in storage via nfs in MAILDIR via /home/us/username(a)domain.ltd/MAILDIR/ I use additionally local dovecot_indexes via SSD disk (/var/dovecot_indexes%h) A few clients have 25K and more e-mail I thinking about use solr like: fts = solr fts_solr = debug url=http://IP:8983/solr/ (solr in external machine) Does it make sense ? use dovecot_indexes and fts ? What is the difference in performance?

5 6

Dovecot local_name TLS SNI regex
by basti 05 Jul '19

05 Jul '19

Hello, does local_name in TLS SNI context support regex? for example: local_name example-(foo|bar).com { ssl_cert = </var/lib/dehydrated/certs/example.com/fullchain.pem ssl_key = </var/lib/dehydrated/certs/example.com/privkey.pem } Best regards

2 1

Email encryption and key protection
by Chris Narkiewicz 05 Jul '19

05 Jul '19

I was reading through Dovecot mail-crypt plugin documentation and I'm wondering what is the benefit of turning the encryption on if private and public keys are both stored on the server? What are the benefits and how the key can be protected (apart from file permissions). Cheers, Chris

2 1

Percent character in mail_crypt_private_password not possible
by mabi 04 Jul '19

04 Jul '19

Hello, I am using the mail_crypt plugin with Dovecot 2.3 and have issues trying to use a mail crypt private password which contains a percent "%" character as you can see below: $ doveadm -o plugin/mail_crypt_private_password=SomethingWith\%Percent mailbox cryptokey generate -u email(a)domain.tld -URf doveadm(email(a)domain.tld): Error: Failed to expand plugin setting mail_crypt_private_password = 'SomethingWith%Percent': Unknown variable '%P' Note here that the percent is escaped with a backslash "\%" in order for the shell not to process it. Regards, Mabi

2 11

mail_crypt: multiple keypairs
by mabi 04 Jul '19

04 Jul '19

Hello, I am testing mail_crypt plugin with per account encryption and wanted to generate a new keypair for an account but noticed that I now end up with 2 keypairs where one is active and the other inactive as you can see below: $ doveadm mailbox cryptokey list -u email(a)domain.tld -U Folder Active Public ID yes 7b140b4f3d6d68eed2c59259ac5e6f6a280dc82990292dc415b4100d6c797f67 no 1c1dd1c955757da7c19f1eeb6d6c4d0d66e6355baa2d844bc2623052e1aa2f91 Does this mean now that all existing emails get encrypted with both keypairs? or does this mean only the active keypair is used to encrypt new emails? Is it possible to delete the inactive keypair? if yes how? Regards, Mabi

3 4

fts_lucene
by Ignacio García 04 Jul '19

04 Jul '19

Hi everybody... I've inherited 2 servers with dovecot and fts_lucene enabled, which I plan to switch to fts-solr instead. My plan is to disable lucene in dovecot.conf, delete all cache associated files, and start configuring the fts plugin from scratch. I need to make sure that I don't mess up things pretty bad and delete the correct files. Are those to be deleted all dovecot.index* files located in the Maildir folder? Is there anything else I should be aware of? Thanks so much in advance for your kind help! Ignacio

1 0

dsync not replicatiing .dovecot.sieve
by Laura Smith 04 Jul '19

04 Jul '19

There was a post on this topic to the list Aug 06, 2018 to which Aki replied "Thank you for reporting this, we'll take a look at this.". But its not clear what (if anything) has happened since ? The problem still seems to exist in 2.3.3 (original report by previous poster was for 2.3.2.1) The scenario I'm seeing is pretty much identical to the original poster's. Mail seems to be replicating fine, but sieve doesn't replicate at all.

2 1

Sieve question
by ＠lbutlr 04 Jul '19

04 Jul '19

I have the following in my active sieve file, and there are no errors logged. if header :contains "to" "+root" { setflag "\\Seen"; fileinto :create "root"; stop; } The message is put in .root, bit is not marked as seen. Is the default action to put mail in a folder matching the extension taking precedence?

2 2

mail_replica equivalent to replicator_host/replicator_port
by Laura Smith 03 Jul '19

03 Jul '19

Silly question but regarding https://wiki.dovecot.org/Replication, is the mail_replica parameter shown in the docs equivalent to replicator_host and replicator_port in 2.3.3 ? 2.3.3 doesn't seem to like the mail_replica param (and indeed doveconf -a doesn't show it as an option) Thanks !

2 1

Dovecot LMTP mixing up users on multi-recipient mail
by Bernhard Schmidt 03 Jul '19

03 Jul '19

Hi, I've upgraded a mailstore from Debian Jessie (aka oldstable) with Dovecot 2.2.13 to Debian Buster (next stable) with Dovecot 2.3.4.1 today. It worked pretty well, except that we're seeing error messages very similar to this old thread https://dovecot.org/pipermail/dovecot/2015-July/101396.html It appears to be happening when a mail with multiple recipients on this message store is getting delivered through lmtp. Jun 27 11:47:36 lxmhs74 dovecot: lmtp(user1)<47683><sGwaD7eQFF1DugAAgkzuhA:18>: Error: open(/var/cache/dovecot/index/n/user2n/.INBOX/dovecot.index.cache) failed: Permission denied (euid=3814520(<unknown>) egid=12(man) missing +x perm: /var/cache/dovecot/index/n/user2, dir owned by 3391995:12 mode=0700) user1 uid is 3814520, user2n uid is 3391995. Dovecot appears to be trying to deliver the message to user1 while using the index directory of user2n. Further configuration: - message store is on NFS - cache directory is on local disk - users are coming from LDAP, one UID per user user_attrs = cn=user,homeDirectory=home,uidNumber=uid,gidNumber=gid - index directory is calculated from the username maildir:~/Maildir:INDEX=/var/cache/dovecot/index/%-1.1n/%n Despite the error messages (which appear dozens of times per delivery attempt) delivery seems to work. Workaround was to set lmtp_destination_recipient_limit = 1 on the postfix in front of the message store. Despite the report linked above being quite old, I can't recall having issues with 2.2.13. === doveconf -n === # OS: Linux 4.19.0-5-amd64 x86_64 Debian 10.0 # Hostname: lxmhs74.srv.lrz.de default_vsz_limit = 512 M deliver_log_format = from=<%e>, size=%p, message-id=<%m>, status=%$ imap_id_log = * imap_id_send = * lda_mailbox_autocreate = yes lda_mailbox_autosubscribe = yes login_greeting = Dovecot ready. login_log_format_elements = user=<%u> method=%m rip=%r lip=%l mpid=%e %c session=<%{session}> cipher=<%k> mail_gid = mstore mail_location = maildir:~/Maildir:INDEX=/var/cache/dovecot/index/%-1.1n/%n mail_plugins = quota listescape mail_uid = mstore 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 mmap_disable = yes namespace inbox { inbox = yes location = mailbox Drafts { auto = subscribe special_use = \Drafts } mailbox Junk { auto = subscribe special_use = \Junk } mailbox Sent { auto = subscribe special_use = \Sent } mailbox "Sent Messages" { special_use = \Sent } mailbox Trash { auto = subscribe special_use = \Trash } prefix = INBOX. separator = . type = private } passdb { args = /etc/dovecot/dovecot-ldap.conf driver = ldap } plugin { quota = maildir quota_rule = *:storage=1024M quota_rule2 = INBOX.Trash:ignore quota_status_nouser = DUNNO quota_status_overquota = 452 4.2.2 Mailbox is full quota_status_success = DUNNO quota_warning = storage=95%% quota-warning 95 %u quota_warning2 = storage=90%% quota-warning 90 %u sieve = ~/currently-active-script.sieve sieve_dir = ~/sieve } pop3_uidl_format = %v-%u protocols = imap lmtp sieve pop3 quota_full_tempfail = yes service anvil { client_limit = 3000 unix_listener anvil { group = sudo mode = 0660 } } service auth { client_limit = 3000 unix_listener auth-userdb { group = mstore mode = 0660 user = mstore } } service imap-login { client_limit = 1024 inet_listener imap { port = 143 } inet_listener imaps { port = 993 ssl = yes } process_limit = 2500 process_min_avail = 4 service_count = 0 } service imap { process_limit = 8192 } service lmtp { inet_listener lmtp { port = 24 } } service managesieve-login { inet_listener sieve { port = 4190 } inet_listener sieve_deprecated { port = 2000 } service_count = 1 } service managesieve { process_limit = 1024 } service pop3-login { inet_listener pop3 { port = 110 } inet_listener pop3s { port = 995 ssl = yes } } service quota-status { client_limit = 20 executable = quota-status -p postfix inet_listener { port = 12340 } } service quota-warning { executable = script /etc/dovecot/quotawarnmsg.sh unix_listener quota-warning { group = mstore mode = 0660 user = mstore } user = mstore } service stats { process_limit = 8192 } ssl_cert = </etc/dovecot/dovecot.pem ssl_dh = # hidden, use -P to show it ssl_key = # hidden, use -P to show it userdb { driver = prefetch } userdb { args = /etc/dovecot/dovecot-ldap-userdb.conf driver = ldap } verbose_proctitle = yes protocol imap { mail_plugins = quota listescape imap_quota imap_zlib } protocol lda { mail_plugins = quota listescape sieve } protocol lmtp { mail_plugins = quota listescape sieve } remote 127.0.0.1 { disable_plaintext_auth = no } remote ::1 { disable_plaintext_auth = no } === Thanks, Bernhard

2 1

Replicate shared folders to warm standby host
by Axel Gluth 03 Jul '19

03 Jul '19

We like to set up our mail system in two datacenters but the wiki<https://wiki.dovecot.org/Replication> says "Shared folder replication doesn't work correctly..." I'm thinking about using an external loadbalancer to ensure that only one host will get connections. Normal operations: client ==imap=> loadbalancer ==imap=> host1 ==replication=> host2 Host1 or Datacenter1 is down: client ==imap=> loadbalancer ==imap=> host2 I see possible problems if host1 comes back and clients connect to host1 before the replication has caught up. But in our case that will be acceptable. Do you consider my idea as safe for production use? Has anybody real world experience with such a setup? Is there a better way to replicate shared folders? Thank you in advance for spending your time on thinking about my problem. Axel

1 0

Dovecot/MSQL issue
by Nathan 03 Jul '19

03 Jul '19

Hello, I'm trying to work through an issue that cropped up on a server I've been working on and haven't found a very good workaround. Dovecot is operating in a jailed environment. The configuration in dovecot-sql.conf.ext has been set appropriately with the host=127.0.0.1 (which works from a jailed environment) and when dovecot attempts to auth it appears to perform a reverse dns lookup and overwrites the host with the result localhost before using the msql credentials 'user'@'localhost' which then fails after timing out. I'm currently running version 2.2.33.2 of dovecot. The workaround seems to be to have two credentials for the same user. 'user@'localhost' and 'user'@'127.0.0.1'; postfix operates in a jail as well and works around the jail issue in the same way but doesn't overwrite the specified host with a reverse dns lookup. Anyone have any suggestions on how to handle this issue better? or maybe there's a way to force different behavior which I haven't yet found in the documentation? Any help is much appreciated. Best Regards.

4 5

dovecot.index.log: duplicate transaction log sequence (3)
by mabi 02 Jul '19

02 Jul '19

Hello, I am running Dovecot 2.3.5.1 on OpenBSD 6.5 with RainLoop as IMAP webmail client and just noticed the following error messages about duplicate transaction log sequences in the index log: Jul 01 13:15:58 Error: imap(<REMOVED_EMAIL1>)<21324><TVSmwJyMd0C5D+Vb>: Transaction log /var/vmail/<REMOVED_DOMAIN>/<REMOVED_EMAIL1>/dovecot.index.log: duplicate transaction log sequence (3) Jul 02 16:33:35 Error: imap(<REMOVED_EMAIL2>)<6812><gn4yobOMJlW5D+Vb>: Transaction log /var/vmail/<REMOVED_DOMAIN>/<REMOVED_EMAIL2>/dovecot.list.index.log: duplicate transaction log sequence (2) Jul 02 16:33:35 Panic: imap(<REMOVED_EMAIL2>)<6812><gn4yobOMJlW5D+Vb>: file mail-index-write.c: line 137 (mail_index_write): assertion failed: (file->hdr.prev_file_seq == hdr->log_file_seq) Jul 02 16:33:35 Fatal: imap(<REMOVED_EMAIL2>)<6812><gn4yobOMJlW5D+Vb>: master: service(imap): child 6812 killed with signal 6 (core not dumped - https://dovecot.org/bugreport.html#coredumps - set service imap { drop_priv_before_exec=yes }) Could this problem occur because I am using a Linux NFS server to store all the mails mounted under /var/mail ? Any hints what I can do to avoid these error messages? Thank you in advance. Best regards, Mabi

2 4

Variable expansion with variables containing '%' (ldap with 2.3.6)
by Matthias Lay 02 Jul '19

02 Jul '19

Hi, there seems to be a problem when expanding variables containing a single '%' in value in dovecot V2.3.6 having a user defined Variable in user_attrs like user_attrs = name=home=/maildir/%Ln, =myvar=path/%L{ldap:sAMAccountName} and sAMAccountName conains a '%', in my example "sonder%zeichen" leads to: lda(sonder%zeichen)<5723><ov9uCHjOGV1bFgAACDoIoQ>: Fatal: Failed to expand plugin setting myvar = 'path/sonder%zeichen': Unknown variable '%z' same setup works with dovecot 2.2.29 Any Feedback appreciated. Thanks. Matze

2 5

Variable expansion with variables containing '%' (ldap with 2.3.6)
by Matthias Lay 01 Jul '19

01 Jul '19

Hi, there seems to be a problem when expanding variables containing a single '%' in value in dovecot V2.3.6 having a user defined Variable in user_attrs like user_attrs = name=home=/maildir/%Ln, =myvar=path/%L{ldap:sAMAccountName} and sAMAccountName conains a '%', in my example "sonder%zeichen" leads to: lda(sonder%zeichen)<5723><ov9uCHjOGV1bFgAACDoIoQ>: Fatal: Failed to expand plugin setting myvar = 'path/sonder%zeichen': Unknown variable '%z' same setup works with dovecot 2.2.29 Any Feedback appreciated. Thanks. Matze

1 0

virtual users, change password on first login?
by David Mehler 29 Jun '19

29 Jun '19

Hello, I've got an email server setup all with virtual users. There only interaction with it will be via a webmail interface in this case roundcube. What I'm wanting to do is set up automatic password change on first login. Would this be considered a dovecot or a roundcube issue? Any solution appreciated. Thanks. Dave.

2 1

Error: quota-status: Client sent invalid recipient address: Invalid character in path
by Lefteris Tsintjelis 29 Jun '19

29 Jun '19

Any idea what this is? Jun 26 23:16:34 quota-status(user(a)example.com)<4975><CLsXEzfSE11vEwAArt9ycg>: Error: quota-status: Client sent invalid recipient address: Invalid character in path I have this enabled in my config service quota-status { client_limit = 1 executable = quota-status -p postfix unix_listener /var/spool/postfix/private/dovquota { mode = 0666 user = postfix } } Lefteris

2 2

Problem in doveadm import dovecot 2.2
by Alexander Varejão 27 Jun '19

27 Jun '19

Dear, I always used dovecot in version 2.0 and in the last month i update my servers to dovecot 2.2 but now i have problems with comand dovecot import, not works for me, bellow i put 2 examples used in my tests in boths cases not works for me. Someone already saw some case similar or can help me with this ? doveadm import -u teste(a)aaaaa.com mdbox:~/mdbox-backup "" mailbox INBOX from testeteste(a)bbbb.com doveadm import -u teste(a)xxx.com mdbox:/var/backup/teste@aaaaa.com/ "" all Thanks a Lot Alexander

2 2

Applying Dovecot for a large / deep folder-hierarchy archive.
by Arnold Opio Oree 26 Jun '19

26 Jun '19

Hello to you all, I'd like to ask about my intended application of Dovecot to create a folder-hierarchy for storing our enterprise emails, which are treated as live data rather than archives for compliance or occasional / reactive retrieval. The data is presently not that large (a few gigabytes), but it is expected to grow rapidly. Up to this stage the data has been containedin a Microsoft Exchange mailbox (2013), and then in an offline PST. The move to the offline PST was by necessity, as the large number offolders, and depth of hierarchy to my best understanding caused the exchange server / outlook / evolution mail clients to begin tomalfunction. To cope with this the archive was broken up and the bulk stored in the offline PST and the most active components stored inonline Exchange mailboxes. I have some understanding of the fs mbox format, and also the mitigations to be made for certain characters / strings. My main concern is whether Dovecot is likely to be able to cope well with a large number of folders / depth of hierarcy. I will really appreciate any help / advice you can give. Best regards, Arnold Opio OreeChief Executive OfficerParallax Digital Technologies arnoldoree(a)parallaxdt.com http://www.parallaxdt.com tel : +44 (0) 333 577 8587fax : +44 (0) 20 8711 2477 Parallax Digital Technologies78A Hatfeild MeadLondonSM4 5PF Parallax Digital Technologies is a trading name of Parallax GlobalLimited. U.K. Co. No. 08836288 The contents of this e-mail are confidential. If you are not theintended recipient you are to delete this e-mail immediately, disregardits contents and disclose them to no other persons.

1 0

Exclude dovecot-uidlist files from a Maildir backup ?
by David Pottage 25 Jun '19

25 Jun '19

Hi, I am using restic to backup my email (stored in dovecot Maildir format) to Amazon S3 As each message is a separate file on disk, and those files don't change after the email has been delivered and read by the user, the incremental backup each day is fairly efficient as it only stored new mails. However, the dovecot-uidlist files change frequently, and are often quite large. The restic backup program detects the file has changed and uploads a new version, but is not smart enough to detect that only a few lines have changed, so it uploads a fresh copy of the entire file to remote storage. I have done some test backups and have noticed, that if I exclude those files from the backup, it completes much faster and uploads far less. Would this be a reasonable policy? My backup is mainly there against unlikely but severe events such as complete hard drive failure, so if I ever had to use it, I would not mind wating for my email client to re-download all my emails. -- David Pottage

1 0

Dovecot LDA error - Invalid -f parameter: Invalid character in path
by Bruno de Paula Larini 25 Jun '19

25 Jun '19

Hi list. I'm using dovecot as postfix's LDA. The version is 2.3.6. Last week some spammer set the envelope's FROM to "foo@bar@domain.com" (with two @). While trying to deliver (as this one didn't hit the spamassassin's score), dovecot said the following: Jun 21 02:35:58 mymailserver postfix/pipe[29736]: ADA268195E: to=<user@mydomain>, relay=dovecot, delay=0.08, delays=0.03/0.02/0/0.04, dsn=5.3.0, status=bounced (command line usage error. Command output: lda: Fatal: Invalid -f parameter: Invalid character in path ) Which caused postfix to put it on the bounce list, but the spammer's destiny don't really exist. I could successfully mimic the spammer using telnet and putting two @ in "mail from" address. I don't think this should be an expected behaviour, right? Or is this some config based error? Thanks!

2 1

Authentication against multiple mysql databases
by Graham S. Jarvis 24 Jun '19

24 Jun '19

Hello, I have setup authorisation against a mysql database. I'd now like to do (additional) authentication against another mysql database. i.e. I have two databases with usernames and passwords and I'd like allow all the users from both databases to be able to login to IMAP. Can I simply extend 10-auth.conf in conf.d with additional !include files - like auth-sql.db1.conf.ext auth-sql.db2.conf.ext and associated filed etc. Or do I have to create a new database and set up a view onto the other two databases / tables? Any ideas? Thanks, -Graham-

1 0

Re: Mail migration problem
by Germán Herrera 24 Jun '19

24 Jun '19

Well, judging by the error message it appears like dovecot hasn't been compiled with support for maildir, which is strange because I don't see any way to disable in the compile-time options. Are you using the precompiled package from the distro or compiling dovecot by yourself? Could you share the output of "dovecot --build-options" and "dovecot --version"? Thanks! On 2019-06-21 17:17, Adam Raszkiewicz wrote: > Hi German, > > I have tried your way and getting the same error message: > > dsync(user(a)domain.com): Debug: Namespace inbox: type=private, prefix=, > sep=, inbox=yes, hidden=no, list=yes, subscriptions=yes > location=maildir:~/Maildir > > dsync(user(a)domain.com): Error: User initialization failed: Namespace > '': Unknown mail storage driver maildir > > Thoughts? Missing dovecot library, something in the configuration? > > Thanks, > > Adam > > FROM: dovecot <dovecot-bounces(a)dovecot.org> on behalf of Germán Herrera > via dovecot <dovecot(a)dovecot.org> > ORGANIZATION: SES Sistemas Electrónicos S.A. > REPLY-TO: Germán Herrera <g.herrera(a)ses.com.ar> > DATE: Friday, June 21, 2019 at 3:10 PM > TO: Adam Raszkiewicz <araszkiewicz(a)medallies.com> > CC: "dovecot(a)dovecot.org" <dovecot(a)dovecot.org> > SUBJECT: Re: Mail migration problem > > Hi Adam > > Can you try: "doveadm sync -u <user> maildir:~/Maildir" > > My mailboxes are in sdbox (I have "mail_location = > sdbox:~/sdbox:ALT=/mnt/archive/%u/sdbox") and after running that > command I managed to successfully migrate the user mailbox to maildir. > Also that is the command I used to migrate all my user's maildirs to > sdbox some time ago. > > Regards > > --- > > Germán Herrera > Responsable de IT > Ingeniería > SES Sistemas Electrónicos S.A.| Espinosa 1045 (C1405AMM) | Buenos Aires > | Argentina > W: +54 11 54530000 | Email: g.herrera(a)ses.com.ar > > ------------------------- > > Denos su opinión aquí > > On 2019-06-21 11:58, Adam Raszkiewicz via dovecot wrote: > >> I'm trying to migrate mdbox to maildir based on >> https://wiki.dovecot.org/Migration/MailFormat >> >> * Modified dovecot.conf and set >> mail_location=maildir:/tmp/destination/mailboxes/ >> * Then I had run >> >> /mnt/testmail/bin/dsync -Dv -u user(a)domain.com mirror >> mdbox:/source/mailboxes/user@domain.com >> >> but that did nothing. Then I have >> >> * Modified dovecot.conf and set mail_location=mdbox:/source/mailboxes >> * Then I had run >> >> /mnt/testmail/bin/dsync -Dv -u user(a)domain.com mirror >> mdbox:/tmp/destination/mailboxes/user@domain.com >> >> that copied over user(a)domain.com mailbox from the source to the >> destination location. As that was working I have tried to run >> >> /mnt/testmail/bin/dsync -Dv -u user(a)domain.com mirror >> maildir:/tmp/destination/mailboxes/user@domain.com >> >> but that got an error: >> >> dsync(user(a)domain.com): Debug: Namespace inbox: type=private, prefix=, >> sep=, inbox=yes, hidden=no, list=yes, subscriptions=yes >> location=maildir:/mnt/testmail/mailboxes >> >> dsync(user(a)domain.com): Error: User initialization failed: Namespace >> '': Unknown mail storage driver maildir >> >> First problem is that based on example #2 from above provided syntax >> in https://wiki.dovecot.org/Migration/MailFormat is incorrect or for >> some reason is not working for me as it should for example #1. >> >> Second issue is not recognizing maildir format - what about that? >> Docecot has some missing libraries? >> >> Thanks, >> >> Adam

2 2

Mail migration problem
by Adam Raszkiewicz 24 Jun '19

24 Jun '19

I’m trying to migrate mdbox to maildir based on https://wiki.dovecot.org/Migration/MailFormat * Modified dovecot.conf and set mail_location=maildir:/tmp/destination/mailboxes/ * Then I had run /mnt/testmail/bin/dsync -Dv -u user(a)domain.com<mailto:user@domain.com> mirror mdbox:/source/mailboxes/user@domain.com<mailto:/source/mailboxes/user@domain.com> but that did nothing. Then I have * Modified dovecot.conf and set mail_location=mdbox:/source/mailboxes * Then I had run /mnt/testmail/bin/dsync -Dv -u user(a)domain.com<mailto:user@domain.com> mirror mdbox:/tmp/destination/mailboxes/user@domain.com<mailto:/source/mailboxes/user@domain.com> that copied over user(a)domain.com<mailto:user@domain.com> mailbox from the source to the destination location. As that was working I have tried to run /mnt/testmail/bin/dsync -Dv -u user(a)domain.com<mailto:user@domain.com> mirror maildir:/tmp/destination/mailboxes/user@domain.com<mailto:/source/mailboxes/user@domain.com> but that got an error: dsync(user(a)domain.com): Debug: Namespace inbox: type=private, prefix=, sep=, inbox=yes, hidden=no, list=yes, subscriptions=yes location=maildir:/mnt/testmail/mailboxes dsync(user(a)domain.com): Error: User initialization failed: Namespace '': Unknown mail storage driver maildir First problem is that based on example #2 from above provided syntax in https://wiki.dovecot.org/Migration/MailFormat is incorrect or for some reason is not working for me as it should for example #1. Second issue is not recognizing maildir format – what about that? Docecot has some missing libraries? Thanks, Adam

3 2

quota-plugin + namespace with wildcards?
by Jost-Philip Matysik 24 Jun '19

24 Jun '19

Hi all! Is the quota-plugin (quota + quota-rule directives) supposed to function for namespaces that are generated dynamically for shared mailboxes? (namespace=shared/%u with %u expanded from userdb) 'Cause I cannot find anything in the wiki that suggests it can't be used that way, but it ain't a-workin'... :o( Thanks! Jost

1 0

last login user tracking
by David Mehler 22 Jun '19

22 Jun '19

Hello, I'm trying to get last login user tracking going, using Dovecot and mysql. I'm using: https://docs.iredmail.org/track.user.last.login.html and it is working, I am seeing an entry and it is updated, the problem is the last login value does not mean anything to me. I was wondering if it's possible to have the value be of a last login date and time, and also a remote ip would be helpful so I can see from where users are logging in from. Thanks. Dave.

4 4

Submission service and SMTP AUTH capability
by Germán Herrera 22 Jun '19

22 Jun '19

Hi Everyone! I've setup dovecot 2.3.2.1 on a Gentoo server. I want to configure the submission service in order to replace the corresponding part in Postfix (which is my SMTP server). I configured submission it with just a few options different of the default ones: submission_client_workarounds = whitespace-before-path submission_relay_host = 127.0.0.1 submission_relay_port = 10026 submission_relay_trusted = yes The issue I'm having is that the SMTP AUTH is enforced and performed correctly, but it doesn't get published on the server capaabilities when the connection doesn't come from localhost. This causes issues with some smtp clients which authenticate (python smtpclient). When I telnet the submission service from localhost I get: 220 (protected hostname) Dovecot ready. EHLO L 250-(protected hostname) 250-8BITMIME 250-AUTH PLAIN LOGIN 250-BURL imap 250-CHUNKING 250-ENHANCEDSTATUSCODES 250-SIZE 250-STARTTLS 250 PIPELINING quit 221 2.0.0 Bye But when I do the same from another host other than the one running dovecot (telnetting the submission port): 220 (protected hostname) Dovecot ready. EHLO L 250-(protected hostname) 250-8BITMIME 250-BURL imap 250-CHUNKING 250-ENHANCEDSTATUSCODES 250-SIZE 250-STARTTLS 250 PIPELINING quit 221 2.0.0 Bye As you can see, the AUTH capability is not there. Do you know what could be causing this issue? Your help is much appreciated! German

3 3

Listener indicated in logs
by jbwlists＠hilltopgroup.com 21 Jun '19

21 Jun '19

I'm looking for a way to indicate which listener a connection came in via in the logs. For instance, I have IMAPS connections coming in via 993 as well as 1993, and would like some way to differentiate in the logging. Is there a way to do this? Thanks in advance, Joseph

2 2

CentOS 7 SeLinux Problem?
by Günther J. Niederwimmer 21 Jun '19

21 Jun '19

Hello, I update my dovecot to the last Version, now I have this error in the audit Log. Can any tell me what I can do, without selinux disabled // SELinux hindert /usr/sbin/dovecot daran, mit getattr-Zugriff auf Datei /proc/ sys/fs/suid_dumpable zuzugreifen. ***** Plugin catchall (100. Wahrscheinlichkeit) schlägt vor ************** If you believe that dovecot should be allowed getattr access on the suid_dumpable file by default. Dann sie sollten dies als Fehler melden. Um diesen Zugriff zu erlauben, können Sie ein lokales Richtlinien-Modul erstellen. Ausführen allow this access for now by executing: # ausearch -c 'dovecot' --raw | audit2allow -M my-dovecot # semodule -i my-dovecot.pp zusätzliche Information: Quellkontext system_u:system_r:dovecot_t:s0 Zielkontext system_u:object_r:proc_security_t:s0 Zielobjekte /proc/sys/fs/suid_dumpable [ file ] Quelle dovecot Quellpfad /usr/sbin/dovecot Port <Unknown> Host <Unknown> RPM-Pakete der Quelle dovecot-2.3.6-2.x86_64 RPM-Pakete des Ziels Richtlinien-RPM selinux-policy-3.13.1-229.el7_6.12.noarch SELinux aktiviert True Richtlinientyp targeted Enforcing-Modus Enforcing Rechnername mx01.example.com Plattform Linux mx01.example.com 3.10.0-957.21.3.el7.x86_64 #1 SMP Tue Jun 18 16:35:19 UTC 2019 x86_64 x86_64 Anzahl der Alarme 1 Zuerst gesehen 2019-06-21 06:15:28 CEST Zuletzt gesehen 2019-06-21 06:15:28 CEST Lokale ID 259a6386-ad49-4cdf-a21b-97f891c997aa Raw-Audit-Meldungen type=AVC msg=audit(1561090528.816:4135): avc: denied { getattr } for pid=28610 comm="dovecot" path="/proc/sys/fs/suid_dumpable" dev="proc" ino=39881 scontext=system_u:system_r:dovecot_t:s0 tcontext=system_u:object_r:proc_security_t:s0 tclass=file permissive=0 type=SYSCALL msg=audit(1561090528.816:4135): arch=x86_64 syscall=stat success=no exit=EACCES a0=556b5394906b a1=7fff567c8e40 a2=7fff567c8e40 a3=7fff567c87e0 items=0 ppid=1 pid=28610 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm=dovecot exe=/usr/sbin/dovecot subj=system_u:system_r:dovecot_t:s0 key=(null) Hash: dovecot,dovecot_t,proc_security_t,file,getattr // when I create a separate my-dovecot.pp I have the same Error :-( -- mit freundliche Grüßen / best regards, Günther J. Niederwimmer

1 0

mdbox to Maildir
by Odhiambo Washington 20 Jun '19

20 Jun '19

I'd like a way to convert all my mailboxes from mdbox to Maildir. Is it possible? How do I do it for ALL mailboxes? -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", grep ^[^#] :-)

4 6

Help on CRAM-MD5
by Jorge Bastos 20 Jun '19

20 Jun '19

Howdy, I'm using dovecot and mysql users, and i'm creating the password with: ENCRYPT('some-passwd',CONCAT('$6$', SUBSTRING(SHA(RAND()), -16))) So far so good, everything's fine. Today saw that i didn't enabled CRAM-MD5, but if I do, and the (at least) IMAP client (roundcube/thunderbird/etc) issues CRAM-MD5 it doesn't authenticate. What am i doing wrong, or that can be done so that all types work (SASL PLAIN LOGIN + CRAM-MD5)? Thanks in advanced,

7 16

Re: mremap_anon() failed: Not enough space
by Joseph Tam 20 Jun '19

20 Jun '19

> It?s also possible that the cache files USED to grow quite large in > previous versions and that now they are much more reasonable, but the > only way to reset their size appears to be to delete them and let > dovecot rebuild them. I seem to recall these cache files ballooned in size when I did some doveadm search queries -- under some circumstances some headers fetches are cached for later searches, which may explain the growth over time as clients do mailbox searches. As for Solaris10 mremap_anon() space failures, I'm a litte hazy on memory mapping and shared memory, but I wonder if this has anything to do with kernel maximum shared memory limits. I know that for some of our Solaris 10 servers, I had to up these values in /etc/system to get some of our services to work. Joseph Tam <jtam.home(a)gmail.com>

1 0

mremap_anon() failed: Not enough space
by Dave McGuire 20 Jun '19

20 Jun '19

Hey folks. Suddenly I'm getting lots and lots of messages like this in my logs: Jun 19 14:47:31 <hostname> dovecot: [ID 583609 local0.error] imap(<address>): Error: mremap_anon(/var/mail/<domain>/<uname>/mailboxes/INBOX/Trash/dbox-Mails/dovecot.index.cache, 255557632) failed: Not enough space I'm running 2.2.36.1 under Solaris 10 (patched to current) on UltraSPARC. There's plenty of memory, plenty of swap, and plenty of disk, but this is a fairly busy mail server. Can anyone point me in the right direction? I'm guessing I have to increase a vsz_limit somewhere, but where? It's not clear to me exactly what is running out of what here. The output of doveconf -n is pasted below. Thanks, -Dave -------------------------------------------------- $ doveconf -n # 2.2.36.1 (5d621cf65): /etc/dovecot/dovecot.conf # Pigeonhole version 0.4.24 (124e06aa) # OS: SunOS 5.10 sun4v # Hostname: mail.neurotica.com auth_failure_delay = 5 secs auth_mechanisms = plain login base_dir = /var/run/dovecot/ debug_log_path = /var/log/dovecot-debug disable_plaintext_auth = no first_valid_uid = 200 login_access_sockets = tcpwrap mail_fsync = never mail_plugins = fts fts_solr 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 editheader mdbox_rotate_size = 64 M mmap_disable = yes namespace inbox { inbox = yes location = mailbox uncaught-spam { auto = subscribe special_use = \Junk } prefix = } passdb { args = /etc/dovecot/dovecot-sql.conf driver = sql } plugin { fts = solr fts_solr = break-imap-search url=http://localhost:8983/solr/ sieve = /var/sieve-scripts/%u.sieve sieve_dir = ~/sieve sieve_extensions = +editheader sieve_global_dir = /var/lib/dovecot/sieve/global/ sieve_global_path = /var/lib/dovecot/sieve/default.sieve } protocols = imap pop3 sieve service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0660 user = postfix } unix_listener auth-master { group = vmail mode = 0600 user = vmail } user = root } service imap-login { process_min_avail = 10 service_count = 10 vsz_limit = 512 M } service imap { executable = /usr/local/libexec/dovecot/imap vsz_limit = 512 M } service managesieve-login { inet_listener sieve { port = 4190 } process_min_avail = 1 service_count = 1 vsz_limit = 64 M } service managesieve { process_limit = 10 } service pop3-login { process_min_avail = 10 service_count = 10 vsz_limit = 512 M } service pop3 { executable = /usr/local/libexec/dovecot/pop3 } service tcpwrap { unix_listener login/tcpwrap { group = $default_login_user mode = 0600 user = $default_login_user } } ssl_cert = </etc/letsencrypt/live/mail.neurotica.com/fullchain.pem ssl_key = # hidden, use -P to show it syslog_facility = local0 userdb { args = /etc/dovecot/dovecot-sql.conf driver = sql } protocol pop3 { pop3_uidl_format = %08Xu%08Xv } protocol sieve { info_log_path = /var/log/dovecot-sieve.log log_path = /var/log/dovecot-sieve-errors.log managesieve_implementation_string = dovecot managesieve_max_line_length = 65536 } protocol lda { mail_fsync = optimized mail_plugins = fts fts_solr sieve postmaster_address = postmaster(a)neurotica.com } protocol imap { imap_capability = IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE IDLE SORT SORT=DISPLAY THREAD=REFERENCES THREAD=REFS MULTIAPPEND UNSELECT CHILDREN NAMESPACE UIDPLUS LIST-EXTENDED I18NLEVEL=1 ESEARCH ESORT SEARCHRES WITHIN CONTEXT=SEARCH LIST-STATUS imap_client_workarounds = tb-extra-mailbox-sep mail_max_userip_connections = 40 mail_plugin_dir = /usr/local/lib/dovecot mail_plugins = fts fts_solr } protocol lmtp { info_log_path = /var/log/dovecot-lmtp.log log_path = /var/log/dovecot-lmtp-errors.log mail_plugins = fts fts_solr sieve } -------------------------------------------------- -- Dave McGuire, AK4HZ New Kensington, PA

4 4

Re: Converting mdbox to mbox/MailDir
by ＠lbutlr 20 Jun '19

20 Jun '19

On 18 Jun 2019, at 20:46, Adam Raszkiewicz <araszkiewicz(a)medallies.com> wrote: > maildir -> mdbox it is maildir to mdbox conversion when I'm looking something opposite: mdbox -> maildir Please go back and read all the words in my previous reply. -- Lead me not into temptation, I can find the way.

3 2

IMAP IDLE
by Jorge Bastos 20 Jun '19

20 Jun '19

Hi, With outlook 2016+ i've seen that IDLE may be missing some configuration. Almost all time, when i'm in the inbox, i don't get new emails if no activity for 1 or 2 minutes (i think), i have to get out of the account and select the inbox or click other folder in the account and go to inbox again for them to appear. My idle conf's are the defaults, the one's bellow. Is there anything else that i need to make it work always and the change folders is not needed for outlook clients? root@fastmail:/etc/dovecot# doveconf |grep -i idle default_idle_kill = 1 mins imap_idle_notify_interval = 2 mins imapc_max_idle_time = 29 mins mailbox_idle_check_interval = 30 secs

2 4

recipient delimiters
by ＠lbutlr 20 Jun '19

20 Jun '19

Since many broken websites and idiot companies will not allow a ‘+’ in an email address, I have long used two delimiters in postfix: recipient_delimiter = +_ However, now that dovecot is handling verification for postfix via reject_unverified_recipient, dovecot complains about any address using an _ as a delimiter. I don’t see a way to tell dovecot what delimiters to use, and it appears it is still using a single delimiter only despite postfix having added support for more than one years ago. Anything that I can do in dovecot to 1) validate these emails and 2) treat user_extension the same as user+extension at delivery? -- Love is like oxygen / You get too much / you get too high / Not enough and you're gonna die

2 3

RFC 8314 § 3.3 support at Dovecot submission proxy service?
by Robert Scheck 20 Jun '19

20 Jun '19

Hello all, I'm currently wondering whether Dovecot submission proxy service supports RFC 8314 § 3.3 as well, which means implicit TLS for SMTP submission. https://github.com/dovecot/core/blob/2cbbe9b4829adb184c83dbf780316f41445590… from Git master just mentions port 587 like this: service submission-login { inet_listener submission { #port = 587 } } As per RFC 8314 § 3.3, I would expect the following to work (which I did not try), and if it already works, I even would expect this snippet part of the future Dovecot example/default configuration: service submission-login { inet_listener submission { #port = 587 } inet_listener submissions { #port = 465 #ssl = yes } } And if it isn't supported yet, I would indeed like to raise this as feature request. Note that 465 is named "submissions" as per RFC 8314 § 7.3. Kind regards Robert Scheck

2 1

Problem syncing mail with IMAP
by Odhiambo Washington 20 Jun '19

20 Jun '19

I am seeing the following errors in my logs, which I believe are preventing Outlook from syncing. How do I solve these? Can I just delete the index.cache?? Jun 18 11:23:34 imap(technical(a)mydomain.co.ke)<59754><g5UC1JSLPhkpUFt/>: Error: Corrupted record in index cache file /var/spool/virtual/ mydomain.co.ke/technical/mdbox/mailboxes/INBOX/dbox-Mails/dovecot.index.cache: UID 29: Broken virtual size in mailbox INBOX: read(/var/spool/virtual/ mydomain.co.ke/technical/mdbox/storage/m.1): FETCH BODY[] got too little data: 131524 vs 772408 Jun 18 11:23:45 imap(sales(a)mydomain.co.ke)<59812><aeLI1JSLoe3FsVm2>: Error: Corrupted record in index cache file /var/spool/virtual/ mydomain.co.ke/sales/mdbox/mailboxes/INBOX/dbox-Mails/dovecot.index.cache: UID 25: Broken virtual size in mailbox INBOX: read(/var/spool/virtual/ mydomain.co.ke/sales/mdbox/storage/m.552): FETCH BODY[] got too little data: 17130 vs 370736 Jun 18 11:24:03 imap(technical(a)mydomain.co.ke)<59891><uJHS1ZSLchkpUFt/>: Error: Corrupted record in index cache file /var/spool/virtual/ mydomain.co.ke/technical/mdbox/mailboxes/INBOX/dbox-Mails/dovecot.index.cache: UID 29: Broken virtual size in mailbox INBOX: read(/var/spool/virtual/ mydomain.co.ke/technical/mdbox/storage/m.1): FETCH BODY[] got too little data: 131524 vs 772408 Jun 18 11:24:12 imap(sales(a)mydomain.co.ke)<59933><q/9j1pSL3e3FsVm2>: Error: Corrupted record in index cache file /var/spool/virtual/ mydomain.co.ke/sales/mdbox/mailboxes/INBOX/dbox-Mails/dovecot.index.cache: UID 25: Broken virtual size in mailbox INBOX: read(/var/spool/virtual/ mydomain.co.ke/sales/mdbox/storage/m.552): FETCH BODY[] got too little data: 17130 vs 370736 Jun 18 11:24:40 imap(sales(a)mydomain.co.ke)<60053><DuQT2JSL9+3FsVm2>: Error: Corrupted record in index cache file /var/spool/virtual/ mydomain.co.ke/sales/mdbox/mailboxes/INBOX/dbox-Mails/dovecot.index.cache: UID 25: Broken virtual size in mailbox INBOX: read(/var/spool/virtual/ mydomain.co.ke/sales/mdbox/storage/m.552): FETCH BODY[] got too little data: 17130 vs 370736 Jun 18 11:24:49 imap(technical(a)mydomain.co.ke)<60079><ChRu2JSLrxkpUFt/>: Error: Corrupted record in index cache file /var/spool/virtual/ mydomain.co.ke/technical/mdbox/mailboxes/INBOX/dbox-Mails/dovecot.index.cache: UID 29: Broken virtual size in mailbox INBOX: read(/var/spool/virtual/ mydomain.co.ke/technical/mdbox/storage/m.1): FETCH BODY[] got too little data: 131524 vs 772408 Jun 18 11:25:09 imap(sales(a)mydomain.co.ke)<60184><i9HC2ZSLEe7FsVm2>: Error: Corrupted record in index cache file /var/spool/virtual/ mydomain.co.ke/sales/mdbox/mailboxes/INBOX/dbox-Mails/dovecot.index.cache: UID 25: Broken virtual size in mailbox INBOX: read(/var/spool/virtual/ mydomain.co.ke/sales/mdbox/storage/m.552): FETCH BODY[] got too little data: 17130 vs 370736 Jun 18 11:25:13 imap(technical(a)mydomain.co.ke)<60204><sPL32ZSLx/cpUFt/>: Error: Corrupted record in index cache file /var/spool/virtual/ mydomain.co.ke/technical/mdbox/mailboxes/INBOX/dbox-Mails/dovecot.index.cache: UID 29: Broken virtual size in mailbox INBOX: read(/var/spool/virtual/ mydomain.co.ke/technical/mdbox/storage/m.1): FETCH BODY[] got too little data: 131524 vs 772408 Jun 18 11:25:42 imap(technical(a)mydomain.co.ke)<60328><QFm325SL9fcpUFt/>: Error: Corrupted record in index cache file /var/spool/virtual/ mydomain.co.ke/technical/mdbox/mailboxes/INBOX/dbox-Mails/dovecot.index.cache: UID 29: Broken virtual size in mailbox INBOX: read(/var/spool/virtual/ mydomain.co.ke/technical/mdbox/storage/m.1): FETCH BODY[] got too little data: 131524 vs 772408 Jun 18 11:26:03 imap(sales(a)mydomain.co.ke)<60358><9ckk3JSLLe7FsVm2>: Error: Corrupted record in index cache file /var/spool/virtual/ mydomain.co.ke/sales/mdbox/mailboxes/INBOX/dbox-Mails/dovecot.index.cache: UID 25: Broken virtual size in mailbox INBOX: read(/var/spool/virtual/ mydomain.co.ke/sales/mdbox/storage/m.552): FETCH BODY[] got too little data: 17130 vs 370736 Jun 18 11:26:11 imap(technical(a)mydomain.co.ke)<60455><SKRs3ZSLJfgpUFt/>: Error: Corrupted record in index cache file /var/spool/virtual/ mydomain.co.ke/technical/mdbox/mailboxes/INBOX/dbox-Mails/dovecot.index.cache: UID 29: Broken virtual size in mailbox INBOX: read(/var/spool/virtual/ mydomain.co.ke/technical/mdbox/storage/m.1): FETCH BODY[] got too little data: 131524 vs 772408 Jun 18 11:26:32 imap(sales(a)mydomain.co.ke)<60548><SAy/3pSLjO7FsVm2>: Error: Corrupted record in index cache file /var/spool/virtual/ mydomain.co.ke/sales/mdbox/mailboxes/INBOX/dbox-Mails/dovecot.index.cache: UID 25: Broken virtual size in mailbox INBOX: read(/var/spool/virtual/ mydomain.co.ke/sales/mdbox/storage/m.552): FETCH BODY[] got too little data: 17130 vs 370736 Jun 18 11:26:33 imap(technical(a)mydomain.co.ke)<60553><j3HE3pSLKBspUFt/>: Error: Corrupted record in index cache file /var/spool/virtual/ mydomain.co.ke/technical/mdbox/mailboxes/INBOX/dbox-Mails/dovecot.index.cache: UID 29: Broken virtual size in mailbox INBOX: read(/var/spool/virtual/ mydomain.co.ke/technical/mdbox/storage/m.1): FETCH BODY[] got too little data: 131524 vs 772408 Jun 18 11:26:45 imap(technical(a)mydomain.co.ke)<60602><p49635SLUhspUFt/>: Error: Corrupted record in index cache file /var/spool/virtual/ mydomain.co.ke/technical/mdbox/mailboxes/INBOX/dbox-Mails/dovecot.index.cache: UID 29: Broken virtual size in mailbox INBOX: read(/var/spool/virtual/ mydomain.co.ke/technical/mdbox/storage/m.1): FETCH BODY[] got too little data: 131524 vs 772408 Jun 18 11:26:51 imap(technical(a)mydomain.co.ke)<60629><NO/K35SLWBspUFt/>: Error: Corrupted record in index cache file /var/spool/virtual/ mydomain.co.ke/technical/mdbox/mailboxes/INBOX/dbox-Mails/dovecot.index.cache: UID 29: Broken virtual size in mailbox INBOX: read(/var/spool/virtual/ mydomain.co.ke/technical/mdbox/storage/m.1): FETCH BODY[] got too little data: 131524 vs 772408 Jun 18 11:26:58 imap(technical(a)mydomain.co.ke)<60660><46ou4JSLa/gpUFt/>: Error: Corrupted record in index cache file /var/spool/virtual/ mydomain.co.ke/technical/mdbox/mailboxes/INBOX/dbox-Mails/dovecot.index.cache: UID 29: Broken virtual size in mailbox INBOX: read(/var/spool/virtual/ mydomain.co.ke/technical/mdbox/storage/m.1): FETCH BODY[] got too little data: 131524 vs 772408 Jun 18 11:27:01 imap(sales(a)mydomain.co.ke)<60678><Sxpv4JSLm+7FsVm2>: Error: Corrupted record in index cache file /var/spool/virtual/ mydomain.co.ke/sales/mdbox/mailboxes/INBOX/dbox-Mails/dovecot.index.cache: UID 25: Broken virtual size in mailbox INBOX: read(/var/spool/virtual/ mydomain.co.ke/sales/mdbox/storage/m.552): FETCH BODY[] got too little data: 17130 vs 370736 Jun 18 11:27:31 imap(sales(a)mydomain.co.ke)<60809><atU54pSLwe7FsVm2>: Error: Corrupted record in index cache file /var/spool/virtual/ mydomain.co.ke/sales/mdbox/mailboxes/INBOX/dbox-Mails/dovecot.index.cache: UID 25: Broken virtual size in mailbox INBOX: read(/var/spool/virtual/ mydomain.co.ke/sales/mdbox/storage/m.552): FETCH BODY[] got too little data: 17130 vs 370736 Jun 18 11:27:59 imap(sales(a)mydomain.co.ke)<60932><9LLs45SL3u7FsVm2>: Error: Corrupted record in index cache file /var/spool/virtual/ mydomain.co.ke/sales/mdbox/mailboxes/INBOX/dbox-Mails/dovecot.index.cache: UID 25: Broken virtual size in mailbox INBOX: read(/var/spool/virtual/ mydomain.co.ke/sales/mdbox/storage/m.552): FETCH BODY[] got too little data: 17130 vs 370736 Jun 18 11:28:49 imap(sales(a)mydomain.co.ke)<61091><ekYq5pSLDO/FsVm2>: Error: Corrupted record in index cache file /var/spool/virtual/ mydomain.co.ke/sales/mdbox/mailboxes/INBOX/dbox-Mails/dovecot.index.cache: UID 25: Broken virtual size in mailbox INBOX: read(/var/spool/virtual/ mydomain.co.ke/sales/mdbox/storage/m.552): FETCH BODY[] got too little data: 17130 vs 370736 Jun 18 11:29:05 imap(sales(a)mydomain.co.ke)<61225><qenN55SLoLC5HrCp>: Error: Corrupted record in index cache file /var/spool/virtual/ mydomain.co.ke/sales/mdbox/mailboxes/Sent Items/dbox-Mails/dovecot.index.cache: UID 1853: Broken virtualsize in mailbox Sent Items: read(/var/spool/virtual/ mydomain.co.ke/sales/mdbox/storage/m.254): FETCH BODY[] got too little data: 3510 vs 1068172 Jun 18 11:29:15 imap(sales(a)mydomain.co.ke)<61272><Sb1s6JSLSe/FsVm2>: Error: Corrupted record in index cache file /var/spool/virtual/ mydomain.co.ke/sales/mdbox/mailboxes/INBOX/dbox-Mails/dovecot.index.cache: UID 25: Broken virtual size in mailbox INBOX: read(/var/spool/virtual/ mydomain.co.ke/sales/mdbox/storage/m.552): FETCH BODY[] got too little data: 17130 vs 370736 Jun 18 11:29:43 imap(sales(a)mydomain.co.ke)<61393><FJIc6pSLfO/FsVm2>: Error: Corrupted record in index cache file /var/spool/virtual/ mydomain.co.ke/sales/mdbox/mailboxes/INBOX/dbox-Mails/dovecot.index.cache: UID 25: Broken virtual size in mailbox INBOX: read(/var/spool/virtual/ mydomain.co.ke/sales/mdbox/storage/m.552): FETCH BODY[] got too little data: 17130 vs 370736 Jun 18 11:30:13 imap(sales(a)mydomain.co.ke)<61532><WGve65SLx+/FsVm2>: Error: Corrupted record in index cache file /var/spool/virtual/ mydomain.co.ke/sales/mdbox/mailboxes/INBOX/dbox-Mails/dovecot.index.cache: UID 25: Broken virtual size in mailbox INBOX: read(/var/spool/virtual/ mydomain.co.ke/sales/mdbox/storage/m.552): FETCH BODY[] got too little data: 17130 vs 370736 Jun 18 11:30:39 imap(sales(a)mydomain.co.ke)<61647><e2x47ZSL+e/FsVm2>: Error: Corrupted record in index cache file /var/spool/virtual/ mydomain.co.ke/sales/mdbox/mailboxes/INBOX/dbox-Mails/dovecot.index.cache: UID 25: Broken virtual size in mailbox INBOX: read(/var/spool/virtual/ mydomain.co.ke/sales/mdbox/storage/m.552): FETCH BODY[] got too little data: 17130 vs 370736 Jun 18 11:31:10 imap(sales(a)mydomain.co.ke)<61782><+L4175SLI/DFsVm2>: Error: Corrupted record in index cache file /var/spool/virtual/ mydomain.co.ke/sales/mdbox/mailboxes/INBOX/dbox-Mails/dovecot.index.cache: UID 25: Broken virtual size in mailbox INBOX: read(/var/spool/virtual/ mydomain.co.ke/sales/mdbox/storage/m.552): FETCH BODY[] got too little data: 17130 vs 370736 Jun 18 11:31:36 imap(sales(a)mydomain.co.ke)<61905><pK/W8JSLafDFsVm2>: Error: Corrupted record in index cache file /var/spool/virtual/ mydomain.co.ke/sales/mdbox/mailboxes/INBOX/dbox-Mails/dovecot.index.cache: UID 25: Broken virtual size in mailbox INBOX: read(/var/spool/virtual/ mydomain.co.ke/sales/mdbox/storage/m.552): FETCH BODY[] got too little data: 17130 vs 370736 Jun 18 11:31:36 imap(technical(a)mydomain.co.ke)<61899><TnXN8JSLifopUFt/>: Error: Corrupted record in index cache file /var/spool/virtual/ mydomain.co.ke/technical/mdbox/mailboxes/INBOX/dbox-Mails/dovecot.index.cache: UID 29: Broken virtual size in mailbox INBOX: read(/var/spool/virtual/ mydomain.co.ke/technical/mdbox/storage/m.1): FETCH BODY[] got too little data: 131524 vs 772408 Jun 18 11:31:37 imap(sales(a)mydomain.co.ke)<61897><IgvJ8JSL4h0pUFt/>: Error: Corrupted record in index cache file /var/spool/virtual/ mydomain.co.ke/sales/mdbox/mailboxes/INBOX/dbox-Mails/dovecot.index.cache: UID 25: Broken virtual size in mailbox INBOX: read(/var/spool/virtual/ mydomain.co.ke/sales/mdbox/storage/m.552): FETCH BODY[] got too little data: 17130 vs 370736 Jun 18 11:31:37 imap(technical(a)mydomain.co.ke)<61916><xhby8JSL6h0pUFt/>: Error: Corrupted record in index cache file /var/spool/virtual/ mydomain.co.ke/technical/mdbox/mailboxes/Deleted Items/dbox-Mails/dovecot.index.cache: UID 2: Broken virtual size in mailbox Deleted Items: read(/var/spool/virtual/mydomain.co.ke/technical/mdbox/storage/m.460): FETCH BODY[] got too little data: 10123 vs 197577 Jun 18 11:31:37 imap(technical(a)mydomain.co.ke)<61919><hSf38JSL7B0pUFt/>: Error: Corrupted record in index cache file /var/spool/virtual/ mydomain.co.ke/technical/mdbox/mailboxes/Sent Items/dbox-Mails/dovecot.index.cache: UID 2: Broken virtual size in mailbox Sent Items: read(/var/spool/virtual/ mydomain.co.ke/technical/mdbox/storage/m.2): FETCH BODY[] got too little data: 3620 vs 817692 Jun 18 11:31:40 imap(sales(a)mydomain.co.ke)<61924><cEP+8JSL7h0pUFt/>: Error: Corrupted record in index cache file /var/spool/virtual/ mydomain.co.ke/sales/mdbox/mailboxes/Sent Items/dbox-Mails/dovecot.index.cache: UID 1: Broken virtual size in mailbox Sent Items: read(/var/spool/virtual/ mydomain.co.ke/sales/mdbox/storage/m.24): FETCH BODY[] got too little data: 5202 vs 1196884 Jun 18 11:31:44 imap(sales(a)mydomain.co.ke)<61937><bd8o8ZSL8B0pUFt/>: Error: Corrupted record in index cache file /var/spool/virtual/ mydomain.co.ke/sales/mdbox/mailboxes/Sent/dbox-Mails/dovecot.index.cache: UID 9: Broken virtual size in mailbox Sent: read(/var/spool/virtual/ mydomain.co.ke/sales/mdbox/storage/m.255): FETCH BODY[] got too little data: 46155 vs 1156185 Jun 18 11:31:46 imap(sales(a)mydomain.co.ke)<61962><cMlt8ZSLqfopUFt/>: Error: Corrupted record in index cache file /var/spool/virtual/ mydomain.co.ke/sales/mdbox/mailboxes/Trash/dbox-Mails/dovecot.index.cache: UID 8: Broken virtual size in mailbox Trash: read(/var/spool/virtual/ mydomain.co.ke/sales/mdbox/storage/m.657): FETCH BODY[] got too little data: 107289 vs 1338249 Jun 18 11:32:07 imap(sales(a)mydomain.co.ke)<62063><ZEiZ8pSLn/DFsVm2>: Error: Corrupted record in index cache file /var/spool/virtual/ mydomain.co.ke/sales/mdbox/mailboxes/INBOX/dbox-Mails/dovecot.index.cache: UID 25: Broken virtual size in mailbox INBOX: read(/var/spool/virtual/ mydomain.co.ke/sales/mdbox/storage/m.552): FETCH BODY[] got too little data: 17130 vs 370736 -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", grep ^[^#] :-)

2 1

User listing returned failure with -A
by ＠lbutlr 19 Jun '19

19 Jun '19

First, I archive the old messages in the INBOX on my list account # doveadm -Dv move -u kremels(a)kreme.com Archive mailbox INBOX BEFORE 90d Debug: Loading modules from directory: /usr/local/lib/dovecot/doveadm Debug: Skipping module doveadm_acl_plugin, because dlopen() failed: /usr/local/lib/dovecot/doveadm/lib10_doveadm_acl_plugin.so: Undefined symbol "acl_user_module" (this is usually intentional, so just ignore this message) Debug: Skipping module doveadm_expire_plugin, because dlopen() failed: /usr/local/lib/dovecot/doveadm/lib10_doveadm_expire_plugin.so: Undefined symbol "expire_set_lookup" (this is usually intentional, so just ignore this message) Debug: Skipping module doveadm_quota_plugin, because dlopen() failed: /usr/local/lib/dovecot/doveadm/lib10_doveadm_quota_plugin.so: Undefined symbol "quota_user_module" (this is usually intentional, so just ignore this message) Debug: Module loaded: /usr/local/lib/dovecot/doveadm/lib10_doveadm_sieve_plugin.so Debug: Skipping module doveadm_fts_plugin, because dlopen() failed: /usr/local/lib/dovecot/doveadm/lib20_doveadm_fts_plugin.so: Undefined symbol "fts_filter_filter" (this is usually intentional, so just ignore this message) Debug: Skipping module doveadm_mail_crypt_plugin, because dlopen() failed: /usr/local/lib/dovecot/doveadm/libdoveadm_mail_crypt_plugin.so: Undefined symbol "mail_crypt_user_get_public_key" (this is usually intentional, so just ignore this message) doveadm(kremels(a)kreme.com)<64937><>: Debug: auth USER input: kremels(a)kreme.com uid=89 gid=89 mail_location=maildir:/usr/local/virtual/kremels@kreme.com/Maildir mail=maildir:/usr/local/virtual/kremels@kreme.com/Maildir home=/usr/local/virtual/kremels(a)kreme.com/ doveadm(kremels(a)kreme.com)<64937><>: Debug: Added userdb setting: mail=maildir:/usr/local/virtual/kremels@kreme.com/Maildir doveadm(kremels(a)kreme.com)<64937><>: Debug: Added userdb setting: mail_location=maildir:/usr/local/virtual/kremels@kreme.com/Maildir doveadm(kremels(a)kreme.com): Debug: Effective uid=89, gid=89, home=/usr/local/virtual/kremels(a)kreme.com/ doveadm(kremels(a)kreme.com): Debug: Namespace inbox: type=private, prefix=, sep=, inbox=yes, hidden=no, list=yes, subscriptions=yes location=maildir:/usr/local/virtual/kremels@kreme.com/Maildir doveadm(kremels(a)kreme.com): Debug: maildir++: root=/usr/local/virtual/kremels(a)kreme.com/Maildir, index=, indexpvt=, control=, inbox=/usr/local/virtual/kremels(a)kreme.com/Maildir, alt= doveadm(kremels(a)kreme.com): Debug: Mailbox Archive: Mailbox opened because: move doveadm(kremels(a)kreme.com): Debug: Mailbox INBOX: Mailbox opened because: move OK. that went well, how about all users now? # doveadm -Dv move -A Archive mailbox INBOX BEFORE 90d Debug: Loading modules from directory: /usr/local/lib/dovecot/doveadm Debug: Skipping module doveadm_acl_plugin, because dlopen() failed: /usr/local/lib/dovecot/doveadm/lib10_doveadm_acl_plugin.so: Undefined symbol "acl_user_module" (this is usually intentional, so just ignore this message) Debug: Skipping module doveadm_expire_plugin, because dlopen() failed: /usr/local/lib/dovecot/doveadm/lib10_doveadm_expire_plugin.so: Undefined symbol "expire_set_lookup" (this is usually intentional, so just ignore this message) Debug: Skipping module doveadm_quota_plugin, because dlopen() failed: /usr/local/lib/dovecot/doveadm/lib10_doveadm_quota_plugin.so: Undefined symbol "quota_user_module" (this is usually intentional, so just ignore this message) Debug: Module loaded: /usr/local/lib/dovecot/doveadm/lib10_doveadm_sieve_plugin.so Debug: Skipping module doveadm_fts_plugin, because dlopen() failed: /usr/local/lib/dovecot/doveadm/lib20_doveadm_fts_plugin.so: Undefined symbol "fts_filter_filter" (this is usually intentional, so just ignore this message) Debug: Skipping module doveadm_mail_crypt_plugin, because dlopen() failed: /usr/local/lib/dovecot/doveadm/libdoveadm_mail_crypt_plugin.so: Undefined symbol "mail_crypt_user_get_public_key" (this is usually intentional, so just ignore this message) Error: User listing returned failure doveadm: Error: Failed to iterate through some users Ok, so I try the following: # cd /usr/local/virtual && for i in *; do doveadm move -u $i Archive mailbox INBOX BEFORE 90d; done And that works fine. Everything is the same up until the Error but since nothing else is logged, where do I go from here? -- There are strange things done in the midnight sun/By the men who moil for gold; The Arctic trails have their secret tales/That would make your blood run cold; The Northern Lights have seen queer sights,/But the queerest they ever did see Was the night on the marge of Lake Lebarge/ When I cremated Sam McGee

2 4

Cannot connect to DOVECOT from Roundcube using SSL on Port 993
by zahn 19 Jun '19

19 Jun '19

Hello I try to connect to dovecot from roundcube using this setup: $config['default_host'] = 'ssl://chogolisa.akadia.com'; $config['default_port'] = 993; and I get the following error message from dovecot: Jun 19 11:30:21 chogolisa dovecot: imap-login: Disconnected (no auth attempts in 0 secs): user=<>, rip=84.253.50.195, lip=84.253.50.195, TLS handshaking: Connection closed, session=<wEra4KmLm+ZU/TLD> When I try to connect from: $config['default_host'] = 'tls://chogolisa.akadia.com'; $config['default_port'] = 143; it works ! Roundcube: 1.0.12 Dovecot: 2.3.6 Can you help me ? -- Schöne Grüsse aus Oberdiessbach Martin Zahn Akadia AG Martin Zahn Software Ing. HTL Oracle Certificate Professional Information Technology Fichtenweg 10 CH-3672 Oberdiessbach Tel: +41 79 410 27 87 Web: www.akadia.com E-Mail: martin.zahn(a)akadia.com

2 1

Shared mailbox: share whole inbox
by Zdeněk Sobotka 19 Jun '19

19 Jun '19

Hi, I'd like to share the whole INBOX of one user with another. That should go through: doveadm acl add -u user1(a)example.cz SharedDirectory user=user2(a)example.cz lookup read insert It's works fine, when I connect through imap I see: . list "" "*"* LIST (\Noselect \HasChildren) "/" shared* LIST (\Noselect \HasChildren) "/" shared/example.cz/name.surname* LIST (\HasNoChildren) "/" shared/example.cz/name.surname/SharedDirectory* LIST (\HasNoChildren) "/" INBOX. OK List completed (0.000 + 0.000 secs). But now I would like to share the whole INBOX by: doveadm acl delete -u user1(a)example.cz SharedDirectory user1(a)example.cz 2 list "" "*" * LIST (\HasNoChildren) "/" INBOX 2 OK List completed (0.000 + 0.000 + 0.002 secs). doveadm acl add -u user1(a)example.cz INBOX user=user2(a)example.cz lookup read insert 2 list "" "*" * LIST (\HasNoChildren) "/" INBOX 2 OK List completed (0.000 + 0.000 + 0.002 secs). But it doesn't do what I expected, IMAP output it's the same and INBOX in shared folder is not subscribed. I'm looking for help to debug what might be wrong. Thanks. Z. auth_cache_size = 10 M auth_default_realm = %d auth_mechanisms = plain login auth_realms = example.cz default_client_limit = 1024 default_process_limit = 1024 dict { acl = pgsql:/etc/dovecot/postgre-acl.conf } mail_location = maildir:/var/vmail/%d/%n/Maildir mail_plugins = acl listescape zlib 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 namespace { list = children location = maildir:/var/vmail/%%d/%%n/Maildir:INDEX=/var/vmail/%d/%n/Maildir/shared/%%d/%%n:INDEXPVT=/var/vmail/%d/%n/Maildir/shared/%%d/%%n prefix = shared/%%d/%%n/ separator = / subscriptions = no type = shared } namespace inbox { inbox = yes location = prefix = separator = / type = private } passdb { args = /etc/dovecot/dovecot-ldap_people.conf.ext driver = ldap } plugin { acl = vfile acl_shared_dict = proxy::acl recipient_delimiter = + sieve = file:/var/vmail/%d/%n/Maildir/sieve;active=/var/vmail/%d/%n/Maildir/dovecot.sieve sieve_before = /usr/local/etc/dovecot/default.sieve sieve_default = /usr/local/etc/dovecot/default.sieve sieve_extensions = +notify +imapflags +duplicate sieve_trace_debug = yes sieve_trace_level = matching sieve_user_log = file:/var/vmail/%d/%n/Maildir/sieve/sieve_user.log } protocols = " imap lmtp sieve" service auth-worker { user = root } service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0660 user = postfix } unix_listener auth-userdb { group = postfix mode = 0660 user = postfix } user = dovecot } service dict { unix_listener dict { mode = 0600 user = vmail } } service imap-login { inet_listener imap { port = 143 } inet_listener imaps { port = 993 ssl = yes } vsz_limit = 1 G } service imap { vsz_limit = 1 G } service lmtp { executable = lmtp -L process_min_avail = 10 unix_listener /var/spool/postfix/private/dovecot-lmtp { group = postfix mode = 0600 user = postfix } } service managesieve-login { inet_listener sieve { port = 4190 } process_min_avail = 1 service_count = 1 vsz_limit = 64 M } ssl_ca = < /etc/ssl/certs/mail.example.cz/mail.example.cz.intermediate.crt ssl_cert = < /etc/ssl/certs/mail.example.cz/mail.example.cz.crt 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_key = # hidden, use -P to show it ssl_prefer_server_ciphers = yes userdb { args = /etc/dovecot/dovecot-ldap_people.conf.ext driver = ldap } protocol lmtp { info_log_path = /var/log/dovecot/dovecot-lmtp.log log_path = /var/log/dovecot/dovecot-lmtp-errors.log mail_plugins = acl listescape zlib quota sieve postmaster_address = admins(a)example.cz } protocol imap { mail_max_userip_connections = 500 mail_plugins = acl listescape zlib imap_acl } protocol sieve { info_log_path = /var/log/dovecot-sieve.log log_path = /var/log/dovecot-sieve-errors.log mail_max_userip_connections = 100 managesieve_implementation_string = Dovecot Pigeonhole managesieve_max_line_length = 65536 }

1 0

Converting mdbox to mbox/MailDir
by Adam Raszkiewicz 19 Jun '19

19 Jun '19

Is there any way to convert Dovecot's mdbox/dbox to mbox, MailDir or eml format (or any other easy to import format)? Thanks, Adam

3 5

per-user mail_max_userip_connections in userdb extra fields
by Eirik Rye 18 Jun '19

18 Jun '19

Hi, The documentation at https://wiki.dovecot.org/UserDatabase/ExtraFields states that "It's possible to override settings from dovecot.conf", as well as the following: > If you want to override settings inside sections, you can separate the > section name and key with '/'. For example: > > namespace default { > inbox = yes > separator = . > location = maildir:~/Maildir > } > > The separator setting can be overridden by returning namespace/default/separator=. extra field. As such, we would expect for it to be possible to override mail_max_userip_connections under the "protocol imap" section, with a passwdfile userdb looking something like this: example:{CRYPT}x:1011:1011::/mail/example::userdb_protocol/imap/mail_max_userip_connections=100 The userdb returns the expected fields in the correct format (according to the documentation): # doveadm user -u example userdb: example user : example uid : 1011 gid : 1011 home : /mail/example protocol/imap/mail_max_userip_connections: 100 However, this new setting is not honoured. To test, I set "mail_max_userip_connections=1" in 20-imap.conf, and noticed that my second connection was closed with the following error: dovecot[13573]: imap-login: Maximum number of connections from user+IP exceeded (mail_max_userip_connections=1) I also attempted the same setting, without the "protocol/imap" prefix. Is this not possible? Are there restrictions to what settings may be overridden in userdb? The documentation appears to suggest that there isn't. Best regards, Eirik Rye

1 0

Dovecot LMTP rejecting mail from address with apostrophe
by Michal Krzysztofowicz 18 Jun '19

18 Jun '19

Hi, I have an OpenSMTPD / Dovecot installation on an OpenBSD server. I recently came across an issue where Dovecot LMTP would reject a message sent to a local user from an address which contains a single apostrophe (e.g. firstname.o'lastname(a)example.com) Apparently apostrophe, as well as a number of other special characters, are valid characters in the local part of the email address (that's everything to the left of the @ character). The message I get in the logs is: Jun 14 11:57:34 atlantic smtpd[42606]: 21749fd12ac76b57 mda delivery evpid=56aed6237d6444a0 from=<firstname.o'lastname(a)example.com> to=<me(a)example.org> rcpt=<me(a)example.org> user=me delay=0s result=PermFail stat=Error ("mail.lmtp: LMTP server error: 501 5.5.4 Invalid FROM: Invalid character in localpart") where example.com is external domain and example.org is a local one. The part of the message: LMTP server error: 501 5.5.4 Invalid FROM: Invalid character in localpart is returned by dovecot-lmtp. I’ve had a brief look at the source code, and it seems the responsible code is somewhere inside src/lib-smtp/smtp-address.c and, if I understand the code correctly, the address parsing in actually done in src/lib-smtp/smtp-parser.c. My question is is there a configuration option, similar to auth_username_chars which lists valid characters in the email address, to stop Dovecot LMTP from rejecting such emails? or maybe you know another way of getting it to accept an email from such address? My dovecot version is: $ dovecot --version 2.3.5.1 (7ec6d0ade) And in case that makes any difference, I'm running OpenBSD 6.5 patched to 005_libssl. Thanks! Mike -- Michal Krzysztofowicz http://beautifulocean.org/

3 7

Problem syncing e-mails with Outlook
by Odhiambo Washington 18 Jun '19

18 Jun '19

Hello all, I am running dovecot- 2.3.5.2 with mdbox storage. I deleted the dovecot.index* from all my folders, which led to mails not being displayed. I rebuilt the indexes for all the users after that, using: doveadm force-resync -u user@domain "*" However, the problem now is that Outlook,configured for IMAP, is not able to sync the mails with the server. I can login to the server using webmail and I see all the e-mails listed. However, when I connect outlook, it does not sync all these e-mails. I am seeing the errors below. Not sure how to fix that. Jun 18 11:23:34 imap(technical(a)mydomain.co.ke)<59754><g5UC1JSLPhkpUFt/>: Error: Corrupted record in index cache file /var/spool/virtual/ mydomain.co.ke/technical/mdbox/mailboxes/INBOX/dbox-Mails/dovecot.index.cache: UID 29: Broken virtual size in mailbox INBOX: read(/var/spool/virtual/ mydomain.co.ke/technical/mdbox/storage/m.1): FETCH BODY[] got too little data: 131524 vs 772408 Jun 18 11:23:45 imap(sales(a)mydomain.co.ke)<59812><aeLI1JSLoe3FsVm2>: Error: Corrupted record in index cache file /var/spool/virtual/ mydomain.co.ke/sales/mdbox/mailboxes/INBOX/dbox-Mails/dovecot.index.cache: UID 25: Broken virtual size in mailbox INBOX: read(/var/spool/virtual/ mydomain.co.ke/sales/mdbox/storage/m.552): FETCH BODY[] got too little data: 17130 vs 370736 Jun 18 11:24:03 imap(technical(a)mydomain.co.ke)<59891><uJHS1ZSLchkpUFt/>: Error: Corrupted record in index cache file /var/spool/virtual/ mydomain.co.ke/technical/mdbox/mailboxes/INBOX/dbox-Mails/dovecot.index.cache: UID 29: Broken virtual size in mailbox INBOX: read(/var/spool/virtual/ mydomain.co.ke/technical/mdbox/storage/m.1): FETCH BODY[] got too little data: 131524 vs 772408 Jun 18 11:24:12 imap(sales(a)mydomain.co.ke)<59933><q/9j1pSL3e3FsVm2>: Error: Corrupted record in index cache file /var/spool/virtual/ mydomain.co.ke/sales/mdbox/mailboxes/INBOX/dbox-Mails/dovecot.index.cache: UID 25: Broken virtual size in mailbox INBOX: read(/var/spool/virtual/ mydomain.co.ke/sales/mdbox/storage/m.552): FETCH BODY[] got too little data: 17130 vs 370736 Jun 18 11:24:40 imap(sales(a)mydomain.co.ke)<60053><DuQT2JSL9+3FsVm2>: Error: Corrupted record in index cache file /var/spool/virtual/ mydomain.co.ke/sales/mdbox/mailboxes/INBOX/dbox-Mails/dovecot.index.cache: UID 25: Broken virtual size in mailbox INBOX: read(/var/spool/virtual/ mydomain.co.ke/sales/mdbox/storage/m.552): FETCH BODY[] got too little data: 17130 vs 370736 Jun 18 11:24:49 imap(technical(a)mydomain.co.ke)<60079><ChRu2JSLrxkpUFt/>: Error: Corrupted record in index cache file /var/spool/virtual/ mydomain.co.ke/technical/mdbox/mailboxes/INBOX/dbox-Mails/dovecot.index.cache: UID 29: Broken virtual size in mailbox INBOX: read(/var/spool/virtual/ mydomain.co.ke/technical/mdbox/storage/m.1): FETCH BODY[] got too little data: 131524 vs 772408 Jun 18 11:25:09 imap(sales(a)mydomain.co.ke)<60184><i9HC2ZSLEe7FsVm2>: Error: Corrupted record in index cache file /var/spool/virtual/ mydomain.co.ke/sales/mdbox/mailboxes/INBOX/dbox-Mails/dovecot.index.cache: UID 25: Broken virtual size in mailbox INBOX: read(/var/spool/virtual/ mydomain.co.ke/sales/mdbox/storage/m.552): FETCH BODY[] got too little data: 17130 vs 370736 Jun 18 11:25:13 imap(technical(a)mydomain.co.ke)<60204><sPL32ZSLx/cpUFt/>: Error: Corrupted record in index cache file /var/spool/virtual/ mydomain.co.ke/technical/mdbox/mailboxes/INBOX/dbox-Mails/dovecot.index.cache: UID 29: Broken virtual size in mailbox INBOX: read(/var/spool/virtual/ mydomain.co.ke/technical/mdbox/storage/m.1): FETCH BODY[] got too little data: 131524 vs 772408 Jun 18 11:25:42 imap(technical(a)mydomain.co.ke)<60328><QFm325SL9fcpUFt/>: Error: Corrupted record in index cache file /var/spool/virtual/ mydomain.co.ke/technical/mdbox/mailboxes/INBOX/dbox-Mails/dovecot.index.cache: UID 29: Broken virtual size in mailbox INBOX: read(/var/spool/virtual/ mydomain.co.ke/technical/mdbox/storage/m.1): FETCH BODY[] got too little data: 131524 vs 772408 Jun 18 11:26:03 imap(sales(a)mydomain.co.ke)<60358><9ckk3JSLLe7FsVm2>: Error: Corrupted record in index cache file /var/spool/virtual/ mydomain.co.ke/sales/mdbox/mailboxes/INBOX/dbox-Mails/dovecot.index.cache: UID 25: Broken virtual size in mailbox INBOX: read(/var/spool/virtual/ mydomain.co.ke/sales/mdbox/storage/m.552): FETCH BODY[] got too little data: 17130 vs 370736 Jun 18 11:26:11 imap(technical(a)mydomain.co.ke)<60455><SKRs3ZSLJfgpUFt/>: Error: Corrupted record in index cache file /var/spool/virtual/ mydomain.co.ke/technical/mdbox/mailboxes/INBOX/dbox-Mails/dovecot.index.cache: UID 29: Broken virtual size in mailbox INBOX: read(/var/spool/virtual/ mydomain.co.ke/technical/mdbox/storage/m.1): FETCH BODY[] got too little data: 131524 vs 772408 Jun 18 11:26:32 imap(sales(a)mydomain.co.ke)<60548><SAy/3pSLjO7FsVm2>: Error: Corrupted record in index cache file /var/spool/virtual/ mydomain.co.ke/sales/mdbox/mailboxes/INBOX/dbox-Mails/dovecot.index.cache: UID 25: Broken virtual size in mailbox INBOX: read(/var/spool/virtual/ mydomain.co.ke/sales/mdbox/storage/m.552): FETCH BODY[] got too little data: 17130 vs 370736 Jun 18 11:26:33 imap(technical(a)mydomain.co.ke)<60553><j3HE3pSLKBspUFt/>: Error: Corrupted record in index cache file /var/spool/virtual/ mydomain.co.ke/technical/mdbox/mailboxes/INBOX/dbox-Mails/dovecot.index.cache: UID 29: Broken virtual size in mailbox INBOX: read(/var/spool/virtual/ mydomain.co.ke/technical/mdbox/storage/m.1): FETCH BODY[] got too little data: 131524 vs 772408 Jun 18 11:26:45 imap(technical(a)mydomain.co.ke)<60602><p49635SLUhspUFt/>: Error: Corrupted record in index cache file /var/spool/virtual/ mydomain.co.ke/technical/mdbox/mailboxes/INBOX/dbox-Mails/dovecot.index.cache: UID 29: Broken virtual size in mailbox INBOX: read(/var/spool/virtual/ mydomain.co.ke/technical/mdbox/storage/m.1): FETCH BODY[] got too little data: 131524 vs 772408 Jun 18 11:26:51 imap(technical(a)mydomain.co.ke)<60629><NO/K35SLWBspUFt/>: Error: Corrupted record in index cache file /var/spool/virtual/ mydomain.co.ke/technical/mdbox/mailboxes/INBOX/dbox-Mails/dovecot.index.cache: UID 29: Broken virtual size in mailbox INBOX: read(/var/spool/virtual/ mydomain.co.ke/technical/mdbox/storage/m.1): FETCH BODY[] got too little data: 131524 vs 772408 Jun 18 11:26:58 imap(technical(a)mydomain.co.ke)<60660><46ou4JSLa/gpUFt/>: Error: Corrupted record in index cache file /var/spool/virtual/ mydomain.co.ke/technical/mdbox/mailboxes/INBOX/dbox-Mails/dovecot.index.cache: UID 29: Broken virtual size in mailbox INBOX: read(/var/spool/virtual/ mydomain.co.ke/technical/mdbox/storage/m.1): FETCH BODY[] got too little data: 131524 vs 772408 Jun 18 11:27:01 imap(sales(a)mydomain.co.ke)<60678><Sxpv4JSLm+7FsVm2>: Error: Corrupted record in index cache file /var/spool/virtual/ mydomain.co.ke/sales/mdbox/mailboxes/INBOX/dbox-Mails/dovecot.index.cache: UID 25: Broken virtual size in mailbox INBOX: read(/var/spool/virtual/ mydomain.co.ke/sales/mdbox/storage/m.552): FETCH BODY[] got too little data: 17130 vs 370736 Jun 18 11:27:31 imap(sales(a)mydomain.co.ke)<60809><atU54pSLwe7FsVm2>: Error: Corrupted record in index cache file /var/spool/virtual/ mydomain.co.ke/sales/mdbox/mailboxes/INBOX/dbox-Mails/dovecot.index.cache: UID 25: Broken virtual size in mailbox INBOX: read(/var/spool/virtual/ mydomain.co.ke/sales/mdbox/storage/m.552): FETCH BODY[] got too little data: 17130 vs 370736 Jun 18 11:27:59 imap(sales(a)mydomain.co.ke)<60932><9LLs45SL3u7FsVm2>: Error: Corrupted record in index cache file /var/spool/virtual/ mydomain.co.ke/sales/mdbox/mailboxes/INBOX/dbox-Mails/dovecot.index.cache: UID 25: Broken virtual size in mailbox INBOX: read(/var/spool/virtual/ mydomain.co.ke/sales/mdbox/storage/m.552): FETCH BODY[] got too little data: 17130 vs 370736 Jun 18 11:28:49 imap(sales(a)mydomain.co.ke)<61091><ekYq5pSLDO/FsVm2>: Error: Corrupted record in index cache file /var/spool/virtual/ mydomain.co.ke/sales/mdbox/mailboxes/INBOX/dbox-Mails/dovecot.index.cache: UID 25: Broken virtual size in mailbox INBOX: read(/var/spool/virtual/ mydomain.co.ke/sales/mdbox/storage/m.552): FETCH BODY[] got too little data: 17130 vs 370736 Jun 18 11:29:05 imap(sales(a)mydomain.co.ke)<61225><qenN55SLoLC5HrCp>: Error: Corrupted record in index cache file /var/spool/virtual/ mydomain.co.ke/sales/mdbox/mailboxes/Sent Items/dbox-Mails/dovecot.index.cache: UID 1853: Broken virtualsize in mailbox Sent Items: read(/var/spool/virtual/ mydomain.co.ke/sales/mdbox/storage/m.254): FETCH BODY[] got too little data: 3510 vs 1068172 Jun 18 11:29:15 imap(sales(a)mydomain.co.ke)<61272><Sb1s6JSLSe/FsVm2>: Error: Corrupted record in index cache file /var/spool/virtual/ mydomain.co.ke/sales/mdbox/mailboxes/INBOX/dbox-Mails/dovecot.index.cache: UID 25: Broken virtual size in mailbox INBOX: read(/var/spool/virtual/ mydomain.co.ke/sales/mdbox/storage/m.552): FETCH BODY[] got too little data: 17130 vs 370736 Jun 18 11:29:43 imap(sales(a)mydomain.co.ke)<61393><FJIc6pSLfO/FsVm2>: Error: Corrupted record in index cache file /var/spool/virtual/ mydomain.co.ke/sales/mdbox/mailboxes/INBOX/dbox-Mails/dovecot.index.cache: UID 25: Broken virtual size in mailbox INBOX: read(/var/spool/virtual/ mydomain.co.ke/sales/mdbox/storage/m.552): FETCH BODY[] got too little data: 17130 vs 370736 Jun 18 11:30:13 imap(sales(a)mydomain.co.ke)<61532><WGve65SLx+/FsVm2>: Error: Corrupted record in index cache file /var/spool/virtual/ mydomain.co.ke/sales/mdbox/mailboxes/INBOX/dbox-Mails/dovecot.index.cache: UID 25: Broken virtual size in mailbox INBOX: read(/var/spool/virtual/ mydomain.co.ke/sales/mdbox/storage/m.552): FETCH BODY[] got too little data: 17130 vs 370736 Jun 18 11:30:39 imap(sales(a)mydomain.co.ke)<61647><e2x47ZSL+e/FsVm2>: Error: Corrupted record in index cache file /var/spool/virtual/ mydomain.co.ke/sales/mdbox/mailboxes/INBOX/dbox-Mails/dovecot.index.cache: UID 25: Broken virtual size in mailbox INBOX: read(/var/spool/virtual/ mydomain.co.ke/sales/mdbox/storage/m.552): FETCH BODY[] got too little data: 17130 vs 370736 Jun 18 11:31:10 imap(sales(a)mydomain.co.ke)<61782><+L4175SLI/DFsVm2>: Error: Corrupted record in index cache file /var/spool/virtual/ mydomain.co.ke/sales/mdbox/mailboxes/INBOX/dbox-Mails/dovecot.index.cache: UID 25: Broken virtual size in mailbox INBOX: read(/var/spool/virtual/ mydomain.co.ke/sales/mdbox/storage/m.552): FETCH BODY[] got too little data: 17130 vs 370736 Jun 18 11:31:36 imap(sales(a)mydomain.co.ke)<61905><pK/W8JSLafDFsVm2>: Error: Corrupted record in index cache file /var/spool/virtual/ mydomain.co.ke/sales/mdbox/mailboxes/INBOX/dbox-Mails/dovecot.index.cache: UID 25: Broken virtual size in mailbox INBOX: read(/var/spool/virtual/ mydomain.co.ke/sales/mdbox/storage/m.552): FETCH BODY[] got too little data: 17130 vs 370736 Jun 18 11:31:36 imap(technical(a)mydomain.co.ke)<61899><TnXN8JSLifopUFt/>: Error: Corrupted record in index cache file /var/spool/virtual/ mydomain.co.ke/technical/mdbox/mailboxes/INBOX/dbox-Mails/dovecot.index.cache: UID 29: Broken virtual size in mailbox INBOX: read(/var/spool/virtual/ mydomain.co.ke/technical/mdbox/storage/m.1): FETCH BODY[] got too little data: 131524 vs 772408 Jun 18 11:31:37 imap(sales(a)mydomain.co.ke)<61897><IgvJ8JSL4h0pUFt/>: Error: Corrupted record in index cache file /var/spool/virtual/ mydomain.co.ke/sales/mdbox/mailboxes/INBOX/dbox-Mails/dovecot.index.cache: UID 25: Broken virtual size in mailbox INBOX: read(/var/spool/virtual/ mydomain.co.ke/sales/mdbox/storage/m.552): FETCH BODY[] got too little data: 17130 vs 370736 Jun 18 11:31:37 imap(technical(a)mydomain.co.ke)<61916><xhby8JSL6h0pUFt/>: Error: Corrupted record in index cache file /var/spool/virtual/ mydomain.co.ke/technical/mdbox/mailboxes/Deleted Items/dbox-Mails/dovecot.index.cache: UID 2: Broken virtual size in mailbox Deleted Items: read(/var/spool/virtual/ mydomain.co.ke/technical/mdbox/storage/m.460): FETCH BODY[] got too little data: 10123 vs 197577 Jun 18 11:31:37 imap(technical(a)mydomain.co.ke)<61919><hSf38JSL7B0pUFt/>: Error: Corrupted record in index cache file /var/spool/virtual/ mydomain.co.ke/technical/mdbox/mailboxes/Sent Items/dbox-Mails/dovecot.index.cache: UID 2: Broken virtual size in mailbox Sent Items: read(/var/spool/virtual/ mydomain.co.ke/technical/mdbox/storage/m.2): FETCH BODY[] got too little data: 3620 vs 817692 Jun 18 11:31:40 imap(sales(a)mydomain.co.ke)<61924><cEP+8JSL7h0pUFt/>: Error: Corrupted record in index cache file /var/spool/virtual/ mydomain.co.ke/sales/mdbox/mailboxes/Sent Items/dbox-Mails/dovecot.index.cache: UID 1: Broken virtual size in mailbox Sent Items: read(/var/spool/virtual/mydomain.co.ke/sales/mdbox/storage/m.24): FETCH BODY[] got too little data: 5202 vs 1196884 Jun 18 11:31:44 imap(sales(a)mydomain.co.ke)<61937><bd8o8ZSL8B0pUFt/>: Error: Corrupted record in index cache file /var/spool/virtual/ mydomain.co.ke/sales/mdbox/mailboxes/Sent/dbox-Mails/dovecot.index.cache: UID 9: Broken virtual size in mailbox Sent: read(/var/spool/virtual/ mydomain.co.ke/sales/mdbox/storage/m.255): FETCH BODY[] got too little data: 46155 vs 1156185 Jun 18 11:31:46 imap(sales(a)mydomain.co.ke)<61962><cMlt8ZSLqfopUFt/>: Error: Corrupted record in index cache file /var/spool/virtual/ mydomain.co.ke/sales/mdbox/mailboxes/Trash/dbox-Mails/dovecot.index.cache: UID 8: Broken virtual size in mailbox Trash: read(/var/spool/virtual/ mydomain.co.ke/sales/mdbox/storage/m.657): FETCH BODY[] got too little data: 107289 vs 1338249 Jun 18 11:32:07 imap(sales(a)mydomain.co.ke)<62063><ZEiZ8pSLn/DFsVm2>: Error: Corrupted record in index cache file /var/spool/virtual/ mydomain.co.ke/sales/mdbox/mailboxes/INBOX/dbox-Mails/dovecot.index.cache: UID 25: Broken virtual size in mailbox INBOX: read(/var/spool/virtual/ mydomain.co.ke/sales/mdbox/storage/m.552): FETCH BODY[] got too little data: 17130 vs 370736 -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", grep ^[^#] :-)

1 0

Deleted dovecot.index.*
by Odhiambo Washington 17 Jun '19

17 Jun '19

I'm using mdbox. What's the consequence of deleting dovecot.index.* from all folders? All mail gets lost or I can rebuild the indexes and get the mails?

3 6

mailbox encryption
by David Mehler 17 Jun '19

17 Jun '19

Hello, I've got dovecot 2.3 going, and I've got a file 10-mailcrypt.conf which is loading mail_crypt, thinking that that plugin would propagate through all the services, sieve, lmtp, and mailbox message storage. I'm not seeing anything in the logs indicating that the encryption is happening. I am using a file format dbox specifically sdbox format, and in my mailbox I am seeing files like u.5 and others, a file check on them reveals them as data. Should I be seeing encryption in the logs? Thanks. Dave.

2 3

LDA vs LMTP change in header
by ＠lbutlr 17 Jun '19

17 Jun '19

Switching to dovecot LMTP appears to have change the information in the received header, which appears to be causing my spam filter to wig out and mark local to local emails as spam. Here’s what the received header used to look like: Received: from [10.0.5.3] (c-71-229-144-93.hsd1.co.comcast.net [71.229.144.93]) by mail.covisp.net (Postfix) with ESMTPS id B67B8118AD59 for <kreme(a)kreme.com>; Sun, 16 Aug 2009 22:19:02 -0600 (MDT) As opposed to now: Received: from darth.lan (c-73-14.161.160.hsd1.co.comcast.net [73.14.161.160]) by mail.covisp.net(Postfix 3.4.5/8.13.0) with SMTP id unknown; Sun, 16 Jun 2019 15:26:32 -0600 (envelope-from <kreme(a)kreme.com>) The first has an ESMTPS id and the other has SMTP id unknown, which seems to be causing Spamass-milter to treat the LMTP emails as unauthenticated and then ding them for being from public IPs. -- Thanks to the human heart by which we live, Thanks to its tenderness, its joys, and fears, To me the meanest flower that blows can give Thoughts that do often lie too deep for tears

1 0

What does Solr index do and how to handle its high avaliablity?
by luckydog xf 17 Jun '19

17 Jun '19

Hi, guys, Can you give me an example of solr usage in dovecot? As far as I know, you can search email easily by MUA like outlook, so which role does solr play? And based on https://dovecot.org/pipermail/dovecot/2019-April/115575.html I'm going to use an VIP to host 2 mail servers. Currently, it works in fail over and fail back test except solr index, so how to resolve this? Is it possible to put dovecot index on shared storage like NFS? How to if it's a yes. It seems it's under /var/solr/data/dovecot/data/ How to rebuild if I don't put index data on shared storage in case of fail over? Thanks,

2 3

Dovecot, quota, warning, and issue with setup?
by David Mehler 16 Jun '19

16 Jun '19

Hello, I'm having an issue or two with my new Dovecot setup. I'm running version 2.3.6 new setup, and using sdbox as the mailbox format. I'm getting the following warning: Jun 16 13:57:16 mail dovecot[9583]: lmtp(59153): Warning: quota: Namespace '' is not Maildir, skipping for Maildir++ quota Jun 16 13:57:16 mail dovecot[9583]: lmtp(username(a)example.net)<59153><rjVgD/yCBl0R5wAATNUJJw>: Warning: quota: Namespace '' is not Maildir, skipping for Maildir++ quota I'm also having issue with the public folder, it's not showing up. Below is my doveconf -n output. Any suggestions welcome. Thanks. Dave. # 2.3.6 (7eab80676): /usr/local/etc/dovecot/dovecot.conf # Pigeonhole version 0.5.6 (92dc263a) # OS: FreeBSD 12.0-RELEASE-p4 amd64 # Hostname: mail.example.local auth_cache_size = 10 M auth_default_realm = example.net auth_mechanisms = plain login auth_realms = example.net example.com dict { acl = mysql:/usr/local/etc/dovecot/dovecot-dict-sql.conf.ext quota = mysql:/usr/local/etc/dovecot/dovecot-dict-sql.conf.ext } first_valid_gid = 2100 first_valid_uid = 2100 hostname = mail.example.net imap_client_workarounds = delay-newmail tb-extra-mailbox-sep tb-lsub-flags imap_idle_notify_interval = 29 mins last_valid_gid = 2100 last_valid_uid = 2100 lda_mailbox_autocreate = yes lda_mailbox_autosubscribe = yes lda_original_recipient_header = X-Original-To listen = 172.16.21.3 lmtp_rcpt_check_quota = yes log_timestamp = "%Y-%m-%d %H:%M:%S " mail_access_groups = vmail mail_fsync = never mail_gid = vmail mail_home = /var/vmail/mailboxes/%d/%n mail_location = dbox:~/sdbox mail_plugins = acl fts fts_lucene mail_log notify quota trash virtual welcome zlib mail_crypt mail_privileged_group = vmail mail_server_admin = mailto:postmaster@example.net mail_uid = vmail 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 spamtest spamtestplus virustest editheader imapflags notify imapsieve vnd.dovecot.imapsieve namespace { location = sdbox:/var/vmail/public/:CONTROL=~/sdbox/public:INDEX=~/sdbox/public prefix = Public/ separator = / subscriptions = yes type = public } namespace inbox { inbox = yes location = mailbox Drafts { auto = subscribe special_use = \Drafts } mailbox Sent { auto = subscribe special_use = \Sent } mailbox Spam { auto = subscribe autoexpunge = 30 days special_use = \Junk } mailbox Trash { auto = subscribe autoexpunge = 30 days special_use = \Trash } prefix = separator = / type = private } passdb { args = /usr/local/etc/dovecot/dovecot-sql.conf.ext driver = sql } plugin { acl = vfile acl_shared_dict = proxy::acl fts = lucene fts_autoindex = yes fts_autoindex_exclude = \Junk fts_autoindex_exclude2 = \Trash fts_autoindex_exclude3 = \Spam fts_autoindex_max_recent_msgs = 80 fts_index_timeout = 90 fts_lucene = whitespace_chars=@. normalize no_snowball imapsieve_mailbox1_before = file:/var/vmail/sieve/global/learn-spam.sieve imapsieve_mailbox1_causes = COPY imapsieve_mailbox1_name = Spam imapsieve_mailbox2_before = file:/var/vmail/sieve/global/learn-ham.sieve imapsieve_mailbox2_causes = COPY imapsieve_mailbox2_from = Spam imapsieve_mailbox2_name = * mail_crypt_curve = prime256v1 mail_crypt_global_private_key = # hidden, use -P to show it mail_crypt_global_public_key = # hidden, use -P to show it mail_crypt_save_version = 2 mail_log_events = delete undelete expunge copy mailbox_delete mailbox_rename mail_log_fields = uid box msgid size quota = maildir:User quota quota_exceeded_message = Storage quota for this account has been exceeded, please try again later. quota_grace = 10%% quota_rule2 = Trash:ignore quota_status_nouser = DUNNO quota_status_overquota = 552 5.2.2 Mailbox is full quota_status_success = DUNNO quota_vsizes = true quota_warning = storage=100%% quota-exceeded 100 %u quota_warning2 = storage=95%% quota-warning 95 %u quota_warning3 = storage=90%% quota-warning 90 %u quota_warning4 = storage=85%% quota-warning 85 %u quota_warning5 = storage=75%% quota-warning 75 %u sieve = file:/var/vmail/sieve/%d/%n/scripts;active=/var/vmail/sieve/%d/%n/active-script.sieve sieve_after = /home/vmail/sieve/after.d sieve_before = /var/vmail/sieve/global/spam-global.sieve sieve_extensions = +notify +imapflags +spamtest +spamtestplus +virustest +editheader sieve_global_dir = /home/vmail/sieve sieve_global_extensions = +vnd.dovecot.pipe +vnd.dovecot.execute +vnd.dovecot.environment sieve_max_redirects = 30 sieve_max_script_size = 1M sieve_pipe_bin_dir = /usr/bin sieve_plugins = sieve_imapsieve sieve_extprograms sieve_spamtest_max_header = X-Spamd-Result: default: [[:alnum:]]+ \[-?[[:digit:]]+\.[[:digit:]]+ / (-?[[:digit:]]+\.[[:digit:]]+)\] sieve_spamtest_status_header = X-Spamd-Result: default: [[:alnum:]]+ \[(-?[[:digit:]]+\.[[:digit:]]+) / -?[[:digit:]]+\.[[:digit:]]+\] sieve_spamtest_status_type = score sieve_user_log = /home/vmail/sieve/sieve_error.log sieve_virustest_status_header = X-Virus-Scan: Found to be (.+)\. sieve_virustest_status_type = text sieve_virustest_text_value1 = clean sieve_virustest_text_value5 = infected trash = /usr/local/etc/dovecot/trash.conf welcome_script = welcome %u postmaster@%d welcome_wait = yes } postmaster_address = postmaster(a)example.net protocols = imap lmtp sieve sendmail_path = /usr/local/sbin/sendmail service auth-worker { user = vmail } service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0660 user = postfix } unix_listener auth-userdb { group = vmail mode = 0666 user = vmail } } service dict { unix_listener dict { mode = 0600 user = vmail } user = root } service imap-login { inet_listener imap { port = 143 } inet_listener imaps { port = 993 ssl = yes } process_min_avail = 1 } service imap { executable = imap } service lmtp { executable = lmtp unix_listener /var/spool/postfix/private/dovecot-lmtp { group = postfix mode = 0660 user = postfix } } service managesieve-login { inet_listener sieve { address = 172.16.21.3 port = 4190 } } service quota-status { client_limit = 1 executable = quota-status -p postfix unix_listener /var/spool/postfix/private/dovecot-quota { group = postfix mode = 0660 user = postfix } } service quota-warning { executable = script /usr/local/etc/dovecot/quota-warning.sh unix_listener quota-warning { group = vmail mode = 0660 user = vmail } user = vmail } service welcome { executable = script /usr/local/etc/dovecot/welcome.sh unix_listener welcome { user = vmail } user = vmail } ssl = required ssl_cert = </usr/local/etc/ssl/acme.sh/example.net/fullchain.crt ssl_cipher_list = ECDH+AESGCM:ECDH+CHACHA20:ECDH+AES256:ECDH+AES128:!aNULL:!SHA1 ssl_curve_list = P-256 ssl_dh = # hidden, use -P to show it ssl_key = # hidden, use -P to show it ssl_min_protocol = TLSv1.2 ssl_options = no_ticket ssl_prefer_server_ciphers = yes userdb { args = /usr/local/etc/dovecot/dovecot-sql.conf.ext driver = sql } protocol lmtp { info_log_path = /var/log/dovecot/dovecot-lmtp.log log_path = /var/log/dovecot/dovecot-lmtp-errors.log mail_fsync = optimized mail_plugins = acl fts fts_lucene mail_log notify quota trash virtual welcome zlib mail_crypt sieve } protocol lda { mail_fsync = optimized mail_plugins = acl fts fts_lucene mail_log notify quota trash virtual welcome zlib mail_crypt sieve } protocol imap { mail_max_userip_connections = 20 mail_plugins = acl fts fts_lucene mail_log notify quota trash virtual welcome zlib mail_crypt imap_acl imap_quota imap_sieve imap_zlib last_login } protocol sieve { info_log_path = /var/log/dovecot/dovecot-sieve.log log_path = /var/log/dovecot/dovecot-sieve-errors.log }

2 1

Self-signed TLS client certificates
by Marvin Gülker 16 Jun '19

16 Jun '19

Dear List, I self-host my e-mail and run Dovecot since ever I do that. Dovecot version is 2.3.4.1 (f79e8e7e4), running on Debian testing. Now I am trying to configure Dovecot for client TLS certificates. I have a self-signed certificate whose private key resides on a smartcard (Yubikey, to be exact). I wanted Dovecot to accept that TLS client certificate instead of a password. So I searched and found this wiki page: <https://wiki2.dovecot.org/SSL/DovecotConfiguration#Client_certificate_verif…> But that Wiki page says: > The CA file should contain the certificate(s) followed by the matching > CRL(s). Note that the CRLs are required to exist. I have now messed three hours or so with OpenSSL to get a CRL generated for my self-signed certificate, but I can't get that to work (the problem appearently being that OpenSSL doesn't play well with private keys on smartcards). It doesn't make sense anyway, why does one need a CRL for a self-signed certificate? If the self-signed certificate's key gets compromised, the CRL does not help at all. So, here are my questions: 1. Is a CRL really a hard requirement? 2. If not: can I just use the self-signed certificate of my private key for the ssl_ca setting? 3. If yes: any idea how I can generate a CRL for my smartcard-bound self-signed certificate? Marvin -- Blog: https://mg.guelker.eu

2 3

failed to pipe to program sa-learn-spam.sh
by ＠lbutlr 16 Jun '19

16 Jun '19

Error: program `/usr/lib/dovecot/sieve/sa-learn-spam.sh' terminated abnormally, signal 11 Error: sieve: pipe action: failed to pipe message to program `sa-learn-spam.sh': refer to server log for more information. [2019-05-29 17:59:12] What server log? This is all that get logged. # pwd /usr/lib/dovecot/sieve # ls -lsa > total 96 > 8 drwxrwxrwx 3 root wheel 512 Jun 18 2018 . > 8 drwxr-xr-x 3 root wheel 512 May 17 17:54 .. > 8 -rw-r--r-- 1 root wheel 86 Jun 15 2018 default.sieve > 8 drwxr-xr-x 2 root wheel 512 Jun 13 2018 global > 8 -rw-r--r-- 1 root wheel 62 May 14 2018 mark-read.sieve > 8 -rw-r--r-- 1 kremels wheel 192 Jun 17 2018 mark-read.svbin > 8 -rwxr-xr-x 1 root wheel 314 Feb 12 2018 report-ham.sieve > 8 -rw-r--r-- 1 lbutler wheel 448 Jun 18 2018 report-ham.svbin > 8 -rwxr-xr-x 1 root wheel 199 Feb 12 2018 report-spam.sieve > 8 -rw-r--r-- 1 kreme wheel 354 Jun 15 2018 report-spam.svbin > 8 -rwxr-xr-x 1 root wheel 131 Jun 18 2018 sa-learn-ham.sh > 8 -rwxr-xr-x 1 root wheel 54 Feb 12 2018 sa-learn-spam.sh # cat sa-learn-spam.sh > #!/bin/sh > exec /usr/local/bin/sa-learn -u ${1} --spam # ls -ls /usr/local/bin/sa-learn > 96 -rwxr-xr-x 1 root wheel 45939 May 29 09:59 /usr/local/bin/sa-learn report-spam.sieve: > require ["vnd.dovecot.pipe", "copy", "imapsieve", "environment", "variables"]; > > if environment :matches "imap.user" "*" { > set "username" "${1}"; > } > > pipe :copy "sa-learn-spam.sh" [ "${username}" ]; in doveconf I have: > 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 ihave > > plugin { > imapsieve_mailbox1_before = file:/usr/lib/dovecot/sieve/report-spam.sieve > imapsieve_mailbox1_causes = COPY > imapsieve_mailbox1_name = Junk > … It WAS working. -- Women and cats will do as they please, and men and dogs should relax an get used to the idea.

3 6

NOTIFY: bug on mailbox renaming and deletion ?
by kael 16 Jun '19

16 Jun '19

Hello, Testing the NOTIFY extension on imap.vivaldi.net, seems there's a bug when a mailbox is renamed or deleted. Requesting events with: A1 NOTIFY SET (inboxes (SubscriptionChange MailboxName)) Here are the sent events: - mailbox creation with automatic subscription (ok): * LIST () "." foo * LIST (\Subscribed) "." foo - mailbox renaming (bug ?): * LIST () "." bar ("OLDNAME" (foo)) * LIST (\Subscribed) "." bar * LIST () "." foo - mailbox deletion (bug ?): * LIST (\NonExistent) "." Trash.bar * LIST () "." Trash.bar It seems that for the two latter cases, the last received event is incorrect, Dovecot notifying of mailbox unsubscription after the mailbox has been renamed or deleted. In that case a client would consider those two last events not as mailbox renaming or deletion, but as a mailbox creation, wouldn't it ? Am I missing something ? Cheers. -- kael

1 0

sdbox format, quota not maildir, and public folder
by David Mehler 16 Jun '19

16 Jun '19

Hello, I'm using Dovecot 2.3.x and using dbox as mailbox storage format, specifically sdbox. I'm getting an error from quota about namespace is not maildir is there a setting I have to use for quota to use the sdbox?

1 0

Dovecot 2.3 error, FreeBSD 12 in a jail
by David Mehler 15 Jun '19

15 Jun '19

Hello, I'm trying to get Dovecot going on my system. It's a FreeBSD 12.0-RELEASE system and it's running dovecot 2.3 via ports in a jail. I'm getting the same error message(s) as in this bug report, which has been marked as closed: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=225078 Dovecot is not starting at all in this jail when starting with service dovecot start. A service dovecot status also reveals the error message about /var/run/dovecot/dovecot.conf file, but a doveconf -n does not reveal any configuration file issues. I did put a symlink in /var/run/dovecot to /usr/local/etc/dovecot/dovecot.conf, this did not correct the issue. Any suggestions welcome. Thanks. Dave.

2 1

LMTP doesn't save to +mailbox
by ＠lbutlr 14 Jun '19

14 Jun '19

Since switching to lmtp in dovecot, mail to user+mailboix(a)example.com does not get saved in ‘.mailbox’ as it did with LDA, instead it gets saved into the INBOX. If it matters, these are users who do NOT have a ~/.active_sieve file. I could understand (though it would bene a bit annoying) if the save overrode this mechanism. I did add lmtp_save_to_detail_mailbox = yes in the protocol lmtp block protocol lmtp { postmaster_address = postmaster(a)covisp.net # required mail_plugins = quota sieve info_log_path = /var/log/dovecot-lmtp.log lmtp_save_to_detail_mailbox = yes } This is the error I am getting when sending to luser+covisp(a)covisp.net lmtp(luser(a)covisp.net)<91193><EqkiJV70A105ZAEAIdGjjQ>: Error: sieve: msgid=<A3ED963A-97FB-4A1F-9F09-45F2AEA96CF6(a)kreme.com>: failed to store into mailbox 'covisp': Mailbox doesn't exist: covisp lmtp(luser(a)covisp.net)<91193><EqkiJV70A105ZAEAIdGjjQ>: Error: sieve: Execution of script /usr/lib/dovecot/sieve/default.sieve failed with unsuccessful implicit keep # cat /usr/lib/dovecot/sieve/default.sieve [13:32] [/var/log] require "fileinto"; if header :contains "X-spam-flag" "YES" { fileinto "Junk"; } (This file hasn’t changed in a year, so it worked fine with the lda instead of the lmtp setup. I mean, I can probably just write a sieve to do it. Let me think… if header :regex "to" “+(.*)@" { fileinto :create “${1}"; stop; } Seems like it should work. Should I add this to default.sieve? # 2.3.6 (7eab80676): /usr/local/etc/dovecot/dovecot.conf # Pigeonhole version 0.5.6 (92dc263a) # OS: FreeBSD 11.2-RELEASE-p10 i386 # Hostname: mail.covisp.net auth_failure_delay = 5 secs auth_mechanisms = PLAIN LOGIN default_client_limit = 4096 default_process_limit = 1024 default_vsz_limit = 768 M disable_plaintext_auth = no first_valid_uid = 89 imap_id_log = * login_log_format_elements = user=<%u> %r %m %c mail_location = maildir:~/Maildir mail_max_userip_connections = 90 managesieve_notify_capability = mailto managesieve_sieve_capability = editheader fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date ihave namespace inbox { inbox = yes location = mailbox Archive { auto = subscribe special_use = \Archive } mailbox Drafts { special_use = \Drafts } mailbox Junk { auto = subscribe special_use = \Junk } mailbox Sent { special_use = \Sent } mailbox Trash { special_use = \Trash } prefix = } passdb { args = /usr/local/etc/dovecot/sql.conf driver = sql } plugin { imapsieve_mailbox1_before = file:/usr/lib/dovecot/sieve/report-spam.sieve imapsieve_mailbox1_causes = COPY imapsieve_mailbox1_name = Junk imapsieve_mailbox2_before = file:/usr/lib/dovecot/sieve/report-ham.sieve imapsieve_mailbox2_causes = COPY imapsieve_mailbox2_from = Junk imapsieve_mailbox2_name = * imapsieve_mailbox3_before = file:/usr/lib/dovecot/sieve/mark-read.sieve imapsieve_mailbox3_causes = COPY imapsieve_mailbox3_name = Archive quota_rule2 = .EXPUNGED:ignore sieve = file:~/.sieve;active=~/.active_sieve sieve_default = /usr/lib/dovecot/sieve/default.sieve sieve_default_name = spamassassin sieve_extensions = +editheader sieve_global_extensions = +vnd.dovecot.pipe +vnd.dovecot.environment sieve_pipe_bin_dir = /usr/lib/dovecot/sieve sieve_plugins = sieve_imapsieve sieve_extprograms sieve_user_log = ~/sieve.log } service auth { unix_listener /var/spool/postfix/private/auth { mode = 0666 } } service imap-login { inet_listener imaps { port = 993 ssl = yes } } service lmtp { unix_listener /var/spool/postfix/private/dovecot-lmtp { group = postfix mode = 0600 user = postfix } } service pop3-login { inet_listener pop3 { port = 0 } inet_listener pop3s { port = 995 ssl = yes } } service stats { unix_listener stats-reader { group = dovecot mode = 0666 user = } unix_listener stats-writer { group = dovecot mode = 0666 user = } } ssl_cert = </usr/local/etc/dehydrated/certs/covisp.net/fullchain.pem ssl_dh = # hidden, use -P to show it ssl_key = # hidden, use -P to show it ssl_min_protocol = TLSv1.1 userdb { args = /usr/local/etc/dovecot/sql.conf default_fields = uid=vpopmail gid=vchkpw mail_location=maildir:/usr/local/virtual/%u/Maildir mail=maildir:/usr/local/virtual/%u/Maildir driver = sql } protocol imap { mail_plugins = " imap_sieve" } protocol lmtp { info_log_path = /var/log/dovecot-lmtp.log lmtp_save_to_detail_mailbox = yes mail_plugins = quota sieve postmaster_address = postmaster(a)covisp.net }

1 2

Dovecot director: show user breakdown by director?
by Eirik Rye 14 Jun '19

14 Jun '19

Hi, We have recently started using the director in some tests. We are using the static passdb setup (proxy=y nopassword=y) for now, where authentication is done on the downstream IMAP servers. "dovecot director status" shows a breakdown of proxied connections per backend, but there does not seem to be a similar breakdown of user connections per director. The output of "doveadm who" is empty. I assume this is due to there being no local userdb/passdb on the directors? root@xxx:/etc/dovecot/conf.d# doveadm who username # proto (pids) (ips) Is there a way in Dovecot to see which (or even how many) users are connected to a specific director without having to count TCP connections? Best regards, Eirik Rye

2 2

Addheader specified field name `Reply-To:' is invalid.
by ＠lbutlr 14 Jun '19

14 Jun '19

Well, progress. At least now editheader loads. Sadly that brings up new errors. specified field name `Reply-To:' is invalid. if header :contains "List-id" "<users.spamassassin.apache.org>" { addheader "Reply-To:" "<users.spamassassin.apache.org>"; addheader "X-added-reply-To:" "True"; fileinto :create “spamassassin"; stop;} -- You only had to look into Teatime's mismatched eyes to know one thing, which was this: if Teatime wanted to find you he would not look everywhere. He'd look in only one place, which would be the place where you were hiding. —Hogfather

2 3

MultiMaster dsync (cluster1 cluster2 cluster3)
by Matthew Brown 14 Jun '19

14 Jun '19

Will MultiMaster dsync work fine or will be big problems ? I configured dovecot to dsync from serv1 to serv2 to serv3 and repeat to serv1 to serv2 to serv3 and repeat... When email received to serv2, it will be synced to serv3, and serv3 will sync it to serv1, and serv1 will sync it to serv2 and will stop here because emails matched. What problems can be with this kind of configuration ? (except that if one of server(cluster) will be stopped, sync will be stopped too until cluster is online again)

2 1

Sieve rewrite headers?
by ＠lbutlr 14 Jun '19

14 Jun '19

I’ve bene looking for examples on how to do this, but so far am coming up short. I want to check certain messages for a reply-ro header and if it is present, rewrite it to X-Reply-To: and then add my own reply-to header. I don’t see anything in the various sieve examples I’ve found on altering the actual message. There is the editheader extension, but I failed to find documentation or examples on how to use it. It appears that I can add a header and delete a header (addheader deleteheader?) but not rewrite one. So something like if header “Reply-to: foo(a)bar.xn--tld-9o0a { addheader "X-Reply-To: foo(a)bar.xn--tld-9o0a deleteheader “Reply-To:” addheader "X-Reply-To: bar(a)foo.xn--tld-9o0a } ?? Do I need to delete the header or will the add header overwrite the one that is there? Also, how do people manage different sieve files? Just cat them all into the active one, or is there a mechanism to import/switch/load other files?

2 1

unknown Sieve Capability `editheader'
by ＠lbutlr 14 Jun '19

14 Jun '19

I am getting "error: error: require command: unknown Sieve capability `editheader’.” In sieve.log: This is the start of .active_sieve ## Active require [ "editheader", "regex", "variables", "fileinto", "envelope", "mailbox", "imap4flags" ]; Editheader is also listed in dovecot.conf managesieve_sieve_capability = editheader fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date ihave

2 1

Re: Re: CASifying dovecot and webmail
by charli AGOSSOU 14 Jun '19

14 Jun '19

Hi. I have been trying for a long time to roundcube but I have trouble doing it. It may therefore be necessary to manage the casification of dovecot. Something that is not easy right now with the operating system version that I use. I am working with a kali 2019, and I have compilation errors when running the make on pam_cas. Any help will be useful to me. Thank you Charlie Harper Best regards,

1 0

Re: Migrated from maildir to sdbox: questions
by Daniel Betz 14 Jun '19

14 Jun '19

Hi Ranbir, i think youre just using the wrong quota backend. https://wiki2.dovecot.org/Quota You should switch from "quota = maildir...." to another one, like dict. Converting your Public mailbox you could try this ( no guarantee .. just guessing. make backup ! ): doveadm -o mail_location="maildir:/var/spool/mail/thesandhufamily.ca/public" sync sdbox:/target/folder Regards, Daniel > > Hi Everyone, > > I migrated my maildir mailboxes to sdbox without any show stopping errors, > but I did see this during the migration and now I'm also seeing it in the log: > > Warning: quota: Namespace '' is not Maildir, skipping for Maildir++ quota > > I'm not quite sure why this is happening. Any ideas? > > I am using a "public" namespace for several mailboxes to share emails: > > # public namespace configuration > namespace { > type = public > # the default separator for Maildir is ".", so that is what should be > # used automatically. > separator = . > prefix = Public. > location = maildir:/var/spool/mail/thesandhufamily.ca/public > subscriptions = no > } > > Under the "public" dir in the old maildir setup, I have folders configured for > various mail accounts. For example: > > .Ads > .Junk > .Bills > > etc. > > These "users" are setup in a passwd file so that I can use a different mail > storage location for them than the one they get from ldap (same as above). > > Using dsync to migrate my other mailboxes was easy, but I don't know how > to migrate these public mailboxes. I looked through the wiki and didn't see > anything about how to do it. Could someone explain how I can migrate the > public mailboxes? > > > -- > Ranbir >

3 2

Outlook renames Junk folder
by Cliff Hayes 13 Jun '19

13 Jun '19

Hello, Some versions of Outlook will randomly rename the Junk folder to Junk Email. This of course causes errors because Dovecot can no longer store junk. I go in to Outlook for each user and add another Junk folder, so now they have Junk and Junk Email. This fix action lasts a while until Outlook decides to do it again. Is there a way to tell Dovecot that if the Junk folder doesn't exist, try sending the email to Junk Email folder? Thanks in advance.

3 3

Sieve logging?
by ＠lbutlr 13 Jun '19

13 Jun '19

I am trying to create some sieve scripts to filter my mailing lists and am wondering if sieve logs anywhere, and it so where? I don’t see anything in mail.log beyond lines like: dovecot: lda(kremels(a)kreme.com)<39790><hNchChSkAV1umwAAIdGjjQ>: sieve: msgid=<267D5D71-D99C-4790-8706-C1A92BCC9F97(a)kreme.com>: stored mail into mailbox ‘INBOX' Which doesn’t really tell me anything other than that the script failed. -- If the #2 pencil is the most popular, why is it still #2?

3 6

Re: Sieve logging?
by Matt Anton 13 Jun '19

13 Jun '19

On 13 Jun 2019, at 14:47, @lbutlr wrote: > What sort of configuration change would I need to do to use LMTP instead of LDA? Regarding dovecot, all you need to do is following: <https://wiki.dovecot.org/LMTP> <https://wiki.dovecot.org/HowTo/PostfixDovecotLMTP> (if postfix is your MTA) <https://wiki.dovecot.org/LMTP/Exim> (if exim is your MTA) > And are there any downsides? Not that I’m aware of. Things remained the same as when I was using LDA but using LMTP over Dovecot’s LDA brings some advantages like better performances (no need to fire up new processes for deliveries) among others one. There were several threads on the list related to LDA vs LMTP, such as: <https://dovecot.org/pipermail/dovecot/2016-June/104670.html> <https://dovecot.org/list/dovecot/2013-July/091617.html> > What do I do about > > lda_mailbox_autocreate = yes > lda_mailbox_autosubscribe = yes > > ? They’re also used by LMTP so no need to worry when migrating from LDA to LMTP. You can check what LDA’s options are specifically also used by LMTP in examples/conf.d/15-lda.conf -- matt [at] lv223.org GPG key ID: 7D91A8CA

1 0

Migrated from maildir to sdbox: questions
by Ranbir 13 Jun '19

13 Jun '19

Hi Everyone, I migrated my maildir mailboxes to sdbox without any show stopping errors, but I did see this during the migration and now I'm also seeing it in the log: Warning: quota: Namespace '' is not Maildir, skipping for Maildir++ quota I'm not quite sure why this is happening. Any ideas? I am using a "public" namespace for several mailboxes to share emails: # public namespace configuration namespace { type = public # the default separator for Maildir is ".", so that is what should be # used automatically. separator = . prefix = Public. location = maildir:/var/spool/mail/thesandhufamily.ca/public subscriptions = no } Under the "public" dir in the old maildir setup, I have folders configured for various mail accounts. For example: .Ads .Junk .Bills etc. These "users" are setup in a passwd file so that I can use a different mail storage location for them than the one they get from ldap (same as above). Using dsync to migrate my other mailboxes was easy, but I don't know how to migrate these public mailboxes. I looked through the wiki and didn't see anything about how to do it. Could someone explain how I can migrate the public mailboxes? -- Ranbir

1 0

Sieve to strip html from multipart messages
by ＠lbutlr 13 Jun '19

13 Jun '19

Is is possible (I’m sure it is, so how) to strip multipart messages that are HTML and text of the HTML portion and leave the bare text message without also stripping other parts (like images or attached files). Or also to take messages that are only HTML and strip the HTML and replace it with a plain text version? I used to do this a long time ago with procmail and lynx, but it was never reliable since procmail doesn’t really understand MIME.

2 2

Updating passwords
by ＠lbutlr 12 Jun '19

12 Jun '19

I created some new users in my MySQL database using postfoxadmin. The passwords looked correct in the database and show the right prefix {SHA256-CRYPT} but logins were failing, so I manually created new passwords from the command line: doveadm pw -s SHA256-CRYPT -p “a password" -u kremels(a)kreme.com {SHA256-CRYPT}$5$ZKsovTv0Ddc9k4… I then went into the postfix database and manually updated the password field in the database. update mailbox set password = '$5$ZKsovTv0Ddc9k4…' where username like 'kremels(a)kreme.com'; SOME of the accounts can now login, but not all. I get a debug line like: dovecot: auth-worker(26599): Debug: sql(kremels(a)kreme.com,xx.xx.xx.xx,<rnadomlookingstuff>): SHA256-CRYPT(a password) != '$5$ZKsovTv0Ddc9k4… -- 'They've given us the answers,' he [Carrot] said. 'Perhaps we can find out what the questions should have been.' --Feet of Clay

1 1

Password issue
by Cerebus the Aardvark 12 Jun '19

12 Jun '19

I am using SHA-256 crypt for dovecot. I have added some new users vi postfoxadmin, which is also configured to use she-256 crypt. looking at the database: {SHA256-CRYPT}$5$lKfXOxua8j9FIFJt$r4rLmMFHUK/FcJ0c.sp.U4paTeE6Obp0t.mj.6eJQx9 # works {SHA256-CRYPT}$5$Gy.zyFNgYHgSsvmh$C/8Fv47Rjij6S73SwkfhCTwuqGgsmiRCjke6blbt1YD # does not work (I changed some random character in each line, but didn't change the length) Jun 12 12:43:09 mail dovecot: auth: Debug: policy(kremels,73.14.161.160,<0VjtyCSLluJJDqGg>): Policy check action is continue Jun 12 12:43:09 mail dovecot: auth-worker(57297): Debug: sql(kremels,73.14.161.160,<0VjtyCSLluJJDqGg>): query: select password FROM mailbox where username ='kremels' Jun 12 12:43:14 mail dovecot: auth: Debug: client passdb out: FAIL#0111#011user=kremel

1 0

LMTP and Sieve with <prefix><recipient_delimiter><user>
by Paul Muster 11 Jun '19

11 Jun '19

Hi there, Dovecot's LMTP implementation and Pigeonhole Sieve already do support the <user><delimiter><suffix> format. RfC 5233, the Sieve subaddress extension, also offers <prefix><delimiter><user>. Could Docecot's LMTP and Pigeonhole be extended to that effect? Thanks & greetings, Paul

1 2

Compile problem on Solaris
by Roderick Johnstone 11 Jun '19

11 Jun '19

Hi Compiling dovecot 2.2.36.1 with the native compiler on Solaris 10 is giving the error below. Can anyone advise a compiler option or code change to resolve this please. Thanks. Roderick Johnstone # make make all-recursive Making all in . /bin/bash ./update-version.sh . . Making all in src Making all in lib-test Making all in lib make all-am source='sha3.c' object='sha3.lo' libtool=yes \ DEPDIR=.deps depmode=none /bin/bash ../../depcomp \ /bin/bash ../../libtool --tag=CC --mode=compile cc -DHAVE_CONFIG_H -I. -I../.. -I/export/home/exim_build_20190605/build_local/include -m64 -c -o sha3.lo sha3.c libtool: compile: cc -DHAVE_CONFIG_H -I. -I../.. -I/export/home/exim_build_20190605/build_local/include -m64 -c sha3.c -KPIC -DPIC -o .libs/sha3.o "sha3.h", line 49: warning: unnamed struct member "sha3.c", line 142: improper member use: s "sha3.c", line 142: improper member use: s "sha3.c", line 166: improper member use: s "sha3.c", line 173: improper member use: s "sha3.c", line 197: improper member use: s "sha3.c", line 200: improper member use: s "sha3.c", line 227: improper member use: s "sha3.c", line 231: improper member use: s "sha3.c", line 233: improper member use: s "sha3.c", line 259: improper member use: sb "sha3.c", line 268: improper member use: sb cc: acomp failed for sha3.c *** Error code 1

2 2

Potfix+Dovecot with dsync replication problem
by Zeljko Dokman 10 Jun '19

10 Jun '19

Hi all, I am in need of some help. Straggling to make something work, trying to configure postfix and dovecote imap server with dovecote replication. Can’t figure out what is wrong with my configuration. Replication is working only for vmail user account, I am getting this error on my secondary server for all other users… dovecot: doveadm: Fatal: setgid(4015(zdokman) from userdb lookup) failed with euid=5000(vmail), gid=5000(vmail), egid=5000(vmail): Operation not permitted (This binary should probably be called with process group set to 4015(zdokman) instead of 5000(vmail)) primary server reports this error: dovecot: doveadm(zdokman): Error: doveadm server disconnected before handshake: EOF dovecot: doveadm(zdokman): Error: sync: Disconnected from remote: EOF doveadm replicator status '*' username priority fast sync full sync success sync failed vmail none 01:58:13 02:05:25 01:58:13 - zdokman none 00:00:25 02:55:26 - y test none 00:01:00 21:48:13 - y doveadm sync * doveadm(root): Fatal: execvp(Maildir) failed: Permission denied dsync-local(root): Error: read(remote) failed: EOF (version not received) I am attaching my dovecot.conf main.cf and master.cf. I think my problem is with permissions but I can figure out how to workaround it. Best regards

2 3

Sql user and maildirs
by ＠lbutlr 10 Jun '19

10 Jun '19

For many years I had the following in my dovecot.conf: userdb { args = /usr/local/etc/dovecot/dovecot-sql.conf.ext default_fields = uid=vpopmail gid=vchkpw mail_location=/usr/local/virtual/%u/Maildir mail=maildir:/usr/local/virtual/%u/Maildir driver = sql } Recently, I started having quite a lot of errors on one MySQL account (used as a bcc backup account) along the lines of Fatal: Namespace '': Ambiguous mail location setting, don't know what to do with it: /usr/local/virtual/backup@domain/Maildir (try prefixing it with mbox: or maildir: Messages were sitting in the mail and were also getting dumped into /usr/local/virtual/backup@domain/new and I ended up running a fun little awk to move them into the right folders: grep -r "<backup+" . |awk -F: '{t=tolower($2); f=tolower($1); gsub(/@.*/, "/", t); sub(/<backup\+/, "../Maildir/", t); sub(/\.\//, "",f); cmd="mv " f" “t; system(cmd); }’ So I changed my doevecot.conf to: userdb { args = /usr/local/etc/dovecot/dovecot-sql.conf.ext default_fields = uid=vpopmail gid=vchkpw mail_location=maildir:/usr/local/virtual/%u/Maildir mail=maildir:/usr/local/virtual/%u/Maildir driver = sql } And the errors went away. So, no problem here to solve, but I am curious why I haven’t been having issues until quite recently? Was there a change or have I stumbled into something where it only looks like I’ve fixed the issue? In case it matters? # cat dovecot-sql.conf.ex [7:57] [/etc/dovecot] driver = mysql connect = host=localhost dbname=postfixusers user=dovecot password=x default_pass_scheme = SHA256-CRYPT password_query = select password FROM mailbox where username ='%u' user_query = select 89 as uid, 89 as gid, concat('/usr/local/virtual/', maildir, 'Maildir') as home FROM mailbox where username = '%u' The only ‘recent’ change I’ve made to my configuration was creating the Maildir/ subfolder for all the virtual users instead of using the ‘mailder’ from the sql table (that is, I added “, ‘Maildir’” to the concat, but that was quite awhile ago. I’m pretty sure I’d have noticed this before. Is that user_query as it should be or should I set concat('/usr/local/virtual/', maildir) as home and also set concat(‘maildir:/usr/local/virtual/', maildir, 'Maildir') as mail here rather than in the userdb block? -- K is for KATE who was struck by an axe L is for Leo who swallowed some tacks

1 1

Re: doveconf complains No matches on !include conf.d/* line but still writes out contents in conf.d
by Ben Ma 10 Jun '19

10 Jun '19

Further investigation shows that `doveconf` called `/usr/lib/dovecot/managesieve` which in return calls `doveconf` again, but with another uid (possible? I'm not sure) and a few extra arguments, which causes a call to `glob` in `src/config/config-parser.c:settings_include` to fail with `GLOB_NOMATCH`. I'd be appreciate if anyone can provide information on suspicious permission-relating operation that `managesieve` does before calling `doveconf`. I just can't find a way to post reply on previous mails, so I decided to post a new one. The original text follows. On 2019/6/6 3:15, Ben Ma wrote: > I'm on dovecot 2.3.3 (dcead646b). Output of `dovecot -n`: > > # 2.3.3 (dcead646b): /etc/dovecot/dovecot.conf # Pigeonhole version > 0.5.3 (f018bbab) doveconf: Fatal: Error in configuration file > /etc/dovecot/dovecot.conf line 98: No matches doveconf: Error: > managesieve-login: dump-capability process returned 89 doveconf: > Fatal: Error in configuration file /etc/dovecot/dovecot.conf line 98: > No matches > > While line 98 of dovecot.conf is just "!include conf.d/*.conf". > > Output of `doveconf -n`: > > # 2.3.3 (dcead646b): /etc/dovecot/dovecot.conf # Pigeonhole version > 0.5.3 (f018bbab) doveconf: Fatal: Error in configuration file > /etc/dovecot/dovecot.conf line 98: No matches doveconf: Error: > managesieve-login: dump-capability process returned 89 # OS: Linux > 4.12.14-lp151.28.4-default x86_64 # Hostname: XXX doveconf: Error: > t_readlink(/var/run/dovecot/dovecot.conf) failed: readlink() failed: > No such file or directory namespace inbox { ............. (Removed for > simplicity) } ssl = required ssl_cert = > </etc/postfix/ssl/certs/phys.cer ssl_options = no_compression > ssl_prefer_server_ciphers = yes userdb { driver = passwd } > > It's strange that all the extra content (especially ssl conf) only > occurs in conf.d/10-ssl.conf. > > To dig on what's happening underneath I ran `strace doveconf -n 2>&1 > |egrep "\.conf|conf\.d"` and got: > > write(1, "# 2.3.3 (dcead646b): /etc/doveco"..., 47# 2.3.3 (dcead646b): > /etc/dovecot/dovecot.conf openat(AT_FDCWD, > "/etc/dovecot/dovecot.conf", O_RDONLY) = 7 wait4(-1, doveconf: Fatal: > Error in configuration file /etc/dovecot/dovecot.conf line 98: No > matches open("/etc/dovecot/conf.d", > O_RDONLY|O_NONBLOCK|O_DIRECTORY|O_CLOEXEC) = 8 openat(AT_FDCWD, > "/etc/dovecot/conf.d/90-sieve.conf", O_RDONLY) = 8 ............. > (Removed for simplicity) openat(AT_FDCWD, > "/etc/dovecot/conf.d/10-ssl.conf", O_RDONLY) = 20 openat(AT_FDCWD, > "/etc/dovecot/conf.d/10-auth.conf", O_RDONLY) = 25 > stat("/etc/dovecot/conf.d/auth-system.conf.ext", > {st_mode=S_IFREG|0644, st_size=2182, ...}) = 0 openat(AT_FDCWD, > "/etc/dovecot/conf.d/auth-system.conf.ext", O_RDONLY) = 26 > stat("/etc/dovecot/local.conf", 0x7ffd94664760) = -1 ENOENT (No such > file or directory) stat("/etc/resolv.conf", {st_mode=S_IFREG|0644, > st_size=709, ...}) = 0 open("/etc/host.conf", O_RDONLY|O_CLOEXEC) = 7 > read(7, "#\n# /etc/host.conf - resolver co"..., 4096) = 370 > open("/etc/resolv.conf", O_RDONLY|O_CLOEXEC) = 7 read(7, "### > /etc/resolv.conf is a symlin"..., 4096) = 709 > readlink("/var/run/dovecot/dovecot.conf", 0x5555db302598, 128) = -1 > ENOENT (No such file or directory) write(2, "doveconf: Error: > t_readlink(/var"..., 112doveconf: Error: > t_readlink(/var/run/dovecot/dovecot.conf) failed: readlink() failed: > No such file or directory > > It seems that files in conf.d is never read before doveconf's > complaint! I have totally no idea why this happens. Any help?

1 0

sieve setup. no svbin ?
by Voytek Eymont 09 Jun '19

09 Jun '19

since moving/upgrading system I've noticed I no longer get sieve script compiled, there is no dovecot.svbin created in /var/vmail/vmail1/sbt.net.au/voytek(a)tld.au/sieve what am I missing, how to check ? also, looking at sieve.log, I see a lot of May 31 06:32:50 lda(voytek(a)sbt.net.au)<1234><c4aVBfI98FzSBAAAyLbbsQ>: Error: sieve: Failed to initialize script execution: Invalid postmaster_address: invalid address `root' specified for the postmaster_address setting # grep root dovecot.conf postmaster_address = root what should I have ? # dovecot --version 2.3.6 (7eab80676)

2 5

FTS Xapian
by Daniel Miller 09 Jun '19

09 Jun '19

For my primary namespace this is working fine - thanks to the developers! It also appears to work great for shared folders as well. But my virtual folders aren't returning results - at least not to the client. The logs show FTS Xapian opening several DB files and getting results - but nothing is being returned to client. Is this a config issue on my side or is this a current limitation of the plugin? -- Daniel

2 5

Last Login Plugin Help
by Júlio Covolato 07 Jun '19

07 Jun '19

Hi, I'm configuring Last_Login plugin whith Mysql back end and all works fine. I just wonder to track besides time_stamp, user and domain, the remote IP and proto (imap or pop3) I tried in dovecot.conf: plugin { ... ... # Track last login time on imap and pop3 last_login_dict = proxy::lastlogin last_login_key = last-login/%u/%d/%r } dict { ... lastlogin = mysql:/etc/dovecot/dovecot-last-login.conf ... } protocol imap { mail_plugins = $mail_plugins ... last_login ... } protocol pop3 { mail_plugins = $mail_plugins last_login ... } And dovecot-last-login.conf: connect = host=127.0.0.1 port=3306 dbname=vmail user=vmailadmin password=xxxxxxxxxxxxxxxxxx map { pattern = shared/last-login/$user/$domain table = last_login value_field = last_login value_type = uint fields { username = $user domain = $domain rip = $rip } } And the table criated in mysql: CREATE TABLE IF NOT EXISTS `last_login` ( `username` VARCHAR(255) NOT NULL DEFAULT '', `domain` VARCHAR(255) NOT NULL DEFAULT '', `last_login` INT(11) DEFAULT NULL, `rip` VARCHAR(16) NOT NULL DEFAULT '', PRIMARY KEY (`username`), INDEX (`domain`), INDEX (`last_login`), INDEX (`rip`) ) ENGINE=InnoDB DEFAULT CHARSET=utf8; And got de error in dovecot log: Jun 06 13:56:59 dict(21157): Error: Failed to initialize dictionary 'lastlogin': dict mysql: Error in configuration file /etc/dovecot/dovecot-last-login.conf line 13: Unused variable: rip Thanks in any help. -- ---------------------------------- _ Engº Julio Cesar Covolato 0v0 <julio(a)psi.com.br> /(_)\ F: +55 11 99175-9260 ^ ^ PSI INTERNET ---------------------------------- --- Este email foi escaneado pelo Avast antivírus. https://www.avast.com/antivirus

2 3

doveconf complains No matches on !include conf.d/* line but still writes out contents in conf.d
by runappz 05 Jun '19

05 Jun '19

I'm on dovecot 2.3.3 (dcead646b). Output of `dovecot -n`: # 2.3.3 (dcead646b): /etc/dovecot/dovecot.conf # Pigeonhole version 0.5.3 (f018bbab) doveconf: Fatal: Error in configuration file /etc/dovecot/dovecot.conf line 98: No matches doveconf: Error: managesieve-login: dump-capability process returned 89 doveconf: Fatal: Error in configuration file /etc/dovecot/dovecot.conf line 98: No matches While line 98 of dovecot.conf is just "!include conf.d/*.conf". Output of `doveconf -n`: # 2.3.3 (dcead646b): /etc/dovecot/dovecot.conf # Pigeonhole version 0.5.3 (f018bbab) doveconf: Fatal: Error in configuration file /etc/dovecot/dovecot.conf line 98: No matches doveconf: Error: managesieve-login: dump-capability process returned 89 # OS: Linux 4.12.14-lp151.28.4-default x86_64 # Hostname: XXX doveconf: Error: t_readlink(/var/run/dovecot/dovecot.conf) failed: readlink() failed: No such file or directory namespace inbox { ............. (Removed for simplicity) } ssl = required ssl_cert = </etc/postfix/ssl/certs/phys.cer ssl_options = no_compression ssl_prefer_server_ciphers = yes userdb { driver = passwd } It's strange that all the extra content (especially ssl conf) only occurs in conf.d/10-ssl.conf. To dig on what's happening underneath I ran `strace doveconf -n 2>&1 |egrep "\.conf|conf\.d"` and got: write(1, "# 2.3.3 (dcead646b): /etc/doveco"..., 47# 2.3.3 (dcead646b): /etc/dovecot/dovecot.conf openat(AT_FDCWD, "/etc/dovecot/dovecot.conf", O_RDONLY) = 7 wait4(-1, doveconf: Fatal: Error in configuration file /etc/dovecot/dovecot.conf line 98: No matches open("/etc/dovecot/conf.d", O_RDONLY|O_NONBLOCK|O_DIRECTORY|O_CLOEXEC) = 8 openat(AT_FDCWD, "/etc/dovecot/conf.d/90-sieve.conf", O_RDONLY) = 8 ............. (Removed for simplicity) openat(AT_FDCWD, "/etc/dovecot/conf.d/10-ssl.conf", O_RDONLY) = 20 openat(AT_FDCWD, "/etc/dovecot/conf.d/10-auth.conf", O_RDONLY) = 25 stat("/etc/dovecot/conf.d/auth-system.conf.ext", {st_mode=S_IFREG|0644, st_size=2182, ...}) = 0 openat(AT_FDCWD, "/etc/dovecot/conf.d/auth-system.conf.ext", O_RDONLY) = 26 stat("/etc/dovecot/local.conf", 0x7ffd94664760) = -1 ENOENT (No such file or directory) stat("/etc/resolv.conf", {st_mode=S_IFREG|0644, st_size=709, ...}) = 0 open("/etc/host.conf", O_RDONLY|O_CLOEXEC) = 7 read(7, "#\n# /etc/host.conf - resolver co"..., 4096) = 370 open("/etc/resolv.conf", O_RDONLY|O_CLOEXEC) = 7 read(7, "### /etc/resolv.conf is a symlin"..., 4096) = 709 readlink("/var/run/dovecot/dovecot.conf", 0x5555db302598, 128) = -1 ENOENT (No such file or directory) write(2, "doveconf: Error: t_readlink(/var"..., 112doveconf: Error: t_readlink(/var/run/dovecot/dovecot.conf) failed: readlink() failed: No such file or directory It seems that files in conf.d is never read before doveconf's complaint! I have totally no idea why this happens. Any help?

1 0

Re: Potfix+Dovecot with dsync replication problem
by Zeljko Dokman 05 Jun '19

05 Jun '19

Hi all, I am still struggling with this issue. I scraped my previous configuration and started from beginning. Thanks to Aki Tuomi and his suggestion I changed the users in my configurations from vmail --> root and that helped. Now I have a working replication but with some problems and strange behavior. Replication works only when I manually execute a command: "doveadm sync -A tcp:secundary:server:12345" Automatic fast and full sync do not work: doveadm replicator status "*" username priority fast sync full sync success sync failed zdokman none 01:46:14 01:46:14 01:46:14 - doveadm replicator status Queued 'sync' requests 0 Queued 'high' requests 0 Queued 'low' requests 0 Queued 'failed' requests 0 Queued 'full resync' requests 0 Waiting 'failed' requests 0 Total number of known users 1 doveadm replicator dsync-status username type status - Not connected maillog has no error entries. my conf files are attached. I don't understand why is this happening and how to fix it, any help is much appreciated. Best regards, On Mon, 13 May 2019 at 15:23, Zeljko Dokman <zdokman(a)gmail.com> wrote: > Hi, > Thank you for your reply Aki. > I changed my configuration and substituted vmail user with root user. > > Now I have no error massages in maillog but replication is not working, > mails are not visible on second server. > > BR > > > > > > On Mon, 13 May 2019 at 10:50, Aki Tuomi <aki.tuomi(a)open-xchange.com> > wrote: > >> Your problem is that you are running service doveadm as vmail, but you >> are using real uids. You need to start doveadm server as root to be able to >> switch into the correct target user. >> >> Aki >> >> >> On 13.5.2019 11.26, Zeljko Dokman via dovecot wrote: >> >> Hi all, >> >> Any suggestion? >> >> BR >> >> On Mon, 6 May 2019 at 14:22, Zeljko Dokman <zdokman(a)gmail.com> wrote: >> >>> Hi all, >>> >>> I am in need of some help. >>> >>> Straggling to make something work, trying to configure postfix and >>> dovecote imap server with dovecote replication. >>> >>> Can’t figure out what is wrong with my configuration. >>> >>> >>> >>> Replication is working only for vmail user account, I am getting this >>> error on my secondary server for all other users… >>> >>> >>> >>> dovecot: doveadm: Fatal: setgid(4015(zdokman) from userdb lookup) failed >>> with euid=5000(vmail), gid=5000(vmail), egid=5000(vmail): Operation not >>> permitted (This binary should probably be called with process group set to >>> 4015(zdokman) instead of 5000(vmail)) >>> >>> >>> >>> primary server reports this error: >>> >>> >>> >>> dovecot: doveadm(zdokman): Error: doveadm server disconnected before >>> handshake: EOF >>> >>> dovecot: doveadm(zdokman): Error: sync: Disconnected from remote: EOF >>> >>> >>> >>> >>> >>> doveadm replicator status '*' >>> >>> username >>> priority fast sync full sync success sync failed >>> >>> vmail >>> none 01:58:13 02:05:25 01:58:13 - >>> >>> zdokman >>> none 00:00:25 02:55:26 - y >>> >>> test >>> none 00:01:00 21:48:13 - y >>> >>> >>> >>> doveadm sync * >>> >>> doveadm(root): Fatal: execvp(Maildir) failed: Permission denied >>> >>> dsync-local(root): Error: read(remote) failed: EOF (version not received) >>> >>> >>> >>> I am attaching my dovecot.conf main.cf and master.cf. >>> >>> >>> >>> I think my problem is with permissions but I can figure out how to >>> workaround it. >>> >>> >>> >>> Best regards >>> >> >> >> -- >> >> >> >> >> >> > > -- > > > > > --

1 1

Stats/Metrics in 2.3
by Nikolai Lusan 03 Jun '19

03 Jun '19

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Greetings, So the changes to the stats modules between v2.2 and v2.3 have broken some of my monitoring. I am attempting to use the new method of gathering "metrics" from "events" - but the details in the documentation are a bit thin. I started with the examples provided at https://wiki2.dovecot.org/Statistics and tried to build from there with only moderate success. What I am trying to achieve is the monitoring of login attempts (with successes and failures as separate modules - as well as aborted attempts), user sessions an bytes transferred. All this for multiple virtual domains and users. I have attached my current /etc/dovecot/conf.d/10-stats.conf so people can see what I have attempted so far. Based on that file the output I get is: # doveadm stats dump metric_name field count sum min max avg median stddev %95 imap_login_attempt_lusan.id.au duration 0 0 0 0 0.00 0 0.00 0 imap_login_lusan.id.au_failed duration 0 0 0 0 0.00 0 0.00 0 imap_login_lusan.id.au_success duration 0 0 0 0 0.00 0 0.00 0 imap_select_no duration 702 197998 89 13942 282.05 133 1247.14 278 imap_select_no_notfound duration 702 197998 89 13942 282.05 133 1330.67 285 imap_command_list duration 14 287397 17595 25823 20528.36 20060 2194.36 25823 imap_command_select duration 1593 2354698 355 81662 1478.15 743 4583.03 4460 imap_command_search duration 0 0 0 0 0.00 0 0.00 0 imap_command_fetch_ok duration 0 0 0 0 0.00 0 0.00 0 storage_http_gets duration 0 0 0 0 0.00 0 0.00 0 Based on the metrics I have set I would expect to see entries in the first 2 lines at least, given that there are multiple users logged into the server from the monitored domain (or at least the domain I am trying to monitor to begin with). I am also not sure how to get the session and data transfer information out of the metrics/stats system. If anyone can help me I would appreciate it. Thanks - -- Nikolai Lusan <nikolai(a)lusan.id.au> -----BEGIN PGP SIGNATURE----- iQIzBAEBCgAdFiEEVfd4GW6z4nsBxdLo4ZaDRV2VL6QFAlzz29EACgkQ4ZaDRV2V L6QnIg/8CcB4V/69QSn+zqNhGNX2sHApoaGK0zCt7ITthOlDDVsdVKNT48hxJ3AR uEtoDQL9g3jcDJOQplsobDXmcs/Z6Po275T++8+CY0Bl5iqWO0/6g5LSvNDi6VlS VZzdLyDvAT0+oemaeTHgT/zPwx2waCrs84ZVwMCnuNVQKlE8l05gV2r6aLpgkRFf /Pc6zBwNEXGdthTcnowV2yPiYZkp87jaEl6+4RcHQcYQO1/Q/JEl38/iYlPWdVFZ NVOHpmzZdY9tGRhN0lqiUgivPLZu7gYyfzBeO6JHDOajLUNFW1NR7aKKhyALEOgM GZmjgSODzLjLw8CYx8iGnyMGRsEBDk+NLrJ1zjDqN+xIZkoUcnjkqwpNzurMIW4c kAkFDaPjquXu9eFy4T6V+r23p9E0z0IcWqTFfUyHkdctQApvkjLBFxoc35Abp1Yy I6LzGlGRmiV2Z2HNQYNM3n0w2O+tl4lDpLDN1UCialzfFO81fbHfopk/f9+RHt7b LHy1gTNrUwnLS+3Lobt5p179zNw3C9gtDMdgq355WC/B8jYYJGrw4Y0Jwh7WoyMF w1lPPEByeGTEl/P4zxegKz7oHL+DDBw9BdRdREJ3praUYAVtnMrZgJCJTS0qGh3Z 3m2wCF6yRSwGG8QkwsmoeIF2A6HwjnXcDWHWbOwkkDwh705BUXo= =QfOl -----END PGP SIGNATURE-----

4 6

Mailman option "Set Reply-To header to list" unavailable
by Ralph Seichter 01 Jun '19

01 Jun '19

Looking at https://dovecot.org/mailman/options/dovecot I see that the option "Set Reply-To header to list?" does not accept any changes from me. I assume this might be related to DMARC related header mangling that was discussed at length before. While I do not want to open that particular can of worms again, I would like to force Reply-To: dovecot(a)dovecot.org for my own (!) postings to this mailing list. I actually set this header in my MUA when I post to the Dovecot ML, but it gets overwritten to include my own sender address in Reply-To, which is not what I want. Is there something I can do on my end to ensure that replies get sent to the list only? If not, Is this something the list owners can set for me? Thanks, Ralph

2 1

[mail-crypt-plugin] Private key location in Folder Key Mode
by emordin 01 Jun '19

01 Jun '19

Nice. It worked but I think there is a little output error (probably not a big issue): When I type the following command I get this output: user'@'host:~$ doveadm -o plugin/mail_crypt_private_private_password=1234 mailbox cryptokey export -u username -U /var/vmail/domain/username/Maildir/dovecot-attributes Folder: Public ID: <Public key ID> Error: -----BEGIN PRIVATE KEY----- <private_key> -----END PRIVATE KEY----- And when I type the following command I get this output: user'@'host:~$ doveadm mailbox cryptokey export -u username -U /var/vmail/domain/username/Maildir/dovecot-attributes Folder: Public ID: <Public key ID> Error: ERROR: error:03070068:bignum routines:BN_mpi2bn:encoding error Key: So in the first command the private key shows but it's under Error, and I believe it should be under Key. Thanks again. Sent with [ProtonMail](https://protonmail.com) Secure Email.

1 0

macOS Notes.app IMAP Syncing Not Working
by Steven Smith 01 Jun '19

01 Jun '19

I’m requesting help getting macOS’s Notes.app to sync notes with a new dovecot IMAP server. Thanks to dovecot’s excellent online documentation and help from this list, I have a new perfectly functioning IMAP server. The issue is that macOS Note.app does not sync with this server. However, iOS Notes.app *does* sync and work well with this IMAP server, and the differences between macOS and iOS Notes apps are well known. (Thanks, Apple.) https://apple.stackexchange.com/questions/265579/notes-wont-sync-via-imap-i… <https://apple.stackexchange.com/questions/265579/notes-wont-sync-via-imap-i…> https://jpmens.net/2015/09/28/experiments-using-imap-for-notes/ <https://jpmens.net/2015/09/28/experiments-using-imap-for-notes/> … I am migrating from a working Server.app system in which Notes.app syncing does work across all devices, and therefore have a working dovecot configuration from Server.app, although it does not contain an explicit configuration for the “Notes” mailbox. I would greatly appreciate any help or pointers for these questions: Does anyone have a working template for dovecot that works with macOS Notes.app? I’ve posted doveconf -n of both the new server and the old Server.app server below. Would you all be able to provide advice on TO-DO’s and NOT-TO-DO’s for mailbox/name-space reconfiguration as I try to muck around with a nicely working, deployed IMAP server? I believe that the solution has something to do with name spaces and separators, and I’ve already changed the separator from the original ‘/’ to ‘.’ on the working server without success or obvious changes. All the mail boxes on the new IMAP server look like this, *without* a prefix ‘.’: > ls -1 /var/mail/tld.domain.mail/username/mdbox/mailboxes/ > Archive/ > Deleted Messages/ > Drafts/ > INBOX/ > Junk/ > Notes/ > Sent/ > Trash/ All the mailboxes on the working Server.app mailserver look like this, *with* a prefix ‘.’: > $ sudo ls -1 /Library/Server/Mail/Data/mail/users/username > .Archive > .Deleted Messages > .Drafts > .Junk > .Notes > .Sent Messages > cur > … > new > subscriptions > tmp Here are the `doveconf -n` of the new server that doesn’t sync macOS Notes.app, and the old Server.app IMAP server that does: New server `dovecot -n` [Note: original separator was set to ‘/’, now changed to ‘.’ in config.d/10-mail.conf]: > # 2.3.6 (): /opt/local/etc/dovecot/dovecot.conf > # Pigeonhole version 0.5.6 () > # OS: Darwin 18.6.0 x86_64 apfs > # Hostname: newhost.domain.tld > auth_cache_size = 10 M > auth_gssapi_hostname = $ALL > auth_krb5_keytab = /opt/local/etc/dovecot/imap.keytab > auth_mechanisms = plain gssapi > auth_realms = newhost.domain.tld > auth_socket_path = /opt/local/var/run/dovecot/auth-userdb > auth_username_format = %Ln > debug_log_path = /opt/local/var/log/mail/mail-debug.log > disable_plaintext_auth = no > first_valid_gid = 6 > first_valid_uid = 6 > imap_id_log = * > imap_id_send = "name" * "version" * > imap_idle_notify_interval = 29 mins > imap_urlauth_submit_user = submit > info_log_path = /opt/local/var/log/mail/mail-info.log > last_valid_gid = 100 > lda_mailbox_autocreate = yes > log_path = /opt/local/var/log/mail/mail-err.log > login_log_format_elements = user=<%u> method=%m rip=%r lip=%l mpid=%e %c > mail_access_groups = mail > mail_attachment_dir = /private/var/mail/tld.domain.mail/attachments > mail_attachment_fs = sis posix:mode=0666 > mail_debug = yes > mail_gid = mail > mail_home = /private/var/mail/tld.domain.mail > mail_location = mdbox:/private/var/mail/tld.domain.mail/%Ln/mdbox > mail_log_prefix = "%s(pid %p user %u): " > mail_plugins = quota zlib acl fts fts_solr fts_lucene > mail_privileged_group = mail > mail_uid = _dovecot > 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 imapsieve vnd.dovecot.imapsieve > mdbox_rotate_size = 200 M > namespace inbox { > inbox = yes > location = > mailbox Archive { > auto = subscribe > special_use = \Archive > } > mailbox Drafts { > auto = subscribe > special_use = \Drafts > } > mailbox Junk { > auto = create > special_use = \Junk > } > mailbox Notspam_train { > auto = create > special_use = \Junk > } > mailbox Sent { > auto = subscribe > special_use = \Sent > } > mailbox "Sent Messages" { > special_use = \Sent > } > mailbox Spam_train { > auto = create > special_use = \Junk > } > mailbox Trash { > auto = create > special_use = \Trash > } > prefix = > separator = . > } > passdb { > driver = pam > name = pam > } > plugin { > fts = solr > fts_autoindex = yes > fts_autoindex_exclude = \Junk > fts_solr = url=http://127.0.0.1:8983/solr/dovecot/ > imapsieve_mailbox1_before = file:/opt/local/etc/dovecot/sieve/report-spam.sieve > imapsieve_mailbox1_causes = COPY APPEND > imapsieve_mailbox1_name = Spam_train > imapsieve_mailbox2_before = file:/opt/local/etc/dovecot/sieve/report-ham.sieve > imapsieve_mailbox2_causes = COPY APPEND > imapsieve_mailbox2_name = Notspam_train > mail_log_events = delete undelete expunge copy mailbox_delete mailbox_rename > mail_log_fields = uid box msgid from subject size flags > quota_grace = 10%% > quota_rule = *:storage=16G > quota_rule2 = Trash:storage=+256M > quota_warning = storage=100%% quota-exceeded %u > quota_warning2 = storage=80%% quota-warning %u > recipient_delimiter = + > sieve = /private/var/mail/tld.domain.mail/rules/%Ln/dovecot.sieve > sieve_after = /opt/local/etc/dovecot/sieve-after.d > sieve_before = /opt/local/etc/dovecot/sieve-before.d > sieve_dir = /private/var/mail/tld.domain.mail/rules/%Ln/%u > sieve_global_extensions = +vnd.dovecot.pipe +vnd.dovecot.environment > sieve_pipe_bin_dir = /opt/local/etc/dovecot/sieve > sieve_plugins = sieve_imapsieve sieve_extprograms > sieve_quota_max_storage = 50M > } > postmaster_address = postmaster(a)domain.tld > protocols = imap lmtp sieve > quota_full_tempfail = yes > sendmail_path = /opt/local/sbin/sendmail > service auth-worker { > group = mail > user = root > } > service auth { > extra_groups = _keytabusers > idle_kill = 15 mins > unix_listener /opt/local/var/spool/postfix/private/auth { > group = mail > mode = 0660 > user = _postfix > } > } > service imap-login { > inet_listener imap { > address = 127.0.0.1, ::1 > port = 143 > } > inet_listener imaps { > port = 993 > ssl = yes > } > process_min_avail = 6 > service_count = 0 > vsz_limit = 2 G > } > service imap { > process_limit = 200 > process_min_avail = 6 > } > service lmtp { > unix_listener /opt/local/var/spool/postfix/private/dovecot-lmtp { > group = mail > mode = 0660 > user = _postfix > } > } > ssl = required > ssl_ca = </etc/certificates/newhost.domain.tld.SHA1.chain.pem > ssl_cert = </etc/certificates/newhost.domain.tld.SHA1.cert.pem > ssl_cipher_list = ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-CHACHA20-POLY1305:ECDHE-RSA-CHACHA20-POLY1305:ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES256-SHA384:ECDHE-RSA-AES256-SHA384:ECDHE-ECDSA-AES128-SHA256:ECDHE-RSA-AES128-SHA256 > ssl_dh = # hidden, use -P to show it > ssl_key = # hidden, use -P to show it > ssl_min_protocol = TLSv1.2 > ssl_prefer_server_ciphers = yes > userdb { > driver = passwd > name = passwd > } > verbose_proctitle = yes > protocol lda { > mail_fsync = optimized > mail_plugins = quota zlib acl fts fts_solr fts_lucene sieve > } > protocol imap { > mail_max_userip_connections = 50 > mail_plugins = quota zlib acl fts fts_solr fts_lucene imap_acl imap_quota imap_zlib imap_sieve > } > protocol lmtp { > mail_fsync = optimized > mail_plugins = quota zlib acl fts fts_solr fts_lucene sieve > } Old Server.app server `dovecot -n`: > # 2.2.30.2 (c0c463e): /Library/Server/Mail/Config/dovecot/dovecot.conf > # Pigeonhole version 0.4.18 (29cc74d) > # OS: Darwin 17.7.0 x86_64 apfs > aps_topic = com.apple.mail.XServer.d7d6581e-37ed-4a8a-8775-92c4c5a4bf28 > auth_gssapi_hostname = $ALL > auth_mechanisms = cram-md5 plain login gssapi > auth_realms = host.domain.tld > auth_socket_path = /var/run/dovecot/auth-userdb > auth_username_format = %n > debug_log_path = /Library/Logs/Mail/mail-debug.log > default_internal_user = _dovecot > default_login_user = _dovenull > disable_plaintext_auth = no > first_valid_gid = 6 > first_valid_uid = 6 > imap_id_log = * > imap_id_send = "name" * "version" * > imap_urlauth_submit_user = submit > info_log_path = /Library/Logs/Mail/mail-info.log > log_path = /Library/Logs/Mail/mail-err.log > login_log_format_elements = user=<%u> method=%m rip=%r lip=%l mpid=%e %c > mail_access_groups = mail > mail_attribute_dict = file:/Library/Server/Mail/Data/attributes/attributes.dict > mail_location = maildir:/Library/Server/Mail/Data/mail/%u > mail_log_prefix = "%s(pid %p user %u): " > mail_plugins = quota zlib acl fts fts_sk > 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 > mdbox_rotate_size = 200 M > namespace acl-mailboxes { > list = children > location = maildir:/Library/Server/Mail/Data/mail/users/%%u:INDEX=/Library/Server/Mail/Data/mail/shared/%%u > prefix = shared.%%u. > separator = . > subscriptions = no > type = shared > } > 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 = > } > namespace list-archives { > list = children > location = maildir:/Library/Server/Mail/Data/listserver/messages/archive/lists/%%u:INDEX=/Library/Server/Mail/Data/listserver/messages/archive/shared/%%u > prefix = archives.%%u. > separator = . > subscriptions = no > type = shared > } > passdb { > driver = od > } > passdb { > args = /Library/Server/Mail/Config/dovecot/submit.passdb > driver = passwd-file > } > plugin { > acl = vfile:/Library/Server/Mail/Config/dovecot/global-acls:cache_secs=300 > acl_shared_dict = file:/Library/Server/Mail/Data/shared/shared-mailboxes > fts = sk > quota = maildir:User quota > quota_warning = storage=100%% quota-exceeded %u > quota_warning2 = storage=80%% quota-warning %u > sieve = /Library/Server/Mail/Data/rules/%u/dovecot.sieve > sieve_dir = /Library/Server/Mail/Data/rules/%u > stats_refresh = 30 secs > stats_track_cmds = yes > } > postmaster_address = postmaster(a)host.domain.tld > protocols = imap pop3 lmtp sieve > quota_full_tempfail = yes > service auth { > extra_groups = _keytabusers > idle_kill = 15 mins > unix_listener auth-userdb { > user = _dovecot > } > } > service dns_client { > unix_listener dns-client { > mode = 0600 > } > } > service imap-login { > inet_listener imap { > port = 143 > } > inet_listener imaps { > port = 993 > ssl = yes > } > service_count = 0 > } > service imap { > client_limit = 5 > process_limit = 200 > service_count = 0 > } > service indexer-worker { > user = _dovecot > } > service lmtp { > unix_listener lmtp { > mode = 0600 > } > } > service managesieve-login { > inet_listener sieve { > port = 4190 > } > } > service pop3-login { > inet_listener pop3 { > port = 110 > } > inet_listener pop3s { > port = 995 > ssl = yes > } > } > service pop3 { > client_limit = 5 > process_limit = 200 > service_count = 0 > } > service quota-exceeded { > executable = script /Applications/Server.app/Contents/ServerRoot/usr/libexec/dovecot/quota-exceeded.sh > unix_listener quota-exceeded { > group = mail > mode = 0660 > user = _dovecot > } > user = _dovecot > } > service quota-warning { > executable = script /Applications/Server.app/Contents/ServerRoot/usr/libexec/dovecot/quota-warning.sh > unix_listener quota-warning { > group = mail > mode = 0660 > user = _dovecot > } > user = _dovecot > } > service stats { > fifo_listener stats-mail { > mode = 0600 > user = _dovecot > } > } > ssl = required > ssl_ca = </etc/certificates/host.domain.tld.SHA1.chain.pem > ssl_cert = </etc/certificates/host.domain.tld.SHA1.cert.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_key = # hidden, use -P to show it > ssl_key_path = # hidden, use -P to show it > ssl_protocols = !SSLv2 !SSLv3 > userdb { > args = partition=/Library/Server/Mail/Config/dovecot/partition_map.conf global_quota=8192 enforce_quotas=yes > driver = od > } > userdb { > args = /Library/Server/Mail/Config/dovecot/submit.passdb > driver = passwd-file > } > verbose_proctitle = yes > protocol lmtp { > mail_plugins = quota zlib acl fts fts_sk sieve push_notify > } > protocol lda { > mail_plugins = quota zlib acl fts fts_sk sieve push_notify > } > protocol imap { > mail_max_userip_connections = 20 > mail_plugins = quota zlib acl fts fts_sk imap_acl imap_quota imap_zlib > } > protocol pop3 { > mail_max_userip_connections = 6 > }

3 6

[mail-crypt-plugin] Private key location in Folder Key Mode
by emordin 01 Jun '19

01 Jun '19

Hi, So I am trying to locate the private key in dovecot-attributes but I can't seem to find it. I have went thru the strings in the file with the lib-dcrypt document as a guide but the private key doesn't seem to be in there. I'm guessing the private key is an internal attribute located here '/private/vendor/vendor.dovecot/pvt' , but according to the mail-attribute.h file that location is not accessible. Is this true? Or is there a way to see the private key? Thanks. Sent with [ProtonMail](https://protonmail.com) Secure Email.

2 1

[mail-crypt-plugin] Password Query for Folder Keys questions
by emordin 31 May '19

31 May '19

> Can you try rm dovecot-attributes file? Okay it worked. I kinda did that by 'rm -rf' the entire /var/vmail/domain, and then I ran the following: doveadm -o plugin/mail_crypt_private_password=desired_password mailbox cryptokey generate -u user -UR And I got the check mark and the ID string of characters. I sent a new email to the server, and was able to open and read the email =) I got confused on the docs... So only if using unencrypted folder keys, could I open a CRYPTED email and read it right away. But if using encrypted folder keys, first I would have to set a password for the key before I could open the CRYPTED email ? I thought logging in to the mailbox would connect the password to the key automatically. Thanks again. Sent with [ProtonMail](https://protonmail.com) Secure Email.

1 0

[mail-crypt-plugin] Password Query for Folder Keys questions
by emordin 31 May '19

31 May '19

So when I tried this way I got the following output: user'@'host:~$ doveadm -o plugin/mail_crypt_private_password=desired_password mailbox > cryptokey generate -u user -UR user'@'host:~$ And when I tried this way I got the following output: user'@'host:~$doveadm -o plugin/mail_crypt_private_password=desired_password mailbox cryptokey generate -u user -UR Folder Public ID user'@'host:~$ In both cases I sent a new email to the server, and I got errors stating the mailbox can't be opened Sent with [ProtonMail](https://protonmail.com) Secure Email.

2 1

(4) [mail-crypt-plugin] Password Query for Folder Keys questions
by emordin 31 May '19

31 May '19

>> Can you try >> >> doveadm -o plugin/mail_crypt_private_password=desired_password mailbox > cryptokey generate -u user -UR >> >> Aki > > I tried that and got the following: > > [user at host](https://dovecot.org/mailman/listinfo/dovecot) :~$ doveadm -o plugin/mail_crypt_private_password=desired_password mailbox > cryptokey generate -u user -UR > > Folder Public ID > > [user at host](https://dovecot.org/mailman/listinfo/dovecot) :~$ > > Then I sent a new email to the mail server, and I checked it with mutt but got 'Internal Error' 'error opening mailbox' and I > > checked the email with Roundcube and I can see the subject header but when I open the email its just blank. I apologize I forgot to add the '>', in the last one, so I added it and got this output: [user at host](https://dovecot.org/mailman/listinfo/dovecot):~$ doveadm -o plugin/mail_crypt_private_password=desired_password mailbox > cryptokey generate -u user -UR [user at host](https://dovecot.org/mailman/listinfo/dovecot):~$ However it still didn't work. I sent a new email and tried to access it with mutt and Roundcube and I still can't access the body message. Sent with [ProtonMail](https://protonmail.com) Secure Email.

1 0

[mail-crypt-plugin] Password Query for Folder Keys questions
by emordin 31 May '19

31 May '19

> Can you try > > doveadm -o plugin/mail_crypt_private_password=desired_password mailbox > cryptokey generate -u user -UR > > Aki I tried that and got the following: user@host:~$ doveadm -o plugin/mail_crypt_private_password=desired_password mailbox > cryptokey generate -u user -UR Folder Public ID user@host:~$ Then I sent a new email to the mail server, and I checked it with mutt but got 'Internal Error' 'error opening mailbox' and I checked the email with Roundcube and I can see the subject header but when I open the email its just blank. Sent with [ProtonMail](https://protonmail.com) Secure Email.

2 1

[mail-crypt-plugin] Password Query for Folder Keys questions
by emordin 31 May '19

31 May '19

So I believe I generated a key successfully with: 'doveadm mailbox cryptokey generate -u user -UR' because I got the output with the check mark and the Public ID string of characters. However I still can't read the CRYPTED emails when logging in with IMAP.. i'm still getting the following error in the mail log: Error: read() failed: read(/var/vmail/[domain . com/user/Maildir/cur/](http://domain.com/user/Maildir/cur/)<email_index>) failed: Private key not available: Cannot decrypt key ... : error:03070068:big num routines:BN_mpi2bn:encoding error I've tried to list the key with 'doveadm mailbox cryptokey list -u user' but I'm only getting the following output: Folder Active Public ID And I've tried to create a password with 'doveadm mailbox cryptokey password -u user -n Password1' and I'm getting the following output: result: dcrypt_key_load_private(...) failed: password missing Also my settings in conf.d: 10-mail.conf - mail_attribute_dict = file:%h/Maildir/dovecot-attributes mail_plugins = $mail_plugins mail_crypt plugins{ mail_crypt_curve = secp512r1 mail_crypt_save_version = 2 mail_crypt_require_encrypted_user_key = yes } 20-lmtp.conf - protocol lmtp{ mail_plugins = $mail_plugins sieve } And my settings in dovecot-sql.conf.ext: driver = mysql connect = host=127.0.0.1 dbname=mailserver user=mailuser password=1234 password_query = SELECT email as user,password, '%w' AS userdb_mail_crypt_private_password FROM virtual_users WHERE email='%u'; In the virtual_users table I have: id, domain_id, email, password Any ideas what the issue may be? Also am I suppose to add the 'userdb_mail_crypt_private_password' into the table and put the virtual users email login password in there? Or is it suppose to be a temporary query? Thanks. Sent with [ProtonMail](https://protonmail.com) Secure Email.

2 1

Problem SSL entrust certificate
by Il Neofita 31 May '19

31 May '19

Hi I have compiled dovecot 2.3.6 on RH 8, and I copied the configuration from dovecot 2.0.9 however, when I try to connect the new machine the certificate is not recognized The same certificate is working with apache CONNECTED(00000004) depth=0 ... verify error:num=20:unable to get local issuer certificate verify return:1 depth=0 ... verify error:num=21:unable to verify the first certificate verify return:1 ... --- No client certificate CA names sent Peer signing digest: SHA256 Peer signature type: RSA-PSS Server Temp Key: X25519, 253 bits --- SSL handshake has read 2311 bytes and written 404 bytes Verification error: unable to verify the first certificate

1 0

[mail-crypt-plugin] Password Query for Folder Keys questions
by emordin 31 May '19

31 May '19

Please disregard the previous question. But I have another... I have set up Folder Key encryption, and have sent an email to my mail server which is CRYPTED, however when I try to login to read the email I'm getting a 'Private key not available: Cannot decrypt <...>: error:03070068:bignum routines:BN_mpi2bn:encoding error'. I've tried to list the user key and generate a new keypair two different ways and have gotten the following output: doveadm mailbox cryptokey list -U user output: Folder Active Public ID doveadm mailbox cryptokey generate -u user -U output: Folder Public ID doveadm mailbox cryptokey generate -u user -Uf output: Panic: file doveadm-mail.c: line 405 (doveadm_mail_next_user): assertion failed: (ctx->exit_code !=0) Error: Raw backtrace: ............. Aborted Any advice? Sent with [ProtonMail](https://protonmail.com) Secure Email.

1 0

SIGABRT on fetching mail
by Peter Nabbefeld 30 May '19

30 May '19

Good Morning, I tried using gdb, but that doesn't work for me: $ ulimit -c unlimited $ sudo systemctl restart dovecot $ sudo -E getmail getmail version 5.13 Copyright (C) 1998-2019 Charles Cazabon. Licensed under the GNU GPL version 2. SimpleIMAPSSLRetriever:peter.nabbefeld@gmx.de@imap.gmx.net:993: getmailrc: operation error (child pid 19702 killed by signal 6) 1 messages (12551 bytes) retrieved, 0 skipped $ gdb bt 19702 GNU gdb (GDB) 8.3 Copyright (C) 2019 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-pc-linux-gnu". Type "show configuration" for configuration details. For bug reporting instructions, please see: <http://www.gnu.org/software/gdb/bugs/>. Find the GDB manual and other documentation resources online at: <http://www.gnu.org/software/gdb/documentation/>. For help, type "help". Type "apropos word" to search for commands related to "word"... bt: Datei oder Verzeichnis nicht gefunden. Attaching to process 19702 ptrace: Kein passender Prozess gefunden. /home/peter/NetBeansProjects/19702: Datei oder Verzeichnis nicht gefunden. (gdb) Finally, I could find a file in /var/lib/systemd/coredump: -rw-r-----+ 1 root root 710416 30. Mai 08:54 core.deliver.1003.d14b28050b8343f5a60c5998ef3947df.19702.1559199286000000.lz4 This is obviously the required dump. However, I'd not attach such a file to a post to the mailing list, so where can I put that? Send it directly to You? Kind regards Peter PS: I'm using Arch Linux - probably the hint above could be added to https://www.dovecot.org/bugreport-mail as a hint for other Arch users, as it's much easier than using gdb for those not using it?

1 0

[mail-crypt-plugin] Password Query for Folder Keys questions
by emordin 29 May '19

29 May '19

In Folder key plugin operation mode, using the following password query: password_query = SELECT \ email as user, password, \ '%w' AS userdb_mail_crypt_private_password \ FROM virtual_users WHERE email='%u'; Say I have two 'email' users...will each 'email' have a 'userdb_mail_crypt_private_password' field with a plaintext password (%w) in it? And is the 'userdb_mail_crypt_private_password' used automatically to decrypt the user private key which is stored in 'mail_attribute_dict' ? Sent with [ProtonMail](https://protonmail.com) Secure Email.

1 0

Convert Maildir to Dbox?
by David Mehler 29 May '19

29 May '19

Hello, I've got a Dovecot 2.3.x setup. Currently it's running Maildir storage. I'd like to convert that to Dbox specifically Sdbox safely. I'm also looking to at the same time or shortly thereafter encrypt the email storage with mail_crypt. Any help appreciated. Thanks. Dave.

6 8

Changes in sieve Dovecot 2.2
by Gter Marcelo 29 May '19

29 May '19

Hi People, I'm use dovecot in my mailbox system, until last month i used the dovecot version 2.0 and now i use version 2.2, version 2.2 works well for me, but i have one small problem, in sieve. In version 2.0 i had rules in sieve similiar to rule bellow: if allof (true){ keep; fileinto "INBOX"; redirect "xxxxxx"xxxxxx.com.br"; stop; } In the new version 2.2 this rules above, i have one problem duplicate messages in account from my clients, in paste INBOX, therefore, i changed rule to bellow ( with remove fileinto inbox) if allof (true){ keep; redirect "xxxxxx"xxxxxx.com.br"; stop; } Dovecot really changed your behavor, i did right to fix this ? Thanks a Lot, Marcelo

2 1

JMAP support in Dovecot
by Andrew Jones 29 May '19

29 May '19

Hi there, I understand there were discussions to try and develop JMAP support for Dovecot. Is this still in the pipeline for Dovecot 2.5? Regards Andrew Sent from my iPhone

10 18

mail_max_userip_connections
by hfh＠cndns.com 29 May '19

29 May '19

mail_max_userip_connections Can I set up an ip whitelist list, and the ip in this whitelist is unrestricted? thanks!!! hfh(a)cndns.com

2 1

Dict issue with PostgreSQL for last_login plugin (duplicate key)
by mabi 29 May '19

29 May '19

Hello, I am trying to setup the last_login plugin on Dovecot 2.3 in order to log a user's last IMAP login into a separate PostgreSQL table called last_login. I am actually following that guide: https://docs.iredmail.org/track.user.last.login.html with the exception that I use PostgreSQL instead of MySQL. So far it works at least for the very first login of a user but it looks like Dict always want to add a new record into my last_login table instead of updating the existing record for a specific user. Here is the error message from Dovecot: May 19 12:45:14-mbox1 dovecot: imap(user(a)domain.tld)<51915><if6KTzuJMZ25D+Vc>: Error: last_login_dict: Failed to write value: dict-server returned failure: sql dict: commit failed: ERROR: duplicate key value violates unique constraint "last_logins_pkey" It looks like Dict with PostgreSQL does not support UPDATEing an already existing record in the table. Or am I missing something? or it does not work with PostgreSQL? Which does not make much sense to me... Regards, Mabi

5 22

SIGABRT on fetching mail
by Peter Nabbefeld 29 May '19

29 May '19

Hello, I've never used gdb, so I don't know why I'm running into problems using "gdb bt". Usually, I'm fetching my mail using "sudo -E getmail", but this doesn't seem to work with backtrace. :-/ Output from "dovecot -n" attached. Kind regards, Peter

2 1

imap userdb Fatal setuid errors
by Steven Smith 28 May '19

28 May '19

I’m trying to configure dovecot lmtp in multi-user mode. My error logs are filled with messages saying that an imap process cannot do a setuid to another user: > May 21 22:28:46 imap(pid 17441 user myuser): Fatal: setuid(512(myuser) from userdb lookup) failed with euid=501(adminuser): Operation not permitted (This binary should probably be called with process user set to 512(myuser) instead of 501(adminuser)) I see that others have had similar issues, but I am not able to apply any of the fixes or workarounds to solve this issue (e.g. setting libexec/dovecot/imap as setuid-root). I’ve also tried other fixes like setting the permissions to 0777 on the userdb auth for postfix smtpd. According to the code (restrict-access.c, linked below), it appears that when a user authenticates, an imap worker process is launched that has the bid of the authenticator. When another user authenticates, this last process is used, but it does not have the permissions to perform a setuid to the new user, resulting in the Fatal error that appears in the logs. Is this a bug, or a configuration issue? I’ve posted my doveconf below. Any pointers would be greatly appreciated. Steve Related: https://serverfault.com/questions/930245/dovecot-operation-not-permitted <https://serverfault.com/questions/930245/dovecot-operation-not-permitted> https://dovecot.org/list/dovecot/2012-May/135549.html <https://dovecot.org/list/dovecot/2012-May/135549.html> https://trac.macports.org/ticket/58506 <https://trac.macports.org/ticket/58506> Code at https://github.com/dovecot/core/blob/master/src/lib/restrict-access.c <https://github.com/dovecot/core/blob/master/src/lib/restrict-access.c>: https://github.com/dovecot/core/blob/863887d4272f962926ab279ac4cf37855dd200… <https://github.com/dovecot/core/blob/863887d4272f962926ab279ac4cf37855dd200…> https://github.com/dovecot/core/blob/863887d4272f962926ab279ac4cf37855dd200… <https://github.com/dovecot/core/blob/863887d4272f962926ab279ac4cf37855dd200…> doveconf -n: > # 2.3.0.1 (ffd8a29): /opt/local/etc/dovecot/dovecot.conf > # Pigeonhole version 0.5.0.1 (d33dca20) > # OS: Darwin 18.6.0 x86_64 apfs > auth_cache_size = 10 M > auth_gssapi_hostname = $ALL > auth_krb5_keytab = /opt/local/etc/dovecot/imap.keytab > auth_mechanisms = plain gssapi > auth_realms = host.domain.tld > auth_socket_path = /opt/local/var/run/dovecot/auth-userdb > auth_username_format = %Ln > debug_log_path = /opt/local/var/log/mail/mail-debug.log > default_internal_user = _dovecot > default_login_user = _dovenull > disable_plaintext_auth = no > first_valid_gid = 6 > first_valid_uid = 6 > imap_id_log = * > imap_id_send = "name" * "version" * > imap_idle_notify_interval = 29 mins > imap_urlauth_submit_user = submit > info_log_path = /opt/local/var/log/mail/mail-info.log > last_valid_gid = 100 > lda_mailbox_autocreate = yes > log_path = /opt/local/var/log/mail/mail-err.log > login_log_format_elements = user=<%u> method=%m rip=%r lip=%l mpid=%e %c > mail_access_groups = mail > mail_attachment_dir = /private/var/mail/tld.domain.mail/attachments > mail_attachment_fs = sis posix:mode=0666 > mail_debug = yes > mail_gid = mail > mail_home = /private/var/mail/tld.domain.mail > mail_location = mdbox:/private/var/mail/tld.domain.mail/%Ln/mdbox > mail_log_prefix = "%s(pid %p user %u): " > mail_plugins = quota zlib acl fts fts_solr fts_lucene > mail_privileged_group = mail > mail_uid = _dovecot > 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 imapsieve vnd.dovecot.imapsieve > mdbox_rotate_size = 200 M > namespace inbox { > inbox = yes > location = > mailbox Archive { > auto = subscribe > special_use = \Archive > } > mailbox Drafts { > auto = subscribe > special_use = \Drafts > } > mailbox Junk { > auto = create > special_use = \Junk > } > mailbox Notspam_train { > auto = create > special_use = \Junk > } > mailbox Sent { > auto = subscribe > special_use = \Sent > } > mailbox Spam_train { > auto = create > special_use = \Junk > } > mailbox Trash { > auto = create > special_use = \Trash > } > prefix = > separator = / > } > passdb { > driver = pam > name = pam > } > plugin { > fts = solr > fts_autoindex = yes > fts_autoindex_exclude = \Junk > fts_solr = url=http://127.0.0.1:8983/solr/dovecot/ > imapsieve_mailbox1_before = file:/opt/local/etc/dovecot/sieve/report-spam.sieve > imapsieve_mailbox1_causes = COPY APPEND > imapsieve_mailbox1_name = Spam_train > imapsieve_mailbox2_before = file:/opt/local/etc/dovecot/sieve/report-ham.sieve > imapsieve_mailbox2_causes = COPY APPEND > imapsieve_mailbox2_name = Notspam_train > mail_log_events = delete undelete expunge copy mailbox_delete mailbox_rename > mail_log_fields = uid box msgid from subject size flags > quota_grace = 10%% > quota_rule = *:storage=16G > quota_rule2 = Trash:storage=+256M > quota_warning = storage=100%% quota-exceeded %u > quota_warning2 = storage=80%% quota-warning %u > recipient_delimiter = + > sieve = /private/var/mail/tld.domain.mail/rules/%Ln/dovecot.sieve > sieve_after = /opt/local/etc/dovecot/sieve-after.d > sieve_before = /opt/local/etc/dovecot/sieve-before.d > sieve_dir = /private/var/mail/tld.domain.mail/rules/%Ln/%u > sieve_global_extensions = +vnd.dovecot.pipe +vnd.dovecot.environment > sieve_pipe_bin_dir = /opt/local/etc/dovecot/sieve > sieve_plugins = sieve_imapsieve sieve_extprograms > sieve_quota_max_storage = 50M > } > postmaster_address = postmaster(a)domain.tld > protocols = imap lmtp sieve > quota_full_tempfail = yes > sendmail_path = /opt/local/sbin/sendmail > service auth-worker { > user = root > } > service auth { > extra_groups = _keytabusers > idle_kill = 15 mins > unix_listener /opt/local/var/spool/postfix/private/auth { > group = mail > mode = 0660 > user = _postfix > } > } > service imap-login { > inet_listener imap { > address = 127.0.0.1, ::1 > port = 143 > } > inet_listener imaps { > port = 993 > ssl = yes > } > process_min_avail = 6 > service_count = 0 > vsz_limit = 2 G > } > service imap { > client_limit = 16 > process_limit = 200 > process_min_avail = 6 > service_count = 0 > } > service lmtp { > unix_listener /opt/local/var/spool/postfix/private/dovecot-lmtp { > group = mail > mode = 0660 > user = _postfix > } > } > ssl = required > ssl_ca = </etc/certificates/chain.pem > ssl_cert = </etc/certificates/cert.pem > ssl_cipher_list = ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-CHACHA20-POLY1305:ECDHE-RSA-CHACHA20-POLY1305:ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES256-SHA384:ECDHE-RSA-AES256-SHA384:ECDHE-ECDSA-AES128-SHA256:ECDHE-RSA-AES128-SHA256 > ssl_dh = # hidden, use -P to show it > ssl_key = # hidden, use -P to show it > ssl_min_protocol = TLSv1.2 > ssl_prefer_server_ciphers = yes > userdb { > driver = passwd > name = passwd > } > verbose_proctitle = yes > protocol lda { > mail_fsync = optimized > mail_plugins = quota zlib acl fts fts_solr fts_lucene sieve > } > protocol imap { > mail_max_userip_connections = 50 > mail_plugins = quota zlib acl fts fts_solr fts_lucene imap_acl imap_quota imap_zlib imap_sieve > } > protocol lmtp { > mail_fsync = optimized > mail_plugins = quota zlib acl fts fts_solr fts_lucene sieve > }

2 2

ssl_dh
by ＠lbutlr 28 May '19

28 May '19

Does ssl_dh need to be manually updated each time the underlying certificate renews? -- 2+2=5 for sufficiently large values of 2.

2 1

Hello some help on login users saying it's disabled
by Remo Mattei 28 May '19

28 May '19

Hello I am experiencing some strange issue with the dovecot, the web round cube works fine but when I try to connect with an iPhone over IMAP IMAPs it tells me that the account is disabled. Please advice here is what I see in the logs: May 25 14:30:32 imap-login: Info: Aborted login (no auth attempts in 0 secs): user=<>, rip=172.10.163.251, lip=208.53.44.237, session=<4AZjBr2J2cisCqP7> May 25 14:30:32 imap-login: Info: Aborted login (no auth attempts in 0 secs): user=<>, rip=172.10.163.251, lip=208.53.44.237, session=<fFVkBr2J2sisCqP7> May 25 14:30:32 imap-login: Info: Aborted login (no auth attempts in 0 secs): user=<>, rip=172.10.163.251, lip=208.53.44.237, session=<TnpkBr2J28isCqP7> May 25 14:30:32 imap-login: Info: Aborted login (no auth attempts in 0 secs): user=<>, rip=172.10.163.251, lip=208.53.44.237, session=<KcplBr2J3MisCqP7> May 25 14:30:34 imap-login: Info: Aborted login (no auth attempts in 0 secs): user=<>, rip=172.10.163.251, lip=208.53.44.237, session=<wPiABr2J3cisCqP7> May 25 14:30:34 imap-login: Info: Aborted login (no auth attempts in 0 secs): user=<>, rip=172.10.163.251, lip=208.53.44.237, session=<gDSCBr2J3sisCqP7> May 25 14:30:37 imap-login: Info: Aborted login (no auth attempts in 0 secs): user=<>, rip=172.10.163.251, lip=208.53.44.237, session=<byuzBr2J4MisCqP7> May 25 14:30:37 imap-login: Info: Aborted login (no auth attempts in 0 secs): user=<>, rip=172.10.163.251, lip=208.53.44.237, session=<ob20Br2J4cisCqP7> May 25 14:30:39 imap-login: Info: Aborted login (no auth attempts in 0 secs): user=<>, rip=172.10.163.251, lip=208.53.44.237, session=<bUfQBr2J4sisCqP7> May 25 14:30:39 imap-login: Info: Aborted login (no auth attempts in 0 secs): user=<>, rip=172.10.163.251, lip=208.53.44.237, session=<tsbRBr2J48isCqP7> And the account does not show any mail whereas the Web shows the mail just fine. Thanks

4 3

pam authentication error?
by unknown＠example.com 28 May '19

28 May '19

Getting this: auth-worker(5045): Error: pam(kremels,xxx.xxx.xxx.xxx: pam_authenticate() failed: authentication error (/etc/pam.d/dovecot missing?) # cat /etc/pam.d/dovcot auth required pam_unix.so nullok account required pam_unix.so (file was last updated in April of 2018) passdb { username_filter = "!*@*" driver = pam } userdb { driver = passwd } service auth { unix_listener auth-userdb { } unix_listener /var/spool/postfix/private/auth { mode = 0666 } } # ls -ls /var/spool/postfix/private/auth 0 srw-rw-rw- 1 root wheel 0 May 27 13:57 /var/spool/postfix/private/auth postfix/main.cf: smtpd_sasl_authenticated_header = yes smtpd_sasl_path = private/auth smtpd_sasl_type = dovecot smtpd_starttls_timeout = 20s smtpd_tls_cert_file = /usr/local/etc/dehydrated/certs/covisp.net/fullchain.pem smtpd_tls_key_file = /usr/local/etc/dehydrated/certs/covisp.net/privkey.pem smtpd_tls_loglevel = 1 smtpd_tls_received_header = yes smtpd_tls_security_level = may 16 -rw------- 1 root 443 4152 May 20 21:08 fullchain-1558408117.pem 0 lrwx------ 1 root 443 24 May 20 21:08 fullchain.pem -> fullchain-1558408117.pem 8 -rw------- 1 root 443 3243 May 20 21:08 privkey-1558408117.pem 0 lrwx------ 1 root 443 22 May 20 21:08 privkey.pem -> privkey-1558408117.pem

2 1

Re: Hello some help on login users saying it's disabled
by Joseph Tam 27 May '19

27 May '19

> Hello I am experiencing some strange issue with the dovecot, the web > round cube works fine but when I try to connect with an iPhone over > IMAP IMAPs it tells me that the account is disabled. > > May 25 14:30:32 imap-login: Info: Aborted login (no auth attempts in 0 secs): user=<>, rip=... > ... It's probably the iPhone mail app trying to be clever and auto-configuring the settings for IMAP (and getting it wrong). To stop this behaviour, hardwire the iPhone IMAP parameters, then disable "Automatic manage connection". If you use SSL/TLS, this will also secure you from plaintext MITM attacks. Other oddities I've seen from Apple mail readers: 1) If you don't disable "Automatic manage connection", it will also hunt around for outgoing mail settings. 2) Once in a while, it initiates an idle authenticated SMTP session (i.e. authenticates, but does nothing). 3) Roofs your user IMAP connection limit when the client does global mail searches. Joseph Tam <jtam.home(a)gmail.com>

1 0

SIGABRT on fetching mail
by Peter Nabbefeld 27 May '19

27 May '19

Hello, I still cannot fetch my mails, relying on my smartphone (which makes it a burden to read my mails ...) - could probably somebody help me? Kind regards, Peter

2 2

Error suggestions please
by Remo Mattei 27 May '19

27 May '19

May 25 15:01:27 imap(xxxxx(a)italy1.com)<10256><LsrOdL2J3uisCqP7>: Error: Mailbox INBOX: UID=208: read(/home/vpopmail/domains/italy1.com/xxxxx/Maildir/cur/1154731221.9257.az… failed: Cached message size smaller than expected (26421 < 26511, box=INBOX, UID=208) (read reason=mail stream) May 25 15:01:27 imap(xxxxxx(a)italy1.com)<10256><LsrOdL2J3uisCqP7>: Error: Corrupted record in index cache file /home/vpopmail/domains/italy1.com/xxxxx/Maildir/dovecot.index.cache: UID 208: Broken physical size in mailbox INBOX: read(/home/vpopmail/domains/italy1.com/xxxxx/Maildir/cur/1154731221.9257.az… failed: Cached message size smaller than expected (26421 < 26511, box=INBOX, UID=208) May 25 15:01:27 imap(xxxxxx(a)italy1.com)<10256><LsrOdL2J3uisCqP7>: Panic: file istream.c: line 315 (i_stream_read_memarea): assertion failed: (old_size <= _stream->pos - _stream->skip) Can someone tell help on how to fix this issue. Thanks

3 3

Unknown error message
by Jerry 26 May '19

26 May '19

dovecot 2.3.6 (7eab80676) FreeBSD 12.0-RELEASE-p5 amd64 I have recently been finding error messages similar to the following in my Dovecot log file: May 26 06:58:32 imap(gerard(a)seibercom.net)<87791><WvXT+LyJHBCubeH6>: Error: stat(/var/mail/vmail/seibercom.net/gerard/.dovecot.sieve/tmp) failed: Not a directory The message is correct as there is no such directory. The question is why has it suddenly started appearing? I checked my maillog file, and there are no messages being transmitted to Dovecot when that error message is created. Neither is there any mail with that ID number either. Could this be someone attempting to hack into my system? Thanks! -- Jerry

2 1

Automatically subscribe to the INBOX folder
by glts 26 May '19

26 May '19

Hello, I am using the ‘auto = subscribe’ feature in the mailbox configuration section in the usual fashion (as shown in conf.d/15-mailboxes.conf): namespace inbox { inbox = yes mailbox Drafts { special_use = \Drafts auto = subscribe } ... } When I connect to an account with the Thunderbird mail client, those mailboxes/folders get autocreated and autosubscribed. Good! INBOX, however, does not get subscribed to automatically. When I look at the account’s subscriptions in Thunderbird, all folders are subscribed, except INBOX. How can I enable autosubscribe for the INBOX folder (like the other folders)? Is there an option for this? This is in Dovecot 2.2.22. Cheers, David

2 1

Workaround for infinite loop in XCLIENT command bug
by mabi 26 May '19

26 May '19

Hello, I am running Dovecot 2.3.5 package on OpenBSD 6.5 and it looks like this bug which has been fixed in 2.3.6 is hitting me: lib-smtp: client: Fix infinite loop in XCLIENT command interaction with server https://github.com/dovecot/core/commit/5d03f39b345127b80d145ee90772739baa7a… so I was wondering if there is any workarounds? Maybe like disabling the XCLIENT command from the config file or something similar? My original post regarding this issue is here: https://www.mail-archive.com/misc@opensmtpd.org/msg04362.html I first thought this was an OpenSMTPD issue but it seems to be that Dovecot bug. Cheers, Mabi

3 6

Dovecot multiple passdb and fail2ban
by Joaquin F 26 May '19

26 May '19

Objective: different password for remote and local imap login Version: 2.2.36 (1f10bfa63) on CentOS 7 Users are from Active Directory, mapped to local users via sssd After much experimentation, I have configured this way: doveconf -n passdb userdb passdb { args = username_format=%Ln /etc/dovecot/remote driver = passwd-file skip = authenticated username_filter = user01 user02 } passdb { driver = pam override_fields = allow_nets=127.0.0.0/8,192.168.1.0/24 skip = authenticated } userdb { driver = passwd } If I put the passdb's in the reverse order, I would get failure messages (when logging in remotely) in /var/log/secure, such as: auth: pam_sss(dovecot:auth): authentication failure; logname= uid=0 euid=0 tty=dovecot ruser=user02 rhost=xx.xx.xx.xx user=user02 Which caused fail2ban to ban that ip /etc/fail2ban/jail.local [dovecot] enabled = true port = imap,imaps If I set "auth_verbose = yes", then I can see messages in (when logging in locally) in /var/log/maillog dovecot: auth: passwd-file(user02,192.168.1.20,<Na/7f8WJC8HAqAEU>): Password mismatch which is probably not a big deal... but seems inefficient? Question: is there a more elegant way to use different passdb depending on ip? Thanks in advance.

1 0

Imap reverse / proxy in front of our clients machines.
by Brent Clark 25 May '19

25 May '19

Good day Guys I have a user story have an imap reverse / proxy in front of our clients servers. Im currently using the following sources for information. https://wiki.failover.de/Email/Dovecot/IMAP/Proxy/ https://gist.github.com/rplessl/dd56d05c84f988706418 https://wiki2.dovecot.org/PasswordDatabase/ExtraFields/Proxy In my vagrant instance, dovecot can connect to the the remote server You can see my debugging and conf: https://pastebin.com/raw/H2AL53Fz https://pastebin.com/raw/hZHSHvcu If anyone can assist it would be greatly appreciated. Many thanks Regards Brent

1 0

Race condition in IMAP NOTIFY for events received NOTIFY_DELAY_MSECS apart
by Guilhem Moulin 25 May '19

25 May '19

Hi there, There seem to be a race condition in IMAP NOTIFY: when two events for the SELECTED mailbox are received soon after one another, sometimes only the first one is being reported to clients that enabled IMAP NOTIFY. On closer look it seems like this is most often reproducible when the delay between the two events is NOTIFY_DELAY_MSECS (500ms). This is with 2.3.4.1 from Debian sid. $ sed -r 's/^\s*//; s/\s+/ /g' >/tmp/dovecot.conf <<-EOF log_path = /tmp/dovecot.log mailbox_list_index = yes mail_home = /dev/shm/dovecot-test/%u mail_location = dbox:~/mail ssl = no EOF (`doveconf -c /tmp/dovecot.conf -n` output enclosed.) $ rm -rf /dev/shm/dovecot-test && mkdir -m0700 /dev/shm/dovecot-test $ env -i USER=user HOME=/dev/shm/dovecot-test/user PATH=/usr/bin:/bin \ doveadm -c /tmp/dovecot.conf exec imap S: * PREAUTH [CAPABILITY IMAP4rev1 … NOTIFY] Logged in as user C: a NOTIFY SET STATUS (SELECTED (MessageNew MessageExpunge FlagChange)) (MAILBOXES (INBOX test) (MessageNew MessageExpunge FlagChange)) S: * STATUS INBOX (MESSAGES 0 UIDNEXT 1 UIDVALIDITY 1558785754 UNSEEN 0 HIGHESTMODSEQ 1) S: a OK NOTIFY completed (0.004 + 0.000 + 0.003 secs). S: * STATUS INBOX (MESSAGES 0 UIDNEXT 1 UIDVALIDITY 1558785754 UNSEEN 0 HIGHESTMODSEQ 1) C: b SELECT INBOX […] S: b OK [READ-WRITE] Select completed (0.001 + 0.000 secs). Now deliver two messages to INBOX with ~500ms in between: $ env -i USER=user HOME=/dev/shm/dovecot-test/user PATH=/usr/bin:/bin sh -c \ 'echo -n . | doveadm -c /tmp/dovecot.conf exec dovecot-lda -e -m INBOX; \ sleep 0.500; \ echo -n . | doveadm -c /tmp/dovecot.conf exec dovecot-lda -e -m INBOX' Only the the first message is reported in the above IMAP session: S: * 1 EXISTS S: * 1 RECENT An UNSELECT doesn't trigger the notification, but (of course) a NOOP does: C: c NOOP S: * 2 EXISTS S: * 2 RECENT S: c OK NOOP completed (0.001 + 0.000 secs). Similarly, for two flag changes within 0.5s only the first is recorded: $ env -i USER=user HOME=/dev/shm/dovecot-test/user PATH=/usr/bin:/bin sh -c \ 'doveadm -c /tmp/dovecot.conf flags add "\\Seen" mailbox INBOX 1; \ sleep 0.500; \ doveadm -c /tmp/dovecot.conf flags add "\\Answered" mailbox INBOX 2' yields a single unsolicited FETCH response: S: * 1 FETCH (MODSEQ (4) FLAGS (\Seen \Recent)) AFAICT this is only reproducible in the ‘SELECTED’ mailbox specifier: after creating a mailbox "test", $ env -i USER=user HOME=/dev/shm/dovecot-test/user PATH=/usr/bin:/bin sh -c \ 'echo -n . | doveadm -c /tmp/dovecot.conf exec dovecot-lda -e -m test; \ sleep 0.500; \ echo -n . | doveadm -c /tmp/dovecot.conf exec dovecot-lda -e -m test' yields two unsolicited STATUS responses as expected: * STATUS test (MESSAGES 1 UIDNEXT 2 UIDVALIDITY 1558787038 UNSEEN 1 HIGHESTMODSEQ 2) * STATUS test (MESSAGES 2 UIDNEXT 3 UIDVALIDITY 1558787038 UNSEEN 2 HIGHESTMODSEQ 3) (And same thing for two flag updates in the "test" mailbox.) This is not specific to INBOX as once "test" is selected the same problem arises. AFAICT the race is in ‘src/lib-storage/list/mailbox-list-index-notify.c’ which for some reason doesn't acknowledge ST_CHANGED() after inotify_rm_watch(), but I couldn't get my head around that file. Cheers, -- Guilhem.

1 0

SIGABRT on fetching mail
by Peter Nabbefeld 24 May '19

24 May '19

Hello, I'm running dovecot with getmail for several months already, but today it's always crashing: "getmailrc: operation error (child pid 2995 killed by signal 6)". The deliver process aborts due to an unknown reason. > tail /var/log/dovecot-info.log May 24 12:10:28 imap-login: Info: Login: user=<peter.nabbefeld(a)gmx.de>, method=PLAIN, rip=::1, lip=::1, mpid=2970, secured, session=<n/dfaJ+JuIMAAAAAAAAAAAAAAAAAAAAB> May 24 12:10:49 lda(peter.nabbefeld(a)gmx.de)<2994><kCP3FifD51yyCwAA7IIYzw>: Info: sieve: msgid=<318D121B-37FC-4E8C-B4B8-93C87E0692B8(a)gmx.de>: stored mail into mailbox 'Gesendet' May 24 15:14:30 imap-login: Info: Login: user=<peter.nabbefeld(a)gmx.de>, method=PLAIN, rip=::1, lip=::1, mpid=6304, secured, session=<+Rae+qGJ4IUAAAAAAAAAAAAAAAAAAAAB> May 24 15:14:31 imap(peter.nabbefeld(a)gmx.de)<6304><+Rae+qGJ4IUAAAAAAAAAAAAAAAAAAAAB>: Info: Connection closed (append finished 0.562 secs ago) in=157758 out=520 deleted=0 expunged=0 trashed=0 hdr_count=0 hdr_bytes=0 body_count=0 body_bytes=0 May 24 15:14:37 imap-login: Info: Login: user=<peter.nabbefeld(a)gmx.de>, method=PLAIN, rip=::1, lip=::1, mpid=6307, secured, session=<MjwD+6GJ4oUAAAAAAAAAAAAAAAAAAAAB> May 24 15:55:28 imap-login: Info: Login: user=<peter.nabbefeld(a)gmx.de>, method=PLAIN, rip=::1, lip=::1, mpid=7205, secured, session=<T9ofjaKJgIYAAAAAAAAAAAAAAAAAAAAB> May 24 15:57:00 imap-login: Info: Login: user=<peter.nabbefeld(a)gmx.de>, method=PLAIN, rip=::1, lip=::1, mpid=7254, secured, session=<nT6XkqKJhIYAAAAAAAAAAAAAAAAAAAAB> May 24 16:08:22 imap-login: Info: Login: user=<peter.nabbefeld(a)gmx.de>, method=PLAIN, rip=::1, lip=::1, mpid=7507, secured, session=<LI40u6KJJIcAAAAAAAAAAAAAAAAAAAAB> May 24 16:16:40 imap(peter.nabbefeld(a)gmx.de)<6307><MjwD+6GJ4oUAAAAAAAAAAAAAAAAAAAAB>: Info: Connection closed (IDLE running for 0.001 + waiting input for 0.001 secs, 2 B in + 10 B out, state=wait-input) in=4251 out=137885 deleted=0 expunged=0 trashed=0 hdr_count=1 hdr_bytes=661 body_count=0 body_bytes=0 May 24 16:16:54 imap-login: Info: Login: user=<peter.nabbefeld(a)gmx.de>, method=PLAIN, rip=::1, lip=::1, mpid=7662, secured, session=<zV++2aKJOIcAAAAAAAAAAAAAAAAAAAAB> > tail /var/log/dovecot.log May 24 11:25:33 master: Warning: Killed with signal 15 (by pid=12275 uid=0 code=kill) May 24 11:25:35 log(660): Warning: Killed with signal 15 (by pid=1 uid=0 code=kill) May 24 12:10:47 lda(peter.nabbefeld(a)gmx.de)<2994><kCP3FifD51yyCwAA7IIYzw>: Warning: Failed to parse return-path header May 24 12:10:50 lda(peter.nabbefeld(a)gmx.de)<2995><hco1BirD51yzCwAA7IIYzw>: Panic: file istream-crlf.c: line 24 (i_stream_crlf_read_common): assertion failed: (ret != -2) May 24 12:10:50 lda(peter.nabbefeld(a)gmx.de)<2995><hco1BirD51yzCwAA7IIYzw>: Error: Raw backtrace: /usr/lib/dovecot/libdovecot.so.0(+0xeee14) [0x7fd668defe14] -> /usr/lib/dovecot/libdovecot.so.0(+0xeee51) [0x7fd668defe51] -> /usr/lib/dovecot/libdovecot.so.0(+0x46268) [0x7fd668d47268] -> /usr/lib/dovecot/libdovecot.so.0(+0x4892e) [0x7fd668d4992e] -> /usr/lib/dovecot/libdovecot.so.0(+0x1004e6) [0x7fd668e014e6] -> /usr/lib/dovecot/libdovecot.so.0(i_stream_read_memarea+0x81) [0x7fd668dfd681] -> /usr/lib/dovecot/libdovecot.so.0(i_stream_read+0x36) [0x7fd668dfd8a6] -> /usr/lib/dovecot/libdovecot.so.0(+0x1058f8) [0x7fd668e068f8] -> /usr/lib/dovecot/libdovecot.so.0(i_stream_read_memarea+0x81) [0x7fd668dfd681] -> /usr/lib/dovecot/libdovecot.so.0(i_stream_read+0x36) [0x7fd668dfd8a6] -> /usr/lib/dovecot/libdovecot.so.0(i_stream_read_data+0x4c) [0x7fd668dfe33c] -> /usr/lib/dovecot/libdovecot.so.0(io_stream_copy+0x8a) [0x7fd668e18aba] -> /usr/lib/dovecot/libdovecot.so.0(+0x119ac2) [0x7fd668e1aac2] -> /usr/lib/dovecot/libdovecot.so.0(o_stream_send_istream+0x4f) [0x7fd668e1874f] -> /usr/lib/dovecot/libdovecot-storage.so.0(index_storage_save_continue+0x2e) [0x7fd668f981ee] -> /usr/lib/dovecot/libdovecot-storage.so.0(maildir_save_continue+0x27) [0x7fd668f36887] -> /usr/lib/dovecot/libdovecot-storage.so.0(mailbox_save_continue+0x44) [0x7fd668f083f4] -> /usr/lib/dovecot/libdovecot-storage.so.0(mail_storage_copy+0xf8) [0x7fd668ef9828] -> /usr/lib/dovecot/libdovecot-storage.so.0(maildir_copy+0x59) [0x7fd668f32639] -> /usr/lib/dovecot/libdovecot-lda.so.0(+0x3d5c) [0x7fd66902ad5c] -> /usr/lib/dovecot/modules/lib20_fts_plugin.so(+0x10eec) [0x7fd668a90eec] -> /usr/lib/dovecot/libdovecot-storage.so.0(+0x58981) [0x7fd668f08981] -> /usr/lib/dovecot/libdovecot-sieve.so.0(+0x4e6df) [0x7fd66676e6df] -> /usr/lib/dovecot/libdovecot-sieve.so.0(sieve_result_execute+0x4e5) [0x7fd666764065] -> /usr/lib/dovecot/libdovecot-sieve.so.0(+0x57259) [0x7fd666777259] -> /usr/lib/dovecot/libdovecot-sieve.so.0(sieve_multiscript_run+0xa2) [0x7fd6667783f2] -> /usr/lib/dovecot/modules/lib90_sieve_plugin.so(+0x3d45) [0x7fd668cecd45] -> /usr/lib/dovecot/libdovecot-lda.so.0(mail_deliver+0xf9) [0x7fd66902c229] How can I find out which message is causing the crash? It would be very helpful, if the message's subject and receipt time could be logged in case of an abort or anything else that could help identify the corrupt message. This would also enable me to send You the message for further investigation (if appropriate). Kind regards Peter

1 0

Panic: file mail-index-util.c: line 10 (mail_index_uint32_to_offset): assertion failed: (offset < 0x40000000)
by Ralf Hildebrandt 24 May '19

24 May '19

I'm encountering a crash which this command: % doveadm import -u restore(a)backup.invalid mdbox:/home/copymail2/mdbox '' mailbox INBOX header X-Spam Yes SAVEDBEFORE 2019-05-23 doveadm(restore(a)backup.invalid): Panic: file mail-index-util.c: line 10 (mail_index_uint32_to_offset): assertion failed: (offset < 0x40000000) doveadm(restore(a)backup.invalid): Error: Raw backtrace: /usr/lib/dovecot/libdovecot.so.0(+0xd9f9e) [0x7fbc52ba7f9e] -> /usr/lib/dovecot/libdovecot.so.0(+0xd9fe1) [0x7fbc52ba7fe1] -> /usr/lib/dovecot/libdovecot.so.0(i_fatal+0) [0x7fbc52b0cc54] -> /usr/lib/dovecot/libdovecot-storage.so.0(mail_index_uint32_to_offset+0x78)[0x7fbc52f525e8] -> /usr/lib/dovecot/libdovecot-storage.so.0(mail_cache_add+0x83b)[0x7fbc52f3ac2b] -> /usr/lib/dovecot/libdovecot-storage.so.0(index_mail_parse_header+0x449)[0x7fbc52f1c969] -> /usr/lib/dovecot/libdovecot.so.0(+0xb6af9) [0x7fbc52b84af9] -> /usr/lib/dovecot/libdovecot.so.0(i_stream_read_memarea+0x7a) [0x7fbc52bb531a] -> /usr/lib/dovecot/libdovecot.so.0(i_stream_read+0x2f) [0x7fbc52bb565f] -> /usr/lib/dovecot/libdovecot.so.0(i_stream_read_data+0x3d)[0x7fbc52bb604d] -> /usr/lib/dovecot/libdovecot.so.0(message_parse_header_next+0x68)[0x7fbc52b8b3f8] -> /usr/lib/dovecot/libdovecot.so.0(message_parse_header+0x52)[0x7fbc52b8bdd2] -> /usr/lib/dovecot/libdovecot-storage.so.0(+0xcadae) [0x7fbc52f26dae] -> /usr/lib/dovecot/libdovecot-storage.so.0(+0xcc0ac) [0x7fbc52f280ac] -> /usr/lib/dovecot/libdovecot-storage.so.0(index_storage_search_next_nonblock+0x11d)[0x7fbc52f288bd] -> /usr/lib/dovecot/libdovecot-storage.so.0(mailbox_search_next_nonblock+0x28)[0x7fbc52ea92e8] -> /usr/lib/dovecot/libdovecot-storage.so.0(mailbox_search_next+0x3d)[0x7fbc52ea934d] -> doveadm(+0x31443) [0x5635b4760443] -> doveadm(+0x2bdb1) [0x5635b475adb1] -> doveadm(+0x2caf9) [0x5635b475baf9] -> doveadm(doveadm_cmd_ver2_to_mail_cmd_wrapper+0x20e) [0x5635b475c9ce] -> doveadm(doveadm_cmd_run_ver2+0x55e) [0x5635b476db7e] -> doveadm(doveadm_cmd_try_run_ver2+0x37) [0x5635b476dbd7] -> doveadm(main+0x1d1) [0x5635b474aec1] -> /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xe7) [0x7fbc5210fb97] -> doveadm(_start+0x2a) [0x5635b474b39a] Version info: ii dovecot-core 2:2.3.6-2~bionic amd64 secure POP3/IMAP server - core files ii dovecot-dbg 2:2.3.6-2~bionic amd64 secure POP3/IMAP server - debug symbols ii dovecot-imapd 2:2.3.6-2~bionic amd64 secure POP3/IMAP server - IMAP daemon ii dovecot-lmtpd 2:2.3.6-2~bionic amd64 secure POP3/IMAP server - LMTP server Backtrace: Program received signal SIGABRT, Aborted. __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51 51../sysdeps/unix/sysv/linux/raise.c: No such file or directory. (gdb) bt #0 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51 #1 0x00007ffff68fa801 in __GI_abort () at abort.c:79 #2 0x00007ffff7373f51 in default_fatal_finish (status=0, type=LOG_TYPE_PANIC) at failures.c:459 #3 fatal_handler_real (ctx=<optimized out>, format=<optimized out>, args=<optimized out>) at failures.c:471 #4 0x00007ffff7373fe1 in default_fatal_handler (ctx=<optimized out>, format=<optimized out>, args=<optimized out>) at failures.c:479 #5 0x00007ffff72d8c54 in i_panic (format=format@entry=0x7ffff772e440 "file %s: line %d (%s): assertion failed: (%s)") at failures.c:523 #6 0x00007ffff771e5e8 in mail_index_uint32_to_offset (offset=<optimized out>) at mail-index-util.c:10 #7 0x00007ffff7706c2b in mail_cache_header_fields_write (ctx=0x55555583d960, buffer=<optimized out>, buffer=<optimized out>) at mail-cache-transaction.c:609 #8 mail_cache_header_add_field (field_idx=15, ctx=0x55555583d960) at mail-cache-transaction.c:690 #9 mail_cache_add (ctx=0x55555583d960, seq=1, field_idx=field_idx@entry=15, data=0x7ffff773ba56, data_size=0) at mail-cache-transaction.c:739 #10 0x00007ffff76eafdc in index_mail_cache_add_idx (mail=mail@entry=0x55555583e2f8, field_idx=field_idx@entry=15, data=data@entry=0x7ffff773ba56, data_size=data_size@entry=0) at index-mail.c:621 #11 0x00007ffff76e8969 in index_mail_parse_header_finish (mail=<optimized out>) at index-mail-headers.c:132 #12 index_mail_parse_header (part=<optimized out>, hdr=<optimized out>, mail=<optimized out>) at index-mail-headers.c:312 #13 0x00007ffff7350af9 in read_header (mstream=0x55555584b7f0) at istream-header-filter.c:357 #14 i_stream_header_filter_read (stream=0x55555584b7f0) at istream-header-filter.c:447 #15 0x00007ffff738131a in i_stream_read_memarea (stream=stream@entry=0x55555584b870) at istream.c:313 #16 0x00007ffff738165f in i_stream_read (stream=stream@entry=0x55555584b870) at istream.c:271 #17 0x00007ffff738204d in i_stream_read_data (stream=0x55555584b870, data_r=data_r@entry=0x7fffffffdbe8, size_r=size_r@entry=0x7fffffffdbf0, threshold=threshold@entry=1) at istream.c:745 #18 0x00007ffff73573f8 in i_stream_read_bytes (wanted=2, size_r=0x7fffffffdbf0, data_r=0x7fffffffdbe8, stream=<optimized out>) at ../../src/lib/istream.h:217 #19 message_parse_header_next (ctx=0x55555584ca70, hdr_r=hdr_r@entry=0x7fffffffdc50) at message-header-parser.c:85 #20 0x00007ffff7357dd2 in message_parse_header (input=<optimized out>, hdr_size=hdr_size@entry=0x0,flags=flags@entry=MESSAGE_HEADER_PARSER_FLAG_CLEAN_ONELINE, callback=callback@entry=0x7ffff76f2310 <search_header>, context=context@entry=0x7fffffffdcc0) at message-header-parser.c:392 #21 0x00007ffff76f2dae in search_arg_match_text (ctx=0x55555583dd20, args=0x555555809690) at index-search.c:760 #22 search_match_once (ctx=0x55555583dd20) at index-search.c:1400 #23 0x00007ffff76f40ac in search_match_next (ctx=0x55555583dd20) at index-search.c:1507 #24 search_more_with_mail (mail=<optimized out>, ctx=0x55555583dd20) at index-search.c:1624 #25 search_more_with_prefetching (mail_r=<optimized out>, ctx=<optimized out>) at index-search.c:1706 #26 search_more (ctx=ctx@entry=0x55555583dd20, mail_r=mail_r@entry=0x7fffffffddf0) at index-search.c:1780 #27 0x00007ffff76f48bd in index_storage_search_next_nonblock(_ctx=0x55555583dd20, mail_r=0x7fffffffdec0, tryagain_r=0x7fffffffde57) at index-search.c:1808 #28 0x00007ffff76752e8 in mailbox_search_next_nonblock (ctx=0x55555583dd20, mail_r=0x7fffffffdec0, tryagain_r=<optimized out>) at mail-storage.c:2141 #29 0x00007ffff767534d in mailbox_search_next (ctx=0x55555583dd20, mail_r=mail_r@entry=0x7fffffffdec0) at mail-storage.c:2126 #30 0x0000555555586682 in doveadm_mail_iter_next (iter=<optimized out>, mail_r=mail_r@entry=0x7fffffffdec0) at doveadm-mail-iter.c:160 #31 0x0000555555585443 in cmd_import_box (search_args=<optimized out>, info=0x555555832118, dest_user=<optimized out>, ctx=0x555555807d78) at doveadm-mail-import.c:142 #32 cmd_import_run (_ctx=0x555555807d78, user=0x55555581c688) at doveadm-mail-import.c:202 #33 0x000055555557fdb1 in doveadm_mail_next_user (ctx=ctx@entry=0x555555807d78, error_r=error_r@entry=0x7fffffffe0a0) at doveadm-mail.c:462 #34 0x0000555555580a0b in doveadm_mail_single_user (ctx=ctx@entry=0x555555807d78, error_r=error_r@entry=0x7fffffffe0a0) at doveadm-mail.c:492 #35 0x0000555555580af9 in doveadm_mail_cmd_exec (ctx=ctx@entry=0x555555807d78, wildcard_user=wildcard_user@entry=0x0) at doveadm-mail.c:653 #36 0x00005555555819ce in doveadm_cmd_ver2_to_mail_cmd_wrapper (cctx=<optimized out>) at doveadm-mail.c:1144 #37 0x0000555555592b7e in doveadm_cmd_run_ver2 (argc=12, argv=0x5555557f5ae8, cctx=cctx@entry=0x7fffffffe290) at doveadm-cmd.c:574 #38 0x0000555555592bd7 in doveadm_cmd_try_run_ver2 (cmd_name=<optimized out>, argc=<optimized out>, argv=<optimized out>, cctx=0x7fffffffe290) at doveadm-cmd.c:496 #39 0x000055555556fec1 in main (argc=<optimized out>, argv=<optimized out>) at doveadm.c:391 -- Ralf Hildebrandt Geschäftsbereich IT | Abteilung Netzwerk Charité - Universitätsmedizin Berlin Campus Benjamin Franklin Hindenburgdamm 30 | D-12203 Berlin Tel. +49 30 450 570 155 | Fax: +49 30 450 570 962 ralf.hildebrandt(a)charite.de | https://www.charite.de

2 2

MailCrypt plugin questions
by MRob 24 May '19

24 May '19

I read the mailcrypt plugin document on the wiki and had couple questions. 1. If I want per-user encryption am I correct I should configure global keys with all related settings override in the userdb lookup? 2. If I do not want to encrypt some user accounts, is it enough to omit the mail_crypt_global_private_key from the userdb lookup? In other word, mail_plugins still active with mail_crypt, will that cause user account to be encrypted unexpectedly if no private key is given? 3. Example command to create EC key does not ask for password, openssl ecparam command does not seem to have password arg. If I want password-protection should I use RSA key which the doc tell to be discouraged?

1 1

Re: Catch all for dovecot authentication?
by Joseph Tam 24 May '19

24 May '19

> as stated by Aki > > > passdb { > > driver = static > > args = nopassword > >} > > works fine and does what I want: accept any SMTP AUTH :-) (Brings back memories of good fun I had with patched Qpopper snare feeding custom messages to the hacker.) Another alternative is to use the checkpassword hook that will accept any username/password. The advantage is you can do post-analysis of credentials as the script has access to them. Joseph Tam <jtam.home(a)gmail.com>

1 0

Catch all for dovecot authentication?
by Tobi 23 May '19

23 May '19

Hi I'm aware that there are several good reasons not to do what I want, but in my use-case it would be an interesting feature. So please no discussions about the reasonableness I have some spamtrap SMTP servers (postfix). Currently SMTP AUTH is disabled. But as I daily have thousands of AUTH tries I thought it would be nice to be able to accept any AUTH request from postfix in dovecot. Is something like this possible with dovecot? If so any good description available on how to achieve? Thanks -- tobi

4 5

How to get original recipient from Postfix when using LMTP?
by MRob 22 May '19

22 May '19

Many people prefer to use LMTP for delivery from postfix for better efficiency but X-Original-to header support still missing after many years. One affect of this is need to set sieve_vacation_dont_check_recipient = yes which violate Sieve standard and cause auto-replyies sent to messages that should not happen. Or abandon LMTP. or abandon postfix?? So while feature request is stalled are there any realistic workarounds?

3 3

weakforced: Possible to access the ip address of report/allow?
by Tobi 22 May '19

22 May '19

Hi I wonder if the information about the origin of report or allow can be accessed somehow. lt.remote gives the IP of the client trying to login but is there anything in lt which gives the ip of the system that connects to wforced? Thanks and have a good one -- tobi

2 3

lmtp report permission denied on delivery to multiple recipients
by Patrick Cernko 22 May '19

22 May '19

Hello, when receiving mails for multiple recipients via LMTP, I often see the following messages on our servers: > May 22 11:06:10 sinon dovecot[44304]: lmtp(119718): Connect from $IP$ > May 22 11:06:11 sinon dovecot[44304]: lmtp($USER1$)<119718><2HnmOgIR5Vym0wEA22L5Rg>: msgid=<$MSGID$>: saved mail to INBOX > May 22 11:06:11 sinon dovecot[44304]: lmtp($USER2$)<119718><2HnmOgIR5Vym0wEA22L5Rg:2>: Error: stat(/IMAP/mail/mailboxes/$USER1$/mdbox/mailboxes/INBOX/dbox-Mails/dovecot.index.cache) failed: Permission denied (euid=$UID2$($USER2$) egid=$GID2$(rbg) missing +x perm: /IMAP/mail/mailboxes/$USER1$, dir owned by $UID1$:$GID2$ mode=0700) > May 22 11:06:11 sinon dovecot[44304]: lmtp($USER2$)<119718><2HnmOgIR5Vym0wEA22L5Rg:2>: Error: open(/IMAP/mail/mailboxes/$USER1$/mdbox/mailboxes/INBOX/dbox-Mails/dovecot.index.cache) failed: Permission denied (euid=$UID2$($USER2$) egid=$GID2$(rbg) missing +x perm: /IMAP/mail/mailboxes/$USER1$, dir owned by $UID1$:$GID2$ mode=0700) > May 22 11:06:11 sinon dovecot[44304]: lmtp($USER2$)<119718><2HnmOgIR5Vym0wEA22L5Rg:2>: Error: lstat(/IMAP/mail/mailboxes/$USER1$/mdbox/mailboxes/INBOX/dbox-Mails/dovecot.index.cache.lock) failed: Permission denied > May 22 11:06:11 sinon dovecot[44304]: lmtp($USER2$)<119718><2HnmOgIR5Vym0wEA22L5Rg:2>: Error: file_dotlock_open(/IMAP/mail/mailboxes/$USER1$/mdbox/mailboxes/INBOX/dbox-Mails/dovecot.index.cache) failed: Permission denied (euid=$UID2$($USER2$) egid=$GID2$(rbg) missing +x perm: /IMAP/mail/mailboxes/$USER1$, dir owned by $UID1$:$GID2$ mode=0700) > May 22 11:06:11 sinon dovecot[44304]: lmtp($USER2$)<119718><2HnmOgIR5Vym0wEA22L5Rg:2>: Error: open(/IMAP/mail/mailboxes/$USER1$/mdbox/mailboxes/INBOX/dbox-Mails/dovecot.index.cache) failed: Permission denied (euid=$UID2$($USER2$) egid=$GID2$(rbg) missing +x perm: /IMAP/mail/mailboxes/$USER1$, dir owned by $UID1$:$GID2$ mode=0700) > May 22 11:06:11 sinon dovecot[44304]: lmtp($USER2$)<119718><2HnmOgIR5Vym0wEA22L5Rg:2>: 2HnmOgIR5Vym0wEA22L5Rg:2: sieve: msgid=<$MSGID$>: stored mail into mailbox 'INBOX' > May 22 11:06:11 sinon dovecot[44304]: lmtp(119718): Disconnect from $IP$: Successful quit (usernames, uids, gids and IP addresses anonymized) So far, I was not able to reproduce this issue on a simple test setup, but I have the strong impression, that is has something to do with the fact, if some of the affected users have a active sieve script and others do not use sieve. In the example above $USER1$ did not have a sieve script configured but $USER2$ had one, as you can see. As a workaround, I configured an empty sieve script for all users with out sieve configured. This seems to work but actually I do not want to have users with empty sieve scripts. This bug seems to be related to https://dovecot.org/list/dovecot/2013-February/088540.html where Timo stated: "LMTP always delivers the mail to the first user. Then it tries to copy the first mail to the second user, because in some setups this can be done using hard links. With mbox that of course doesn't work, but looks like instead of failing silently it logs an error. So everything is working as it should, except there are these unnecessary errors logged. I'll see about getting rid of them." Is it possible to get rid of these error messages, either by a config setting that prevents if they do not lead to a real problem or by changing the code to avoid the behaviour described by Timo? Attached you can find doveconf -n output and the used ldap.conf (both anonymized), the referenced /etc/dovecot/passdb.deny and /etc/dovecot/userdb.overrides are usually empty files and only used during mailbox migrations. Best regards, -- Patrick Cernko <pcernko(a)mpi-klsb.mpg.de> +49 681 9325 5815 Joint Administration: Information Services and Technology Max-Planck-Institute fuer Informatik & Softwaresysteme

1 0

Integrity check mdbox?
by Marc Roos 22 May '19

22 May '19

Is it possible to do some sort of integrity check on mdbox's

2 1

Converting user mailboxes from maildir to sdbox
by David Mehler 22 May '19

22 May '19

Hello, I've got a Postfix/Dovecot server setup. Currently Dovecot is version 2.3.6, and it's using Maildir storage. The mailbox is: mail_home = /home/vmail/mailboxes/%d/%n mail_location = maildir:~/mail:LAYOUT=fs I'm wanting to convert from Maildir to sdbox. I looked at: https://wiki2.dovecot.org/MailboxFormat I was initially thinking mdbox but that's multiple messages per file, which I do not believe is what I want. Am I correct that in the sdbox format if a single message file is corrupted only that message is corrupt and not the rest of the messages as would be the case in a mdbox setup? On the page: https://wiki2.dovecot.org/Migration/MailFormat " maildir -> sdbox migration. Set mail_location=sdbox:~/sdbox and run dsync -u username mirror maildir:~/Maildir " If I set mail_location=sdbox:~/sdbox will that put the user mailboxes in mail_home/sdbox? So it would be: /home/vmail/mailboxes/example.com/username/sdbox I am needing to do this migration, but am paranoid about loosing mail or corrupting mailboxes. All of my users are virtual users and they are stored in a mysql database. Thanks. Dave.

2 1

[mail-crypt-plugin] How to decrypt mailbox?
by emordin 22 May '19

22 May '19

How do I enable the mail-crypt-plugin globally? Do I have to place 'mail_plugins = $mail_plugins mail_crypt' inside ever conf.d file where there is a protocol code block? Like for example the protocol lda codeblock in 15-lda.conf and the protocol imap codeblock in 20-imap.conf I placed 'mail_plugins = $mail_plugins mail_crypt' in 20-lmtp.conf inside the protocol lmtp code block, and the actual plugin settings are inside 90-plugin.conf inside the plugin codeblock. And I was able to get CRYPTED mail with this config. If I place 'mail_plugins = $mail_plugins mail_crypt' inside 90-plugin.conf, I get an error telling me to put 'mail_plugins = $mail_plugins mail_crypt' in 20-lmtp.conf Sent with [ProtonMail](https://protonmail.com) Secure Email.

2 1

Problems after upgrade from 2.2 to 2.3
by Lampa 21 May '19

21 May '19

Hello, i was using dovecot version 2.2 on debian server. After upgrade to debian version 2.3 i have problems. After some time imap doesn't work. There are lot of messages in log 2019-05-21T10:27:49.186373+02:00 hermes dovecot: imap-login: Error: master(imap): net_connect_unix(imap) failed: Resource temporarily unavailable - http://wiki2.dovecot.org/SocketUnavailable (client-pid=24810, client-id=148, rip=2.2.2.2, created 551 msecs ago, received 0/4 bytes) 2019-05-21T10:27:50.808136+02:00 hermes dovecot: imap-login: Error: master(imap): net_connect_unix(imap) failed: Resource temporarily unavailable - http://wiki2.dovecot.org/SocketUnavailable (client-pid=24810, client-id=169, rip=2.2.2.2, created 531 msecs ago, received 0/4 bytes) Tried client_limit set to 1 , service_count to 1 or 0 , still same results. It's imap server for 3k users. Any suggestions, please let me know. Thank you very much. Regards -- Lampa

1 0

Dovecot with LDAP Proxy
by Federico Bartolucci 21 May '19

21 May '19

Hello, configuring Dovecot with LDAP authentication, adding the parameter in ther sql config file: pass_attrs = \ =proxy=y I see then backend connections always addressed to localhot port 143: /user=utente1(a)domanin.com proxy lip=127.0.0.1 lport=143 / while I expect that connections would be managed by the director and then addressed to my backend IPs and specific port. Is there a way to configure ldap proxy to get that behavior? Thanks in advance. -federico

2 3

Dovecot documentation
by ＠lbutlr 21 May '19

21 May '19

the make config options for dovecot on FreeBSD list list [x] ICU Use libicu for FTS unicode normalization but https://wiki2.dovecot.org/Plugins/FTS makes no mention of libicu (nor of icu at all). is linicu simply in addition to the four options of Solar, Lucene, fts-xapian, and fts-dovecot? Also, the link to fts-dovecot goes to https://wiki2.dovecot.org/Plugins/FTS/Dovecot which is a 404. -- Man is born free, but is everywhere in chains.

1 0

[mail-crypt-plugin] How to decrypt mailbox?
by emordin 21 May '19

21 May '19

Hi, So I am able to encrypt email using the crypt plugin, but when I try to access the email by logging in thru mutt or roundcube the email is still encrypted. Is the decryption process automatic or do I have to create a custom program with the decrypt.rb code? Thanks. Sent with [ProtonMail](https://protonmail.com) Secure Email.

2 1

Further issues on FTS engine
by Joan Moreau 20 May '19

20 May '19

Hi, Additionally to the long list of problem on the FTS previously discussed, here a new: WHen I reset the indexes, the indexer-worker seems paralelleizing the indexing (which is good), however, the number available in "ps aux | grep dove" shows that it does not move: dovecot 28549 0.0 0.0 8620 3920 ? S 06:20 0:00 dovecot/indexer [0 clients, 3 requests] mailuse+ 28550 98.6 0.1 167412 86916 ? R 06:20 5:28 dovecot/indexer-worker [jom(a)grosjo.net XXXX - 800/37755] Looking further, if I put a tracer in teh backend, it treats the *same* message several times in parallel, and therefore does not move very fast on the global indexing of the box ANy clue ? THanks

2 1

enforcing multiple per-mailbox quotas for shared mailboxes
by Jost-Philip Matysik 20 May '19

20 May '19

Hi! I'm trying to get quotas for shared mailboxes set up on my server. It's not working, and I fail to understand why. Documentation for setup of this complexity is rather scarce on the web, and the discussions I found either don't directly apply or terminate with "I got it working" but no explanation. Can someone please help? The setup is rather lengthy and complicated, so I'll try to give a summary first for easier understanding. All help is appreciated! Please respond if you need more info! Thanks! Best regards, Jost Basic setup (where am I coming from?): ====================================== - This is a Debian 9 system with a more recent version of dovecot installed from https://repo.dovecot.org/ce-2.3-latest/debian/stretch - users have individual mailboxes with individual quotas -- this works great! - users can share mailboxes with other users through ACLs. To achieve this, there exists a wildcarded namespace with prefix="ZZZ_Freigaben/%%u" --this also works great! ==> up to here it's pretty much following the examples from the Wiki to the letter. Configuration goal (what do I want to achieve?): ================================================ - attach quotas to mailboxes, not logins - when copying/moving mails across shared mailboxes during imap sessions, enforce quota based on target mailbox, not logged-in user doing the copying. To clarify: ==> so if Bob has a quota of 500MB, all messages in Bob's mailbox should count against (and only against!) Bob's quota, regardless of who put them there. ==> if Alice has access to her own mailbox (directly), as well as Bob's mailbox and Dave's mailbox (through sharing), she should see 3 individual quotas when logging in: her own quota (200MB) for everything in her mailbox, bob's quota (300MB) for everything in Bob's mailbox, and Dave's quota (10GB) for everything in Dave's mailbox. These 3 quotas should be completely independant and neither block, nor override each other. Setup Idea (how I tried to get there): ====================================== - "quota=..." "quota_rule" and "quota_rule2" always refer to the user's own mailbox (with an additional rule for Trash). Everyone has those, so these are loaded statically from dovecot config file. - "quota_rule" is overwritten from userdb with the user's individual mailbox quota (the more I like you, the more space you get...) - since the number of different additional quotas required per user depends on how many mailboxes are shared with that user, individual "quota2=...", "quota3=...", "quotaN=..." fields are dynamically generated by the MySQL backend and loaded from userdb upon login. - consequently, for each "quotaN=..." entry, a corresponding "quotaN_rule=*:storage=XXX" is generated and returned from userdb (substitute N=1,2,3,4,... accordingly) Observations: ============= 1. enforcing quota for the user's personal mailbox works as expected, both through IMAP and when delivering incoming mail 2. overriding "quota_rule=..." from userdb for the user's personal mailbox works great. Individual quota is recognized and enforced both through IMAP and when delivering incoming mail. 3. dynamically loading "quota2=...", "quota3=..." etc. from userdb doesn't seem to work at all! I can see them being added as extra fields in the logs upon user login, but the quota-plugin seems to completely ignore them. They are not enforces, and tools like 'doveadm quota' list the userdb fields in the debug messages, but do not interpret them in any way. They do not throw errors either, the additional quota roots are just silently ignored. 4. the end result is that in an IMAP session the logged-in user's quota is enforced for their individual mailbox, but as soon as they write to someone else's mailbox (move a mail to /ZZZFreigaben/bob/Some-Subfolder), no quota is enforced at all! Additional debugging done: ========================== if I hardcode a "quota2=" and/or "quota3=" in the config file, I can observe the following: - If I hardcode "quota2=count:some_name:ns=ZZZ_Freigaben/", dovecot and doveadm will recognize the additional quota root. But since the folder "ZZZ_Freigaben/" on its own isn't a mailbox (it's just a path CONTAINING mailboxes), the quota is neither displayed in clients, nor enforced. It has no real-word effect, other than 'doveadm quota' showing an additional line. - If I hardcode "quota2=count:other_name:ns=ZZZ_Freigaben/postmaster/" in the config file (with that path being the real IMAP path to a shared mailbox), dovecot will complain in the log saying Error: quota: Unknown namespace: ZZZ_Freigaben/postmaster/ dovecot will start and work for the most part, but again completely ignore settings for the additional quota. - additionally, trying to override "quota2_rule=..." from userdb doesn't work as it does with "quota_rule=..."! If I have both "quota_rule=..." and "quota2_rule=..." in the config file as well as returned from userdb (with different values), dovecot will use "quota_rule" from userdb, but "quota2_rule" from config file. This behavior seems inconsistent! - I tried both maildir and count backends (seperately or mixed). Both show the same behavior. - I tried appending or removing an empty "ns=" to the first "quota=..." entry (the wiki shows some examples with it, some without). Makes no difference... Configuration Dumps below (slightly redacted to remove complete email addresses or IPs) ========================== output of dovecot -n: # 2.3.6 (7eab80676): /etc/dovecot/dovecot.conf # Pigeonhole version 0.5.6 (92dc263a) # OS: Linux 4.9.0-9-amd64 x86_64 Debian 9.9 # Hostname: [censored] auth_failure_delay = 10 secs auth_mechanisms = plain login default_vsz_limit = 512 M dict { acl = mysql:/etc/dovecot/dovecot-dict-sql.conf.ext } listen = * lmtp_rcpt_check_quota = yes login_greeting = Mail system ready. mail_gid = vmail mail_location = maildir:~/Maildir mail_plugins = " quota acl" mail_uid = vmail 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 imapsieve vnd.dovecot.imapsieve namespace Freigaben { list = children location = maildir:%%h/Maildir:INDEXPVT=%h/Maildir/Freigaben/%%u prefix = ZZZ_Freigaben/%%u/ separator = / subscriptions = no type = shared } namespace inbox { inbox = yes location = mailbox Drafts { auto = subscribe special_use = \Drafts } mailbox Junk { auto = subscribe autoexpunge = 61 days special_use = \Junk } mailbox Sent { auto = subscribe special_use = \Sent } mailbox "Sent Messages" { special_use = \Sent } mailbox Trash { auto = subscribe autoexpunge = 61 days special_use = \Trash } prefix = separator = / subscriptions = yes type = private } passdb { args = /etc/dovecot/dovecot-sql.conf.username driver = sql } plugin { acl = vfile:/etc/dovecot/dovecot-acl acl_defaults_from_inbox = yes acl_shared_dict = proxy::acl imapsieve_mailbox1_before = file:/etc/dovecot/sieve/learn-spam.sieve imapsieve_mailbox1_causes = COPY imapsieve_mailbox1_name = Junk imapsieve_mailbox2_before = file:/etc/dovecot/sieve/learn-ham.sieve imapsieve_mailbox2_causes = COPY imapsieve_mailbox2_from = Junk imapsieve_mailbox2_name = * quota = count:User quota:ns= quota_grace = 1%% quota_rule = *:storage=5G quota_rule2 = Trash:storage=+100M quota_status_nouser = DUNNO quota_status_overquota = 552 5.2.2 Mailbox is full quota_status_success = DUNNO quota_vsizes = yes sieve = file:~/sieve;active=~/.dovecot.sieve sieve_after = /etc/dovecot/sieve-after sieve_global_extensions = +vnd.dovecot.pipe +vnd.dovecot.environment sieve_max_script_size = 10M sieve_pipe_bin_dir = /etc/dovecot/sieve sieve_plugins = sieve_imapsieve sieve_extprograms sieve_quota_max_storage = 50M } postmaster_address = postmaster(a)matysik-ingenieurwesen.de protocols = " imap lmtp sieve" service auth-worker { user = vmail } service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0660 user = postfix } unix_listener auth-userdb { mode = 0666 } } service dict { unix_listener dict { group = vmail mode = 0660 user = dovecot } } service imap-login { inet_listener imap { port = 0 } inet_listener imaps { address = [censored] port = 993 ssl = yes } } service imap { process_limit = 1024 } service lmtp { unix_listener /var/spool/postfix/private/dovecot-lmtp { group = postfix mode = 0600 user = postfix } } service managesieve-login { inet_listener sieve { address = [censored] port = 4190 } service_count = 1 } service managesieve { process_limit = 64 } ssl_cert = </etc/letsencrypt/live/fullchain.pem ssl_cipher_list = ECDH+AESGCM:DH+AESGCM:ECDH+AES256:DH+AES256:ECDH+AES128:DH+AES:ECDH+3DES:DH+3DES:RSA+AESGCM:RSA+AES:RSA+3DES:!aNULL:!MD5:!DSS ssl_dh = # hidden, use -P to show it ssl_key = # hidden, use -P to show it ssl_min_protocol = TLSv1.2 ssl_options = no_compression ssl_prefer_server_ciphers = yes # comment: since imap logins differ from email-addresses I have 2 # userdb queries. One will return fields for %u='login', the other will # return fields for %u='email(a)domain.tld'. # no %u will ever make BOTH userdbs return rows (they are mutually exclusive) userdb { args = /etc/dovecot/dovecot-sql.conf.email driver = sql } userdb { args = /etc/dovecot/dovecot-sql.conf.username driver = sql } protocol lmtp { mail_plugins = " quota acl sieve" } protocol imap { mail_plugins = " quota acl imap_sieve imap_quota imap_acl" } example userdb output: ======================= root@server:/# doveadm -Dv user jost Debug: Loading modules from directory: /usr/lib/dovecot/modules Debug: Module loaded: /usr/lib/dovecot/modules/lib01_acl_plugin.so Debug: Module loaded: /usr/lib/dovecot/modules/lib10_quota_plugin.so Debug: Loading modules from directory: /usr/lib/dovecot/modules/doveadm Debug: Module loaded: /usr/lib/dovecot/modules/doveadm/lib10_doveadm_acl_plugin.so Debug: Skipping module doveadm_expire_plugin, because dlopen() failed: /usr/lib/dovecot/modules/doveadm/lib10_doveadm_expire_plugin.so: undefined symbol: expire_set_deinit (this is usually intentional, so just ignore this message) Debug: Module loaded: /usr/lib/dovecot/modules/doveadm/lib10_doveadm_quota_plugin.so Debug: Module loaded: /usr/lib/dovecot/modules/doveadm/lib10_doveadm_sieve_plugin.so Debug: Skipping module doveadm_fts_lucene_plugin, because dlopen() failed: /usr/lib/dovecot/modules/doveadm/lib20_doveadm_fts_lucene_plugin.so: undefined symbol: lucene_index_iter_deinit (this is usually intentional, so just ignore this message) Debug: Skipping module doveadm_fts_plugin, because dlopen() failed: /usr/lib/dovecot/modules/doveadm/lib20_doveadm_fts_plugin.so: undefined symbol: fts_user_get_language_list (this is usually intentional, so just ignore this message) Debug: Skipping module doveadm_mail_crypt_plugin, because dlopen() failed: /usr/lib/dovecot/modules/doveadm/libdoveadm_mail_crypt_plugin.so: undefined symbol: mail_crypt_box_get_pvt_digests (this is usually intentional, so just ignore this message) field valuedoveadm(jost)<25290><>: Debug: auth USER input: jost home=/var/vmail/matysik.it/jost-philip uid=5000 gid=5000 acl_groups=matysik,admin quota_rule=*:storage=10G quota_rule2 = Trash:storage=+100M quota2 = count:shared quota for maschinen:ns=ZZZ_Freigaben/maschinen/ quota2_rule = *:storage=500M quota3 = count:shared quota for matysik:ns=ZZZ_Freigaben/matysik/ quota3_rule = *:storage=10G quota4 = count:shared quota for postmaster:ns=ZZZ_Freigaben/postmaster/ quota4_rule = *:storage=1G uid 5000 gid 5000 home /var/vmail/matysik.it/jost-philip mail maildir:~/Maildir acl_groups matysik,admin quota_rule *:storage=10G quota_rule2 Trash:storage=+100M quota2 count:shared quota for maschinen:ns=ZZZ_Freigaben/maschinen/ quota2_rule *:storage=500M quota3 count:shared quota for matysik:ns=ZZZ_Freigaben/matysik/ quota3_rule *:storage=10G quota4 count:shared quota for postmaster:ns=ZZZ_Freigaben/postmaster/ quota4_rule *:storage=1G

1 0

Create a malicious directory
by lty 20 May '19

20 May '19

Use scripts to create some malicious directories. Here is my creation process. How can I prevent the creation of these directories? I used the python imapclient script to create a directory. There may be no big threat to dovecot, but it is dangerous for doveadm.

4 3

Directory name have some malicious characters.
by hfh＠cndns.com 20 May '19

20 May '19

Directory name have some malicious characters, is it safe?How can I exclude some characters,thanks!

1 0

Plugins/Mailcrypt: mail_crypt_private_password not assigned by password_query
by Max Kostikov 20 May '19

20 May '19

I try to use Mailcrypt encrypted user keys with conjustion with dbsync replication(Dovecot 2.3.6 in FreeBSD 12.0 enviroment) but was unsuccessful. If I provide a password in mail_crypt_private_password variable directly in Dovecot config all things works as expected plugin { mail_crypt_curve = prime256v1 mail_crypt_save_version = 2 mail_crypt_require_encrypted_user_key = yes mail_crypt_private_password = 12345 } but when I remove this and trying to get the same user password in password_query it seems password doesn't assigned password_query = SELECT username AS user, password, \ '%w' AS userdb_mail_crypt_private_password \ FROM mailbox WHERE username = LCASE('%u') \ AND active = '1' with errors like this in log at server where message was accepted from remote system May 20 00:40:31 server1 dovecot[35417]: dsync-local(foo(a)example.com)<Y51qBF/b4VyHigAAJQnBKg>: Error: dsync(server1.example.com): read() failed: read(/var/mail/example.com/foo/new/1558305609.M674400P35456.server1.example… failed: Private key not available: Cannot decrypt key a4ceb2df0287c0c0ccb0d76e31d91824e1f13e9ffe63d1e04a9a233a073d8a64: Cannot decrypt key 5d19a9246ddce2759a21462974add562dd90f2cb2aa3ff6a5af1af1e3e9b58e6: Password not available (last sent=mail, last recv=mail_request (EOL)) and errors at replica server May 20 00:40:31 server2 dovecot[63985]: dsync-local(foo(a)example.com)<MpW+HV/b4VwD+wAAfP91Tw>: Error: dsync(server2.example.com): read() failed: read() failed: dot-input stream ends without '.' line (last sent=mail_request (EOL), last recv=mail) The question is it possible to have password encrypted user keys with Dovecot dbsync replication or we found a new bug? -- With best regards, Max Kostikov W: https://kostikov.co | DeltaChat: mk(a)eprove.net

1 0

Permission denied
by ＠lbutlr 19 May '19

19 May '19

mail dovecot: lda(user@domain)<955><rPK3B2Gr4Vy7AwAAIdGjjQ>: msgid=<4562Sm6YyYzvmrD(a)mail.covisp.net>: save failed to INBOX: Mailbox INBOX: open(/usr/local/virtual/user(a)domain/tmp/1558293345.M130062P955.mail.covisp.net) failed: Permission denied The permissions on /usr/local/virual have not changed and are still owed by user/group 89/89 dovecot-sql.conf.ext: user_query = select 89 as uid, 89 as gid, concat('/usr/local/virtual/', maildir) as home FROM mailbox where username = '%u' dovecot.conf: first_valid_uid = 89 # ls -lsdn /usr/local/virtual/ 8 drwx------ 29 89 89 1536 Mar 12 23:30 /usr/local/virtual/ # ls -lsdn /usr/local/virtual/backup\(a)southgaylord.com 184 drwx------ 2056 89 89 92672 May 19 12:43 /usr/local/virtual/user@domain Do I need to compile dovecot with vpopmail support? -- I WILL NOT DO THE DIRTY BIRD Bart chalkboard Ep. AABF08

1 0

Repo for RHEL8
by TG Servers 19 May '19

19 May '19

2 2

Merging existing mailboxes to aliases
by Lefteris Tsintjelis 19 May '19

19 May '19

I am trying to merge all, existing or not, different mailboxes in one with the mailbox alias plugin. If I add the following lines, will the existing mailboxes automatically merge in one mailbox and corresponding links auto create? If not, do I have to do this manually? mailbox_alias_new = Spam mailbox_alias_new2 = Junk E-mail mailbox_alias_new3 = Sent Items mailbox_alias_new4 = Sent Messages mailbox_alias_new5 = Deleted Items mailbox_alias_old = Junk mailbox_alias_old2 = Junk mailbox_alias_old3 = Sent mailbox_alias_old4 = Sent mailbox_alias_old5 = Trash Lefteris

3 4

Do we need ssl_dh_parameters_length in version 2.3
by MRob 19 May '19

19 May '19

Hi, I couldn't really find documentation about ssl_dh_parameters_length except for mention in passing on the page https://wiki2.dovecot.org/SSL/DovecotConfiguration For version 2.3 and above is that setting necessary? If so what are the values I can use, is setting it high like 4096 beneficial or make any problems for clients? Thanks for assistance.

2 1

Re: imap failing
by LuKreme 18 May '19

18 May '19

Ugh. Sorry about this, using gmail and it’s weird and annoying meant to send to list On Thu, May 16, 2019 at 00:46 LuKreme <kremels(a)kreme.com> wrote: > One more bit of info. After leaving s_client up for a bit, I got another > line > > CONNECTED(00000003) > 675481056:error:140790E5:SSL routines:ssl23_write:ssl handshake > failure:/usr/src/crypto/openssl/ssl/s23_lib.c:177: > --- > no peer certificate available > --- > No client certificate CA names sent > --- > SSL handshake has read 0 bytes and written 307 bytes > --- > New, (NONE), Cipher is (NONE) > Secure Renegotiation IS NOT supported > Compression: NONE > Expansion: NONE > No ALPN negotiated > SSL-Session: > Protocol : TLSv1.2 > Cipher : 0000 > Session-ID: > Session-ID-ctx: > Master-Key: > Key-Arg : None > PSK identity: None > PSK identity hint: None > SRP username: None > Start Time: 1557988789 > Timeout : 300 (sec) > Verify return code: 0 (ok) > --- > > I guess I wasn't patient enough before. But the certs are in the exact > same place as they've been all along and are working fine with apache. > I can also send mail, if that is at all relevant. (postconf -n is in > another post in this thread) > -- Sent from Gmail Mobile

3 3

Find last day of login
by Lefteris Tsintjelis 18 May '19

18 May '19

I am using dovecot virtual maildir accounts. Is it possible to find last day of login for an account by checking the last modification time of the maildir files? Lefteris

3 4

How to continuously gather statistics?
by Roel van Duijnhoven 17 May '19

17 May '19

Hello, I recently upgraded to the latest version of Dovecot, and want to use the newly introduced logging / event system. I want to fetch the statistics every couple of seconds, and push those to our logging platform. Metrics such as: number of IMAP commands, average time they took, etc. However the metrics as reported by Dovecot continously increment. So I see two solutions: - Our solution could keep track of the previous values. But that could also break if the statistics are reset for some reason (e.g. threshold reached). - My second thought was to use "stats -r". That *should* clear the statistics directly after fetching them. And thus, give a better picture. However I am not sure if this gives me actual useful results. Or is there maybe a better approach to fetch statistics that I overlooked? Thanks a lot. Best, Roel van Duijnhoven

2 1

Dovecot Separator change
by Oliver Werner 16 May '19

16 May '19

Hi community, actually we are using dovecot 2.2.27 without shares mailboxes. Now we would like to implement it. So the problem is that our separator is dot „.“ and the username like „firstname.surname“. That’s doesn’t works with shared mailboxes. Are there a migration guide for changing „.“ to „/„ or it's not possible? kind regards Oliver

1 0

File-dictionary based quotas and SETQUOTA
by Ganael Laplanche 16 May '19

16 May '19

Hello, I am trying to set up file-dictionary based quotas while supporting the SETQUOTA IMAP command. I am using the following configuration : ---- plugin { quota = dict:User quota::file:%h/Maildir/dovecot-quota quota_set = dict:file:%h/Maildir/dovecot-quota } ---- which enables correct quota accounting + setting through SETQUOTA. A user's dovecot-quota file ends with the following contents : ---- priv/quota/limit/storage 5242880 priv/quota/limit/messages 20 priv/quota/messages 1 priv/quota/storage 8506282 ---- which shows a correct accounting (1 mail received, ~8MB used) and correct setting after having used the following IMAP command through a master user : A2 SETQUOTA "User quota" (STORAGE 5242880 MESSAGE 20) *But* the problem is that I am unable to fetch the limits and consume them from userdb (as a consequence, the limits are never applied). On the consuming side, I am using a dictionary userdb to try to fetch the 'priv/quota/limit/storage' value from the file but it does not work because the key is never found. Here is my configuration : ---- userdb { driver = dict args = /etc/dovecot/dovecot-dict-quota.conf.ext } ---- and my dovecot-dict-quota.conf.ext file : ---- uri = file:%h/Maildir/dovecot-quota iterate_disable = yes key quota { key = priv/quota/limit/storage default_value = 100 } userdb_fields { quota_rule = *:storage=%{dict:quota} } ---- If I try to fetch the quota for that user : # doveadm quota get -u ganael.laplanche(a)centralesupelec.fr Quota name Type Value Limit % User quota STORAGE 8307 100 8307 User quota MESSAGE 1 - 0 the default rule is returned (100). The logs show : May 16 12:02:45 mailhost1-saclay dovecot: auth-worker(12899): Debug: dict(Ganael.Laplanche(a)centralesupelec.fr): Lookup: shared/priv/quota/limit/ storage not found, using default value 100 We can see that the default quota rule has been applied because the key is not found. The problem is that a "shared/" prefix is always prepended when looking for the key I configured (priv/quota/limit/storage). If I test the dictionary manually, the key is found : # doveadm dict get -u ganael.laplanche(a)centralesupelec.fr "file:/var/vmail/l/ laplanche_gan/Maildir/dovecot-quota" priv/quota/limit/storage 5242880 Does anyone know how to prevent Dovecot from adding that prefix and make it fetch the correct value from userdb ? Best regards, -- Ganael Laplanche <ganael.laplanche(a)centralesupelec.fr> Unix Systems Engineer @CentraleSupelec Rennes

1 0

Password database - external verification
by Richard Hector 16 May '19

16 May '19

Hi all, I'm currently using a PostgreSQL database for my user/password db, directly from dovecot. The trouble with that is that I'm stuck with whatever hash algorithms dovecot supports - which IIRC means (a subset of?) what libc has been compiled with, which can be a bit restrictive. So I'd like to use an external tool, which would also let me integrate other applications (eg web apps). PAM seems to be most suited to sharing accounts with the OS, which isn't what I want. BSDAuth likewise, but I'm not using BSD. CheckPassword looks like a somewhat convoluted protocol, but maybe the best bet? IMAP - well, that's circular :-) OAuth2 looks possible, but seems to be focused on http? Any suggestions? And recommended implementations? How hard is it to add extra methods? Thanks, Richard

2 2

Dovecot not connecting to OpenLDAP
by Elias Falconi 16 May '19

16 May '19

Hi, We recently shutdown our old LDAP server and repointed our mail server (dovecot + postfix) to our new LDAP server and ever since we've been unable to fetch mail. Mail is getting delivered, but we just can't pop it. We're using Ubuntu 16.04, btw. We keep on getting the following error messages in /var/log/dovecote: 2019-05-15 16:27:43 auth: Error: LDAP /etc/dovecot/dovecot-ldap.conf.ext: ldap_start_tls_s() failed: Can't contact LDAP server 2019-05-15 16:39:36 auth: Error: LDAP /etc/dovecot/dovecot-ldap.conf.ext: ldap_start_tls_s() failed: Connect error 2019-05-15 16:39:43 auth: Error: LDAP /etc/dovecot/dovecot-ldap.conf.ext: ldap_start_tls_s() failed: Local error However, our server is finding our LDAP users and postfix doesn't seem to have a problem, just Dovecot. Also, when we try to connect via Dovecot, we get the following message: -ERR [SYS/TEMP] Temporary authentication failure. [mail:2019-05-15 21:40:06] Our /etc/dovecot/dovecot.conf contains the following: ## Dovecot configuration file # If you're in a hurry, see http://wiki2.dovecot.org/QuickConfiguration # "doveconf -n" command gives a clean output of the changed settings. Use it # instead of copy&pasting files when posting to the Dovecot mailing list. # '#' character and everything after it is treated as comments. Extra spaces # and tabs are ignored. If you want to use either of these explicitly, put the # value inside quotes, eg.: key = "# char and trailing whitespace " # Most (but not all) settings can be overridden by different protocols and/or # source/destination IPs by placing the settings inside sections, for example: # protocol imap { }, local 127.0.0.1 { }, remote 10.0.0.0/8 { } # Default values are shown for each setting, it's not required to uncomment # those. These are exceptions to this though: No sections (e.g. namespace {}) # or plugin settings are added by default, they're listed only as examples. # Paths are also just examples with the real defaults being based on configure # options. The paths listed here are for configure --prefix=/usr # --sysconfdir=/etc --localstatedir=/var # Enable installed protocols !include_try /usr/share/dovecot/protocols.d/*.protocol # A comma separated list of IPs or hosts where to listen in for connections. # "*" listens in all IPv4 interfaces, "::" listens in all IPv6 interfaces. # If you want to specify non-default ports or anything more complex, # edit conf.d/master.conf. #listen = *, :: # Base directory where to store runtime data. #base_dir = /var/run/dovecot/ # Name of this instance. In multi-instance setup doveadm and other commands # can use -i <instance_name> to select which instance is used (an alternative # to -c <config_path>). The instance name is also added to Dovecot processes # in ps output. #instance_name = dovecot # Greeting message for clients. #login_greeting = Dovecot ready. # Space separated list of trusted network ranges. Connections from these # IPs are allowed to override their IP addresses and ports (for logging and # for authentication checks). disable_plaintext_auth is also ignored for # these networks. Typically you'd specify your IMAP proxy servers here. #login_trusted_networks = # Space separated list of login access check sockets (e.g. tcpwrap) #login_access_sockets = # With proxy_maybe=yes if proxy destination matches any of these IPs, don't do # proxying. This isn't necessary normally, but may be useful if the destination # IP is e.g. a load balancer's IP. #auth_proxy_self = # Show more verbose process titles (in ps). Currently shows user name and # IP address. Useful for seeing who are actually using the IMAP processes # (eg. shared mailboxes or if same uid is used for multiple accounts). #verbose_proctitle = no # Should all processes be killed when Dovecot master process shuts down. # Setting this to "no" means that Dovecot can be upgraded without # forcing existing client connections to close (although that could also be # a problem if the upgrade is e.g. because of a security fix). #shutdown_clients = yes # If non-zero, run mail commands via this many connections to doveadm server, # instead of running them directly in the same process. #doveadm_worker_count = 0 # UNIX socket or host:port used for connecting to doveadm server #doveadm_socket_path = doveadm-server # Space separated list of environment variables that are preserved on Dovecot # startup and passed down to all of its child processes. You can also give # key=value pairs to always set specific settings. #import_environment = TZ ## ## Dictionary server settings ## # Dictionary can be used to store key=value lists. This is used by several # plugins. The dictionary can be accessed either directly or though a # dictionary server. The following dict block maps dictionary names to URIs # when the server is used. These can then be referenced using URIs in format # "proxy::<name>". dict { #quota = mysql:/etc/dovecot/dovecot-dict-sql.conf.ext #expire = sqlite:/etc/dovecot/dovecot-dict-sql.conf.ext quota = ldap:/etc/dovecot/dovecot-ldap.conf.ext expire = ldap:/etc/dovecot/dovecot-ldap.conf.ext } # Most of the actual configuration gets included below. The filenames are # first sorted by their ASCII value and parsed in that order. The 00-prefixes # in filenames are intended to make it easier to understand the ordering. !include conf.d/*.conf # A config file can also tried to be included without giving an error if # it's not found: !include_try local.conf # Added by Elias protocols = pop3 imap #ssl_cert = </etc/ssl/certs/server.crt #ssl_key = </etc/ssl/private/server.key ssl_cert = </etc/ssl/certs/ssl-cert-snakeoil.pem ssl_key = </etc/ssl/private/ssl-cert-snakeoil.key log_path = /var/log/dovecote info_log_path = /var/log/dovecote_info log_timestamp = "%Y-%m-%d %H:%M:%S " #syslog_facility = mail_dovecote #ssl = no #mail_location = mbox:~/:INBOX=/var/mail/%u #namespace { # type = private # separator = . # inbox = yes #} mail_privileged_group = mail mail_full_filesystem_access = yes mail_debug = yes mmap_disable = yes mail_nfs_storage = yes mail_nfs_index = yes mail_fsync = always mbox_read_locks = dotlock mbox_write_locks = dotlock passdb ldap { driver = ldap # Path for LDAP configuration file args = /etc/dovecot/dovecot-ldap.conf.ext } userdb { driver=passwd } userdb ldap { driver = ldap # Path for LDAP configuration file args = /etc/dovecot/dovecot-ldap.conf.ext } And our /etc/dovecot/dovecot-ldap.conf.ext has this: # This file is commonly accessed via passdb {} or userdb {} section in # conf.d/auth-ldap.conf.ext # This file is opened as root, so it should be owned by root and mode 0600. # # http://wiki2.dovecot.org/AuthDatabase/LDAP # # NOTE: If you're not using authentication binds, you'll need to give # dovecot-auth read access to userPassword field in the LDAP server. # With OpenLDAP this is done by modifying /etc/ldap/slapd.conf. There should # already be something like this: # access to attribute=userPassword # by dn="<dovecot's dn>" read # add this # by anonymous auth # by self write # by * none # Space separated list of LDAP hosts to use. host:port is allowed too. hosts = 139.147.9.135 # LDAP URIs to use. You can use this instead of hosts list. Note that this # setting isn't supported by all LDAP libraries. #uris = ldaps://139.147.9.135 # Distinguished Name - the username used to login to the LDAP server. # Leave it commented out to bind anonymously (useful with auth_bind=yes). dn = cn=admin,dc=cs,dc=lafayette,dc=edu # Password for LDAP server, if dn is specified. dnpass = blahblah123 # Use SASL binding instead of the simple binding. Note that this changes # ldap_version automatically to be 3 if it's lower. Also note that SASL binds # and auth_bind=yes don't work together. #sasl_bind = no # SASL mechanism name to use. #sasl_mech = # SASL realm to use. #sasl_realm = # SASL authorization ID, ie. the dnpass is for this "master user", but the # dn is still the logged in user. Normally you want to keep this empty. #sasl_authz_id = # Use TLS to connect to the LDAP server. tls = yes # TLS options, currently supported only with OpenLDAP: #tls_ca_cert_file =/etc/ssl/certs/ldap.crt tls_ca_cert_file =/etc/ssl/certs/ldap6_cacert.pem #tls_ca_cert_dir =/etc/ssl/certs/ #tls_cipher_suite = # TLS cert/key is used only if LDAP server requires a client certificate. #tls_cert_file = /etc/ssl/certs/ldap01_slapd_cert.pem #tls_key_file = /etc/ssl/private/ldap01_slapd_key.pem # Valid values: never, hard, demand, allow, try #tls_require_cert = demand # Use the given ldaprc path. #ldaprc_path = # LDAP library debug level as specified by LDAP_DEBUG_* in ldap_log.h. # -1 = everything. You may need to recompile OpenLDAP with debugging enabled # to get enough output. #debug_level = 0 # Use authentication binding for verifying password's validity. This works by # logging into LDAP server using the username and password given by client. # The pass_filter is used to find the DN for the user. Note that the pass_attrs # is still used, only the password field is ignored in it. Before doing any # search, the binding is switched back to the default DN. auth_bind = yes # If authentication binding is used, you can save one LDAP request per login # if users' DN can be specified with a common template. The template can use # the standard %variables (see user_filter). Note that you can't # use any pass_attrs if you use this setting. # # If you use this setting, it's a good idea to use a different # dovecot-ldap.conf.ext for userdb (it can even be a symlink, just as long as # the filename is different in userdb's args). That way one connection is used # only for LDAP binds and another connection is used for user lookups. # Otherwise the binding is changed to the default DN before each user lookup. # # For example: # auth_bind_userdn = cn=%u,ou=people,o=org # #auth_bind_userdn = # LDAP protocol version to use. Likely 2 or 3. ldap_version = 3 # LDAP base. %variables can be used here. # For example: dc=mail, dc=example, dc=org base = ou=People,dc=cs,dc=lafayette,dc=edu # Dereference: never, searching, finding, always deref = never # Search scope: base, onelevel, subtree scope = subtree # User attributes are given in LDAP-name=dovecot-internal-name list. The # internal names are: # uid - System UID # gid - System GID # home - Home directory # mail - Mail location # # There are also other special fields which can be returned, see # http://wiki2.dovecot.org/UserDatabase/ExtraFields user_attrs = homeDirectory=home,uidNumber=uid,gidNumber=gid # Filter for user lookup. Some variables can be used (see # http://wiki2.dovecot.org/Variables for full list): # %u - username # %n - user part in user@domain, same as %u if there's no domain # %d - domain part in user@domain, empty if user there's no domain user_filter = (&(objectClass=posixAccount)(uid=%u)) # Password checking attributes: # user: Virtual user name (user@domain), if you wish to change the # user-given username to something else # password: Password, may optionally start with {type}, eg. {crypt} # There are also other special fields which can be returned, see # http://wiki2.dovecot.org/PasswordDatabase/ExtraFields pass_attrs = uid=user,userPassword=password # If you wish to avoid two LDAP lookups (passdb + userdb), you can use # userdb prefetch instead of userdb ldap in dovecot.conf. In that case you'll # also have to include user_attrs in pass_attrs field prefixed with "userdb_" # string. For example: #pass_attrs = uid=user,userPassword=password,\ # homeDirectory=userdb_home,uidNumber=userdb_uid,gidNumber=userdb_gid # Filter for password lookups pass_filter = (&(objectClass=posixAccount)(uid=%u)) # Attributes and filter to get a list of all users #iterate_attrs = uid=user #iterate_filter = (objectClass=posixAccount) # Default password scheme. "{scheme}" before password overrides this. # List of supported schemes is in: http://wiki2.dovecot.org/Authentication #default_pass_scheme = CRYPT What do you suppose could be the problem? Thanks, Elias

3 2

imap failing
by ＠lbutlr 16 May '19

16 May '19

mail kernel: pid 59433 (imap-login), uid 0: exited on signal 11 (core dumped) master: Error: service(imap-login): command startup failed, throttling for 16 secs May 15 17:21:37 imap-login: Fatal: master: service(imap-login): child 92934 killed with signal 11 (core dumped) I also get a password error for a user unknown, but if I connect to the database with the credentials dovecot uses, I get a password. MariaDB [postfix]> select password FROM mailbox where username ='sample(a)domain.munged'; +-------------------------------------------------------------------------------+ | password | +-------------------------------------------------------------------------------+ | {SHA256-CRYPT}$5$042......................................................... | +-------------------------------------------------------------------------------+ MariaDB [postfix]> select 89 as uid, 89 as gid, concat('/usr/local/virtual/', maildir) as home FROM mailbox where username = 'sample(a)domain.munged'; +-----+-----+------------------------------------------+ | uid | gid | home | +-----+-----+------------------------------------------+ | 89 | 89 | /usr/local/virtual/sample(a)domain.munged/ | +-----+-----+------------------------------------------+ 1 row in set (0.00 sec) I updated my system to openssl111 and rebuilt dovecot and postfix (and a hundred other packages). <y configuration files have not changed. I've looked through he logs for other info, but I don't see anything. Trying to connect via openssl gives me: # openssl s_client -connect mail.covisp.net:993 -starttls imap CONNECTED(00000003)

3 5

Setting up individual encrypted user keys using mail-crypt-plugin
by emordin 16 May '19

16 May '19

Hi, I have setup up a simple mail server using the ISPMail tutorial and I'm trying to learn how to create email encryption at rest. I'm having a tough time understanding how to set this up... So say a user logins thru roundcube and they type in their password...so the password authenticates to the mysql database which is storing their encrypted private key?? And once they access that private key, how do they use that private key to unencrypt their mailbox? I'm a super noob at this, and I may be off, but I don't know where to start when it comes to setting this up... if I'm way off could you just recommend some tutorials or other basics I should learn first before moving on to setting this up? Sent with [ProtonMail](https://protonmail.com) Secure Email.

2 1

Mutual auth and MS Outlook
by dovecot＠scottsavarese.com 16 May '19

16 May '19

I am trying to get Dovecot IMAP and Outlook to talk to each other with SSL and client certificates enabled. In Dovecot, I have the following options enabled: ssl_ca = ... ssl_verify_client_cert = yes auth_ssl_require_client_cert = yes auth_ssl_username_from_cert = yes when I try to connect with Outlook, I get: May 12 08:07:50 mail dovecot: imap-login: Disconnected (client didn't send a cert): user=<>, method=PLAIN, rip=192.168.1.245, lip=192.168.2.5, TLS: Disconnected, session=<is7gpa+Im97AqAH1> But when I use openssl directly with the same certificates it seems to pass the certificate in just fine. Does anybody have any ideas? Thanks in advance.

2 1

Permissions fix
by Lefteris Tsintjelis 16 May '19

16 May '19

Is there a fast way for dovecot to set and/or fix its directory permissions?

2 2

Anyone using object storage ceph?
by Marc Roos 15 May '19

15 May '19

Just curious if there are already people actively using object storage? https://github.com/ceph-dovecot/dovecot-ceph-plugin https://docplayer.net/docs-images/40/9935441/images/page_13.jpg

2 1

Re: weakforced and GeoIP lookups
by Neil Cook 15 May '19

15 May '19

Hi Tobi, This looks like you haven’t included the libmaxmind libraries before running configure. GeoIP support is only compiled in if it finds the right libs. This would be libmaxminddb-dev on Ubuntu for example. Neil >> Hi list >> >> hope it's okay to ask weakforced questions here as well, but I could not >> find a dedicated mailinglist for wforce. >> >> I want to enable GeoIP lookups in my wforce daemon. In a first step I >> installed luarocks and lua-compat53 to install mmdblua module. >> Then I added >> >> newGeoIP2DB("country", "/usr/local/share/GeoIP/GeoLite2-Country.mmdb") >> local mygeodb = getGeoIP2DB("country") >> if(mygeodb:lookupCountry(lt.remote) == 'XX') >> then >> return -1, "country blocked", "country blocked", { country="XX" } >> end >> >> to wforce.conf and tried to restart wforce but that ends up in a >> >> > Fatal Lua error: [string "chunk"]:28: attempt to call global >> > 'newGeoIP2DB' (a nil value) >> >> Any ideas what I could be missing here? >> >> Cheers >> >> tobi > > > Neil Cook > neil.cook(a)open-xchange.com <mailto:neil.cook@open-xchange.com> > > ------------------------------------------------------------------------------------- > Open-Xchange AG, Rollnerstr. 14, 90408 Nuremberg, District Court Nuremberg HRB 24738 > Managing Board: Rafael Laguna de la Vera, Carsten Dirks, Michael Knapstein, Stephan Martin > Chairman of the Board: Richard Seibt > > European Office: > Open-Xchange GmbH, Olper Huette 5f, D-57462 Olpe, Germany, District Court Siegen, HRB 8718 > Managing Director: Frank Hoberg > > US Office: > Open-Xchange. Inc., 530 Lytton Avenue, Palo Alto, CA 94301, USA > ------------------------------------------------------------------------------------- > Neil Cook neil.cook(a)open-xchange.com <mailto:neil.cook@open-xchange.com> ------------------------------------------------------------------------------------- Open-Xchange AG, Rollnerstr. 14, 90408 Nuremberg, District Court Nuremberg HRB 24738 Managing Board: Rafael Laguna de la Vera, Carsten Dirks, Michael Knapstein, Stephan Martin Chairman of the Board: Richard Seibt European Office: Open-Xchange GmbH, Olper Huette 5f, D-57462 Olpe, Germany, District Court Siegen, HRB 8718 Managing Director: Frank Hoberg US Office: Open-Xchange. Inc., 530 Lytton Avenue, Palo Alto, CA 94301, USA -------------------------------------------------------------------------------------

2 4

LDA-based vacation responses bouncing
by micah anderson 14 May '19

14 May '19

I've got dovecot vacataion auto-responses working via sieve, but when the responses are sent, they are sent as if they are to be locally delivered, which causes them to bounce for domains that I am not local for. How can I get dovecot's sieve vacation response to check the domain is local or not? Here is an example of what happens: The LDA notices it needs to send a vacation response: 2019-05-14T10:50:47.827466-07:00 brant dovecot: lda(user(a)example.org)<14817><xL6LL/f/2lzhOQAAh856Uw>: sieve: msgid=<20190514135045.012486@localhost>: sent vacation response to <someone(a)somewhere.org> but that response was sent via the postfix pipe through the dovecot lda transport... because that is local, and the domain it is sending to is not local, it bounces: 2019-05-14T10:50:47.923333-07:00 brant postfix/pipe[14821]: C998381539: to=<someone(a)somewhere.org>, relay=dovecot, delay=0.11, delays=0.04/0.01/0/0.06, dsn=5.1.1, status=bounced (user unknown) Postfix is set to do this: dovecot unix - n n - - pipe flags=DRhu user=mail argv=/usr/bin/spamc --connect-retries=1 -H -d 10.0.1.92 -s 10240000 -t 100 -u ${recipient} -e /usr/lib/dovecot/dovecot-lda -f ${sender} -d ${recipient} require ["fileinto", "vacation"]; vacation :days 2 :subject "Helllo" "Hi"; Here is my doveconf -n: # 2.3.4.1 (f79e8e7e4): /etc/dovecot/dovecot.conf # Pigeonhole version 0.5.4 () # OS: Linux 4.9.0-8-amd64 x86_64 Debian 9.8 auth_worker_max_count = 120 default_client_limit = 6144 default_process_limit = 256 default_vsz_limit = 512 M dict { expire = mysql:/etc/dovecot/dovecot-dict-sql.conf quota = mysql:/etc/dovecot/dovecot-dict-sql.conf } disable_plaintext_auth = no first_valid_gid = 8 first_valid_uid = 8 last_valid_gid = 8 last_valid_uid = 8 listen = * login_greeting = howdy, ready. login_log_format_elements = user=<%u> method=%m rip=%r lip=%l mpid=%e %c %k mail_location = mdbox:~/mdbox mail_plugins = expire quota zlib maildir_very_dirty_syncs = yes namespace { inbox = yes location = prefix = separator = . } namespace { alias_for = hidden = yes inbox = no list = no location = prefix = INBOX. separator = . } passdb { args = /etc/dovecot/dovecot-sql.conf driver = sql } plugin { expire = Trash expire2 = Trash/* expire3 = Spam expire_dict = proxy::expire quota = dict:Your mail quota::proxy::quota quota_rule = *:bytes=100663296 quota_rule2 = Trash:bytes=+20%% quota_rule3 = Spam:bytes=+10%% quota_rule4 = INBOX.Trash:bytes=+20%% quota_rule5 = INBOX.Spam:bytes=+10%% quota_rule6 = INBOX.restored_from_backups:bytes=+500%% sieve = ~/.dovecot.sieve sieve_after = /var/lib/dovecot/sieve/after.sieve sieve_before = /var/lib/dovecot/sieve/default.sieve sieve_dir = ~/sieve zlib_save = gz zlib_save_level = 6 } protocols = " imap pop3" service anvil { unix_listener anvil { group = dovecot mode = 0660 user = root } } service auth { client_limit = 6144 unix_listener auth-userdb { group = mail mode = 0600 user = mail } } service dict { unix_listener dict { group = mail mode = 0600 user = mail } } service imap-login { process_min_avail = 10 service_count = 0 vsz_limit = 512 M } service imap-postlogin { executable = script-login /usr/local/sbin/postlogin_imap } service imap { executable = imap imap-postlogin process_limit = 6144 } service pop3-login { process_min_avail = 10 service_count = 0 vsz_limit = 512 M } service pop3-postlogin { executable = script-login /usr/local/sbin/postlogin_pop } service pop3 { executable = pop3 pop3-postlogin } service stats { unix_listener stats-writer { group = mail mode = 0660 } } ssl_cert = </etc/certs/wildcard/cert.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-AES256-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_dh = # hidden, use -P to show it ssl_key = # hidden, use -P to show it ssl_prefer_server_ciphers = yes userdb { args = /etc/dovecot/dovecot-sql.conf driver = sql } verbose_proctitle = yes verbose_ssl = yes protocol lda { mail_plugins = expire quota trees zlib sieve plugin { quota_exceeded_message = Sorry, your message cannot be delivered to that person because their mailbox is full. If you can contact them another way, you may wish to tell them of this problem. quota_rule7 = INBOX:bytes=+10%% } } protocol imap { imap_client_workarounds = delay-newmail tb-extra-mailbox-sep mail_plugins = expire quota trees zlib imap_quota imap_zlib plugin { quota_exceeded_message = You are over quota. To avoid losing mail, immediately empty your Trash and Sent folders and delete emails with large attachments. } } protocol pop3 { mail_plugins = expire quota trees zlib pop3_client_workarounds = outlook-no-nuls oe-ns-eoh pop3_uidl_format = %g } remote 127.0.0.1 { mail_max_userip_connections = 60 } Thanks for any suggestions, micah

1 1

Graceful dovecot reload for LE certificate renewals
by Sidsel Jensen 14 May '19

14 May '19

Hi Dovecot-gurus With the introduction of LE certificates the certificate renewal cycle is a lot faster, unfortunately even a "dovecot reload" cuts the existing connections when doing the cert updates, which is quite frustrating - and yes most clients automatically reconnect but still... Is any work going into implementing a more “graceful reload” for dovecot like the one for nginx where existing connections are preserved with the old cert and new connections get the new cert? Kind Regards, Sidsel Jensen Systems Engineer @ One.com <http://one.com/>

2 1

Graceful dovecot reload for LE certificate renewals
by Sidsel Jensen 14 May '19

14 May '19

Hi Dovecot-gurus With the introduction of LE certificates the certificate renewal cycle is a lot faster, unfortunately even a "dovecot reload" cuts the existing connections when doing the cert updates, which is quite frustrating - and yes most clients automatically reconnect but still... Is any work going into implementing a more “graceful reload” for dovecot like the one for nginx where existing connections are preserved with the old cert and new connections get the new cert? Kind Regards, Sidsel Jensen Systems Engineer @ One.com <http://one.com/>

1 0

weakforced and GeoIP lookups
by Tobi 14 May '19

14 May '19

Hi list hope it's okay to ask weakforced questions here as well, but I could not find a dedicated mailinglist for wforce. I want to enable GeoIP lookups in my wforce daemon. In a first step I installed luarocks and lua-compat53 to install mmdblua module. Then I added newGeoIP2DB("country", "/usr/local/share/GeoIP/GeoLite2-Country.mmdb") local mygeodb = getGeoIP2DB("country") if(mygeodb:lookupCountry(lt.remote) == 'XX') then return -1, "country blocked", "country blocked", { country="XX" } end to wforce.conf and tried to restart wforce but that ends up in a > Fatal Lua error: [string "chunk"]:28: attempt to call global > 'newGeoIP2DB' (a nil value) Any ideas what I could be missing here? Cheers tobi

1 0

Is it possible to (re)direct only 1 imap user to the new server
by Marc Roos 14 May '19

14 May '19

I haven't used dovecot proxy or director. If I have a setup where all my users are connecting to HOSTNAMEOLD, is it possible to have 1 imap user that is connecting to HOSTNAMEOLD directed/forwarded to HOSTNAMENEW? Without changing my dns settings and preferably without creating any new servers. I think I can route one users mail to HOSTNAMENEW with sendmail ldap routing. So the only thing I need to be able to do is have the incoming imap requests on HOSTNAMEOLD been handled by HOSTNAMENEW. HOSTNAMEOLD HOSTNAMENEW +--------------+ +--------------+ | SENDMAIL | | SENDMAIL | | | | | | | | | | | V | | V | |--------------| |--------------| | lmtp | | NS /INBOX | | | | | mbox on | | V | | block device | |--------------| | | | NS /INBOX | |--------------| | mdbox on | | NS /ARCHIVE | | block device | | mdbox on | | | | clustered fs | |--------------| | | | NS /ARCHIVE | +--------------+ | mdbox on | | clustered fs | | | +--------------+

1 0

email notification regression between 2.2 and 2.3
by Thomas Capricelli 14 May '19

14 May '19

Hi, Hello. For the last year, each time i've tried updating dovecot from 2.2.x to 2.3.x, I had to rollback because of the following problem: Users don't "see" new emails arriving in subdirs. To be specific * we mostly use/tested thunderbird client * we use maildrop for delivery * this is using imap, not pop3 * when a new email arrives, thunderbird renders the dir name in blue and appends a "(1)" (or more..). That's what we call 'see' * this happens only on 'subdirs', not the main directory. * the server is a typical linux amd64, using the gentoo distribution More testing shows that * if we switch delivery to dovecot-lda, it works ok. But we can't commit that change, or at least not now/easily. Our users heavily use .mailfilter * if the user is currently viewing the subdir, then email notification is working * better : if the user went on the subdir and then in another dir, it keeps on working. It seems we need to 'open' it at least once for notification to work * "maildir_very_dirty_syncs = no" doesn't help (we had =yes) * "mailbox_list_index = no" doesn't help * i can confirm inotify was detected/used in autoconf when installed (anyway it works well with 2.2) I'm always on freenode (orzel). I'll be in #dovecot the next days at least. greetings, -- Thomas Capricelli

1 0

Userdb userdb_mail=, error Mailbox list driver maildir++: maildir_name not supported by this driver
by Marc Roos 14 May '19

14 May '19

I have this default configuration [0], when use the userdb_mail to point to the mdbox location, the inbox subfolders show differently in a firebird client. So I decided to copy the whole default mail_location into the userdb_mail configuration [2]. But then I get errors [3]. Should I change the namespace configuration here, how? My default namespaces are inbox and 4archives [0] [@ ]# doveconf | grep mail_loc mail_location = mbox:~/mail:INBOX=/var/spool/mail/%u:CONTROL=~/mail/control:INDEX=/var/d ovecot/%u/index:LAYOUT=maildir++ [1] [@dovecot]# cat special-userdb test:x:8267:231:Account with special settings for dovecot:/home/popusers/test:/bin/false:userdb_mail=mdbox:~/mdbox [2] [@dovecot]# cat special-userdb test:x:8267:231:Account with special settings for dovecot:/home/popusers/test:/bin/false:userdb_mail=mdbox:~/mdbox:INBOX=/ var/spool/mail/%u:CONTROL=~/mail/control:INDEX=/var/dovecot/%u/index:LAY OUT=maildir++ [3] May 13 22:41:32 mail04 dovecot: imap-login: Login: user=<test>, method=PLAIN, rip=192.168.10.219, lip=192.168.10.44, mpid=1138, TLS, session=<Gk4K8cqIkdHAqArb> May 13 22:41:32 mail04 dovecot: imap(test): Debug: Loading modules from directory: /usr/lib64/dovecot May 13 22:41:32 mail04 dovecot: imap(test): Debug: Module loaded: /usr/lib64/dovecot/lib15_notify_plugin.so May 13 22:41:32 mail04 dovecot: imap(test): Debug: Module loaded: /usr/lib64/dovecot/lib20_listescape_plugin.so May 13 22:41:32 mail04 dovecot: imap(test): Debug: Added userdb setting: mail=mdbox:~/mdbox:INBOX=/var/spool/mail/test:CONTROL=~/mail/control:IND EX=/var/dovecot/test/index:LAYOUT=maildir++ May 13 22:41:32 mail04 dovecot: imap(test): Debug: Effective uid=8267, gid=231, home=/home/popusers/test May 13 22:41:32 mail04 dovecot: imap(test): Debug: Namespace inbox: type=private, prefix=, sep=/, inbox=yes, hidden=no, list=yes, subscriptions=yes location=mdbox:~/mdbox:INBOX=/var/spool/mail/test:CONTROL=~/mail/control :INDEX=/var/dovecot/test/index:LAYOUT=maildir++ May 13 22:41:32 mail04 dovecot: imap(test): Error: Namespace '': Mailbox list driver maildir++: maildir_name not supported by this driver May 13 22:41:32 mail04 dovecot: imap(test): Namespace '': Mailbox list driver maildir++: maildir_name not supported by this driver in=0 out=378

2 5

doveadm 2.2.36-3.el7.x86_64 mailbox list -u test, does not use symlinked mailboxes
by Marc Roos 14 May '19

14 May '19

Maybe this has been already fixed, but symlinked mailboxes are not shown by [@ dovecot]# doveadm mailbox list -u test | sort Archive Archive/2018 Archive/2019 Archive/2019old Archive/Archive Drafts INBOX INBOX/test1 INBOX/test2 INBOX/test3 Junk Sent test testing-folder-home testing-folder-home/another folder Trash dovecot-2.2.36-3.el7.x86_64 CentOS Linux release 7.6.1810 (Core)

1 0

Sieve scripting
by Lefteris Tsintjelis 14 May '19

14 May '19

I want to monitor a special folder and execute a shell script each time I put an email to it. I would like to automate that way the process of SPAM reporting (SPAMCop). Is that possible with sieve? Lefteris

2 3

Doveadm sync, Error: read(remote) failed: EOF, Error: read(remote) failed: EOF
by Marc Roos 13 May '19

13 May '19

In the manual page this command is used for converting a mailbox doveadm sync -u test mdbox:~/mdbox -x INBOX -x INBOX/* Yet I am getting this error and the mdbox folder is not created. dsync-local(test): (version not received) doveadm(test): Fatal: execvp(mdbox:~/mdbox) failed: No such file or directory [@ dovecot]# doveconf | grep mail_locat mail_location = mbox:~/mail:INBOX=/var/spool/mail/%u:CONTROL=~/mail/control:INDEX=/var/d ovecot/%u/index:LAYOUT=maildir++ Users are not having shell access so something like su test -c '' will also not work. What would be a work-around for this?

2 2

dovecot 2.2.36 and wforce
by Tobi 13 May '19

13 May '19

Hi list I'm trying to setup dovecot 2.2.36 on a Centos6 to communicate with a wforce daemon on the remote side. wforce is latest released from git repo. Daemon part is working and I can successfully send queries from remote systems to wforce via curl For dovecot I configured in /etc/dovecot/conf.d/95-wforce.conf > auth_policy_server_url = http://REMOTE_IP:8084/ > auth_policy_hash_nonce = my_random > auth_policy_server_api_header = Authorization: Basic <BASE64 of wforce:my_password> > auth_policy_request_attributes = login=%{requested_username} pwhash=%{hashed_password} remote=%{rip} device_id=%{client_id} protocol=%s restarted dovecot without errors, but upon testing via imap I cannot see just one single tcp paket leaving direction REMOTE_IP on port 8084. It looks like auth policy in not involved at all. Thanks for any idea tobi

2 2

Re: Re: Dovecot not surviving OpenLDAP restart
by Dag Nygren 12 May '19

12 May '19

One more obvious line from the log: dovecot[26621]: auth: Error: LDAP: Connection lost to LDAP server, reconnecting Where it claims to reconnect, but after that there is no LDAP authentication. And the same configuration has worked fine since at least 10 years ago up to some recent update of dovecot or openldap. Best Dag

2 1