- dovecot - dovecot.org

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

massive mail move
by David Mehler 20 Apr '18

20 Apr '18

Hello, I've got dovecot 2.3 going and a mailbox with a lot of system messages in it. What I'm wanting to do is massively move them to another mailbox. Is this doable with sieve? Thanks. Dave.

2 2

maildir vs dbox?
by David Mehler 20 Apr '18

20 Apr '18

Hello, I've got a Dovecot virtual email setup using maildir as the mailbox format. I am wondering from others who have chosen dbox a comparison between maildir and dbox or those who have migrated from one format to another. I am wondering if changing to dbox would be beneficial? Thanks. Dave.

4 3

Replication between servers with different mail_home path
by Arie Peterson 19 Apr '18

19 Apr '18

Hi, I have two dovecot servers that are configured to be replicated using dsync over ssh. This has been working well for a long time. Recently I changed the mail_home path on one of the servers, because of mail data migration. The old file system is still available, but has been made read-only for now – I plan to remove it once everything runs smoothly again. Now it seems replication is failing: the mail.err log file on both servers has lots of error messages saying that it tried to open a file on the old location and failed because it is read-only. Is this setup, with different mail_home paths on the two servers being replicated, even supported? If so, do I need to specify this explicitly in the configuration? I couldn't find relevant settings in the documentation.

1 0