- dovecot - dovecot.org

imap-login segfaulting on 2.3.1
by Grant Keller 24 Apr '18

24 Apr '18

Hello, I have a new director ring I am setting up on centos 7 with dovecot 2.3.1. I haven't been able to replecate this in testing, but as soon as I start pushing production traffic to the new ring I see dozens of these in the logs: Apr 18 00:34:00 d.director.imapd.sonic.net kernel: imap-login[163107]: segfault at 10 ip 00007ff625698dd5sp 00007ffe4b77bb28 error 4 in libdovecot.so.0.0.0[7ff6255bf000+16e000] My config: # 2.3.1 (c5a5c0c82): /etc/dovecot/dovecot.conf # OS: Linux 3.10.0-693.21.1.el7.x86_64 x86_64 CentOS Linux release 7.4.1708 (Core) # Hostname: c.director.imapd.sonic.net auth_master_user_separator = * auth_username_format = %Ln auth_verbose = yes default_client_limit = 20000 director_mail_servers = 64.142.111.75 64.142.111.43 64.142.111.76 64.142.111.39 64.142.111.81 director_servers = c.director.imapd.sonic.net d.director.imapd.sonic.net disable_plaintext_auth = no doveadm_port = 1842 login_trusted_networks = 64.142.18.0/24 64.142.105.2 64.142.111.67 64.142.111.36 64.142.105.3 64.142.111.35 64.142.111.68 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/master-users driver = passwd-file master = yes pass = yes } passdb { args = proxy=y nopassword=y driver = static } service anvil { client_limit = 40103 } service auth { client_limit = 41704 } service director { fifo_listener login/proxy-notify { mode = 0666 } inet_listener { port = 9321 } unix_listener login/director { mode = 0666 } } service imap-login { executable = imap-login director process_limit = 20000 process_min_avail = 32 } service imap { process_limit = 20480 } service ipc { unix_listener ipc { user = dovecot } } service pop3-login { executable = pop3-login director process_limit = 20000 process_min_avail = 32 } ssl_cert = </etc/dovecot/ssl/imap.sonic.net.pem ssl_cipher_list = ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-AES256-GCM-SHA384:DHE-RSA-AES128-GCM-SHA256:DHE-DSS-AES128-GCM-SHA256:kEDH+AESGCM:ECDHE-RSA-AES128-SHA256:ECDHE-ECDSA-AES128-SHA256:ECDHE-RSA-AES128-SHA:ECDHE-ECDSA-AES128-SHA:ECDHE-RSA-AES256-SHA384:ECDHE-ECDSA-AES256-SHA384:ECDHE-RSA-AES256-SHA:ECDHE-ECDSA-AES256-SHA:DHE-RSA-AES128-SHA256:DHE-RSA-AES128-SHA:DHE-DSS-AES128-SHA256:DHE-RSA-AES256-SHA256:DHE-DSS-AES256-SHA:DHE-RSA-AES256-SHA:AES128-GCM-SHA256:AES256-GCM-SHA384:AES128-SHA256:AES256-SHA256:AES128-SHA:AES256-SHA:AES:CAMELLIA:DES-CBC3-SHA:!aNULL:!eNULL:!EXPORT:!DES:!RC4:!MD5:!PSK:!aECDH:!EDH-DSS-DES-CBC3-SHA:!EDH-RSA-DES-CBC3-SHA:!KRB5-DES-CBC3-SHA ssl_dh = # hidden, use -P to show it ssl_key = # hidden, use -P to show it syslog_facility = local0 protocol imap { imap_max_line_length = 128 k ssl_cert = </etc/dovecot/ssl/imap.sonic.net.pem ssl_key = # hidden, use -P to show it } protocol pop3 { ssl_cert = </etc/dovecot/ssl/pop.sonic.net.pem ssl_key = # hidden, use -P to show it } backtrace: Stack trace of thread 56084: #0 0x00007fe529be2dd5 i_stream_get_root_io (libdovecot.so.0) #1 0x00007fe529be2e39 i_stream_set_input_pending (libdovecot.so.0) #2 0x00007fe527415a59 openssl_iostream_bio_sync (libssl_iostream_openssl.so) #3 0x00007fe527415c2a openssl_iostream_more (libssl_iostream_openssl.so) #4 0x00007fe527415c6b openssl_iostream_destroy (libssl_iostream_openssl.so) #5 0x00007fe529e8be72 client_unref (libdovecot-login.so.0) #6 0x00007fe529e90441 login_proxy_free_full (libdovecot-login.so.0) #7 0x00007fe529e90e07 login_proxy_finished (libdovecot-login.so.0) #8 0x00007fe529becfb5 io_loop_call_io (libdovecot.so.0) #9 0x00007fe529bee89f io_loop_handler_run_internal (libdovecot.so.0) #10 0x00007fe529bed0b2 io_loop_handler_run (libdovecot.so.0) #11 0x00007fe529bed2d8 io_loop_run (libdovecot.so.0) #12 0x00007fe529b69673 master_service_run (libdovecot.so.0) #13 0x00007fe529e93532 login_binary_run (libdovecot-login.so.0) #14 0x00007fe529767c05 __libc_start_main (libc.so.6) #15 0x00005567b256050a _start (imap-login) Grant Keller System Operations grant.keller(a)sonic.com

2 2

Re: Merging mailboxes with doveadm
by Carsten Schmitz 24 Apr '18

24 Apr '18

Hello Aki, yes, that's it - thank you. For reference this works: sudo doveadm import -u destination(a)company.net maildir:/var/vmail/company.net/some.name/Maildir some_name ALL Thanks again Carsten On 23.04.2018 15:06, Aki Tuomi wrote: > The command you are looking for is doveadm import > > --- > Aki Tuomi > Dovecot oy > > -------- Original message -------- > From: Carsten Schmitz <carsten.schmitz(a)limesurvey.org> > Date: 23/04/2018 15:46 (GMT+02:00) > To: dovecot(a)dovecot.org > Subject: Merging mailboxes with doveadm > > Hello, > > I am trying to merge(=copy) all mails of all user mailboxes into one > mailbox for one-time archival purposes. > > The command I am using is > > sudo doveadm -v copy -A archive(a)somedomain.net ALL > > > The error I get for every mailbox is: > > doveadm(someuser1(a)somedomain.net): Error: Can't open mailbox > 'a(a)somedomain.net': Mailbox doesn't exist: archive(a)somedomain.net > > doveadm(someuser2(a)somedomain.net): Error: Can't open mailbox > 'a(a)somedomain.net': Mailbox doesn't exist: archive(a)somedomain.net > > [etc...] > > I don't exactly understand why. I think I am don't understand the > 'destination' parameter correctly, so somebody can enlighten me, please? > > Thank you > > > Carsten > > >

1 0

Sieve "redirect" changes envelope sender in 2.3. / pigeonhole 0.5
by Olaf Hopp 24 Apr '18

24 Apr '18

Hi (Stephan?), is it a new feature of dovecot 2.3 /pigeonhole 0.5 that a sieve "redirect" changes the envelope sender of a redirected mail or simply a bug ? A sends mail to B, B redirects to C C sees B (not A!) as envelope sender. It is not a problem if C gets the mail but if that mail bounces for various reasons it goes back to B and A will never know about this. I thick this is came with 2.3 / pigeonhole 0.5 ? # 2.3.1 (c5a5c0c82): /etc/dovecot/dovecot.conf # Pigeonhole version 0.5.devel (61b47828) # OS: Linux 2.6.32-696.23.1.el6.x86_64 x86_64 CentOS release 6.9 (Final) Regards, Olaf -- Karlsruher Institut für Technologie (KIT) ATIS - Abt. Technische Infrastruktur, Fakultät für Informatik Dipl.-Geophys. Olaf Hopp - Leitung IT-Dienste - Am Fasanengarten 5, Gebäude 50.34, Raum 009 76131 Karlsruhe Telefon: +49 721 608-43973 Fax: +49 721 608-46699 E-Mail: Olaf.Hopp(a)kit.edu atis.informatik.kit.edu www.kit.edu KIT – Die Forschungsuniversität in der Helmholtz-Gemeinschaft Das KIT ist seit 2010 als familiengerechte Hochschule zertifiziert.

4 10

dovecot vs. mutt: no full index sync on Maildir new/ mtime change
by Michael Büker 24 Apr '18

24 Apr '18

Hi, everyone! This is a follow-up to "Looks like a bug to me: Dovecot ignores Maildir/new timestamp" from Fredrik Roubert on 01.12.2015: https://www.dovecot.org/list/dovecot/2015-December/102585.html I've run into the same problem as Fredrik: When manipulating my Maildir locally with mutt, deleting a message from new/ doesn't cause a full update of the index. Therefore, IMAP clients still see the deleted message. I've read and understood Timo's reply saying that dovecot only performs a "partial sync" of the index when the mtime of new/, but not of cur/, changes. This makes perfect sense for performance reasons for most users: https://www.dovecot.org/list/dovecot/2015-December/102588.html I, however, would be willing to take the performance hit of a full index sync whenever the mtime of new/ changes. Therefore, I looked at the code and tried to implement a config option (maildir_fullsync_on_new_mtime_change) for this behavior. However, my understanding of src/lib-storage/index/maildir/maildir-sync.c was not good enough – I probably put the ctx->mbox->storage->set->maildir_fullsync_on_new_mtime_change check in the wrong place, and all my patch did was ruin the index ;) So, to summarize my question: I'd like dovecot to perform a full index sync when the mtime of a Maildir's new/ has changed. I'm willing to take the performance hit, because it would fix a problem I'm having with using mutt and dovecot together. Can this be done in principle by adding a config option check like ctx->mbox->storage->set->maildir_fullsync_on_new_mtime_change in the right place in src/lib-storage/index/maildir/maildir-sync.c? If so, where should it be put? Thanks for your time, Michael

2 1

smtp crashing with "out of memory" for ONE particular user
by Jacek Osiecki 24 Apr '18

24 Apr '18

Hi, I’m using dovecot 2.0.16 (I know, it’s oooold, but I have too many users to risk the upgrade while so many things have changed since) and virtual users based on MySQL. Today I had some troubles with user, who’s mailbox stopped working. No emails were delivered, with just following error line in EXIM mainlog: LMTP connection closed after end of data When I checked dovecot’s main log, and here’s what I found: Apr 23 14:06:17 lmtp(9963, jmk(a)silvercube.pl) Fatal: block_alloc(67108864): Out of memory Apr 23 14:06:17 lmtp(9963, jmk(a)silvercube.pl) Error: Raw backtrace: /usr/lib64/dovecot/libdovecot.so.0(+0x3dbda) [0x7f92f3193bda] -> /usr/lib64/dovecot/libdovecot.so.0(+0x3dc1e) [0x7f92f3193c1e] -> /usr /lib64/dovecot/libdovecot.so.0(i_error+0) [0x7f92f316d8cd] -> /usr/lib64/dovecot/libdovecot.so.0(+0x4cc45) [0x7f92f31a2c45] -> /usr/lib64/dovecot/libdovecot.so.0(+0x4cc7f) [0x7f92f31a2c7f] -> /usr/lib64/ dovecot/libdovecot.so.0(p_strdup+0x3e) [0x7f92f31ae08e] -> /usr/lib64/dovecot/libdovecot-storage.so.0(maildir_uidlist_sync_next_uid+0xf9) [0x7f92f3653e69] -> /usr/lib64/dovecot/libdovecot-storage.so.0(ma ildir_uidlist_sync_next+0x12) [0x7f92f3654232] -> /usr/lib64/dovecot/libdovecot-storage.so.0(+0x6bd3a) [0x7f92f3651d3a] -> /usr/lib64/dovecot/libdovecot-storage.so.0(+0x6c7d3) [0x7f92f36527d3] -> /usr/li b64/dovecot/libdovecot-storage.so.0(maildir_storage_sync_init+0x171) [0x7f92f3652d91] -> /usr/lib64/dovecot/libdovecot-storage.so.0(mailbox_sync_init+0x31) [0x7f92f36173a1] -> /usr/lib64/dovecot/libdovec ot-storage.so.0(mailbox_sync+0x27) [0x7f92f36174b7] -> /usr/lib64/dovecot/plugins/lib10_quota_plugin.so(quota_count+0x132) [0x7f92f1f34fe2] -> /usr/lib64/dovecot/plugins/lib10_quota_plugin.so(+0x8430) [0 x7f92f1f36430] -> /usr/lib64/dovecot/plugins/lib10_quota_plugin.so(+0x863d) [0x7f92f1f3663d] -> /usr/lib64/dovecot/plugins/lib10_quota_plugin.so(quota_get_resource+0x72) [0x7f92f1f344c2] -> /usr/lib64/do vecot/plugins/lib10_quota_plugin.so(quota_test_alloc+0x175) [0x7f92f1f34d45] -> /usr/lib64/dovecot/plugins/lib10_quota_plugin.so(+0xb0ba) [0x7f92f1f390ba] -> /usr/lib64/dovecot/libdovecot-storage.so.0(ma ilbox_save_begin+0x46) [0x7f92f3617f56] -> /usr/lib64/dovecot/libdovecot-storage.so.0(mail_storage_copy+0x7e) [0x7f92f361100e] -> /usr/lib64/dovecot/libdovecot-storage.so.0(maildir_copy+0x51) [0x7f92f364 a8a1] -> /usr/lib64/dovecot/plugins/lib10_quota_plugin.so(+0xaefa) [0x7f92f1f38efa] -> /usr/lib64/dovecot/libdovecot-storage.so.0(mailbox_copy+0x5a) [0x7f92f3617eba] -> /usr/lib64/dovecot/libdovecot-siev e.so.0(+0x36ed6) [0x7f92f1ae9ed6] -> /usr/lib64/dovecot/libdovecot-sieve.so.0(+0x2d83c) [0x7f92f1ae083c] -> /usr/lib64/dovecot/libdovecot-sieve.so.0(sieve_result_execute+0x2fd) [0x7f92f1ae1a0d] -> /usr/l ib64/dovecot/libdovecot-sieve.so.0(sieve_execute+0x7d) [0x7f92f1af0a9d] Apr 23 14:06:17 master: Error: service(lmtp): child 9963 returned error 83 (Out of memory (vsz_limit=256 MB, you may need to increase it)) What was interesting - it happenned only with this particular mailbox. It does not has large sieve file (actually, other mailboxes have muuuch bigger ones, actually nothing strange with the account - but it was failing. I have increased vsz_limit to 384MB - didn’t help. Finally, 512MB helped. But it is quite strange to me… Why one particular mailbox, what could be causing it? Greetings, — Jacek Osiecki josiecki(a)silvercube.pl

2 1

question about using cram-md5 login passwords
by Fabian A. Santiago 23 Apr '18

23 Apr '18

hello dovecot community, question; if my user database and dovecot installation is currently setup to use plain login passwords, and i want to convert to cram-md5, after i configure dovecot accordingly and reset passwords into cram-md5, if anyone uses plain login method again in the future, will it still work? or must they always from this point on use encrypted passwords? Thanks. -- Thanks, Fabian S. OpenPGP: 0x643082042DC83E6D94B86C405E3DAA18A1C22D8F (new key) 0x3C3FA072ACCB7AC5DB0F723455502B0EEB9070FC (to be retired / revoked)

2 2

lost connection while sending end of data error
by Christos Chatzaras 23 Apr '18

23 Apr '18

I use dovecot-lmtp and postfix. When I send e-mail to 2 recipients (or more) at the same time and if one of them is over quota (or under quota and the message I send is bigger than his free space) mailq shows: -Queue ID- --Size-- ----Arrival Time---- -Sender/Recipient------- 20B03336F22 26099 Thu Apr 19 18:02:47 support(a)example.com (lost connection with server25.example.org[private/dovecot-lmtp] while sending end of data -- message may be sent more than once) user1(a)example.com user2(a)example.com E-mails sent from the same domain on same server so it's a local delivery. If I send the e-mail to the over quota user ( only him on To: ) then I get a bounce that says that user is over quota which is the correct behaviour. I think the problem started after I upgrade dovecot-2.2.35 to dovecot-2.3.1. Is this a known bug?

2 3

Merging mailboxes with doveadm
by Carsten Schmitz 23 Apr '18

23 Apr '18

Hello, I am trying to merge(=copy) all mails of all user mailboxes into one mailbox for one-time archival purposes. The command I am using is sudo doveadm -v copy -A archive(a)somedomain.net ALL The error I get for every mailbox is: doveadm(someuser1(a)somedomain.net): Error: Can't open mailbox 'a(a)somedomain.net': Mailbox doesn't exist: archive(a)somedomain.net doveadm(someuser2(a)somedomain.net): Error: Can't open mailbox 'a(a)somedomain.net': Mailbox doesn't exist: archive(a)somedomain.net [etc...] I don't exactly understand why. I think I am don't understand the 'destination' parameter correctly, so somebody can enlighten me, please? Thank you Carsten

2 1

2.3.1 -> "doveadm backup -A" not working
by spamvoll＠googlemail.com 21 Apr '18

21 Apr '18

Hi, I'm running 2.3.1 and trying to do a backup. Wiki and manpage showes that -A will backup all mailboxes. It seems that "doveadm -Dv backup -A mdbox:/mnt/BACKUP/DOVECOT/" is saving each mailbox to " /mnt/BACKUP/DOVECOT/" but after finishing one, its overwriting the data from the previous user. So it ends with only the mails from the last user processed. I tried %u but thats not recognized and used as String in the path. Hans

1 0

RE: Re: Filesystem level backups?
by DurgaPrasad - DatasoftComnet 20 Apr '18

20 Apr '18

Hello all, Does doveadm backup - backup the attachments as well when using SIS ? Regards Durga Prasad +919849111010 -----Original Message----- From: dovecot [mailto:dovecot-bounces@dovecot.org] On Behalf Of Marc Stürmer Sent: 09 April 2018 18:05 To: Steve Atkins Cc: dovecot(a)dovecot.org Subject: {Spam?} Re: Filesystem level backups? Am 2018-04-09 00:55, schrieb Steve Atkins: > Will a simple backup of all the files of an multi-dbox give me a > consistent state when I recover, or do I need to do something (e.g. > lock writes to the mailbox) while I run a backup? If you are doing this backup with a fully operational mail storage: no, it won't. The reason is quite simple: mdbox saves the data of an email in several files, so there's a good chance that those files might slightly change during backup, while with Maildir all necessary data for the restore is stored in the file names. If you want to do a consistent backup, you do need file system snapshots and should make sure that this snapshot is consistent or to turn off the mail store during backup completely. But just doing rsync on the fly as with Maildir is just begging on your side to run into problems sooner or later... -- Greetings, Marc --- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus

3 4