similar to: New index file code

A bit quiet here, so here's some more thoughts about indexes. Even though I was thinking only how to make them usable with NFS (I wrote it to doc/nfs.txt), it then occured to me that exactly the same tricks would help with local filesystem indexes as well. Especially the lockless reading would help with lock contention issues I was worrying about earlier with shared mailboxes. Also it occured

I've been doing some thinking on a new better mailbox format that'd be faster than mbox and maildir for most common uses. Comments welcome. It won't come to Dovecot v1.0, but I'll probably create another branch to Dovecot CVS where I'll start implementing it and some other possibly destabilizing changes. Generic ------- The point is to have a mailbox format where the mailbox

Although Dovecot is already read-lockless and it uses only short- lived write locks, it's be really nice to just get rid of the locking completely. :) I just figured out that O_APPEND is pretty great. If the operating system updates seek position after writing to a file opened with O_APPEND, writes to Dovecot's transaction log file can be made lockless. I see that this works with

Updated version. The previous one was a bit too complicated with flag updates for pretty minimal benefits. Changes: - writing/reading mail flags can be disabled to get better performance without it requiring any changes to how the files are normally handled (so mixed more works fine). - writing flags now requires getting shared locks. so there's the overhead of locking but flag writers

http://dovecot.procontrol.fi/test/ I think I've fixed the problems that were corrupting indexes with the new code. It happened every time you had expunged some messages and new messages arrived. I think this release might actually work :) disable_plaintext_auth = yes will be default from now on. It allows plaintext authentication from localhost (127.*, ::1) however. I just figured out

This is about how to implement multiple msgs/file dbox format. The current v1.1's one msg/file design would stay pretty much the same and it would be compatible with this new design. dbox directories with multiple msgs/file would be like: ~/dbox/storage/ has the actual mail data for all mailboxes ~/dbox/mailboxes/ has subdirectories containing mailboxes and their indexes Also since dbox

On 2018-02-23 (16:47 MST), Joseph Tam <jtam.home at gmail.com> wrote: > > On Fri, 23 Feb 2018, @lbutlr wrote: > >> $ doveadm -f table fetch -u kremels 'hdr.message-id guid uid >> hdr.x-listname' mailbox "Archive" | sort| awk 'cnt[$1]++{if >> (cnt[$1]==2) print prev[$1]; print} {prev[$1]=$0}' |grep -E "[0-9] +$" >> |awk

Fixes a lot of bugs. The next release will be the first "release candidate" instead of a beta. * PAM: Don't call pam_setcred() unless setcred=yes PAM passdb argument was given. * Moved around settings in dovecot-example.conf to be in more logical groups. + Local delivery agent (deliver binary) works again. + LDAP: Added support for SASL binding. Patch by Geert Jansen +

Fixes a lot of bugs. The next release will be the first "release candidate" instead of a beta. * PAM: Don't call pam_setcred() unless setcred=yes PAM passdb argument was given. * Moved around settings in dovecot-example.conf to be in more logical groups. + Local delivery agent (deliver binary) works again. + LDAP: Added support for SASL binding. Patch by Geert Jansen +

Hi. doveadm -D fetch -u login \ 'imap.envelope imap.bodystructure size.virtual date.received' '*' according to mail archives allows to regenerate indexes and precache specified headers for imap usage. What headers are needed for dovecot pop3 daemon? I have one server where dovecot works for imap only. For pop3 there is different software being used. I want to migrate to

http://dovecot.org/releases/2.2/rc/dovecot-2.2.28.rc2.tar.gz http://dovecot.org/releases/2.2/rc/dovecot-2.2.28.rc2.tar.gz.sig I'm assuming that most of the bugs are now found and fixed, so the final 2.2.28 should be out in a day or two. Changes since rc1: * Reverted [UNKNOWN-CTE] -> [PARSE] change + pop3c: Added pop3c_features=no-pipelining setting to prevent using PIPELINING extension

http://dovecot.org/releases/2.2/rc/dovecot-2.2.28.rc2.tar.gz http://dovecot.org/releases/2.2/rc/dovecot-2.2.28.rc2.tar.gz.sig I'm assuming that most of the bugs are now found and fixed, so the final 2.2.28 should be out in a day or two. Changes since rc1: * Reverted [UNKNOWN-CTE] -> [PARSE] change + pop3c: Added pop3c_features=no-pipelining setting to prevent using PIPELINING extension

I don't think anyone uses dbox currently, so the whole format could still be redesigned. So I was thinking about doing two major changes: 1. Rely on index files a lot more. The flags are already stored in index files, so there's no need to waste I/O updating them to dbox files all the time. They could still be updated (if indexes get deleted, the flags aren't all gone), but less

http://dovecot.org/releases/2.2/dovecot-2.2.28.tar.gz http://dovecot.org/releases/2.2/dovecot-2.2.28.tar.gz.sig * director: "doveadm director move" to same host now refreshes user's timeout. This allows keeping user constantly in the same backend by just periodically moving the user there. * When new mailbox is created, use initially INBOX's dovecot.index.cache

http://dovecot.org/releases/2.2/dovecot-2.2.28.tar.gz http://dovecot.org/releases/2.2/dovecot-2.2.28.tar.gz.sig * director: "doveadm director move" to same host now refreshes user's timeout. This allows keeping user constantly in the same backend by just periodically moving the user there. * When new mailbox is created, use initially INBOX's dovecot.index.cache

https://dovecot.org/releases/2.2/dovecot-2.2.31.tar.gz https://dovecot.org/releases/2.2/dovecot-2.2.31.tar.gz.sig This should be a great and stable release for the summer :) v2.2.32 is planned for the end of August. Hopefully soon afterwards we can get back to v2.3. * LMTP: Removed "(Dovecot)" from added Received headers. Some installations want to hide it, and there's not

https://dovecot.org/releases/2.2/dovecot-2.2.31.tar.gz https://dovecot.org/releases/2.2/dovecot-2.2.31.tar.gz.sig This should be a great and stable release for the summer :) v2.2.32 is planned for the end of August. Hopefully soon afterwards we can get back to v2.3. * LMTP: Removed "(Dovecot)" from added Received headers. Some installations want to hide it, and there's not

hi there... i HAVE practically searched in ALL messages from 2004 year, and haven't any luck with this problem, so I'm inserting here "dovecot.conf" content: ## Dovecot 1.0 configuration file # Default values are shown after each value, it's not required to uncomment # any of the lines. Exception to this are paths, they're just examples # with real defaults being based

On Tue, Jun 20, 2017 at 12:45 PM, Timo Sirainen <tss at iki.fi> wrote: > https://dovecot.org/releases/2.2/rc/dovecot-2.2.31.rc1.tar.gz > https://dovecot.org/releases/2.2/rc/dovecot-2.2.31.rc1.tar.gz.sig > > Unless new bugs are found, this will be the final v2.2.31 release, which > will be released on Monday. > > * LMTP: Removed "(Dovecot)" from added Received

https://dovecot.org/releases/2.2/rc/dovecot-2.2.31.rc1.tar.gz https://dovecot.org/releases/2.2/rc/dovecot-2.2.31.rc1.tar.gz.sig Unless new bugs are found, this will be the final v2.2.31 release, which will be released on Monday. * LMTP: Removed "(Dovecot)" from added Received headers. Some installations want to hide it, and there's not really any good reason for anyone to