- dovecot - dovecot.org

Proxy IMAP/POP
by Luis Miguel Flores dos Santos 25 Sep '16

25 Sep '16

Hello, I'm try configure dovecot to proxy imap and pop but I can't, follow my configurations: dovecot version = 2.2.10 My configuration: dovecot -n # 2.2.10: /etc/dovecot/dovecot.conf # OS: Linux 3.18.35 x86_64 CentOS Linux release 7.2.1511 (Core) auth_mechanisms = plain login auth_username_format = %n disable_plaintext_auth = no mail_location = maildir:~/Maildir mbox_write_locks = fcntl 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 { driver = pam } passdb { args = /etc/dovecot/dovecot-sql.conf.ext driver = sql } ssl = no ssl_cert = </etc/pki/dovecot/certs/dovecot.pem ssl_key = </etc/pki/dovecot/private/dovecot.pem userdb { driver = passwd } userdb { args = /etc/dovecot/dovecot-sql.conf.ext driver = sql } grep -v '^ *$#.*$\?$' dovecot-sql.conf driver = mysql connect = "host=127.0.0.1 dbname=mail user=root password=PASS" password_query = SELECT NULL AS password, 'Y' as nopassword, host, destuser, 'Y' AS proxy FROM proxy WHERE user = '%u' /var/log/maillog: RHDOVECOT dovecot: auth: Fatal: Unknown database driver 'mysql' **OBS: I followed this wiki: http://wiki2.dovecot.org/PasswordDatabase/ExtraFields/Proxy and installed dovecot-mysql.x86_64, My server is a CentOS Linux release 7.2.1511 (Core) Anyone can help me? Thanks. -------- Atenciosamente, Luis Miguel

2 1

dovecot-2.2.18 / net_listen_unix(...) failed: Value too large for defined data type
by Christophe Bricout 25 Sep '16

25 Sep '16

Dear All, SUMMARY: Dovecot shows an issue when "localstatedir" path is too long The issue exists also with dovecot-2.2.25 CONFIGURATION: The configure options are: ./configure --prefix=${TARGET_DIR} \ --sysconfdir=${TARGET_DIR}/cfg \ --localstatedir=${TARGET_DIR}/var \ --with-ssl=openssl \ --with-sqlite \ --disable-shared RESULTS: When executing dovecot (as root), the followin message appears: Error: service(dict): net_listen_unix(/<user>/localbin/minnowboard-turbot-applications/1.0/linux/x86_64-linux/localbin/dovecot/2.2.18/linux/x86_64-linux/var/run/dovecot/dict) failed: Value too large for defined data type Error: service(config): net_listen_unix(<user>/localbin/minnowboard-turbot-applications/1.0/linux/x86_64-linux/localbin/dovecot/2.2.18/linux/x86_64-linux/var/run/dovecot/config) failed: Value too large for defined data type --- WORKAROUND: The problem is solved by defining shorten localstatedir or using base_dir = /var/run/dovecot. It seems the path lengh causing a such issue. Path Lengh > 127 Available for additional experiments Best Regards

2 1

Re:Self-Signed Certificate issue
by dovecot＠outputservices.com 23 Sep '16

23 Sep '16

Try this: Create a directory and do the following in that directory. Create the file openssl.cnf with the following information: [ req ] default_md = sha2 distinguished_name = req_distinguished_name [ req_distinguished_name ] countryName = US localityName = Boulder organizationName = Your orginizations name here organizationalUnitName = IT Department emailAddress = some email address at your company commonName = "Just a simple statement about the company" [ certauth ] subjectKeyIdentifier = hash authorityKeyIdentifier = keyid:always,issuer:always basicConstraints = CA:true [ client ] basicConstraints = critical,CA:FALSE keyUsage = digitalSignature, keyEncipherment, dataEncipherment extendedKeyUsage = clientAuth Just change the things you need to for you. Then issue the following command. openssl req -config ./openssl.cnf -newkey rsa:2048 -nodes -keyform PEM -keyout dovecot.key -x509 - days 365 -extensions certauth -outform PEM -out dovecot.pem -subj "/C=US/postalCode=00000/ST=state/L=city/streetAddress=some street/O=company name/OU=IT Department/CN=dovecort cert/emailAddress=email(a)yourcompany.com" Just change the C, O, OU, etc for your needs. Then verify the contents via: openssl x509 -noout -in dovecot.pem -subject openssl x509 -noout -in dovecot.pem -issuer openssl x509 -noout -in dovecot.pem -enddate openssl x509 -noout -in dovecot.pem -text This will show what is in the certificate. Now copy the pem & key files to where you want them. Restart dovecot. You may have to change the configuration to use the names just created. Dave Ryan On 09/23/16 11:07, Darryl Baker wrote: > My apologies if this is a repeat but my search of the archive did not turn > it up in the recent past. If this has been covered just point me at the > previous thread, please. > > I am running a small email site which I am moving from uw-imapd and Solaris > to Ubuntu and Dovecot imaps and pop3s. I am trying to use a self-signed > certificate for this site. I am using Thunderbird as the test client. I've > tried both the pre-built snakeoil certificate and building a special one > for dovecot. In /var/log/mail.err I keep getting what I am interpreting as > a missing CA cert. The message is: > > dovecot: imap-login: Error: SSL: Stacked error: error:14094418:SSL > routines:ssl3_read_bytes:tlsv1 alert unknown ca: SSL alert number 48 > > > The certificate was created by: > > openssl req -new -x509 -days 365 -nodes -out /etc/ssl/certs/dovecot.pem > -keyout /etc/ssl/private/dovecot.pem > > > The Dovecot version is 2.2.22 (fe789d2) The Ubuntu version is 16.04 LTS > current patches. > > > *Darryl Baker* > >

1 0

Director keeping IMAP connections alive
by Webert de Souza Lima 23 Sep '16

23 Sep '16

Hello, I have a 2 director - 2 dovecot set up in a cluster. >From time to time I notice high usage of RAM by dovecot process, and analyzing with doveadm who, I see many users with dozens, even hundreds of PIDs. Inspecting those PIDs I see each one of them is an IMAP connection, coming from either director process, and ESTABILISHED. A deeper analysis shows me that there ltos of connections from the same users to BOTH dovecot instances, but as I am using director, this shouldn't happen, right? Ok. The thing is, one of the dovecot instances have only old connections (like 3 days old) and the other dovecot have some old and some newer connections. So, director is redirecting recent connections to the right dovecot, as expected, but it is keeping many of old and unused connections open, consuming resources. output of doveconf -n from dovecot: http://pastebin.com/trMEjeAs output of doveconf -n from director: http://pastebin.com/EUpHYMKY Thanks.

1 1

Broken auth-* sockets.
by ygrishin＠pyramidheadgroup.ca 23 Sep '16

23 Sep '16

Hello. I am migrating my servers to Ubuntu and have been having an issue with Dovecot authenticator service. Exim is set up to use dovecot-auth, anticipating the question whether exim binary was compiled with support of Dovecot authenticator, it was: --- # exim -bV Exim version 4.86_2 #1 built 05-Apr-2016 12:21:41 Copyright (c) University of Cambridge, 1995 - 2015 (c) The Exim Maintainers and contributors in ACKNOWLEDGMENTS file, 2007 - 2015 Berkeley DB: Berkeley DB 5.3.28: (September 9, 2013) Support for: crypteq iconv() IPv6 PAM Perl Expand_dlfunc GnuTLS move_frozen_messages Content_Scanning DKIM Old_Demime DNSSEC PRDR OCSP Lookups (built-in): lsearch wildlsearch nwildlsearch iplsearch cdb dbm dbmjz dbmnz dnsdb dsearch ldap ldapdn ldapm mysql nis nis0 passwd pgsql sqlite Authenticators: cram_md5 cyrus_sasl dovecot plaintext spa tls Routers: accept dnslookup ipliteral iplookup manualroute queryprogram redirect Transports: appendfile/maildir/mailstore/mbx autoreply lmtp pipe smtp Fixed never_users: 0 Size of off_t: 8 Configuration file is /etc/exim4/exim4.conf --- The problem is sockets Dovecot creates are somehow broken. Exim reports something like: --- 2016-09-21 14:45:26 dovecot_plain authenticator failed for *** ([***]) [***]: 435 Unable to authenticate at present: authentication socket connection error 2016-09-21 14:45:26 dovecot_login authenticator failed for *** ([***]) [***]: 435 Unable to authenticate at present: authentication socket connection error --- and I initially thought it was wrong permissions for the socket, triple checked and they are 100% right. More than that, I temporarily chmodded it "rw" for the world as follows: --- # ls -l /var/dovecot/auth-* srw-rw-rw- 1 Debian-exim root 0 Aug 17 21:20 /var/dovecot/auth-client srw------- 1 dovecot root 0 Aug 17 21:20 /var/dovecot/auth-login srw-rw-rw- 1 Debian-exim root 0 Aug 17 21:20 /var/dovecot/auth-master -rw------- 1 root root 32 Aug 15 19:35 /var/dovecot/auth-token-secret.dat srw-rw-rw- 1 dovecot root 0 Aug 17 21:20 /var/dovecot/auth-userdb srw------- 1 dovecot root 0 Aug 17 21:20 /var/dovecot/auth-worker --- and Exim reports the same problem. What makes me think that it's Dovecot's and not Exim's problem? The fact that the socket is really broken, on the server where it's not working: --- # socat - UNIX-CONNECT:/var/dovecot/auth-client 2016/09/22 17:58:27 socat[15192] E connect(5, AF=1 "/var/dovecot/auth-client", 26): Connection refused --- on the server where it is working (version 2.2.13 is installed there), precisely same command: --- # socat - UNIX-CONNECT:/var/dovecot/auth-client VERSION 1 1 MECH PLAIN plaintext MECH LOGIN plaintext MECH CRAM-MD5 dictionary active MECH DIGEST-MD5 dictionary active mutual-auth MECH APOP private dictionary active SPID 535 CUID 880 COOKIE 0311e84ed191fb63334819b1fc3bf2e3 DONE --- with a different result!!! The system: --- uname -a Linux *** 4.4.0-38-generic #57-Ubuntu SMP Tue Sep 6 15:41:41 UTC 2016 i686 i686 i686 GNU/Linux --- Doveconf: --- # dovecot -n # 2.2.22 (fe789d2): /etc/dovecot/dovecot.conf # Pigeonhole version 0.4.13 (7b14904) # OS: Linux 4.4.0-38-generic i686 Ubuntu 16.04.1 LTS ext3 auth_debug = yes auth_debug_passwords = yes auth_mechanisms = plain login cram-md5 digest-md5 apop debug_log_path = /var/log/dovecot-debug.log default_internal_user = dovenull disable_plaintext_auth = no first_valid_uid = 114 log_path = /var/log/dovecot.log login_greeting = IMAP/POP3 server is ready. login_log_format_elements = user=<%u> method=%m rip=%r lip=%l %c mail_location = maildir:/var/mail/exim/%d/%n mail_log_prefix = "%Us(%u): " 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 { driver = pam } passdb { args = /etc/dovecot/dovecot-sql.conf driver = sql } protocols = imap pop3 service auth { unix_listener auth-client { mode = 0660 user = Debian-exim } unix_listener auth-master { mode = 0600 user = Debian-exim } user = root } service imap-login { chroot = login client_limit = 8 inet_listener imap { address = * port = 143 } inet_listener imaps { address = * port = 10143 } process_limit = 8 process_min_avail = 5 service_count = 1 user = dovenull vsz_limit = 64 M } service imap { drop_priv_before_exec = yes process_limit = 64 vsz_limit = 2 G } service pop3-login { chroot = login client_limit = 8 inet_listener pop3 { address = * port = 110 } inet_listener pop3s { address = * port = 10110 } process_limit = 8 process_min_avail = 5 service_count = 1 user = dovenull vsz_limit = 64 M } service pop3 { drop_priv_before_exec = yes process_limit = 64 vsz_limit = 2 G } ssl = no ssl_cert = </etc/dovecot/ssl/server.crt ssl_cipher_list = ALL:!LOW:!SSLv2 ssl_key = </etc/dovecot/ssl/server.key userdb { driver = passwd } userdb { args = /etc/dovecot/dovecot-sql.conf driver = sql } verbose_proctitle = yes protocol lda { auth_socket_path = /var/dovecot/auth-master info_log_path = /var/log/dovecot-lda.log log_path = /var/log/dovecot-lda-errors.log postmaster_address = postmaster@*** } protocol imap { imap_client_workarounds = delay-newmail tb-extra-mailbox-sep } protocol pop3 { pop3_client_workarounds = outlook-no-nuls oe-ns-eoh pop3_uidl_format = %08Xu%08Xv } --- Sounds like a broken Dovecot install, doesn't it? Looks like not the case: --- # apt-get check Reading package lists... Done Building dependency tree Reading state information... Done --- What else to check?

2 2

Logging of custom mail headers
by Francesco Fiore 22 Sep '16

22 Sep '16

Hi, I need to configure Dovecot to log some custom mail headers. I red the documentation of the mail_log plugin but I didn't found which field I've to use as value for mail_log_fields parameter. So, I red the plugin code but in mail-log-plugin.c there're defined only "from" and "subject" fields that match some email header. I found three alternatives: 1. use the mail_filter plugin (spawning a new process, ecc.) 2. coding a new plugin using the notify plugin 3. propose a patch to the mail_log plugin that use a new configuration parameter (es. mail_log_headers) and log the specified mail headers Which is the better solution for you? Thanks in advance Francesco

1 1

Sieve vacation won't send second reply after timeout interval.
by David Williams 21 Sep '16

21 Sep '16

Hi I solved this by updating to Dovecot 2.2.24 David

1 0

dsync-server: Configure lock-file location?
by Udo Waechter 21 Sep '16

21 Sep '16

Good day everyone, I have a situation where my mail-folder structure (mdbox) ist like this: My users have the following data: $ doveadm user XYZ(a)xx.com field value home /srv/mail/ mail mdbox:foo/XYZ@xx.com/ I also do replication between 2 nodes. Now, I sometimes (when a lot of replication is happening I get the following errors: dovecot: dsync-local(XYZ(a)xx.com): Error: Couldn't lock /srv/mail//.dovecot-sync.lock: Timed out after 60 seconds This of course not only for XYZ(a)xx.com It seems to me, that my mailbox structure should rather be: $ doveadm user XYZ(a)xx.com field value home /srv/mail/foo mail mdbox:XYZ@xx.com/ in order to get rid of these messages? Unfortunatly I cannot change that. I've searched around and took a look into the code of dsync-server, unfortunatly the path to the lockfile is not configurable. Is there a way to somehow configure the lock-file location for dsync-server? Thanks very much, udo.

1 0

ldap sasl bind and auth_bind
by Matwey V. Kornilov 20 Sep '16

20 Sep '16

Hello, I am using # dovecot --version 2.2.18 # dovecot -n # 2.2.18: /etc/dovecot/dovecot.conf # Pigeonhole version 0.4.8 (0c4ae064f307+) doveconf: Warning: NOTE: You can get a new clean config file with: doveconf -n > dovecot-new.conf doveconf: Warning: Obsolete setting in /etc/dovecot/dovecot.conf:24: 'imaps' protocol can no longer be specified (use protocols=imap). to disable non-ssl imap, use service imap-login { inet_listener imap { port=0 } } doveconf: Warning: NOTE: You can get a new clean config file with: doveconf -n > dovecot-new.conf doveconf: Warning: Obsolete setting in /etc/dovecot/dovecot.conf:24: 'imaps' protocol can no longer be specified (use protocols=imap). to disable non-ssl imap, use service imap-login { inet_listener imap { port=0 } } # OS: Linux 4.1.27-27-default x86_64 openSUSE 42.1 (x86_64) first_valid_uid = 1 mail_location = maildir:~/Maildir 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 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 = /etc/dovecot/dovecot-ldap.conf.ext driver = ldap } plugin { sieve = file:~/sieve;active=~/.dovecot.sieve } protocols = lmtp imap service imap-login { inet_listener imap { port = 0 } } ssl = required ssl_ca = /etc/pki/trust/anchors/rootCA.pem ssl_cert = </etc/openldap/openldap.crt ssl_dh_parameters_length = 2048 ssl_key = </etc/openldap/openldap.key ssl_options = no_compression ssl_prefer_server_ciphers = yes userdb { args = /etc/dovecot/dovecot-ldap.conf.ext driver = ldap override_fields = uid=vmail gid=vmail home=/var/spool/mail/%d/%n } I use LDAP for user and passwd databases as the following: uris = ldapi:/// sasl_bind = yes sasl_mech = EXTERNAL auth_bind = yes And I found that only first authentication after dovecot restart is successful, the others always fail with temp. The reason is that dovecot rebinds to anonymous bind after succesful auth bind instead of rebinding to external sasl bind.

1 1

Sieve vacation won't send second reply after timeout interval.
by David Williams 20 Sep '16

20 Sep '16

Hi there I'm having problems getting sieve to send a second vacation response. For testing I've set sieve_vacation_min_period = 500s and the seconds option in the script is 600. I send the first test message and get a reply fine I then wait about 12 minutes send a second message and get no reply. In the log I get "discarded duplicate response". I've restarted dovecot and removed the .dovecot.lda-dupes file before running the last test. I'm using LMTP for delivery to Dovecot. The sieve script is require ["vacation-seconds"]; # rule:[Vacation] if true { vacation :seconds 600 :addresses "username(a)mydomain.com" :subject "vacation" "test"; } and doveconf -n is # 2.2.19: /etc/dovecot/dovecot.conf # Pigeonhole version 0.4.9 (357ac0a0e68b+) # OS: Linux 3.18.12-gentoo x86_64 Gentoo Base System release 2.2 ext4 auth_username_format = %Ln disable_plaintext_auth = no imap_capability = +XLIST mail_location = maildir:/srv/mail/%n/Maildir 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 vacation-seconds imapflags notify namespace inbox { inbox = yes location = mailbox Drafts { auto = subscribe special_use = \Drafts } mailbox "Sent Items" { auto = subscribe special_use = \Sent } mailbox Spam { auto = subscribe special_use = \Junk } mailbox Trash { auto = subscribe special_use = \Trash } prefix = } passdb { args = * driver = pam } plugin { sieve = file:~/sieve;active=~/.dovecot.sieve sieve_before = /var/lib/dovecot/sieve/default.sieve sieve_default = /var/lib/dovecot/sieve/default.sieve sieve_extensions = +notify +imapflags +vacation-seconds sieve_vacation_default_period = 1d sieve_vacation_min_period = 500s sieve_vacation_use_original_recipient = yes } postmaster_address = postmaster(a)mydomain.com protocols = imap lmtp sieve service auth { unix_listener auth-userdb { group = mode = 0777 user = } } service lmtp { inet_listener lmtp { address = 127.0.0.1 port = 10024 } } service managesieve-login { inet_listener sieve { port = 4190 } } ssl_cert = </etc/ssl/dovecot/server.pem ssl_key = </etc/ssl/dovecot/server.key submission_host = localhost userdb { driver = passwd override_fields = home=/srv/mail/%n } protocol lmtp { mail_plugins = sieve } protocol lda { mail_plugins = sieve } I've changed the identifying info to stop any spammers. Any ideas, suggestions or just another pair of eyes telling me I've done something stupid would be much appreciated. Many thanks David

1 0

[Dovecot] Plugins: virtuals vs acls
by Leho Kraav 20 Sep '16

20 Sep '16

Hi all dovecot-virtual: * all when dovecot-acl files restrict some subset of * for a user, does dovecot respect these ACLs when collecting messages for virtual folder? I'd like a confirmation about what I should be seeing when I start implementing this setup.

2 3

Dovecot and imapproxy
by Grant 20 Sep '16

20 Sep '16

imapproxy sped things up a lot for me when I was using courier. I switched to dovecot a while back and kept using imapproxy. Lately I've been noticing weird TCP Queuing spikes in my munin graphs and discontinuing my use of imapproxy seems to have smoothed them out completely and I haven't noticed a slowdown in webmail. Is imapproxy generally not necessary with dovecot? - Grant

2 1

Re: Dovecot 2.2.25 fails on SSL
by Joseph Tam 19 Sep '16

19 Sep '16

"Andreas M. Kirchwitz" <amk(a)spamfence.net> writes: >> OK, the origin of your problem becomes clearer. You can hardcode these >> paths into the executables by doing something like >> >> env CFLAGS='-I/my'ssl/include' \ >> LDFLAGS='-L/your/ssl/lib -Wl,-rpath,/my/ssl/lib' \ >> configure ... > > Based on your mail I've tried CFLAGS/LDFLAGS again, and > now Dovecot didn't even compile any longer. I don't use the same OS as you, but what errors dis you get? Joseph Tam <jtam.home(a)gmail.com>

1 0

Panic: file auth-request.c
by Chris Wik 19 Sep '16

19 Sep '16

Hello Dovecot list, We've been running a really old CentOS 5 server with the stock dovecot from yum (1.0.7) for years and years with absolutely no problems. If it ain't broke, don't fix it, or something like that. Well it finally broke, but only due to the server no longer being able to handle the load of the increasing user base (many thousands now, with hundreds of concurrent IMAP connections any any given time) So we upgraded to a new CentOS 7 server with SSD RAID, fast CPUs and tons of RAM. No more load problems. We compiled the latest dovecot from source (as the version from CentOS yum repo is already quite old, figure we might as well run the latest version since we were upgrading anyway). Thanks to excellent documentation on dovecot.org and fairly thorough testing, the upgrade was quite smooth. We kept all the message UUIDs intact and tried to match the supported authentication methods etc to the old setup, and we didn't have any problems with clients re-downloading or re-syncing mail. We do however have one problem, which prompted me to join this list. It is the same problem as described in this thread from last month: http://dovecot.org/list/dovecot/2016-July/104899.html Here's the excerpt from our maillog: Sep 17 19:34:57 mail dovecot: auth: Panic: file auth-request.c: line 1049 (auth_request_lookup_credentials): assertion failed: (request->credentials_scheme == scheme) Sep 17 19:34:57 mail dovecot: auth: Error: Raw backtrace: /usr/local/lib/dovecot/libdovecot.so.0(+0x89470) [0x7fa9cb8af470] -> /usr/local/lib/dovecot/libdovecot.so.0(+0x8954e) [0x7fa9cb8af54e] -> /usr/local/lib/dovecot/libdovecot.so.0(i_fatal+0) [0x7fa9cb851f75] -> dovecot/auth() [0x4165bc] -> dovecot/auth() [0x4221fb] -> dovecot/auth() [0x41620b] -> dovecot/auth(auth_request_lookup_credentials_callback+0x58) [0x4162f8] -> dovecot/auth(passdb_handle_credentials+0x6a) [0x4254ba] -> dovecot/auth() [0x425b62] -> dovecot/auth() [0x41c1f8] -> /usr/local/lib/dovecot/libdovecot.so.0(io_loop_call_io+0x4c) [0x7fa9cb8c207c] -> /usr/local/lib/dovecot/libdovecot.so.0(io_loop_handler_run_internal+0xd7) [0x7fa9cb8c3377] -> /usr/local/lib/dovecot/libdovecot.so.0(io_loop_handler_run+0x25) [0x7fa9cb8c2105] -> /usr/local/lib/dovecot/libdovecot.so.0(io_loop_run+0x38) [0x7fa9cb8c22b8] -> /usr/local/lib/dovecot/libdovecot.so.0(master_service_run+0x13) [0x7fa9cb857f33] -> dovecot/auth(main+0x2eb) [0x40ccdb] -> /lib64/libc.so.6(__libc_start_main+0xf5) [0x7fa9c9dc2b15] -> dovecot/auth() [0x40cf15] On the client side, it manifests as an authentication failure, and the user is prompted to re-enter their password. The reports we've had are all from users who have their passwords saved in a local password manager, so the client is definitely sending the correct password. It's not related to a particular mail client. It is also definitely not related to the particular user or password, as the user will authenticate many times successfully and then (seemingly) randomly be hit by this bug and prompted to re-enter their password. We enabled verbose logging and even logging of passwords for failed authentication attempts in an attempt to find a pattern, but so far we have not found one. Similar to the original poster in the above thread, we are using a MySQL backend, and CentOS 7 on x86_64 It happens quite frequently: in the past 6 days it happened 49175 times, according to a grep of the maillog. In the same period there were 294167 successful IMAP logins and 160322 POP3 logins. For now we have downgraded to 2.2.4 and so far have not seen the crash recorded in the maillog. What can we do to help track down and fix this bug? # dovecot -n # 2.2.24 (a82c823): /usr/local/etc/dovecot/dovecot.conf # OS: Linux 3.10.0-327.28.3.el7.x86_64 x86_64 CentOS Linux release 7.2.1511 (Core) ext4 auth_debug = yes auth_debug_passwords = yes auth_mechanisms = plain login digest-md5 cram-md5 ntlm rpa apop auth_verbose = yes auth_verbose_passwords = plain debug_log_path = /var/log/dovecot-debug.log default_client_limit = 5000 default_process_limit = 1000 disable_plaintext_auth = no first_valid_uid = 89 mail_debug = yes mail_fsync = never mail_gid = 89 mail_location = maildir:/var/virtual/%d/%n mail_uid = 89 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 = /usr/local/etc/dovecot/dovecot-sql.conf.ext driver = sql } pop3_client_workarounds = outlook-no-nuls oe-ns-eoh service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0660 user = postfix } } ssl_ca = <*** ssl_cert = <*** ssl_key = <*** userdb { args = /usr/local/etc/dovecot/dovecot-sql.conf.ext driver = sql } verbose_ssl = yes protocol lmtp { mail_fsync = optimized } protocol lda { mail_fsync = optimized } protocol imap { mail_max_userip_connections = 50 } protocol pop3 { mail_max_userip_connections = 20 } -- Chris Wik Anu Internet Services www.anu.net | www.cwik.ch

3 5

dovecot --hostdomain
by dovecot＠nspace.de 19 Sep '16

19 Sep '16

Hi, I'm currently debugging replication issues and I found that both servers answer to a "dovecot --hostdomain" simply with localhost From what I've read, this can lead to problems. Where do I configure the dovecot hostdomain name? The machine itself has a valid name in /etc/hostname Thanks, Thomas

2 1

Re: Dovecot 2.2.25 fails on SSL
by Andreas M. Kirchwitz 19 Sep '16

19 Sep '16

Joseph Tam <jtam.home(a)gmail.com> wrote: >> For every program I compile myself, I link it against my custom >> OpenSSL library (always newest version; distributions usually tend >> to stick with a specific version and only apply security fixes). > > OK, the origin of your problem becomes clearer. You can hardcode these > paths into the executables by doing something like > > env CFLAGS='-I/my'ssl/include' \ > LDFLAGS='-L/your/ssl/lib -Wl,-rpath,/my/ssl/lib' \ > configure ... Yes, exactly, that's my usual approach. I've used this as well for building other software with custom libraries. Unfortunately, I remember CFLAGS/LDFLAGS didn't play well with Dovecot, so I used SSL_CFLAGS/SSL_LIBS as suggested by the documentation and that worked well. > I use this myself (except the -Wl part since these libs are > symlinked to my shared library path). I think "-R/my/ssl/lib" > might also be synonymous with -Wl,... Based on your mail I've tried CFLAGS/LDFLAGS again, and now Dovecot didn't even compile any longer. I was close to giving up. But obviously, I didn't ... :-) After some investigation I found the non-default linker option "-Wl,--as-needed" as problem which is enabled by Dovecot for unknown reasons. Finally, this call to "configure" generates proper Makefile files to build Dovecot with a custom SSL library: env CPPFLAGS="-I/usr/local/ssl/include" LDFLAGS="-L/usr/local/ssl/lib -Wl,-R/usr/local/ssl/lib" LIBS="-Wl,--no-as-needed -lcrypto -lssl" SSL_CFLAGS="-I/usr/local/ssl/include" SSL_LIBS="-L/usr/local/ssl/lib -Wl,-R/usr/local/ssl/lib -Wl,--no-as-needed -lcrypto -lssl" ./configure --prefix=/usr/local/dovecot --with-ssl=openssl (chances are that SSL_CFLAGS/SSL_LIBS could be removed completely but it won't hurt) I've read the section in the "ld" manual but still don't understand why Dovecot enables --as-needed (never seen that before with other software) and why it's such a big problem. But I'm no expert here. > I don't have that problem -- I use configure to tell dovecot where to find > my self-compiled openssl, and the resulting executables load from where I > want. Thanks for pointing me at the proper direction again. Now Dovecot 2.2.25 compiles for me with a custom SSL. I understand that this issue might not have a high priority but maybe one of the developers could check if "--as-needed" is really needed (as it confuses people who try to use custom libraries) and what's the deeper meaning of SSL_CFLAGS/SSL_LIBS. My system is a regular CentOS 6 (latest sub-release with all patches), nothing special except for a custom SSL installation. Greetings, Andreas

1 0

BUG - DELETE Public/Folder not working with Thunderbird
by Leander Schäfer 18 Sep '16

18 Sep '16

Hi, Unfortunately it looks like the parameter: "imap_client_workarounds = tb-extra-mailbox-sep" does not work. Neither inside nor outside "protocol imap {}" configuration section. ACLs are set correctly. Manual "DELETE Public/Test" via telnet is working as expected. Is this a known bug? See: - https://help.ubuntu.com/community/Dovecot#Thunderbird - http://wiki.dovecot.org/Clients#Thunderbird # 2.2.25 (7be1766): /usr/local/etc/dovecot/dovecot.conf # Pigeonhole version 0.4.15 (97b3da0) # OS: FreeBSD 10.3-RELEASE amd64 [...] imap_client_workarounds = delay-newmail tb-extra-mailbox-sep tb-lsub-flags [...] namespace { list = children location = maildir:%%h/maildir:INDEX=~/maildir/Shared/%%u:CONTROL=~/maildir/Shared/%%u:INDEXPVT=~/maildir/Shared prefix = Shared/%%u/ separator = / subscriptions = no type = shared } namespace { hidden = no list = children location = maildir:~/../Public:LAYOUT=fs:INDEX=~/../Public:CONTROL=~/../Public:INDEXPVT=~/maildir/Public prefix = Public/ separator = / subscriptions = no type = public } [...] Best regards Leander Schäfer

2 4

how to mass delete after a hacked mail?
by voytek＠sbt.net.au 17 Sep '16

17 Sep '16

I had a hacked user account resulting in several thousand bounces back to that email inbox, account now corrected, but, how can I mass delete bounces with say subject like: "Undelivered Mail Returned to Sender" (by from ? ""Mail Delivery System" <MAILER-DAEMON(a)emu.sbt.net.au>") or what other ways to clean the mess ? thanks, V

4 3

converting maildir to mailbox
by Anton Yuzhaninov 16 Sep '16

16 Sep '16

Hi all! There is a script to convert maildir to mailbox in wiki: http://wiki.dovecot.org/Migration/MailFormat but it doesn't convert any message flags (seen e.t.c.). I wrote a script, which converts most flags and labels: https://bitbucket.org/citrin/scripts/src/tip/dovecot-maildir2mbox.pl It doesn't convert recent flag and UIDs though, because it was not necessary in my case. Do you think link to the script should be added to dovecot wiki? -- WBR, Anton Yuzhaninov P. S. My use case was: get maildir from other server, convert to mbox, compress (gzip -9) and add to my mailbox as read-only archive.

3 2

Crash with latest -git as of 2.2.devel (c06590c)
by Reuben Farrelly 16 Sep '16

16 Sep '16

Hi, Looks like something has been committed to master-2.2 in the last week which is causing crashes as soon as the remote user logs in: Sep 17 01:11:19 thunderstorm.reub.net dovecot: dsync-server(reuben): Error: read(lightning.reub.net) failed: EOF (last sent=mailbox_state, last recv=mail (EOL)) Sep 17 01:11:31 thunderstorm.reub.net dovecot: imap(reuben): Panic: file fts-api.c: line 128 (fts_backend_set_cur_mailbox): assertion failed: (ctx->cur_box != NULL) Sep 17 01:11:31 thunderstorm.reub.net dovecot: imap(reuben): Error: Raw backtrace: /usr/lib64/dovecot/libdovecot.so.0(+0xb7f9f) [0x7f4cd5b4cf9f] -> /usr/lib64/dovecot/libdovecot.so.0(+0xb9515) [0x7f4cd5b4e515] -> /usr/lib64/dovecot/libdovecot.so.0(i_fatal+0) [0x7f4cd5b4d332] -> /usr/lib64/dovecot/lib20_fts_plugin.so(+0x96b4) [0x7f4cd50b86b4] -> /usr/lib64/dovecot/lib20_fts_plugin.so(fts_backend_update_deinit+0x45) [0x7f4cd50b872b] -> /usr/lib64/dovecot/lib20_fts_plugin.so(+0x142ed) [0x7f4cd50c32ed] -> /usr/lib64/dovecot/libdovecot-storage.so.0(maildir_sync_index+0x98e) [0x7f4cd5e4eed7] -> /usr/lib64/dovecot/libdovecot-storage.so.0(+0x5f209) [0x7f4cd5e51209] -> /usr/lib64/dovecot/libdovecot-storage.so.0(+0x5f497) [0x7f4cd5e51497] -> /usr/lib64/dovecot/libdovecot-storage.so.0(maildir_storage_sync_init+0xb2) [0x7f4cd5e517de] -> /usr/lib64/dovecot/libdovecot-storage.so.0(mailbox_sync_init+0x6d) [0x7f4cd5e2cc41] -> dovecot/imap(imap_sync_init+0xc7) [0x42e408] -> dovecot/imap() [0x42f96b] -> dovecot/imap() [0x42febc] -> dovecot/imap(cmd_sync_delayed+0x34) [0x42fef2] -> dovecot/imap(client_handle_input+0x138) [0x41e9d1] -> dovecot/imap(client_input+0xf5) [0x41eb02] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_call_io+0xcd) [0x7f4cd5b6b054] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_handler_run_internal+0x209) [0x7f4cd5b6d5c1] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_handler_run+0x24) [0x7f4cd5b6b1fd] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_run+0xaf) [0x7f4cd5b6b149] -> /usr/lib64/dovecot/libdovecot.so.0(master_service_run+0x2e) [0x7f4cd5aca603] -> dovecot/imap(main+0x300) [0x431169] -> /lib64/libc.so.6(__libc_start_main+0xf0) [0x7f4cd571c710] -> dovecot/imap(_start+0x29) [0x40c7b9] Sep 17 01:11:31 thunderstorm.reub.net dovecot: imap(reuben): Fatal: master: service(imap): child 1740 killed with signal 6 (core dumped) thunderstorm reuben # file core core: ELF 64-bit LSB core file x86-64, version 1 (SYSV), SVR4-style, from 'dovecot/imap postlogin', real uid: 0, effective uid: 0, real gid: 0, effective gid: 0, execfn: '/usr/libexec/dovecot/imap', platform: 'x86_64' thunderstorm reuben # gdb /usr/libexec/dovecot/imap core GNU gdb (Gentoo 7.11.1 vanilla) 7.11.1 Copyright (C) 2016 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: <https://bugs.gentoo.org/>. 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"... Reading symbols from /usr/libexec/dovecot/imap...done. [New LWP 1740] warning: Could not load shared library symbols for linux-vdso.so.1. Do you need "set solib-search-path" or "set sysroot"? [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib64/libthread_db.so.1". Core was generated by `dovecot/imap postlogin'. Program terminated with signal SIGABRT, Aborted. #0 0x00007f4cd572f1f8 in raise () from /lib64/libc.so.6 (gdb) bt full #0 0x00007f4cd572f1f8 in raise () from /lib64/libc.so.6 No symbol table info available. #1 0x00007f4cd573064a in abort () from /lib64/libc.so.6 No symbol table info available. #2 0x00007f4cd5b4cfee in default_fatal_finish (type=LOG_TYPE_PANIC, status=0) at failures.c:201 backtrace = 0x27446a0 "/usr/lib64/dovecot/libdovecot.so.0(+0xb7f9f) [0x7f4cd5b4cf9f] -> /usr/lib64/dovecot/libdovecot.so.0(+0xb9515) [0x7f4cd5b4e515] -> /usr/lib64/dovecot/libdovecot.so.0(i_fatal+0) [0x7f4cd5b4d332] -> /usr"... #3 0x00007f4cd5b4e515 in i_internal_fatal_handler (ctx=0x7fff509f3750, format=0x7f4cd50cb000 "file %s: line %d (%s): assertion failed: (%s)", args=0x7fff509f3770) at failures.c:670 status = 0 #4 0x00007f4cd5b4d332 in i_panic (format=0x7f4cd50cb000 "file %s: line %d (%s): assertion failed: (%s)") at failures.c:275 ctx = {type = LOG_TYPE_PANIC, exit_status = 0, timestamp = 0x0, timestamp_usecs = 0} args = <error reading variable args (Attempt to dereference a generic pointer.)> #5 0x00007f4cd50b86b4 in fts_backend_set_cur_mailbox (ctx=0x26f6e70) at fts-api.c:128 __FUNCTION__ = "fts_backend_set_cur_mailbox" #6 0x00007f4cd50b872b in fts_backend_update_deinit (_ctx=0x268b3b8) at fts-api.c:143 ctx = 0x26f6e70 backend = 0x26825e0 ret = 32588 #7 0x00007f4cd50c32ed in fts_mailbox_sync_notify (box=0x268aaa0, uid=0, sync_type=(unknown: 0)) at fts-storage.c:665 flist = 0x2683000 fbox = 0x268b258 #8 0x00007f4cd5e4eed7 in maildir_sync_index (ctx=0x268eb40, partial=true) at maildir-sync-index.c:649 mbox = 0x268aaa0 view = 0x26f4f30 view2 = 0x0 iter = 0x0 trans = 0x270ef20 hdr = 0x268b8b0 empty_hdr = {major_version = 176 '\260', minor_version = 57 '9', base_header_size = 20639, header_size = 32767, record_size = 3588796538, compat_flags = 76 'L', unused = "\177\000", indexid = 1352612272, flags = 32512, uid_validity = 40955680, next_uid = 0, messages_count = 40849200, unused_old_recent_messages_count = 0, seen_messages_count = 40857728, deleted_messages_count = 0, first_recent_uid = 136, first_unseen_uid_lowwater = 0, first_deleted_uid_lowwater = 40428608, log_file_seq = 0, log_file_tail_offset = 1352612384, log_file_head_offset = 32767, unused_old_sync_size = 139967982787820, unused_old_sync_stamp = 40913568, day_stamp = 0, day_first_uid = { 41174496, 0, 41174440, 0, 40413856, 0, 1352612384, 32767}} rec = 0x26d7188 seq = 0 seq2 = 0 uid = 1043 prev_uid = 1043 uflags = (MAILDIR_UIDLIST_REC_FLAG_MOVED | MAILDIR_UIDLIST_REC_FLAG_RECENT | MAILDIR_UIDLIST_REC_FLAG_NONSYNCED) filename = 0x2711a00 "1474037293.M664229P7078.thunderstorm,S=18760,W=19334:2,Sd" uid_validity = 1466133870 next_uid = 3585376580 hdr_next_uid = 1044 first_recent_uid = 1044 first_uid = 1 changes = 1 ret = 0 time_before_sync = 1474038691 expunged_guid_128 = "\247\332=\207\337[1\a\367\217\025\307\024|-Y" private_flags_mask = 0 expunged = true full_rescan = false __FUNCTION__ = "maildir_sync_index" #9 0x00007f4cd5e51209 in maildir_sync_context (ctx=0x27445a8, forced=false, find_uid=0x0, lost_files_r=0x7fff509f3afa) at maildir-sync.c:951 sync_flags = MAILDIR_UIDLIST_SYNC_PARTIAL flags = (MAILDIR_UIDLIST_REC_FLAG_NEW_DIR | MAILDIR_UIDLIST_REC_FLAG_MOVED | MAILDIR_UIDLIST_REC_FLAG_RECENT | MAILDIR_UIDLIST_REC_FLAG_NONSYNCED | MAILDIR_UIDLIST_REC_FLAG_RACING | unknown: 32736) new_changed = false cur_changed = false lock_failure = false fname = 0x268aaa0 "" why = (unknown: 0) ret = 1 __FUNCTION__ = "maildir_sync_context" #10 0x00007f4cd5e51497 in maildir_sync_run (mbox=0x268aaa0, flags=MAILBOX_SYNC_FLAG_EXPUNGE, force_resync=false, uid=0x0, lost_files_r=0x7fff509f3afa) at maildir-sync.c:1024 _data_stack_cur_id = 5 ctx = 0x27445a8 retry = false lost_files = false ret = 0 #11 0x00007f4cd5e517de in maildir_storage_sync_init (box=0x268aaa0, flags=MAILBOX_SYNC_FLAG_EXPUNGE) at maildir-sync.c:1097 mbox = 0x268aaa0 lost_files = false force_resync = false ret = 0 __FUNCTION__ = "maildir_storage_sync_init" #12 0x00007f4cd5e2cc41 in mailbox_sync_init (box=0x268aaa0, flags=MAILBOX_SYNC_FLAG_EXPUNGE) at mail-storage.c:1728 _data_stack_cur_id = 4 ctx = 0x0 #13 0x000000000042e408 in imap_sync_init (client=0x2687680, box=0x268aaa0, imap_flags=IMAP_SYNC_FLAG_SAFE, flags=MAILBOX_SYNC_FLAG_EXPUNGE) at imap-sync.c:229 ctx = 0x268b770 __FUNCTION__ = "imap_sync_init" #14 0x000000000042f96b in cmd_sync_client (sync_cmd=0x2688280) at imap-sync.c:737 client = 0x2687680 ctx = 0x2 flags = MAILBOX_SYNC_FLAG_EXPUNGE imap_flags = IMAP_SYNC_FLAG_SAFE no_newmail = false #15 0x000000000042febc in cmd_sync_delayed_real (client=0x2687680) at imap-sync.c:858 cmd = 0x2688280 first_expunge = 0x2688280 first_nonexpunge = 0x0 __FUNCTION__ = "cmd_sync_delayed_real" #16 0x000000000042fef2 in cmd_sync_delayed (client=0x2687680) at imap-sync.c:866 _data_stack_cur_id = 3 ret = 80 #17 0x000000000041e9d1 in client_handle_input (client=0x2687680) at imap-client.c:1118 ret = false remove_io = false handled_commands = true __FUNCTION__ = "client_handle_input" #18 0x000000000041eb02 in client_input (client=0x2687680) at imap-client.c:1149 cmd = 0x7fff509f3cc0 output = 0x26880a0 bytes = 28 __FUNCTION__ = "client_input" #19 0x00007f4cd5b6b054 in io_loop_call_io (io=0x268ca30) at ioloop.c:564 ioloop = 0x264f760 t_id = 2 __FUNCTION__ = "io_loop_call_io" #20 0x00007f4cd5b6d5c1 in io_loop_handler_run_internal (ioloop=0x264f760) at ioloop-epoll.c:220 ctx = 0x2651270 events = 0x26520a0 event = 0x26520a0 list = 0x26881d0 io = 0x268ca30 tv = {tv_sec = 256, tv_usec = 707889} events_count = 5 msecs = 256708 ret = 1 i = 0 j = 0 call = true __FUNCTION__ = "io_loop_handler_run_internal" #21 0x00007f4cd5b6b1fd in io_loop_handler_run (ioloop=0x264f760) at ioloop.c:612 No locals. #22 0x00007f4cd5b6b149 in io_loop_run (ioloop=0x264f760) at ioloop.c:588 __FUNCTION__ = "io_loop_run" #23 0x00007f4cd5aca603 in master_service_run (service=0x264f600, callback=0x430dd6 <client_connected>) at master-service.c:641 No locals. #24 0x0000000000431169 in main (argc=2, argv=0x264f390) at main.c:460 set_roots = {0x43bbe0 <imap_setting_parser_info>, 0x646340 <lda_setting_parser_info>, 0x0} login_set = {auth_socket_path = 0x2647048 "\001", postlogin_socket_path = 0x2647078 "z`\005", postlogin_timeout_secs = 60, callback = 0x430af0 <login_client_connected>, failure_callback = 0x430d41 <login_client_failed>, request_auth_token = 1} service_flags = MASTER_SERVICE_FLAG_KEEP_CONFIG_OPEN storage_service_flags = (MAIL_STORAGE_SERVICE_FLAG_DISALLOW_ROOT | MAIL_STORAGE_SERVICE_FLAG_AUTOEXPUNGE) username = 0x0 auth_socket_path = 0x43cd85 "auth-master" c = -1 (gdb) Reuben

1 0

Dovecot lmtp support for SMTPUTF8
by Igor Colombi 16 Sep '16

16 Sep '16

Hello, I'm using dovecot lmtp with Postfix. I'm enabling SMTPUTF8 (EAI), but when Postfix (v 3.1.2) tries to deliver the message to dovecot-lmtp it receive this error: status=bounced (SMTPUTF8 is required, but was not offered by host dlvmx.espsrv.net[private/dovecot-lmtp] I'm not sure if Dovecot lda and lmpt support EAI and how can I enable it. I've just found and old thread: http://www.dovecot.org/list/dovecot/2013-January/087756.html Thanks for your help. -- Igor Colombi

1 0

pop3 deleted count
by Dave 16 Sep '16

16 Sep '16

On pop3 logout, we're seeing log lines where the deleted count is blank (using default pop3_logout_format), so "del=%d/%m" is displaying in the logs as: "del=/1186" for example. In src/pop3/pop3-client.c:552: tab[4].value = client->delete_success ? dec2str(client->deleted_count) : 0; Shouldn't this be: tab[4].value = client->delete_success ? dec2str(client->deleted_count) : "0"; (very minor bug) -- Dave

2 2

dovecot-keywords and mbox
by Anton Yuzhaninov 15 Sep '16

15 Sep '16

Hello, With Maildir++ it is possible to store list of IMAP message keyworkds (tags in Thunderbird) on server in dovecot-keywords file. Is it possible the same with mbox mailboxes? My mbox directory contains .subscriptions file, but no .dovecot-keywords file. -- WBR, Anton Yuzhaninov

2 1

Re: 2.2.25 dumps core with "Panic: file imap-client.c: line 837 (client_check_command_hangs): assertion failed: (client->io != NULL)"
by Piper Andreas 15 Sep '16

15 Sep '16

Hello Timo, from the maintainer of the OpenCSW package I got the below answer. As the newly build package yields another different commit hash (which I cannot find on GitHub too), I would ask, if you are sure that the commit hash-output in 'doveconf -n' is generated correctly? The headline of 'doveconf -n' with the newly build package is # 2.2.25 (68082dc): /etc/opt/csw/dovecot/dovecot.conf Many thanks for your help, Andreas -------- Weitergeleitete Nachricht -------- Betreff: Re: OpenCSW question about package CSWdovecot Datum: Tue, 30 Aug 2016 08:56:44 -0700 Von: jgoerzen <jgoerzen(a)opencsw.org> An: piper(a)hrz.uni-marburg.de Hello Andreas, The OpenCSW dovecot package was built using the 2.2.25 version release tarball. No code changes or patches have been applied. I'm not sure what happened. I will respin new packages and then check to see if the git-commit hash is correct. When the packages are done building I'll put them in the experimental catalog: http://buildfarm.opencsw.org/experimental.html#jgoerzen Thanks, Jake On 08/29/2016 11:59 PM, piper(a)hrz.uni-marburg.de wrote: > Hello, > > with your newest dovecot-package 2.2.25,REV=2016.07.01, I sometimes get core-dumps as documented in my bug-report at the dovecot-mailing-list: http://dovecot.org/list/dovecot/2016-August/105321.html > In reaction to my bug-report, Timo Sirainen asks, which git-commit of the dovecot-sources was used for this package: http://dovecot.org/list/dovecot/2016-August/105332.html > > Could you shed some light on this? > > Thanks a lot, > Andreas

3 8

No Autoindex?
by Larry Rosenman 14 Sep '16

14 Sep '16

I used to get my mail auto-indexed, but something(tm) changed recently, but I'm not sure what. I do have fts_autoindex = yes in my dovecot config, and if I do a doveadm index \* it does the index. Ideas? doveconf -n attached -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 214-642-9640 (c) E-Mail: larryrtx(a)gmail.com US Mail: 17716 Limpia Crk, Round Rock, TX 78664-7281

1 0