- dovecot - dovecot.org

TLS problem after upgrading from v2.2 to v2.3
by Jan Vejvalka 07 Jan '18

07 Jan '18

Thanks for your reply; I used the defaults, both before and after the upgrade, cf. https://wiki2.dovecot.org/Upgrading/2.3 -> Setting default changes. The new defaults broke the connection. Jan > what are your settings? > > Mine are below and they work just fine: > > ssl_cipher_list = > ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-AES256-GCM-SHA384:DHE-RSA-AES128-GCM-SHA256:DHE-DSS-AES128-GCM-SHA256:kEDH+AESGCM:ECDHE-RSA-AES128-SHA256:ECDHE-ECDSA-AES128-SHA256:ECDHE-RSA-AES128-SHA:ECDHE-ECDSA-AES128-SHA:ECDHE-RSA-AES256-SHA384:ECDHE-ECDSA-AES256-SHA384:ECDHE-RSA-AES256-SHA:ECDHE-ECDSA-AES256-SHA:DHE-RSA-AES128-SHA256:DHE-RSA-AES128-SHA:DHE-DSS-AES128-SHA256:DHE-RSA-AES256-SHA256:DHE-DSS-AES256-SHA:DHE-RSA-AES256-SHA:!aNULL:!eNULL:!EXPORT:!DES:!RC4:!3DES:!MD5:!PSK:!SSLv2:!SSLv3

2 2

TLS problem after upgrading from v2.2 to v2.3
by Jan Vejvalka 06 Jan '18

06 Jan '18

Hi *, The change in default SSL settings between 2.2 and 2.3 cut off a few clients; Microsoft-hosted Exchange (?) being one of them: Jan 4 11:02:56 kremail dovecot: pop3-login: Disconnected (no auth attempts in 0 secs): user=<>, rip=40.101.4.hisip, lip=myip, TLS handshaking: SSL_accept() failed: error:1408A0C1:SSL routines:SSL3_GET_CLIENT_HELLO:no shared cipher, session=<8SGob/BhTdcoZQS1> Explicitly setting ssl_cipher_list to the old defaults helped: ssl_cipher_list = ALL:!LOW:!SSLv2:!EXP:!aNULL Does someone have an idea what to recommend to the poor user or should I accept that I stay with the old defaults ? The guy is cooperative, so we can find out which of the !'s in the new defaults actually breaks the connection... if you think it's worth. Thanks for your help, Jan

2 1

dovecot-2.3.0 'make check' error
by Eric Broch 05 Jan '18

05 Jan '18

Hello list, I've configured dovecot-2.3.0 on CentOS 6 with the following options. CFLAGS="-O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -m64 -mtune=generic -fno-strict-aliasing" \ LDFLAGS="-Wl,-z,now -Wl,-z,relro" \ ./configure \ --docdir=/usr/share/doc/dovecot-2.3.0 \ --with-lzma \ --disable-static \ --disable-rpath \ --with-nss \ --with-shadow \ --with-pam \ --with-gssapi=plugin \ --with-ldap=plugin \ --with-sql=plugin \ --with-lua=plugin \ --with-pgsql \ --with-mysql \ --with-sqlite \ --with-vpopmail=/etc/libvpopmail \ --with-zlib \ --with-libcap \ --with-libwrap \ --with-ssl=openssl \ --with-ssldir=/etc/pki/dovecot \ --with-solr \ --with-docs and compiled with the following: # make -j2 When I run a 'make check': # make check I get the following error: make[3]: Entering directory `/root/dovecot/dovecot-ce-2.3.0/src/lib-compression' for bin in test-compression; do \ if ! /bin/sh ../../run-test.sh ../.. ./$bin; then exit 1; fi; \ done compression handler gz ............................................... : ok compression handler bz2 .............................................. : ok compression handler deflate .......................................... : ok compression handler xz ............................................... : ok gz concat ............................................................ : ok gz no concat ......................................................... : ok gz large header ...................................................... : ok 0 / 7 tests failed ==4468== Conditional jump or move depends on uninitialised value(s) ==4468== at 0x3A6160ACB2: ??? (in /usr/lib64/liblzma.so.0.0.0) ==4468== by 0x3A6160AEA9: ??? (in /usr/lib64/liblzma.so.0.0.0) ==4468== by 0x3A61603121: ??? (in /usr/lib64/liblzma.so.0.0.0) ==4468== by 0x3A616061A0: ??? (in /usr/lib64/liblzma.so.0.0.0) ==4468== by 0x3A61605212: lzma_easy_encoder (in /usr/lib64/liblzma.so.0.0.0) ==4468== by 0x406ACF: o_stream_create_lzma (ostream-lzma.c:206) ==4468== by 0x403D89: test_compression_handler (test-compression.c:36) ==4468== by 0x4040BD: test_compression (test-compression.c:96) ==4468== by 0x408281: test_run_funcs (test-common.c:244) ==4468== by 0x4083E0: test_run (test-common.c:315) ==4468== by 0x40398B: main (test-compression.c:308) ==4468== Failed to run: ./test-compression make[3]: *** [check-local] Error 1 make[3]: Leaving directory `/root/dovecot/dovecot-ce-2.3.0/src/lib-compression' make[2]: *** [check-am] Error 2 make[2]: Leaving directory `/root/dovecot/dovecot-ce-2.3.0/src/lib-compression' make[1]: *** [check-recursive] Error 1 make[1]: Leaving directory `/root/dovecot/dovecot-ce-2.3.0/src' make: *** [check-recursive] Error 1 Has anyone seen the above error and/or, Can anyone give me a reason why it's occurring? -- Eric Broch White Horse Technical Consulting (WHTC)

1 0

Re: Bug in dovecot 2.3 virtual plugin
by Jakob Schürz 05 Jan '18

05 Jan '18

So hello back again! Am 05.01.2018 um 14:31 schrieb Jakobus Schürz: > > > Am 05.01.2018 um 10:25 schrieb Aki Tuomi: >> This is a different bug, and I suspect it might be caused by virtual >> plugin. We'll look into it. >> >> Aki > > It was a problem with selfhealing the index... I deleted all my emails and mailboxes and rebuild the tree of mailboxes again with doveadm. Then i put back email for email from the cur-folders from backup to the new-folders in the rebuild mailboxes. From the filename i cut of the part with hostname and size and flags. The archive now is in a separate namespace, because there are really a lot of emails in. Now it works great again (exept one error, i posted before) Maybe you can find something to improve dovecot in selfhealing broken index. Thanks for the great work on this server! jakob

1 0

Released Pigeonhole v0.5.0.1 for Dovecot v2.3.0.
by Stephan Bosch 05 Jan '18

05 Jan '18

Hello Dovecot users, This is a bugfix release to mend some problems that were found in v0.5.0. The imap4flags bug is actually not first seen in the 0.5.0 release (it is ancient), but I included the fix for it anyway. Changelog v0.5.0.1: - imap4flags extension: Fix binary corruption occurring when setflag/addflag/removeflag flag-list is a variable. - sieve-extprograms plugin: Fix segfault occurring when used in IMAPSieve context. The release is available as follows: https://pigeonhole.dovecot.org/releases/2.3/dovecot-2.3-pigeonhole-0.5.0.1.… https://pigeonhole.dovecot.org/releases/2.3/dovecot-2.3-pigeonhole-0.5.0.1.… Refer to http://pigeonhole.dovecot.org and the Dovecot v2.x wiki for more information. Have fun testing this release and don't hesitate to notify me when there are any problems. Regards, -- Stephan Bosch stephan(a)rename-it.nl

2 1

Dovecot 2.3 - using doveadm as non-root?
by Rob Hoelz 04 Jan '18

04 Jan '18

Hi dovecot developers and users, I recently upgraded my server running Arch Linux to dovecot 2.3.0, and I noticed some of my cron jobs started issuing me error messages. These cron jobs run as a non-root user associated with my mail account, and they use doveadm to tidy things up (ex. purging the trash, moving old mail in certain folders into the trash). The error message is: > Error: net_connect_unix(/var/run/dovecot/stats-writer) failed: > Permission denied I assume this is doveadm trying to participate in the new 2.3 stats process, and after reading the code a bit, I can't see way to tell doveadm to not connect to the stats writer. The socket is owned by root with 600 permissions. What would be the right way to remedy this? AFAICT, I could potentially run doveadm as root (which I would prefer to avoid), or I could change the permissions on the stats writer socket, but I would hate to introduce any sort of security vulnerability by doing so. I currently have a scrappy Perl script that just runs doveadm and filters out the error message (it doesn't seem to affect the behavior of doveadm other than the message), but that feels dirty and I would prefer a cleaner solution. Any advice? Thanks, Rob

3 2

sieve/internal error/detail subaddress and IMAP4FLAGS.
by Larry Rosenman 04 Jan '18

04 Jan '18

I'm trying to set an IMAP Flag with the detail part of an address, but getting an internal error: an 3 13:37:27 thebighonker exim[537]: 1eWoqt-00008f-4u <= ler(a)lerctr.org H=(lrosenman.local) [74.203.163.58]:4650 I=[192.147.25.65]:587 P=esmtpsa X=TLSv1.2:ECDHE-RSA-AES256-GCM-SHA3 84:256 CV=no SNI="smtp.lerctr.org" A=dovecot_login:ler S=769 id=20180103193716.oofszdaxopnkgfvd(a)lrosenman.local Jan 3 13:37:27 thebighonker dovecot: lmtp(549): Connect from local Jan 3 13:37:27 thebighonker dovecot: lmtp(ler(a)lerctr.org/549): save: box=INBOX, uid=127797, msgid=<20180103193716.oofszdaxopnkgfvd(a)lrosenman.local>, size=1033, vsize=1062, from=Larry Rosenman <ler(a)lerctr.org>, subject=testd, flags=() Jan 3 13:37:27 thebighonker dovecot: lmtp(ler(a)lerctr.org/549): sieve: msgid=<20180103193716.oofszdaxopnkgfvd(a)lrosenman.local>: stored mail into mailbox 'INBOX' (subject=testd from=le r(a)lerctr.org size=1062) Jan 3 13:37:27 thebighonker dovecot: lmtp(ler(a)lerctr.org/549): Error: sieve: !!BUG!!: Binary compiled from /home/ler/.dovecot.sieve is still corrupt; bailing out and reverting to def ault delivery Jan 3 13:37:27 thebighonker dovecot: lmtp(549): Disconnect from local: Client has quit the connection (state = READY) Jan 3 13:37:27 thebighonker exim[545]: 1eWoqt-00008f-4u == ler_testd(a)lerctr.org R=localuser T=dovecot_lmtp defer (-46): LMTP error after end of data: 451 4.2.0 <ler_testd(a)lerctr.org> BUG: Unknown internal error Jan 3 13:37:27 thebighonker dovecot: indexer-worker(ler(a)lerctr.org/536): Indexed 1 messages in INBOX (UIDs 127797..127797) .dovecot.sieve points to master.sieve (below), and the rest of the scripts (including master.sieve) are at http://www.lerctr.org/~ler/sieve. require ["fileinto","imap4flags","include","mailbox", "envelope","subaddress","variables"]; require "vnd.dovecot.debug"; global "MyFlags"; if envelope :detail "to" "freebsd" { addflag "FreeBSD"; addflag "MyFlags" "FreeBSD"; } if envelope :matches :detail "to" "*" { set "detail" "${1}"; addflag "${detail}"; addflag "MyFlags" "${detail}"; } debug_log "MyFlags=${MyFlags}, detail=${detail}"; include :personal "spam"; include :personal "freebsd"; include :personal "postgresql"; include :personal "misc"; include :personal "mailinglist"; Doveconf -n: # 2.3.0 (c8b89eb): /usr/local/etc/dovecot/dovecot.conf # Pigeonhole version 0.5.0 (d68c23a1) # OS: FreeBSD 11.1-STABLE amd64 auth_mechanisms = plain login auth_realms = lerctr.org thebighonker.lerctr.org tbh.lerctr.org thejonesonair.com thejonesonair.net default_vsz_limit = 1 G deliver_log_format = msgid=%m: %$ (subject=%s from=%f size=%w) doveadm_password = # hidden, use -P to show it first_valid_gid = 0 first_valid_uid = 0 lda_mailbox_autocreate = yes listen = 192.147.25.65, :: login_access_sockets = tcpwrap mail_attribute_dict = file:%h/mail/.imap/dovecot-mail-attributes mail_location = mbox:~/mail:INBOX=~/mail/INBOX mail_log_prefix = "%s(%u/%p): " mail_plugins = " fts fts_solr notify virtual" mail_privileged_group = mail mail_server_admin = mailto:ler@lerctr.org mail_server_comment = LERCTR Mail Server 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 vacation-seconds editheader mboxmetadata servermetadata vnd.dovecot.debug imapsieve vnd.dovecot.imapsieve namespace archive { hidden = no list = no location = mbox:~/MAIL-ARCHIVE prefix = ARCHIVE/ separator = / } namespace inbox { inbox = yes location = mailbox Drafts { special_use = \Drafts } mailbox INBOX { auto = create } mailbox SENT { special_use = \Sent } mailbox SPAM { special_use = \Junk } mailbox "Sent Messages" { special_use = \Sent } mailbox Trash { special_use = \Trash } mailbox virtual/Flagged { special_use = \Flagged } mailbox virtual/all { special_use = \All } prefix = separator = / } namespace virtual { hidden = no list = yes location = virtual:~/MAIL-VIRTUAL:INDEX=MEMORY prefix = Virtual/ separator = / } passdb { args = /usr/local/etc/dovecot/dovecot-sql.conf.ext driver = sql } passdb { args = user=%Ln noauthenticate driver = static skip = authenticated } passdb { args = failure_show_msg=yes session=yes max_requests=20 driver = pam skip = authenticated } plugin { fts = solr fts_autoindex = yes fts_solr = url=http://thebighonker.lerctr.org:8983/solr/dovecot/ fts_tika = http://localhost:9998/tika/ imapsieve_mailbox1_before = file:/usr/local/share/dovecot-pigeonhole/sieve/report-spam.sieve imapsieve_mailbox1_causes = COPY imapsieve_mailbox1_name = SPAM imapsieve_mailbox2_before = file:/usr/local/share/dovecot-pigeonhole/sieve/report-ham.sieve imapsieve_mailbox2_causes = COPY imapsieve_mailbox2_from = SPAM imapsieve_mailbox2_name = * imapsieve_url = sieve://thebighonker.lerctr.org mail_log_events = delete undelete expunge copy mailbox_delete mailbox_rename flag_change append mail_log_fields = uid box msgid size from subject vsize flags recipient_delimiter = +-_ sieve = ~/.dovecot.sieve sieve_dir = ~/sieve sieve_execute_bin_dir = /usr/local/share/dovecot-pigeonhole/sieve sieve_extensions = +editheader +vacation-seconds +mboxmetadata +servermetadata +vnd.dovecot.debug sieve_global_extensions = +vnd.dovecot.pipe +vnd.dovecot.execute sieve_pipe_bin_dir = /usr/local/share/dovecot-pigeonhole/sieve sieve_plugins = sieve_imapsieve sieve_extprograms } protocols = imap pop3 lmtp sieve recipient_delimiter = +-_ service anvil { unix_listener anvil { group = mail mode = 0660 } } service auth { unix_listener auth-client { mode = 0666 } unix_listener auth-master { mode = 0666 } } service doveadm { inet_listener http { port = 8080 ssl = yes } } service indexer-worker { drop_priv_before_exec = yes } service lmtp { inet_listener lmtp { address = 127.0.0.1 port = 24 } } service managesieve-login { inet_listener sieve { port = 4190 } inet_listener sieve_deprecated { port = 2000 } } service stats { unix_listener stats-reader { group = mail mode = 0660 user = } unix_listener stats-writer { group = mail mode = 0660 user = } } service tcpwrap { unix_listener login/tcpwrap { group = $default_login_user mode = 0600 user = $default_login_user } } ssl_cert = </home/ler/letsencrypt-home/lerctr.org/fullchain.cer ssl_cipher_list = EECDH+ECDSA+AESGCM:EECDH+aRSA+AESGCM:EECDH+ECDSA+SHA384:EECDH+ECDSA+SHA256:EECDH+aRSA+SHA384:EECDH+aRSA+SHA256:EECDH+AESGCM:EECDH:EDH+AESGCM:EDH+aRSA:HIGH:!MEDIUM:!LOW:!aNULL:!eNULL:!LOW:!RC4:!MD5:!EXP:!PSK:!SRP:!DSS ssl_dh = # hidden, use -P to show it ssl_key = # hidden, use -P to show it userdb { args = /usr/local/etc/dovecot/dovecot-sql.conf.ext driver = sql } userdb { args = username_format=%Ln /etc/passwd driver = passwd-file } verbose_proctitle = yes protocol lmtp { mail_plugins = " fts fts_solr notify virtual sieve mail_log" } protocol lda { mail_plugins = " fts fts_solr notify virtual sieve mail_log" } protocol pop3 { mail_plugins = " fts fts_solr notify virtual mail_log" } protocol !doveadm { mail_plugins = " fts fts_solr notify virtual mail_log" } protocol imap { imap_client_workarounds = tb-extra-mailbox-sep tb-lsub-flags imap_logout_format = in=%i out=%o fhc=%{fetch_hdr_count} fhb=%{fetch_hdr_bytes} fbc=%{fetch_body_count} fbb=%{fetch_body_bytes} del=%{deleted} exp=%{expunged} trash=%{trashed} imap_metadata = yes mail_max_userip_connections = 50 mail_plugins = " fts fts_solr notify virtual mail_log imap_sieve" } -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 214-642-9640 E-Mail: larryrtx(a)gmail.com US Mail: 5708 Sabbia Drive, Round Rock, TX 78665-2106

2 2

Re: dovecot v2.3.0: imap segfault when sieve_extprograms_plugin.so called
by Daniel Kenzelmann 04 Jan '18

04 Jan '18

That's the point, the fix was committed afterwards... https://github.com/dovecot/pigeonhole/commit/321a39be974deb2e7eff7b2a50 9a3ee6ff2e5ae1 So, any 0.5.1 release on the horizon? Thanks, Daniel Am Mittwoch, den 03.01.2018, 22:14 +0200 schrieb Aki Tuomi: > pigeonhole 0.5.0 has been already released... > > > > --- > Aki Tuomi > Dovecot oy > > -------- Original message -------- > From: Daniel Kenzelmann <dovecot.org(a)k8n.de> > Date: 03/01/2018 21:31 (GMT+02:00) > To: Rhys Williams <lux+mailinglists(a)melted.me>, dovecot(a)dovecot.org > Subject: Re: dovecot v2.3.0: imap segfault when > sieve_extprograms_plugin.so called > > Hi, > > see the following thread: > > https://www.dovecot.org/pipermail/dovecot/2017-December/110448.html > > We need to wait for an updated pigeonhole/dovecot... :-( > > Is there maybe some ETA for an updated release? (just wondering if it > makes sense to create an updated ebuild with the patch for gentoo) > > -Daniel > > > Am Mittwoch, den 03.01.2018, 18:12 +0000 schrieb Rhys Williams: > > Hi, > > > > I have recently upgraded to dovecot v2.3 on Ubuntu 16.04.3 from > > repo.dovecot.org and I switched to IMAPSieve for rspamd with the > > guide from the wiki. When a mail is moved from Junk to another > Inbox > > or vice-versa imap segfaults. > > > > I have posted debug logs and versions below, any help will be > greatly > > appreciated. > > > > Thanks, > > Rhys Williams > > > > lux@bifrost:~$ dovecot --version > > 2.3.0 (c8b89eb) > > > > lux@bifrost:~$ uname -a > > Linux bifrost 4.10.0-43-generic #47~16.04.1-Ubuntu SMP Wed Dec 13 > > 19:23:27 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux > > > > Log of the crash: https://paste.ubuntu.com/26314370/ (https://paste > .u > > buntu.com/26314370/) > > Core dump: https://paste.ubuntu.com/26314349/ (https://paste.ubuntu > .c > > om/26314349/) > > dovecot -n: https://paste.ubuntu.com/26314365/ (https://paste.ubunt > u. > > com/26314365/)

2 1

Dovecot auth SASL for exim and plain auth issue without initial response
by Daniel Kenzelmann 04 Jan '18

04 Jan '18

Hi, I'm not entirely sure whether this issue is with exim or with dovecot. First some background: I'm using exim with dovecot-auth which in turn is using LDAP for authentication. When using AUTH PLAIN with the optional initial response argument, everything is fine. However when using AUTH PLAIN without the optional response argument, instead of getting an empty challenge ("334 ") as per RFC i am getting a "535 Incorrect authentication data". Example: Working: 220 XXXX ESMTP 2018-01-02 22:32:33+0100 EHLO test 250-XXXX Hello XXXXX [x.x.x.x] 250-SIZE 52428800 250-8BITMIME 250-PIPELINING 250-AUTH PLAIN LOGIN 250-CHUNKING 250 HELP AUTH PLAIN XXXXXXXXXXXXXXXXXXXXXXXX== 235 Authentication succeeded NOT-WORKING: 220 XXXX ESMTP 2018-01-02 22:34:37+0100 EHLO test 250-XXXX Hello XXXXX [x.x.x.x] 250-SIZE 52428800 250-8BITMIME 250-PIPELINING 250-AUTH PLAIN LOGIN 250-CHUNKING 250 HELP AUTH PLAIN 535 Incorrect authentication data Here the SASL mechanism should return an empty challenge as per RFC (i.e. "334 " in SMTP): RFC 4954 - SMTP Service Extension for Authentication 4. The AUTH Command [..] The optional initial response argument to the AUTH command is used to save a round-trip when using authentication mechanisms that support an initial client response. ====> If the initial ====> response argument is omitted and the chosen mechanism requires ====> an initial client response, the server MUST proceed as defined ====> in Section 5.1 of [SASL]. In SMTP, a server challenge that ====> contains no data is defined as a 334 reply with no text part. ====> Note that there is still a space following the reply code, so ====> the complete response line is "334 ". [..] RFC 4422 - Simple Authentication and Security Layer (SASL) 5. Mechanism Requirements SASL mechanism specifications MUST supply the following information: 1) The name of the mechanism (see Section 3.1). This name MUST be registered as discussed in Section 7.1. 2) A definition of the server-challenges and client-responses of the authentication exchange, as well as the following: a) An indication of whether the mechanism is client-first, variable, or server-first. ===> If a SASL mechanism is defined as ===> client-first and the client does not send an initial response ===> in the authentication request, then the first server challenge ===> MUST be empty (the EXTERNAL mechanism is an example of this case). If a SASL mechanism is defined as variable, then the specification needs to state how the server behaves when the initial client response in the authentication request is omitted (the DIGEST-MD5 mechanism [DIGEST-MD5] is an example of this case). If a SASL mechanism is defined as server-first, then the client MUST NOT send an initial client response in the authentication request (the CRAM-MD5 mechanism [CRAM-MD5] is an example of this case). Thanks, Daniel

2 5

Dovecot panic for one user after upgrading
by Owen B. Mehegan 04 Jan '18

04 Jan '18

The EC2 instance that I run Dovecot on (personal mail server) was forcibly "retired" yesterday, and as a result I ended up rebuilding from backups. In the process I switched from Ubuntu Precise to Ubuntu Xenial (12.04 to 16.04), and this in turn caused me to upgrade Dovecot from 2.0.19 to 2.0.22. Now, although accessing mail seems to work OK using my various clients, I am seeing these errors in my logs: Jan 3 05:56:58 -- dovecot: imap(owen): Panic: file mail-index-sync-keywords.c: line 227 (keywords_update_records): assertion failed: (data_offset >= sizeof(struct mail_index_record)) Jan 3 05:56:58 -- dovecot: imap(owen): Error: Raw backtrace: /usr/lib/dovecot/libdovecot.so.0(+0x7aee2) [0x7fe9c08dbee2] -> /usr/lib/dovecot/libdovecot.so.0(+0x7afcd) [0x7fe9c08dbfcd] -> /usr/lib/dovecot/libdovecot.so.0(i_fatal+0) [0x7fe9c0880a61] -> /usr/lib/dovecot/libdovecot-storage.so.0(mail_index_sync_keywords+0x828) [0x7fe9c0c1fdd8] -> /usr/lib/dovecot/libdovecot-storage.so.0(mail_index_sync_record+0xef) [0x7fe9c0c2079f] -> /usr/lib/dovecot/libdovecot-storage.so.0(mail_index_sync_map+0x238) [0x7fe9c0c21758] -> /usr/lib/dovecot/libdovecot-storage.so.0(mail_index_map+0x71) [0x7fe9c0c18de1] -> /usr/lib/dovecot/libdovecot-storage.so.0(+0xd28fd) [0x7fe9c0c2e8fd] -> /usr/lib/dovecot/libdovecot-storage.so.0(+0xd2f03) [0x7fe9c0c2ef03] -> /usr/lib/dovecot/libdovecot-storage.so.0(mail_index_open+0x78) [0x7fe9c0c2efe8] -> /usr/lib/dovecot/libdovecot-storage.so.0(index_storage_mailbox_open+0x92) [0x7fe9c0c08042] -> /usr/lib/dovecot/libdovecot-storage.so.0(+0x5e8d2) [0x7fe9c0bba8d2] -> /usr/lib/dovecot/libdovecot-storage.so.0(+0x5e9b8) [0x7fe9c0bba9b8] -> /usr/lib/dovecot/libdovecot-storage.so.0(+0x37b86) [0x7fe9c0b93b86] -> /usr/lib/dovecot/libdovecot-storage.so.0(mailbox_open+0x20) [0x7fe9c0b93d00] -> /usr/lib/dovecot/libdovecot-storage.so.0(index_storage_get_status+0x20) [0x7fe9c0c073b0] -> /usr/lib/dovecot/libdovecot-storage.so.0(mailbox_get_status+0x37) [0x7fe9c0b940e7] -> dovecot/imap(imap_status_get+0x77) [0x55d3b4c3f977] -> dovecot/imap(cmd_status+0x1a9) [0x55d3b4c32969] -> dovecot/imap(command_exec+0x9c) [0x55d3b4c3806c] -> dovecot/imap(+0x193e2) [0x55d3b4c363e2] -> dovecot/imap(+0x1946c) [0x55d3b4c3646c] -> dovecot/imap(client_handle_input+0x165) [0x55d3b4c36825] -> dovecot/imap(client_input+0x82) [0x55d3b4c36db2] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_call_io+0x4c) [0x7fe9c08efc6c] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run_internal+0x101) [0x7fe9c08f1101] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run+0x25) [0x7fe9c08efcf5] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_run+0x38) [0x7fe9c08efe98] Jan 3 05:56:59 -- dovecot: imap(owen): Fatal: master: service(imap): child 18289 killed with signal 6 (core dumped) I have deleted the dovecot.* files in the Maildir for all users (did this while Dovecot was stopped, then started it again), but the errors persist. They are especially frequent for one particular user. I can't figure out where the core file is, it doesn't seem to be in my home or in /var/run/dovecot Here's my dovecot -n output: # 2.2.22 (fe789d2): /etc/dovecot/dovecot.conf # Pigeonhole version 0.4.13 (7b14904) # OS: Linux 4.4.0-1043-aws x86_64 Ubuntu 16.04.3 LTS mail_location = maildir:~/Maildir namespace inbox { inbox = yes location = mailbox Drafts { special_use = \Drafts } mailbox Junk { special_use = \Junk } mailbox Sent { special_use = \Sent } mailbox "Sent Messages" { special_use = \Sent } mailbox Trash { special_use = \Trash } prefix = } passdb { driver = pam } protocols = " imap" service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0660 user = postfix } } ssl_cert = </etc/letsencrypt/live/mydomain/cert.pem ssl_key = </etc/letsencrypt/live/mydomain/privkey.pem userdb { driver = passwd } Thanks in advance for any support you can offer!

2 2