- dovecot - dovecot.org

Second private namespace
by André Rodier 19 Sep '19

19 Sep '19

Hello, I have Dovecot working, with a private namespace only. I would like to know if the following is feasible. - Add a second private namespace, in another directory scheme, for instance /mnt/backup/homebox/<user>/Mails/... - This namespace would be read-only. Perhaps the index and flags should be stored in a different folder with r/w access (e.g. /var, or even /tmp, it's not important) Now, as a matter of fact, this folder would be mounted on demand, via systemd-automount and fuse and is likely to be remote. This might implies some flags or caching on Dovecot performance. Thanks for your insights, André

1 0

Recent Dovecot on old operating system
by geho781＠justmail.de 19 Sep '19

19 Sep '19

Hi, sorry for the dumb question and please ignore this post if you think it's far beyond; i know it's not the way to go, but for reasons ... Has anyone running a self compiled recent dovecot (2.2.36.4) on Debian-7 and does it work? Or thinks it should work. Surprisingly it actually compiles flawlessly on Debian-7, but i wonder wether it will become a complete mess replacingthe existing dovecot (2.1.7) with the new one, serving a few dozens users and any kind of mail clients. Libraries of the compiled Dovecot: $ ldd ./src/master/.libs/dovecot linux-vdso.so.1 => (0x00007ffeacfb1000) libdovecot.so.0 => /usr/local/00-DBAI/dovecot/lib/dovecot/libdovecot.so.0 (0x00007f557b2a9000) libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007f557af1c000) libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x00007f557ad18000) librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1 (0x00007f557ab10000) /lib64/ld-linux-x86-64.so.2 (0x00007f557b5dc000) libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x00007f557a8f4000) libc6 versions: Debian-7: 2.13-38 Debian-9: 2.24-11 thanks so far, gerald

2 1

Dovecot 2.3.7.2 lucene segfault and coredump
by Domenico Pastore 19 Sep '19

19 Sep '19

Hi, i have a problem with libclucene-core.so.2.3.3.4. I See segfault error to messages log, when dovecot store mail to INBOX. set 12 13:41:21 box02.par-tec.it kernel: doveadm-server[20285]: segfault at 38 ip 00007f575b68fc42 sp 00007ffc0272e750 error 4 in libclucene-core.so.2.3.3.4[7f575b569000+188000] set 12 13:41:22 box02.par-tec.it kernel: doveadm-server[18871]: segfault at 38 ip 00007f9bea6d2c42 sp 00007fff47bceae0 error 4 in libclucene-core.so.2.3.3.4[7f9bea5ac000+188000] In the dovecot logs: 2019-09-12 13:45:09 auth: Debug: ldap(test4444client(a)newsvilXXXX,10.0.8.128<mailto:test4444client@newsvilXXXX,10.0.8.128>): Finished userdb lookup 2019-09-12 13:45:09 auth: Debug: userdb out: USER 1 test4444client@newsvilXXXX home=/pec_store/pec_mailbox/pec_mailbox_devel01/4/5/6/7/1/45671_18231 quota_rule=*:bytes=1048576000 mail_plugins+= 2019-09-12 13:45:10 SKENO8Uvel0gbAAA5ZKy4w doveadm(test4444client@newsvilXXXX): Fatal: master: service(doveadm): child 27680 killed with signal 11 (core dumped) 2019-09-12 13:45:10 auth: Debug: master in: USER 1 test4444client@newsvilXXXX service=doveadm lip=192.160.10.3 lport=924 rip=10.0.8.128 rport=36760 2019-09-12 13:45:10 auth: Debug: ldap(test4444client@newsvilXXXX 10.0.8.128): Performing userdb lookup I have attach the coredump of error and dovecot.conf Thanks for support. Br, Domenico ------------------- info: ------------------- # 2.3.7.2 (3c910f64b): /pec/config/dovecot/dovecot-devel01/dovecot.conf # Pigeonhole version 0.5.7.2 (7372921a) # OS: Linux 3.10.0-957.27.2.el7.x86_64 x86_64 CentOS Linux release 7.6.1810 (Core) # Hostname: box02

2 5

fts-elastic plugin
by Filip Hanes 19 Sep '19

19 Sep '19

Hi all, I have recently worked on fts plugin for ElasticSearch. https://github.com/filiphanes/fts-elastic It is forked from fts-elasticsearch as you can see in PR https://github.com/atkinsj/fts-elasticsearch/pull/21 with following changes (maybe some more) - no duplicate json keys in indexed documents, so compatible with ES 7.x - 1 elastic index for all users with routing by username - _id field similar to fts-solr (uid/box_guid/user) - better json response parsing - no need to use _source - added rawlog_dir to config and some more - renamed all elasticsearch to elastic for shorter names - fixed http_client leaks - fixed some compile warnings I would appreciate if someone with better experience in c and dovecot code would review my code and suggest/push changes. In my opinion fts-elastic is now functionally on level as currently recommended FTS plugin: fts-solr. I would like to implement proper rescan inspired by fts-lucene so it would become the most complete fts plugin for dovecot. -- Filip Hanes

3 2

Imaptest stall
by Marc Roos 18 Sep '19

18 Sep '19

I have been testing with imaptest and getting 'stalls', I tried even building from source and static. Even running it on the same host. Anyone knows what I could doing wrong? [@~]# ./imaptest - append=100,0 logout=0 host=192.168.10.44 port=143 user=test2 pass=xxxxxxxx seed=100 secs=240 clients=1 mbox=64kb.mbox box=INBOX/test Logi Sele Appe 100% 100% 100% 1 1 5 1/ 1 0 0 9 1/ 1 0 0 13 1/ 1 0 0 5 1/ 1

3 7

Namespace overlap
by Daniel Miller 17 Sep '19

17 Sep '19

Given an existing default namespace: namespace inbox { type = private separator = / prefix = location = sdbox:/var/mail/%d/%n/sdbox inbox = yes hidden = no list = yes subscriptions = yes } And mailboxes like: INBOX INBOX/Archives INBOX/Archives/2018 if I then define a new namespace: namespace archives { type = private separator = / prefix = Archives/ location = mdbox:/var/mail/%d/%n/Archives/mdbox subscriptions = no list = children } What will happen to the previous existing mailboxes & mails? Will they simply be "masked" by the new namespace and remain pending other operations? Or would they be moved/deleted? If they remain - is it possible to refer to the old mailboxes via either IMAP or doveadm? -- Daniel

1 0

CVE-2019-11500 and LMTP error
by Gabriele Nencioni 16 Sep '19

16 Sep '19

Hi all, does the dovecot fixed version: 2.3.7.2, 2.2.36.4 (as the CVE-2019-11500 says) fix the LMTP error "Got unexpected reply" as well? The LMTP error "Got unexpected reply" is described here: https://dovecot.org/pipermail/dovecot/2018-August/112562.html https://dovecot.org/pipermail/dovecot/2018-August/112666.html Thanks in advance Regards, -- Gabriele Nencioni

2 1

Repo for Debian-Buster
by slater.ch 16 Sep '19

16 Sep '19

Hi, is there already a release date for Debian Buster packages? kind regards Christian

3 2

corrupted mdbox
by sch tel 16 Sep '19

16 Sep '19

Hello list, i run into another problem. It seems there are some null bytes in the middle of an compressed mdbox, if i look into it with hexdump after run doveadm dump. With mdbox-recover.pl i could recover ~2k messages. What should i do to recover this broken mdbox file and dsync can finish? Sep 06 18:47:28 doveadm: Error: zlib.read(/var/spool/mail/<user>/storage/m.770): unexpected EOF at 7947710 Sep 06 18:47:28 doveadm: Error: dsync(server1): read(zlib(/var/spool/mail/<user>/storage/m.770)) failed: read(/var/spool/mail/<user>/storage/m.770) failed: zlib.read(/var/spool/mail/<user>/storage/m.770): unexpected EOF at 7947710 (last sent=mail, last recv=mail_request (EOL)) Sep 06 18:47:29 dsync-local(<user>)<+mJrOaCNcl2eZwAA0H466A>: Error: zlib.read(/var/spool/mail/<user>/storage/m.770): unexpected EOF at 7947710 Sep 06 18:47:29 dsync-local(<user>)<+mJrOaCNcl2eZwAA0H466A>: Error: dsync(server1): read(zlib(/var/spool/mail/<user>/storage/m.770)) failed: read(/var/spool/mail/<user>/storage/m.770) failed: zlib.read(/var/spool/mail/<user>/storage/m.770): unexpected EOF at 7947710 (last sent=mail, last recv=mail_request (EOL))

2 1

question about Mailcrypt plugin
by Daniel Niewerth 14 Sep '19

14 Sep '19

Hi everybody, I have a question about the Dovecot Mailcrypt Plugin. I'm trying to understand what the security of this plugin is based on. The encryption with private and public key and elliptic curves is basically a good thing. But the keys are in the file system together with the encrypted mails. The passwords for the private keys are in the user database. I guess the passwords have to be in plaintext for it to work. Is that true, or did I misunderstand something? Then the encryption would make no sense at all, right? For what purpose was the plugin developed? Can anyone explain this to me? Best regards Daniel

2 2