- dovecot - dovecot.org

Localhost imap server fails after upgrade from 2.2.33.2-1 to 1:2.3.2.1
by cpblpublic+dovecot＠gmail.com 20 Jan '19

20 Jan '19

I use a localhost dovecot imap server in order to access maildir folders from Alpine (see 2009 instructions for my set up here https://cpbl.wordpress.com/2009/11/07/alpine-offlineimap-and-gmail-under-ub… ) My configuration has worked nicely since 2009, but failed after a recent upgrade of dovecot (during basic upgrade from Ubuntu 18.04 to 18.10). The version of Alpine did not change. Uninstalling dovecot-core and dovecot-imapd, and reinstalling the older versions, fully fixes the problem. I would like to know how to get my configuration working with the new version of dovecot. Here's what the problem looks like: I have a file auto-dovecot.conf with only the following two lines. verbose_proctitle = yes mail_location = maildir:/home/meuser/imap/gmailStanford:LAYOUT=fs:INBOX=/home/meuser/imap/gmailStanford/INBOX Other /etc/ files are unchanged from installation defaults. Alpine calls imapd when it starts, with the following command: /usr/lib/dovecot/imap -c /home/meuser/dotfiles/auto-dovecot.conf When I run that command, I get: imap(meuser,)Error: net_connect_unix(/var/run/dovecot/stats-writer) failed: Permission denied * PREAUTH [CAPABILITY IMAP4rev1 SASL-IR LOGIN-REFERRALS ID ENABLE IDLE SORT SORT=DISPLAY THREAD=REFERENCES THREAD=REFS THREAD=ORDEREDSUBJECT MULTIAPPEND URL-PARTIAL CATENATE UNSELECT CHILDREN NAMESPACE UIDPLUS LIST-EXTENDED I18NLEVEL=1 CONDSTORE QRESYNC ESEARCH ESORT SEARCHRES WITHIN CONTEXT=SEARCH LIST-STATUS BINARY MOVE SNIPPET=FUZZY LITERAL+ NOTIFY] Logged in as meuser so I am guessing that the first line is the issue, since when the older version I get instead: * PREAUTH [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE IDLE SORT SORT=DISPLAY THREAD=REFERENCES THREAD=REFS THREAD=ORDEREDSUBJECT MULTIAPPEND URL-PARTIAL CATENATE UNSELECT CHILDREN NAMESPACE UIDPLUS LIST-EXTENDED I18NLEVEL=1 CONDSTORE QRESYNC ESEARCH ESORT SEARCHRES WITHIN CONTEXT=SEARCH LIST-STATUS BINARY MOVE] Logged in as meuser Can anyone help me? I cannot find documentation for using a localhost server for Alpine, except my own from 2009. Many thanks! Chris

5 9

Issue with LMTP proxying and port number
by Steven Craig 20 Jan '19

20 Jan '19

Hello there, Everything was working fine on Dovecot 2.2.10 (on CentOS 7), but after updating to version 2.2.36, our director servers are not able to proxy LMTP. We are sending mail from exim to the local Dovecot LMTP socket, which then used to send it to our internal mail servers on port 24. Besides the update, nothing has changed in the config files. The configuration has been working great for months … Then we had a great idea of doing holiday maintenance. (Currently, we are working around this issue by having exim send mail to the IP and port, instead of the socket.) Doing a tcpdump capture shows no TCP traffic either. The logs seem to say that it is trying to go to port 0, so my guess is that it’s not getting the port directive from either static or sql — since the docs state that if these settings aren't specified, it will always use the same connection type for the proxy that it received the connection on. Any thoughts? I can share config if necessary.

2 5

Authentication/Penalty disabled (socket mode=0) introduces constant 5 sec delays (2.27 on debian 9)
by Ludovic Pouzenc 20 Jan '19

20 Jan '19

Hi, I hit a bizare problem with dovecot 2.2.7 on debian 9 with LMTP enabled and auth/penalty disabled as documented here : https://wiki.dovecot.org/Authentication/Penalty Use case : I run a swaks command to send an email to an exim4 that tries to make a callout to dovecot-lmtp. At RCPT TO: swaks hangs 5.0<something-small> seconds then process normally (exim is waiting for callout completion). with strace, I see 5 second delay with many tries to socket connection. (PID 9652 was an auth process freshly forked) [pid 9652] socket(AF_UNIX, SOCK_STREAM, 0) = 14 [pid 9652] fcntl(14, F_GETFL) = 0x2 (flags O_RDWR) [pid 9652] fcntl(14, F_SETFL, O_RDWR|O_NONBLOCK) = 0 [pid 9652] connect(14, {sa_family=AF_UNIX, sun_path="anvil-auth-penalty"}, 110) = -1 ECONNREFUSED (Connection refused) [pid 9652] close(14) = 0 [pid 9652] nanosleep({tv_sec=0, tv_nsec=20000000}, NULL) = 0 [pid 9652] socket(AF_UNIX, SOCK_STREAM, 0) = 14 [pid 9652] fcntl(14, F_GETFL) = 0x2 (flags O_RDWR) [pid 9652] fcntl(14, F_SETFL, O_RDWR|O_NONBLOCK) = 0 [pid 9652] connect(14, {sa_family=AF_UNIX, sun_path="anvil-auth-penalty"}, 110) = -1 ECONNREFUSED (Connection refused) [pid 9652] close(14) = 0 [pid 9652] nanosleep({tv_sec=0, tv_nsec=50000000}, NULL) = 0 [pid 9652] socket(AF_UNIX, SOCK_STREAM, 0) = 14 [pid 9652] fcntl(14, F_GETFL) = 0x2 (flags O_RDWR) [pid 9652] fcntl(14, F_SETFL, O_RDWR|O_NONBLOCK) = 0 [pid 9652] connect(14, {sa_family=AF_UNIX, sun_path="anvil-auth-penalty"}, 110) = -1 ECONNREFUSED (Connection refused) [pid 9652] close(14) = 0 [pid 9652] nanosleep({tv_sec=0, tv_nsec=90000000}, NULL) = 0 with ddd I get to: src/lib-master/anvil-client.c: int anvil_client_connect(struct anvil_client *client, bool retry) { //[...] fd = retry ? net_connect_unix_with_retries(client->path, 5000) : net_connect_unix(client->path); //[...] and retry is forced to TRUE by the caller and net_connect_unix_with_retries retries in case of ECONNREFUSED. How I get into it : ssh -X root@telegraphe-test apt install dovecot-dbg cd /dev/shm apt source dovecot cd dovecot-2.2.27 pidof dovecot ddd /usr/sbin/dovecot set follow-fork-mode child attach 11833 cont # Send an e-mail from swaks to exim that use transport=smtp in LMTP mode to dovecot-lmtp, press interrupt while exim is blocking after RCPT TO: (gdb) bt #0 0x00007f81528af270 in __nanosleep_nocancel () at ../sysdeps/unix/syscall-template.S:84 #1 0x00007f81528d8b84 in usleep (useconds=<optimized out>) at ../sysdeps/posix/usleep.c:32 #2 0x00007f815329368e in net_connect_unix_with_retries (path=0x562dc200ce10 <error: Cannot access memory at address 0x562dc200ce10>, msecs=msecs@entry=5000) at net.c:347 #3 0x00007f815320ce0d in anvil_client_connect (client=0x562dc200cda0, retry=retry@entry=true) at anvil-client.c:136 #4 0x0000562dc1429f5d in auth_penalty_init (path=0x562dc1451846 <error: Cannot access memory at address 0x562dc1451846>) at auth-penalty.c:37 #5 0x0000562dc1424166 in main_preinit () at main.c:202 #6 main (argc=<optimized out>, argv=<optimized out>) at main.c:396 (gdb) bt full #1 0x00007f81528d8b84 in usleep (useconds=<optimized out>) at ../sysdeps/posix/usleep.c:32 ts = {tv_sec = 0, tv_nsec = 80000000} #2 0x00007f815329368e in net_connect_unix_with_retries (path=0x562dc200ce10 <error: Cannot access memory at address 0x562dc200ce10>, msecs=msecs@entry=5000) at net.c:347 start = {tv_sec = 1545319486, tv_usec = 241864} now = {tv_sec = 1545319490, tv_usec = 198061} fd = -1 #3 0x00007f815320ce0d in anvil_client_connect (client=0x562dc200cda0, retry=retry@entry=true) at anvil-client.c:136 fd = <optimized out> __FUNCTION__ = <error reading variable __FUNCTION__ (Cannot access memory at address 0x7f81532a8260)> #4 0x0000562dc1429f5d in auth_penalty_init (path=0x562dc1451846 <error: Cannot access memory at address 0x562dc1451846>) at auth-penalty.c:37 No locals. #5 0x0000562dc1424166 in main_preinit () at main.c:202 mod_set = <error reading variable mod_set (Cannot access memory at address 0x7ffda885db80)> #6 main (argc=<optimized out>, argv=<optimized out>) at main.c:396 c = <optimized out> Backtrace stopped: Cannot access memory at address 0x7ffda885dbf8 (gdb) Code I've read : src/auth/main.c: static void main_preinit(void) if (!worker) auth_penalty = auth_penalty_init(AUTH_PENALTY_ANVIL_PATH); auth_request_stats_init(); src/auth/auth-penalty.c: struct auth_penalty *auth_penalty_init(const char *path) if (anvil_client_connect(penalty->client, TRUE) < 0) penalty->disabled = TRUE; else { src/lib-master/anvil-client.c: int anvil_client_connect(struct anvil_client *client, bool retry) fd = retry ? net_connect_unix_with_retries(client->path, 5000) : net_connect_unix(client->path); src/lib/net.c : int net_connect_unix_with_retries(const char *path, unsigned int msecs) { struct timeval start, now; int fd; if (gettimeofday(&start, NULL) < 0) i_panic("gettimeofday() failed: %m"); do { fd = net_connect_unix(path); if (fd != -1 || (errno != EAGAIN && errno != ECONNREFUSED)) // <------------------ HERE, I go into ECONNREFUSED case during 5 seconds break; /* busy. wait for a while. */ usleep(((rand() % 10) + 1) * 10000); if (gettimeofday(&now, NULL) < 0) i_panic("gettimeofday() failed: %m"); } while (timeval_diff_msecs(&now, &start) < (int)msecs); return fd; } Additionnal environment infos (mailboxes are NFS-backed) : lsb_release -a No LSB modules are available. Distributor ID: Debian Description: Debian GNU/Linux 9.2 (stretch) Release: 9.2 Codename: stretch mount | grep ^/ /dev/sda1 on / type ext4 (rw,relatime,errors=remount-ro,data=ordered) mount | grep nfs nfs1:/mail/maildir on /var/maildir type nfs (rw,relatime,vers=3,rsize=65536,wsize=65536,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,mountaddr=172.16.2.28,mountvers=3,mountport=635,mountproto=udp,local_lock=none,addr=172.16.2.28) nfs1:/mail on /var/mail type nfs (rw,relatime,vers=3,rsize=65536,wsize=65536,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,mountaddr=172.16.2.28,mountvers=3,mountport=635,mountproto=udp,local_lock=none,addr=172.16.2.28) cifs1:/homepermanents/info/lpouzenc on /home/lpouzenc type nfs (rw,nosuid,nodev,relatime,vers=3,rsize=65536,wsize=65536,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,mountaddr=172.16.2.29,mountvers=3,mountport=635,mountproto=udp,local_lock=none,addr=172.16.2.29) telegraphe-test:~# apt-cache policy dovecot-core dovecot-core: Installé : 1:2.2.27-3+deb9u2 Candidat : 1:2.2.27-3+deb9u2 Table de version : *** 1:2.2.27-3+deb9u2 500 500 http://miroir/debian stretch/main amd64 Packages 500 http://security.debian.org/debian-security stretch/updates/main amd64 Packages 100 /var/lib/dpkg/status telegraphe-test:~# dovecot -n # 2.2.27 (c0f36b0): /etc/dovecot/dovecot.conf # Pigeonhole version 0.4.16 (fed8554) doveconf: Warning: service auth { client_limit=10000 } is lower than required under max. load (10240) # OS: Linux 4.9.0-4-amd64 x86_64 Debian 9.2 nfs auth_verbose = yes default_client_limit = 10000 default_process_limit = 2048 lda_mailbox_autocreate = yes lda_mailbox_autosubscribe = yes mail_debug = yes mail_fsync = always mail_location = maildir:/var/mail/maildir/%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 mmap_disable = yes 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 = separator = / } passdb { driver = pam } plugin { sieve = file:/var/mail/mailconf/%1u/%u/sieve;active=/var/mail/mailconf/%1u/%u/.dovecot.sieve sieve_before = /var/mail/mailconf/global/sieve/before.d sieve_global = /var/mail/mailconf/global/sieve sieve_vacation_dont_check_recipient = yes } protocols = " imap lmtp sieve sieve" service anvil { unix_listener anvil-auth-penalty { mode = 00 } } service lmtp { inet_listener lmtp { port = 24 } } service managesieve { process_limit = 16 } ssl_cert = </etc/ssl/certs/telegraphe7_cert.pem ssl_key = # hidden, use -P to show it syslog_facility = local0 userdb { driver = passwd } verbose_proctitle = yes protocol lmtp { auth_username_format = %n mail_plugins = " sieve" } protocol imap { mail_max_userip_connections = 20 } Could you see a config tuning that keeps auth-penalty out of the way (it seems to behaves badly here, because we have perdition IMAP proxy in front, and it keeps track only of his IP and adds 2/4/8/15s delays to "random" legit clients. Could it be saved with a dedicated config entry to disable auth-penalty ? Is there solution to have auth-penalty working while having perdition IMAP proxy ? Regards, Ludovic Pouzenc -- Ludovic POUZENC - Ingénieur Système IMT Mines Albi (http://www.imt-mines-albi.fr) 81013 ALBI CT Cedex 09 - Tel : 05 63 49 33 56

2 3

panic when using dovecot master account
by André Rodier 20 Jan '19

20 Jan '19

Hello, I am running dovecot 2.2.34 (874deae), on Debian stable, from backports. I just tried the master account, and although everything worked in the email client, I had logs in the error logs: > imap(mirina): Panic: file mail-index-sync.c: line 413 > (mail_index_sync_begin_to2): assertion failed: (!index->syncing) > Nov 08 22:06:24 osaka dovecot[1450]: imap(mirina): Error: Raw > backtrace: /usr/lib/dovecot/libdovecot.so.0(+0x9e412) [0x7f20ae813412] > -> /usr/lib/dovecot/libdovecot.so.0(+0x9e50d) [0x7f20ae81350d] -> > /usr/lib/dovecot/libdovecot.so.0(i_fatal+0) [0x7f20ae7a2c51] -> > /usr/lib/dovecot/libdovecot-storage.so.0(+0xe0fe4) [0x7f20aeb88fe4] -> > /usr/lib/dovecot/libdovecot-storage.so.0(mail_index_sync_begin_to+0x4f) > [0x7f20aeb890bf] -> > /usr/lib/dovecot/libdovecot-storage.so.0(mail_index_sync_begin+0x1c) > [0x7f20aeb8915c] -> > /usr/lib/dovecot/modules/lib20_virtual_plugin.so(virtual_storage_sync_init+0x218) > [0x7f20ad51f308] -> > /usr/lib/dovecot/libdovecot-storage.so.0(mailbox_sync_init+0x44) > [0x7f20aeaf02d4] -> > /usr/lib/dovecot/libdovecot-storage.so.0(mailbox_sync+0x37) > [0x7f20aeaf0387] -> > /usr/lib/dovecot/libdovecot-storage.so.0(index_storage_get_status+0x31) > [0x7f20aeb6bbf1] -> > /usr/lib/dovecot/modules/lib20_virtual_plugin.so(+0x936d) > [0x7f20ad51c36d] -> /usr/lib/dovecot/libdovecot-storage.so.0(+0xa8771) > [0x7f20aeb50771] -> > /usr/lib/dovecot/modules/lib20_fts_plugin.so(+0xfd46) [0x7f20adb8bd46] > -> /usr/lib/dovecot/libdovecot-storage.so.0(mailbox_get_status+0x31) > [0x7f20aeaf0781] -> > /usr/lib/dovecot/modules/lib20_virtual_plugin.so(virtual_storage_sync_init+0x10b8) > [0x7f20ad5201a8] -> > /usr/lib/dovecot/libdovecot-storage.so.0(mailbox_sync_init+0x44) > [0x7f20aeaf02d4] -> > /usr/lib/dovecot/libdovecot-storage.so.0(mailbox_sync+0x37) > [0x7f20aeaf0387] -> > /usr/lib/dovecot/libdovecot-storage.so.0(index_storage_get_status+0x31) > [0x7f20aeb6bbf1] -> > /usr/lib/dovecot/modules/lib20_virtual_plugin.so(+0x936d) > [0x7f20ad51c36d] -> /usr/lib/dovecot/libdovecot-storage.so.0(+0xa8771) > [0x7f20aeb50771] -> > /usr/lib/dovecot/modules/lib20_fts_plugin.so(+0xfd46) [0x7f20adb8bd46] > -> /usr/lib/dovecot/libdovecot-storage.so.0(mailbox_get_status+0x31) > [0x7f20aeaf0781] -> > /usr/lib/dovecot/modules/lib20_virtual_plugin.so(virtual_storage_sync_init+0x10b8) > [0x7f20ad5201a8] -> > /usr/lib/dovecot/libdovecot-storage.so.0(mailbox_sync_init+0x44) > [0x7f20aeaf02d4] -> > /usr/lib/dovecot/libdovecot-storage.so.0(mailbox_sync+0x37) > [0x7f20aeaf0387] -> dovecot/imap(cmd_select_full+0x16b) > [0x557de970cc3b] -> dovecot/imap(command_exec+0x5c) [0x557de971444c] -> > dovecot/imap(+0x1a912) [0x557de9712912] > Nov 08 22:06:24 osaka dovecot[1450]: imap(mirina): Fatal: master: > service(imap): child 4289 killed with signal 6 (core dumps disabled) I attach my dovecot configuration too. Thanks for your help.

3 6

Moving messages on test server, dovecot.index.log was locked for x seconds on cephfs
by Marc Roos 20 Jan '19

20 Jan '19

I am getting on a test environment were no users are logging in a dovecot.index.log was locked when moving messages with doveadm move -u testuser Archive/2012 mailbox INBOX/inbox BEFORE 2013-01-01. doveadm(testuser): Warning: Transaction log file /var/dovecot/testuser/index/.INBOX.inbox/dovecot.index.log was locked for 215 seconds (rotating while syncing) I have read about how this can be related to default locking fcntl and nfs, anyone having this solved with cephfs? https://www.dovecot.org/list/dovecot/2009-January/036194.html

1 0

Dovecot 2.3 no longer accepts ssl_key_password
by Chris Kiakas 20 Jan '19

20 Jan '19

Hit a little problem when I upgraded a system from FreeBSD 10.3 to 11.2. I did not receive any errors in the upgrade. The system is running 4 jails and everything seems to work except in Dovecot dovecot-2.3.4_5 where when using the exact same configuration which worked in 10.3 with the same password protected certificate key. (doveconf -n -P shows the correct password.) ssl_ca = </usr/local/etc/site.keys/name_com.ca-bundle ssl_cert = </usr/local/etc/site.keys/name_com.crt ssl_dh = </usr/local/etc/dovecot/dh.pem ssl_key = </usr/local/etc/site.keys/name.com.key ssl_key_password = keypassword The password works with openssl. Changing the password on the key has no effect. Removing the password on the cert with openssl and running dovecot with the new key works. I installed on another system and I am experiencing the same results. The issue persists whether I install dovecot from ports or pkg. I can't see where the problem is. It seems that Dovecot is unable to read the key when password protected even though it has the correct password. Has anyone experienced this? Chris

3 2

Re: Feature request SCRAM-SHA-256
by Stephan Bosch 20 Jan '19

20 Jan '19

Op 16/12/2018 om 10:06 schreef Tributh via dovecot: > > Am 16.12.18 um 09:42 schrieb Aki Tuomi: >>> On 16 December 2018 at 10:27 Tributh via dovecot <dovecot(a)dovecot.org> wrote: >>> >>> >>> Hi, >>> is that here the right place to make feature requests? >>> >>> dovecot supports as authentication mechanism >>> SCRAM-SHA-1 from RFC 5802 >>> which was updated to >>> SCRAM-SHA-256 in RFC 7677 >>> >>> Can SCRAM-SHA-256 be added to the authentication mechanisms? >>> >>> I would not like to request, that SCRAM-SHA-1 will be exchanged by >>> SCRAM-SHA-256, since several applications only support SCRAM-SHA-1 >>> >>> Regards >>> >>> Torsten >> Hi! >> >> Adding this is possible, it can even be done as a separate plugin. But I have to ask, why? Do you actually have clients that support this? >> >> Aki >> > Hi Aki, > let me first answer the second question. > Sadly I have no client which supports it, yet. > Here we have a chicken or the egg causality dilemma. > There was some communication with mail-client developers which stated > that they would start developing it, when they have a publicly usable > server to test against. > Now I hope that the most common IMAP server could be the one, which > gives this possibility. > Sadly, most communication is not publicly available. > > In the past CRAM-MD5 was very popular. When the insecurity came out, > everything just shifted to TLS, but that prevented not from sending a > plain password now. If a malicious actor is able to change DNS/TLS > endpoints, he will receive the plain passwords immediately. > I am not the expert in explaining how such an actor could do this. I > just wanted to have possibilities for everybody to prevent this possible > exposure of a plain password, which could than easily used abusively. > > I just hope for better security in the future. I looked a this a bit and since it is basically only a matter of replacing the hash algorithm, I created a quick implementation (after some refactoring): https://github.com/stephanbosch/dovecot-core/commits/auth-scram-sha-256 However, since there is no client that actually supports this, I cannot test this myself. I've briefly tested that the old SHA-1 still works (using mpop) and that the server properly announces the new mechanism when enabled, but that is it. It is based on the master branch. Configuration is identical to SCRAM-SHA-1, apart from the mechanism (and password scheme) name of course. Don't expect this to be released or even merged to the master branch any time soon: this is likely currently very low on our priority list. But, at least you can run your own server with SCRAM-SHA-256 support (and so can client developers). Maybe if this gets endorsed and supported by clients and gets some testing in the field, we can speed it along a bit, but that is not something I can promise. So, I hatched a chick for you. I hope you can make it lay a few eggs in the future... Regards, Stephan.

2 2

IMAP preauth and stats-writer
by Mark Hills 20 Jan '19

20 Jan '19

I use IMAP preauth; I connect with Alpine over SSH which is very useful. The last few upgrades this has become more difficult to to. Last time (moving 2.2 -> 2.3, I think) I had to put in a workaround: stats_writer_socket_path = It prevented /usr/local/libexec/dovecot/imap attempting to connect to a central stats service. As of an upgrade today (2.3.2.1_1 -> 2.3.4_3 on FreeBSD) it looks like that 'fix' stopped working, and I get: imap(mark,)Error: net_connect_unix() failed: Permission denied It goes to stderr, which breaks Alpine. "()" is actually the filename. It seems that the empty string is no longer an indication to disable it. Here it is with the default configuration: imap(mark,)Error: net_connect_unix(/var/run/dovecot/stats-writer) failed: Permission denied I do also have a dovecot running as a system daemon, and, interestingly, disable this and it's 'fixed'; no attempt to connect. However, disabling the service is not an option (needed for smartphone) The best I've come up with so far is when using preauth to hack it to send stderr to /dev/null. And yes, probably Alpine is at fault for interpreting stderr content (separate issue) * Is there a way to cleanly disable reporting to the stats service? Previously, running as preauth was all very clean. * Just wanted to highlight that IMAP preauth is really useful. Even though it might not be mainstream, it seems healthy to be able to easily install dovecot as an unprivilidged user in a "unixy" way. I'm on FreeBSD 11.2, with dovecot from ports. dovecot.conf below. -- Mark # # Dovecot configuration # mail_location = maildir:~/Maildir postmaster_address = postmaster namespace { inbox = yes } ssl = required ssl_cert = </etc/ssl/lets.crt ssl_key = </etc/ssl/local.key ssl_dh = </etc/ssl/dh.pem # # No writing of statistics to a priviledged service; # this is troublesome for a user to run the IMAP client # #stats_writer_socket_path = # # Authentication: only allow passwords sent over TLS, and # check against the system password database # passdb { driver = pam } userdb { driver = passwd } # # Disable all except standard IMAP with TLS logins # service imap-login { inet_listener imaps { port = 0 } } service pop3-login { inet_listener pop3 { port = 0 } inet_listener pop3s { port = 0 } } # # An authentication service to allow Exim to use the # same credentials as Dovecot # service auth { unix_listener auth-client { mode = 0600 user = mailnull } } protocol imap { mail_max_userip_connections = 40 } # END

4 9

BUG 'doveadm mailbox' list does not honour symlinks to (mbox) mailboxes
by Marc Roos 20 Jan '19

20 Jan '19

doveadm mailbox list does not honour symlinks to at least the mbox mailboxes I relocated temporarily. You would expect it to behave similar to the server and use the symlinks. dovecot-2.2.36-3.el7.x86_64 CentOS Linux release 7.6.1810 (Core)

1 0

Re: Feature request SCRAM-SHA-256
by Stephan Bosch 20 Jan '19

20 Jan '19

Hi, Op 13/01/2019 om 17:48 schreef Tributh via dovecot: > Hi, > sorry for my late reply. Was too busy during the week. > Thank you for your patches. I hope I will be able with them to get now > some client support for SCRAM-SHA-256. Will report how I succeed in the > future. I managed to test it successfully using MailKit: https://github.com/jstedfast/MailKit I used the IMAP demo in samples/ImapClientDemo. I limited the available mechanisms presented by the server to SCRAM-SHA-256 exclusively, so the demo needs no modification. So, from our end it seems to work fine. Regards, Stephan.

1 0

Reloading dovecot after certificate renewal?
by ＠lbutlr 17 Jan '19

17 Jan '19

Is it enough to issue a `service restart dovecot` when a certificate renews or do I need to service stop/start? -- "A thousand years ago we thought the world was a bowl. Five hundred years ago we knew it was a globe. Today we know it is flat and round carried through space on the back of a turtle. Don't you wonder what shape it will turn out to be tomorrow?" [Lord Vetinari]

1 1

Re: Authentication lost within session
by Sami Ketola 17 Jan '19

17 Jan '19

> On 17 Jan 2019, at 14.19, Marc Roos <M.Roos(a)f1-outsourcing.eu> wrote: > > > Same ip, connection, session happens after a few seconds, all on local > test network. Sorry I mistakenly overlooked at the ip:s. But anyway that is multiple connections and seems that PAM has some concurrency limit and refuses the third connection Thunderbird opens. so you probably have pam_limits with maxlogins=2 enabled. Sami

2 2

Need help deduplicating messages fetched with getmail into dovecot mailbox
by Gabriel Kaufmann 17 Jan '19

17 Jan '19

Hello everyone, I'm using getmail to fetch some external mails from POP3 into a dovecot mailbox (providing IMAP). Getmail seems to have some serious problems keeping track of mails already fetched. I have every Mail exactly twice in my Mailbox delivered by Dovecot. Of course they are not in the original external POP3 Inbox. I hope I'm in right place here. I think the problem is not dovecot related, but getmail. As there is a huge number of user complains about getmail (and obviously no alternative?!) I hope to find some help here for a workaround. I noticed getmail can be configured for some kind of filtering to sort out Mails for local delivery to dovecot. http://pyropus.ca/software/getmail/configuration.html#filter-examples Does anyone know how to query the message-id (given by mail-headers) with doveadm? My first test was this: > doveadm fetch -u my-mailbox(a)domain.net "mailbox date.sent" message-id > "<369408722.286104911.1547114312259.Foo.root(a)someone.org>" But then I noticed this is only ment to be used with dovecot internal GUID - I think... Is it possible to query for the mail message-id also? Is it posible to reconfigure indexing to include this propery from the original message-file? I made a small perl-script to extract it using Perl-Lib Email::Simple. > To: my-mailbox(a)domain.net > *Message-ID: <369408722.286104911.1547114312259.Foo.root(a)someone.org>* > Subject: Some test I also already tried the doveadm deduplicate, but this also doesn't work as it is also basing on the internal GUID of dovecot and every duplicate-message seems to have a new, unique GUID. > doveadm deduplicate -u gabriel.kaufmann(a)gmx.net mailbox-guid May be anyone know a better solution. -- Best regards Gabriel Kaufmann

2 4

Accidentally deleted .imap folder, how can I reindex?
by Les 17 Jan '19

17 Jan '19

Hello, I have several users with Maildir format. After upgrading from 2.2 to 2.3, some directories could not be opened from thunderbird. The server log shows all kinds of errors including these: Corrupted record in index cache file /home/user01/Maildir/.Elk&APw-ld&APY-tt/dovecot.index.cache: UID 2802: Broken physical size in mailbox Cached message size larger than expected (18 > 17, box=Sent, UID=2802) While trying to fix the problem, I have accidentally deleted some of the index/cache directories. In particular, Maildir/.Sent/.imap and Maildir/.Sent/cur/.imap folders were deleted, but all of the mail message files are there. When I try to open the "Sent" folder from thunderbird, it does not show all of the messages. It only shows messages until 2019.01.12. If I send out an email from thunderbird, then a new message is copied into the Maildir/.Sent/ folder, but it is not visible from thunderbird. I have already tried to unsubscribe + subscribe to the Sent folder, but it did not work - it re-downloads all messages until 2019.01.12, but not after that. Can I somehow regenerate the index files, force dovecot to recreated .imap foder, and force thunderbird to re-download and show all of the files somehow? Thank you, Laszlo

2 2

Authentication lost within session
by Marc Roos 17 Jan '19

17 Jan '19

When I open the mail client (thunderbird), I can access the mailboxes and all of a sudden, I am loosing the authenticated session. Any idea's where to look? Jan 17 12:42:04 mail04 dovecot: imap-login: Login: user=<usertest>, method=PLAIN, rip=192.168.10.219, lip=192.168.10.44, mpid=13403, TLS, session=<NsYo4qV/CNfAqArb> Jan 17 12:42:04 mail04 dovecot: imap(usertest): Debug: Loading modules from directory: /usr/lib64/dovecot Jan 17 12:42:04 mail04 dovecot: imap(usertest): Debug: Module loaded: /usr/lib64/dovecot/lib15_notify_plugin.so Jan 17 12:42:04 mail04 dovecot: imap(usertest): Debug: Module loaded: /usr/lib64/dovecot/lib20_listescape_plugin.so Jan 17 12:42:04 mail04 dovecot: imap(usertest): Debug: Effective uid=8267, gid=231, home=/home/popusers/usertest Jan 17 12:42:04 mail04 dovecot: imap(usertest): Debug: Namespace inbox: type=private, prefix=, sep=/, inbox=yes, hidden=no, list=yes, subscriptions=yes location=mbox:~/mail:INBOX=/var/spool/mail/usertest:CONTROL=~/mail/contr ol:INDEX=/var/dovecot/usertest/index:LAYOUT=maildir++ Jan 17 12:42:04 mail04 dovecot: imap(usertest): Debug: maildir++: root=/home/popusers/usertest/mail, index=/var/dovecot/usertest/index, indexpvt=, control=/home/popusers/usertest/mail/control, inbox=/var/spool/mail/usertest, alt= Jan 17 12:42:04 mail04 dovecot: imap-login: Login: user=<usertest>, method=PLAIN, rip=192.168.10.219, lip=192.168.10.44, mpid=13404, TLS, session=<yRkp4qV/CtfAqArb> Jan 17 12:42:04 mail04 dovecot: imap(usertest): Debug: Loading modules from directory: /usr/lib64/dovecot Jan 17 12:42:04 mail04 dovecot: imap(usertest): Debug: Module loaded: /usr/lib64/dovecot/lib15_notify_plugin.so Jan 17 12:42:04 mail04 dovecot: imap(usertest): Debug: Module loaded: /usr/lib64/dovecot/lib20_listescape_plugin.so Jan 17 12:42:04 mail04 dovecot: imap(usertest): Debug: INBOX: Mailbox opened because: SELECT Jan 17 12:42:04 mail04 dovecot: imap(usertest): Debug: Effective uid=8267, gid=231, home=/home/popusers/usertest Jan 17 12:42:04 mail04 dovecot: imap(usertest): Debug: Namespace inbox: type=private, prefix=, sep=/, inbox=yes, hidden=no, list=yes, subscriptions=yes location=mbox:~/mail:INBOX=/var/spool/mail/usertest:CONTROL=~/mail/contr ol:INDEX=/var/dovecot/usertest/index:LAYOUT=maildir++ Jan 17 12:42:04 mail04 dovecot: imap(usertest): Debug: maildir++: root=/home/popusers/usertest/mail, index=/var/dovecot/usertest/index, indexpvt=, control=/home/popusers/usertest/mail/control, inbox=/var/spool/mail/usertest, alt= Jan 17 12:42:04 mail04 dovecot: imap(usertest): Debug: INBOX/test: Mailbox opened because: SELECT Jan 17 12:42:12 mail04 dovecot: imap-login: Login: user=<usertest>, method=PLAIN, rip=192.168.10.219, lip=192.168.10.44, mpid=13405, TLS, session=<MOKk4qV/C9fAqArb> Jan 17 12:42:12 mail04 dovecot: imap(usertest): Debug: Loading modules from directory: /usr/lib64/dovecot Jan 17 12:42:12 mail04 dovecot: imap(usertest): Debug: Module loaded: /usr/lib64/dovecot/lib15_notify_plugin.so Jan 17 12:42:12 mail04 dovecot: imap(usertest): Debug: Module loaded: /usr/lib64/dovecot/lib20_listescape_plugin.so Jan 17 12:42:12 mail04 dovecot: imap(usertest): Debug: Effective uid=8267, gid=231, home=/home/popusers/usertest Jan 17 12:42:12 mail04 dovecot: imap(usertest): Debug: Namespace inbox: type=private, prefix=, sep=/, inbox=yes, hidden=no, list=yes, subscriptions=yes location=mbox:~/mail:INBOX=/var/spool/mail/usertest:CONTROL=~/mail/contr ol:INDEX=/var/dovecot/usertest/index:LAYOUT=maildir++ Jan 17 12:42:12 mail04 dovecot: imap(usertest): Debug: maildir++: root=/home/popusers/usertest/mail, index=/var/dovecot/usertest/index, indexpvt=, control=/home/popusers/usertest/mail/control, inbox=/var/spool/mail/usertest, alt= Jan 17 12:42:12 mail04 dovecot: imap(usertest): Debug: Drafts: Mailbox opened because: SELECT Jan 17 12:42:14 mail04 dovecot: auth-worker(13400): pam(usertest,192.168.10.219,<fLyv4qV/DNfAqArb>): pam_authenticate() failed: Authentication failure (password mismatch?) Jan 17 12:42:22 mail04 dovecot: auth-worker(13400): pam(usertest,192.168.10.219,<fLyv4qV/DNfAqArb>): pam_authenticate() failed: Authentication failure (password mismatch?) Jan 17 12:42:25 mail04 dovecot: auth-worker(13400): pam(usertest,192.168.10.219,<slYR46V/DdfAqArb>): pam_authenticate() failed: Authentication failure (password mismatch?)

2 1

Dovecot + Weakforced Policy server
by alberto bersol 16 Jan '19

16 Jan '19

Hi, I'm trying to set Weakforced with Dovecot and I cannot log in policy server. This is the config: /root/weakforced/wforce/wforce.conf ----------------------------------- ... webserver("0.0.0.0:8084", "super") ... /etc/dovecot/conf.d/95-policy.conf ---------------------------------- auth_policy_server_url = http://localhost:8084/ #auth_policy_hash_nonce = wforce:super auth_policy_hash_nonce = {SHA256-CRYPT}$5$Ue5UrToV.Bam02bQ$Bi9OJ62Mkgc20L2HnLVmD2OCHyXaKje6Hh7qNjnOkB9 I'm following the instructions of Dovecot's wiki: https://wiki.dovecot.org/Authentication/Policy ... "To generate the hash, you concatenate nonce, login name, nil byte, password and run it through the hash algorithm once. The hash is truncated when truncation is set to non-zero. The hash is truncated by first choosing bits from MSB to byte boundary (rounding up), then right-shifting the remainding bits. hash = H(nonce||user||'\x00'||password) bytes = round8(bits*8) hash = HEX(hash[0:bytes] >> (bytes-bits*8)) And I set hash with password (super) in this way: vm-weakforced:~# doveadm pw -p noncewforce\x00super -s SHA256-CRYPT {SHA256-CRYPT}$5$ZWIX2dnU7NJvGHgC$hYFbeCCaHYZv0yPP80GHygxQMPmI5BjMx2ttRe9zti2 But if I log in Dovecot Server: vm-weakforced:~# doveadm auth login usuario Password: passdb: usuario auth succeeded extra fields: user=usuario userdb extra fields: usuario system_groups_user=usuario uid=1000 gid=1000 home=/home/usuario Answer of Weakforced is always "...authentication failed": WforceWebserver: HTTP Request "/" from 127.0.0.1:39720: Web Authentication failed And Dovecot logs don't show anything else: ... Jan 15 16:50:50 vm-weakforced dovecot: auth: Debug: auth client connected (pid=967) Jan 15 16:50:50 vm-weakforced dovecot: auth: Debug: client in: AUTH#0111#011PLAIN#011service=doveadm#011resp=dXN1YXJpbwB1c3VhcmlvAHVzdWFyaW8= (previous base64 data may contain sensitive data) Jan 15 16:50:50 vm-weakforced dovecot: auth: Debug: policy(usuario): Policy request http://localhost:8084/?command=allow Jan 15 16:50:50 vm-weakforced dovecot: auth: Debug: policy(usuario): Policy server request JSON: {"device_id":"","login":"usuario","protocol":"doveadm","pwhash":"0a00","remote":"","tls":false} Jan 15 16:50:50 vm-weakforced dovecot: auth: Debug: http-client[1]: queue http://localhost:8084: Set request timeout to 2019-01-15 16:50:52.236 (now: 2019-01-15 16:50:50.236) Jan 15 16:50:50 vm-weakforced dovecot: auth: Debug: http-client: peer 127.0.0.1:8084 (shared): Peer created Jan 15 16:50:50 vm-weakforced dovecot: auth: Debug: http-client: peer 127.0.0.1:8084: Peer pool created Jan 15 16:50:50 vm-weakforced dovecot: auth: Debug: http-client[1]: peer 127.0.0.1:8084: Peer created Jan 15 16:50:50 vm-weakforced dovecot: auth: Debug: http-client[1]: queue http://localhost:8084: Setting up connection to 127.0.0.1:8084 (1 requests pending) Jan 15 16:50:50 vm-weakforced dovecot: auth: Debug: http-client[1]: peer 127.0.0.1:8084: Linked queue http://localhost:8084 (1 queues linked) Jan 15 16:50:50 vm-weakforced dovecot: auth: Debug: http-client[1]: queue http://localhost:8084: Started new connection to 127.0.0.1:8084 Jan 15 16:50:50 vm-weakforced dovecot: auth: Debug: http-client[1]: request [Req4: POST http://localhost:8084/?command=allow] Submitted (requests left=1) Jan 15 16:50:50 vm-weakforced dovecot: auth: Debug: http-client[1]: peer 127.0.0.1:8084: Creating 1 new connections to handle requests (already 0 usable, connecting to 0, closing 0) Jan 15 16:50:50 vm-weakforced dovecot: auth: Debug: http-client[1]: peer 127.0.0.1:8084: Making new connection 1 of 1 (0 connections exist, 0 pending) Jan 15 16:50:50 vm-weakforced dovecot: auth: Debug: http-client[1]: conn 127.0.0.1:8084 [2]: (127.0.0.1:8084): Connecting Jan 15 16:50:50 vm-weakforced dovecot: auth: Debug: http-client[1]: conn 127.0.0.1:8084 [2]: (127.0.0.1:8084): Waiting for connect (fd=20) to finish for max 0 msecs Jan 15 16:50:50 vm-weakforced dovecot: auth: Debug: http-client[1]: conn 127.0.0.1:8084 [2]: HTTP connection created (1 parallel connections exist) Jan 15 16:50:50 vm-weakforced dovecot: auth: Debug: http-client[1]: conn 127.0.0.1:8084 [2]: (127.0.0.1:8084): Client connected (fd=20) Jan 15 16:50:50 vm-weakforced dovecot: auth: Debug: http-client[1]: conn 127.0.0.1:8084 [2]: Connected Jan 15 16:50:50 vm-weakforced dovecot: auth: Debug: http-client[1]: conn 127.0.0.1:8084 [2]: Ready for requests Jan 15 16:50:50 vm-weakforced dovecot: auth: Debug: http-client[1]: peer 127.0.0.1:8084: Successfully connected (1 connections exist, 0 pending) Jan 15 16:50:50 vm-weakforced dovecot: auth: Debug: http-client: peer 127.0.0.1:8084: Successfully connected (1 connections exist, 0 pending) Jan 15 16:50:50 vm-weakforced dovecot: auth: Debug: http-client[1]: peer 127.0.0.1:8084: Using 1 idle connections to handle 1 requests (1 total connections ready) Jan 15 16:50:50 vm-weakforced dovecot: auth: Debug: http-client[1]: queue http://localhost:8084: Connection to peer 127.0.0.1:8084 claimed request [Req4: POST http://localhost:8084/?command=allow] Jan 15 16:50:50 vm-weakforced dovecot: auth: Debug: http-client[1]: conn 127.0.0.1:8084 [2]: Claimed request [Req4: POST http://localhost:8084/?command=allow] Jan 15 16:50:50 vm-weakforced dovecot: auth: Debug: http-client[1]: request [Req4: POST http://localhost:8084/?command=allow] Sent header Jan 15 16:50:50 vm-weakforced dovecot: auth: Debug: http-client[1]: request [Req4: POST http://localhost:8084/?command=allow] Send more (sent 95, buffered=303) Jan 15 16:50:50 vm-weakforced dovecot: auth: Debug: http-client[1]: request [Req4: POST http://localhost:8084/?command=allow] Finished sending payload Jan 15 16:50:50 vm-weakforced dovecot: auth: Debug: http-client[1]: peer 127.0.0.1:8084: No more requests to service for this peer (1 connections exist, 0 pending) Jan 15 16:50:50 vm-weakforced dovecot: auth: Debug: http-client[1]: conn 127.0.0.1:8084 [2]: Got 401 response for request [Req4: POST http://localhost:8084/?command=allow] (took 4 ms + 3 ms in queue) Jan 15 16:50:50 vm-weakforced dovecot: auth: Error: policy(usuario): Policy server HTTP error: 401 Unauthorized Jan 15 16:50:50 vm-weakforced dovecot: auth: Debug: http-client[1]: conn 127.0.0.1:8084 [2]: Response payload stream destroyed (0 ms after initial response) Jan 15 16:50:50 vm-weakforced dovecot: auth: Debug: http-client[1]: request [Req4: POST http://localhost:8084/?command=allow] Finished Jan 15 16:50:50 vm-weakforced dovecot: auth: Debug: http-client[1]: queue http://localhost:8084: Dropping request [Req4: POST http://localhost:8084/?command=allow] Jan 15 16:50:50 vm-weakforced dovecot: auth: Debug: http-client[1]: request [Req4: POST http://localhost:8084/?command=allow] Free (requests left=1) Jan 15 16:50:50 vm-weakforced dovecot: auth: Debug: http-client[1]: peer 127.0.0.1:8084: No requests to service for this peer (1 connections exist, 0 pending) Jan 15 16:50:50 vm-weakforced dovecot: auth: Debug: http-client[1]: conn 127.0.0.1:8084 [2]: No more requests queued; going idle (timeout = 10000 msecs) ... Any idea? Thank you so much Regards,

2 4

doveadm neglecting to exit in failure?
by Felipe Gasper 16 Jan '19

16 Jan '19

----- cpssltest(a)cpanelssltest.org [/usr/local/cpanel]# doveadm -v expunge -u cpssltest -- mailbox-guid b8a359119e771b58484a0000a841250d savedbefore 365days; echo $? doveadm(cpssltest): Error: net_connect_unix(/var/run/dovecot/stats-writer) failed: Permission denied 0 ----- ^^ In the above, shouldn’t the “doveadm” command have exited nonzero to indicate a failure to connect? Thanks! -Felipe Gasper Mississauga, Ontario

3 2

MySQL 8.0: Supported?
by Larry Rosenman 16 Jan '19

16 Jan '19

I got a complaint from a FreeBSD user that they couldn't compile dovecot against MySQL 8.0. Is MySQL 8.0 support with 2.3.4? they receive: checking for mysql_init in -lmysqlclient... no configure: error: Can't build with MySQL support: libmysqlclient not found ===> Script "configure" failed unexpectedly. Please report the problem to ler(a)FreeBSD.org [maintainer] and attach the "/wrkdirs/usr/ports/mail/dovecot/work/dovecot-2.3.4/config.log" including the output of the failure of your make command. Also, it might be a good idea to provide an overview of all packages installed on your system (e.g. a /usr/local/sbin/pkg-static info -g -Ea). *** Error code 1 thanks! -- 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

3 11

Import mailbox from different domain
by Sergio Belkin 15 Jan '19

15 Jan '19

Hi folks, Let's say that I have on dovecot the domain example.net and on MS Exchange example.com. I've tried to import a mailbox from MS Exchange to Dovecot but it fails, I've run: dsync -Dv backup -R -u joe.doe imapc: dsync(joe.doe(a)example.net): Error: imapc(192.168.0.2:993): Authentication failed: AUTHENTICATE failed. Is there a way to submit different domains both on MS Exchange and Dovecot and to make everyone be happy :) ? Thanks in advance -- -- Sergio Belkin LPIC-2 Certified - http://www.lpi.org

2 1

mdbox + zlib performing less than just mdbox
by Marc Roos 14 Jan '19

14 Jan '19

I have test environment to determine what would be best settings. I have been told that enabling zlib compression would be good to save iops on storage. But doing the test now, I get worse results. [@test2 ~]# pr -m -t mail04-mdbox-vdb-append-64kb-6.log mail04-mdbox-vdb-append-64kb-8.log |less Logi Sele Appe Logi Sele Appe 100% 100% 100% 100% 100% 100% 1 1 6 1/ 1 1 1 6 1/ 1 0 0 9 1/ 1 0 0 8 1/ 1 0 0 7 1/ 1 0 0 8 1/ 1 0 0 10 1/ 1 0 0 9 1/ 1 0 0 7 1/ 1 0 0 6 1/ 1 0 0 8 1/ 1 0 0 8 1/ 1 0 0 9 1/ 1 0 0 8 1/ 1 0 0 10 1/ 1 0 0 8 1/ 1 0 0 9 1/ 1 0 0 7 1/ 1 0 0 11 1/ 1 0 0 7 1/ 1 29 3 1093 ms/cmd avg 43 2 1232 ms/cmd avg Logi Sele Appe Logi Sele Appe 100% 100% 100% 100% 100% 100% 0 0 10 1/ 1 0 0 9 1/ 1 0 0 9 1/ 1 0 0 7 1/ 1 0 0 10 1/ 1 0 0 7 1/ 1 0 0 9 1/ 1 0 0 6 1/ 1 0 0 11 1/ 1 0 0 8 1/ 1 0 0 9 1/ 1 0 0 7 1/ 1 0 0 8 1/ 1 0 0 6 1/ 1 0 0 11 1/ 1 0 0 7 1/ 1 0 0 9 1/ 1 0 0 5 1/ 1 0 0 9 1/ 1 0 0 9 1/ 1 0 0 1063 ms/cmd avg 0 0 1413 ms/cmd avg Logi Sele Appe Logi Sele Appe 100% 100% 100% 100% 100% 100% 0 0 8 1/ 1 0 0 8 1/ 1 0 0 10 1/ 1 0 0 8 1/ 1 0 0 7 1/ 1 0 0 8 1/ 1 0 0 10 1/ 1 0 0 6 1/ 1 0 0 10 1/ 1 0 0 7 1/ 1 0 0 11 1/ 1 0 0 8 1/ 1 0 0 7 1/ 1 0 0 8 1/ 1 0 0 11 1/ 1 0 0 6 1/ 1 0 0 8 1/ 1 0 0 7 1/ 1 0 0 10 1/ 1 0 0 8 1/ 1 0 0 1077 ms/cmd avg 0 0 1382 ms/cmd avg Logi Sele Appe Logi Sele Appe 100% 100% 100% 100% 100% 100% 0 0 7 1/ 1 0 0 6 1/ 1 0 0 9 1/ 1 0 0 4 1/ 1 0 0 6 1/ 1 0 0 7 1/ 1 0 0 9 1/ 1 0 0 7 1/ 1 0 0 8 1/ 1 0 0 7 1/ 1 0 0 10 1/ 1 0 0 5 1/ 1 0 0 9 1/ 1 0 0 8 1/ 1 0 0 7 1/ 1 0 0 6 1/ 1 0 0 9 1/ 1 0 0 6 1/ 1 0 0 7 1/ 1 0 0 8 1/ 1 0 0 1246 ms/cmd avg 0 0 1524 ms/cmd avg ... ... ... Logi Sele Appe Logi Sele Appe 100% 100% 100% 100% 100% 100% 0 0 8 1/ 1 0 0 5 1/ 1 0 0 6 1/ 1 0 0 4 1/ 1 0 0 6 1/ 1 0 0 4 1/ 1 0 0 7 1/ 1 0 0 4 1/ 1 0 0 5 1/ 1 0 0 5 1/ 1 0 0 5 1/ 1 0 0 4 1/ 1 0 0 6 1/ 1 0 0 4 1/ 1 0 0 7 1/ 1 0 0 5 1/ 1 0 0 6 1/ 1 0 0 4 1/ 1 0 0 7 1/ 1 0 0 5 1/ 1 0 0 1596 ms/cmd avg 0 0 2308 ms/cmd avg Logi Sele Appe Logi Sele Appe 100% 100% 100% 100% 100% 100% 0 0 7 1/ 1 0 0 4 1/ 1 0 0 1583 ms/cmd avg 0 0 4 1/ 1 0 0 2331 ms/cmd avg Totals: Logi Sele Appe Totals: 100% 100% 100% Logi Sele Appe 1 1 1978 100% 100% 100% 1 1 1145

2 2

Re: [FTS Xapian] Beta release
by Tuomi, Aki 14 Jan '19

14 Jan '19

You copied your Makefile.am there. Stephan made you a working version, can you try that? (sorry for dup) Aki -------- Original message --------From: Joan Moreau <jom(a)grosjo.net> Date: 13/01/2019 21:39 (GMT+02:00) To: Stephan Bosch <stephan(a)rename-it.nl> Cc: Aki Tuomi <aki.tuomi(a)open-xchange.com> Subject: Re: [FTS Xapian] Beta release I used the skeleton from Aki : https://github.com/grosjo/fts-xapian However, when I try to act as a visitor, I reach teh follwoing error: # autoreconf -vi autoreconf: Entering directory `.' autoreconf: configure.ac: not using Gettext autoreconf: running: aclocal -I m4 autoreconf: configure.ac: tracing autoreconf: running: libtoolize --copy libtoolize: putting auxiliary files in AC_CONFIG_AUX_DIR, '.'. libtoolize: copying file './ltmain.sh' libtoolize: putting macros in AC_CONFIG_MACRO_DIRS, 'm4'. libtoolize: copying file 'm4/libtool.m4' libtoolize: copying file 'm4/ltoptions.m4' libtoolize: copying file 'm4/ltsugar.m4' libtoolize: copying file 'm4/ltversion.m4' libtoolize: copying file 'm4/lt~obsolete.m4' autoreconf: running: /usr/bin/autoconf autoreconf: running: /usr/bin/autoheader autoreconf: running: automake --add-missing --copy --no-force configure.ac:9: installing './compile' configure.ac:11: installing './config.guess' configure.ac:11: installing './config.sub' configure.ac:7: installing './install-sh' configure.ac:7: installing './missing' src/Makefile.am: installing './depcomp' /usr/share/automake-1.16/am/depend2.am: error: am__fastdepCXX does not appear in AM_CONDITIONAL /usr/share/automake-1.16/am/depend2.am: The usual way to define 'am__fastdepCXX' is to add 'AC_PROG_CXX' /usr/share/automake-1.16/am/depend2.am: to 'configure.ac' and run 'aclocal' and 'autoconf' again src/Makefile.am: error: C++ source seen but 'CXX' is undefined src/Makefile.am: The usual way to define 'CXX' is to add 'AC_PROG_CXX' src/Makefile.am: to 'configure.ac' and run 'autoconf' again. src/Makefile.am:11: warning: variable 'NOPLUGIN_LDFLAGS' is defined but no program or src/Makefile.am:11: library has 'NOPLUGIN' as canonical name (possible typo) autoreconf: automake failed with exit status: 1 On 2019-01-13 20:24, Stephan Bosch wrote: Oh, right, a distribution tarball doesn't include some of the necessary files for your repository like autogen.sh and .gitignore. The attached tarball includes all those and is ready for `git init`. The previous tarball was made with `make distcheck` from this one. Regards, Stephan. Op 13/01/2019 om 20:14 schreef Stephan Bosch: Hi Joan, Op 13/01/2019 om 19:03 schreef Aki Tuomi: Yes, from compiling point of view it is done. Unfortunately what is not done is all the other work involved, such as fixing all the inevitable bugs it has and maintaining it. We do not want, at this moment, take up maintaining and developing yet another FTS plugin as we have plenty of things to do already. I invite you to setup your own repository and provide this plugin from there, being the maintainer of this plugin. We can add a link to your plugin on our FTS page so people can also find it. There are other plugins like this, e.g. https://github.com/st3fan/dovecot-xaps-plugin I turned the code you provided into a separate plugin package. The distribution tarball is attached. Notable changes: - Added example copyright headers and COPYING and AUTHORS files. You should modify those to your preference. - Added README and INSTALL files (in markdown using Pandoc). Those need to be amended with details. - Amended the plugin code to display a debug message with the plugin name and version upon plugin load. I advise you to turn this into a git repository and continue from there. I do not recommend releasing this plugin with the -fpermissive flag and the resulting warning as it is now. But I'm assuming this is still a work in progress, so that is OK. Regards, Stephan. On 13 January 2019 at 19:52 Joan Moreau <jom(a)grosjo.net> wrote: The only point here of this fts-xapian is to get rid of solr (because it is just a nightmare to setup) and squat (because it is considere obsolete). I already sent the changed in configure.ac, makefile.am, etc.. in order to include it in the dovecot, and it compiles properly The only remaining point is to push it in hte git (yes, everything is already done) On 2019-01-13 18:45, Aki Tuomi wrote: On 13 January 2019 at 17:05 Joan Moreau via dovecot <dovecot(a)dovecot.org> wrote: Hi Please find attached the beta release of FTS Xapian, with the objective to replace fts_squat that is being deprecated. Configuration is exactly the same as for fts_squat: plugin { plugin = fts fts_xapian (...) fts = xapian fts_autoindex = yes fts_enforced = yes fts_xapian = partial=2 full=20 This is installed on my production server (>120Gb of mailboxes), and I will observe it during the coming days. I will definitely appreciate that this is added in the core git of docevot, in order to have a versionning of it, to remove squat and let basic users able to avoid Solr alternative as much as possible. Thanks JM Hi! I still recommend you setup a, say, github repository for your plugin. We are not able to currently include your work in dovecot core as it is more work than just pushing the code into the repo. Maybe it can be included in the future. If you want, I can help you in setting up the required configuration scripts and such to make it possible to compile it as plugin. Then anyone can download it and install it for their dovecot, even if dovecot itself has been installed from packages, and also makes it possible for package maintainers to consider including it in distributions. Aki

6 22

What does the mdbox_rotate_size influence?
by Marc Roos 14 Jan '19

14 Jan '19

I wondered why mdbox_rotate_size is 2MB by default. I thought if I increased it to 16MB, maybe there would be less disk io, but I dont see any difference. Furthermore I read in some thread that increasing it from 2MB, could give problems when deleting messages, can someone explain this? Does anyone have this on a cephfs mount, does it make sense to set this to 4MB? [@test2 ~]# pr -m -t mail04-mdbox-vdb-append-64kb-4MB-6.log mail04-mdbox-vdb-append-64kb-16MB-7.log |less Logi Sele Appe Logi Sele Appe 100% 100% 100% 100% 100% 100% 1 1 6 1/ 1 1 1 8 1/ 1 0 0 9 1/ 1 0 0 9 1/ 1 0 0 7 1/ 1 0 0 7 1/ 1 0 0 10 1/ 1 0 0 8 1/ 1 0 0 7 1/ 1 0 0 10 1/ 1 0 0 8 1/ 1 0 0 9 1/ 1 0 0 9 1/ 1 0 0 10 1/ 1 0 0 10 1/ 1 0 0 9 1/ 1 0 0 9 1/ 1 0 0 7 1/ 1 0 0 11 1/ 1 0 0 8 1/ 1 29 3 1093 ms/cmd avg 37 1 1110 ms/cmd avg Logi Sele Appe Logi Sele Appe 100% 100% 100% 100% 100% 100% 0 0 10 1/ 1 0 0 8 1/ 1 0 0 9 1/ 1 0 0 8 1/ 1 0 0 10 1/ 1 0 0 10 1/ 1 0 0 9 1/ 1 0 0 10 1/ 1 0 0 11 1/ 1 0 0 8 1/ 1 0 0 9 1/ 1 0 0 9 1/ 1 0 0 8 1/ 1 0 0 6 1/ 1 0 0 11 1/ 1 0 0 9 1/ 1 0 0 9 1/ 1 0 0 7 1/ 1 0 0 9 1/ 1 0 0 9 1/ 1 0 0 1063 ms/cmd avg 0 0 1202 ms/cmd avg Logi Sele Appe Logi Sele Appe 100% 100% 100% 100% 100% 100% 0 0 8 1/ 1 0 0 8 1/ 1 0 0 10 1/ 1 0 0 10 1/ 1 0 0 7 1/ 1 0 0 11 1/ 1 0 0 10 1/ 1 0 0 10 1/ 1 0 0 10 1/ 1 0 0 10 1/ 1 0 0 11 1/ 1 0 0 9 1/ 1 0 0 7 1/ 1 0 0 8 1/ 1 0 0 11 1/ 1 0 0 9 1/ 1 0 0 8 1/ 1 0 0 10 1/ 1 0 0 10 1/ 1 0 0 7 1/ 1 0 0 1077 ms/cmd avg 0 0 1060 ms/cmd avg Logi Sele Appe Logi Sele Appe 100% 100% 100% 100% 100% 100% 0 0 7 1/ 1 0 0 9 1/ 1 0 0 9 1/ 1 0 0 10 1/ 1 0 0 6 1/ 1 0 0 6 1/ 1 0 0 9 1/ 1 0 0 7 1/ 1 0 0 8 1/ 1 0 0 9 1/ 1 0 0 10 1/ 1 0 0 10 1/ 1 0 0 9 1/ 1 0 0 9 1/ 1 0 0 7 1/ 1 0 0 10 1/ 1 0 0 9 1/ 1 0 0 9 1/ 1 0 0 7 1/ 1 0 0 9 1/ 1 0 0 1246 ms/cmd avg 0 0 1138 ms/cmd avg ... ... ... ... 0 0 8 1/ 1 0 0 9 1/ 1 0 0 6 1/ 1 0 0 8 1/ 1 0 0 6 1/ 1 0 0 7 1/ 1 0 0 7 1/ 1 0 0 8 1/ 1 0 0 5 1/ 1 0 0 9 1/ 1 0 0 5 1/ 1 0 0 10 1/ 1 0 0 6 1/ 1 0 0 11 1/ 1 0 0 7 1/ 1 0 0 9 1/ 1 0 0 6 1/ 1 0 0 9 1/ 1 0 0 7 1/ 1 0 0 10 1/ 1 0 0 1596 ms/cmd avg 0 0 1126 ms/cmd avg Logi Sele Appe Logi Sele Appe 100% 100% 100% 100% 100% 100% 0 0 7 1/ 1 0 0 8 1/ 1 0 0 1583 ms/cmd avg 0 0 1140 ms/cmd avg Totals: Totals: Logi Sele Appe Logi Sele Appe 100% 100% 100% 100% 100% 100% 1 1 1978 1 1 2021

1 0

mdbox import error from read-only filesystem
by hby 14 Jan '19

14 Jan '19

Dovecot version: 2.2.34 doveadm import tries to call open() on the source indexes/logs of mdbox data, but even if it should work as it is just a read-related call, it fails on read-only filesystems. The main use case for read-only filesystem is restoring from backup: the massive deduplicated backup data is exposed using FUSE. For deduplication to work efficiently, we have to backup the whole mail storage and thus the only way to handle the restore to mount the whole data. I would like to ask for some proper solution for this problem. Suggestions: first, the doveadm import should never modify the indexes, and second: the open() calls should respect the read-only filesystem and should fall back to "r" flag when using open. The problem goes further when using SIS (which goes beyond multiple terrabytes). The only workaround currently is to export the whole mdbox data to a writeable storage, and parametrize the import command to use that and the mounted SIS data separately for import...which is just problematic, ugly and error prune. Thank you for the continous work on dovecot, I hope you get this feedback in a good way.

2 2

Freebsd: Fatal error - Support not compiled in for passdb driver 'sql'
by Graham S. Jarvis 14 Jan '19

14 Jan '19

Hello, I have the following fatal error when I uncomment #!include auth-sql.conf.ext in .../conf.d/10-auth.conf dovecot: auth: Fatal: Support not compiled in for passdb driver 'sql' I have installed via 'pkg'. Do I have to install the ports tree to get sql support ? Thanks, -Graham-

4 9

managesieve configuration
by Dominik Menke 14 Jan '19

14 Jan '19

Hello list, I'm trying to get pidgeonhole/managesieve running, and I'm stuck connecting clients to the server (Dovecot 2.2.33.2-1ubuntu4.1 on an Ubnutu 18.04 machine). So far, my config looks like this: protocols = imap lmtp sieve disable_plaintext_auth = yes auth_mechanisms = plain login scram-sha-1 service managesieve-login { inet_listener sieve { port = 4190 ssl = yes } service_count = 1 } service managesieve { process_limit = 256 } protocol sieve { managesieve_max_line_length = 65536 } (please let me know if you need more details). When I connect via openssl s_client -connect $myserver:4190 I get the following prompt (after the usual certificate prompt): "IMPLEMENTATION" "Dovecot (Ubuntu) Pigeonhole" "SIEVE" "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 vacation-seconds imapsieve vnd.dovecot.imapsieve" "NOTIFY" "mailto" "SASL" "PLAIN LOGIN SCRAM-SHA-1" "VERSION" "1.0" OK "Dovecot (Ubuntu) ready." and I can login successfully: AUTHENTICATE "PLAIN" "base64(0x00 $user 0x00 $password)" OK "Logged In." Note how this is different from the troubleshooting guide [1], which suggests gnutls-bin and waiting for the STARTTLS capability before hitting Ctrl-D. This is what I get with gnutls-bin: $ gnutls-cli --starttls --insecure -p 4190 $myserver Processed 0 CA certificate(s). Resolving '$myserver:4190'... Connecting to '$myserverip:4190'... - Simple Client Mode: _ where "_" denotes the waiting prompt. When I hit Ctrl-D here, I get an output similar that of s_client. Now, my problem are the clients: neither Thunderbird's sieve extenstion [2], nor the Ruby ManageSieve class [3], nor Roundcube's managesieve plugin [4] (via Net_Sieve module [5]) are able to communicate with my server. They all wait for a "STARTTLS" line, before they attempt to perform a TLS handshake. This leads me to my question: How do I force Dovecot to print at least a STARTTLS line after a client connects to port 4190? Looking Kind regards, Dominik [1]: https://wiki.dovecot.org/Pigeonhole/ManageSieve/Troubleshooting#Manual_TLS_… [2]: https://github.com/thsmi/sieve [3]: https://www.rubydoc.info/gems/ruby-managesieve/0.4.3/ManageSieve [4]: https://github.com/roundcube/roundcubemail/tree/1.3.8/plugins/managesieve [5]: http://pear.php.net/package/Net_Sieve/docs/1.3.4/Net_Sieve/Net_Sieve.html

4 11