similar to: Server move complete

Hello Timo, Timo Sirainen <tss at iki.fi> writes: > Thanks, looks like this was broken with Maildir and mbox formats. It > also caused expunges in some other situations to be lost. Fixed: > > https://github.com/dovecot/core/commit/950a6e61d6c2dac961ce031bdd8b2895bc32b827 Thanks a lot for the fix, testing it now! Is this patch suitable of being backported to 2.2.13? (Debian

http://dovecot.org/releases/1.0/dovecot-1.0.6.tar.gz http://dovecot.org/releases/1.0/dovecot-1.0.6.tar.gz.sig * IDLE: Interval between mailbox change notifies is now 1 second, because some clients keep a long-running IDLE connection and use other connections to actually read the mails. * SORT: If Date: header is missing or broken, fallback to using INTERNALDATE (as the SORT draft

http://dovecot.org/releases/1.0/dovecot-1.0.6.tar.gz http://dovecot.org/releases/1.0/dovecot-1.0.6.tar.gz.sig * IDLE: Interval between mailbox change notifies is now 1 second, because some clients keep a long-running IDLE connection and use other connections to actually read the mails. * SORT: If Date: header is missing or broken, fallback to using INTERNALDATE (as the SORT draft

It doesn't in my current 2.2.18 setup with the config I posted. On Mon, Sep 7, 2015 at 5:22 PM, Timo Sirainen <tss at iki.fi> wrote: > It should. > > On 08 Sep 2015, at 01:01, Larry Rosenman <larryrtx at gmail.com> wrote: > > should fts_autoindex handle that case? > > > On Mon, Sep 7, 2015 at 5:00 PM, Timo Sirainen <tss at iki.fi> wrote: >

It works for me. I don't know why it wouldn't work for you. Looking at the autoindexing code I don't see how it could be possible that it works for saving but not copying. > On 10 Sep 2015, at 21:05, Larry Rosenman <larryrtx at gmail.com> wrote: > > Is there a fix coming for this, Timo? Or is it a longer term issue? > > On Mon, Sep 7, 2015 at 5:23 PM, Larry

should fts_autoindex handle that case? On Mon, Sep 7, 2015 at 5:00 PM, Timo Sirainen <tss at iki.fi> wrote: > On 09/08/2015 12:56 AM, Larry Rosenman wrote: > > that the fts data gets lost? > > All full text search backends are now implemented so that if you > copy/move mails, the mails need to be indexed again the destination folder. > > Alternative would be to

I had originally thought that I'd do a complete audit of the Dovecot's sources this weekend, but looks like I didn't. Hopefully I've been writing good enough code that the "1000 EUR for security hole" offer lasts for a long time. :) This release should fix the SSL parameter regeneration problem. There were two changes that were needed to fix it, but I had forgotten the

http://hg.dovecot.org/dovecot-2.0/ I just did the initial commit for master process rewrite, which marks the beginning of Dovecot v2.0. Several things are still missing/broken, but at least I was just able to successfully log in using imap :) I left v1.3 hg tree there for now, but once v2.0 tree is fully usable I'll just delete the v1.3 tree. Note the new dovecot-master-example.conf, which

http://dovecot.org/tmp/dovecot-1.0.2-rc.tar.gz Unless someone finds something broken, I'll release v1.0.2 in a few days. The most important changes since v1.0.1: * dbox isn't built anymore by default. It will be redesigned so it shouldn't be used. + Maildir: Support reading dovecot-uidlist (v3) files created by Dovecot v1.1. - Maildir: "UIDVALIDITY changed" errors

my monthly archive script does: echo `date` start ${i} doveadm mailbox create \#ARCHIVE/${YEAR_LAST_MONTH}/${i} doveadm -f tab mailbox status messages ${i} doveadm move \#ARCHIVE/${YEAR_LAST_MONTH}/${i} mailbox \ ${i} BEFORE ${TODAY} SINCE ${FIRST_LAST_MONTH} doveadm -f tab mailbox status messages ${i} echo `date` done ${i} for each mailbox that has >= 1 message in

I'm a bit too busy nowadays because of school so I haven't had time to look at everyone's bug reports and some other mails. They're still marked as unread in my mailbox, so hopefully I'll get to them soon. And I don't mind you resend them if I don't answer in a few weeks :) Changes: - Fixed maildir syncing errors about wrong UIDs - Maildir was re-read all the time,

v0.99.11 2004-09-04 Timo Sirainen <tss at iki.fi> + 127.* and ::1 IP addresses are treated as secured with disable_plaintext_auth = yes + auth_debug setting for extra authentication debugging + Some documentation and error message updates + Create PID file in /var/run/dovecot/master.pid + home setting is now optional in static userdb + Added mail setting to static userdb - After

Sorry, the authentication problem still wasn't actually fixed in beta6. Now, this time I tested every possible authentication case that it really works. I'll soon create a CVS branch which is going to stabilize into the 1.0 release. I won't add new features there so it shouldn't really get broken anymore, at least because of new features.. So, two changes in this release:

Hi, is there a newer public key available? root at dc:/usr/local/src# gpg --verify dovecot-2.2.29.1.tar.gz.sig dovecot-2.2.29.1.tar.gz gpg: Signature made Wed 12 Apr 2017 12:40:03 PM CEST using DSA key ID 40558AC9 gpg: Can't check signature: public key not found root at dc:/usr/local/src# gpg --search-keys 40558AC9 gpg: searching for "40558AC9" from hkp server keys.gnupg.net (1)

Since there have been so many requests, I guess it's time for beta3 now. There are a couple of issues that I'm still concerned about, but those probably happen with beta2 as well. If you're beginning to see more connection hangs/timeouts with this release, please tell me. * Dotlock code changed to timeout faster in some situations when the lock file is old. + Added support for

Parts of dovecot.org will be down for a few hours while I'm moving to a new server (and to a new ISP as well). The new server won't be virtual anymore, so I'm hoping to get a bit better performance from it as well (the old virtual server had some disk I/O hogs). The DNS records have been using 1 hour TTL for last few days, so this move should be fast for everyone. Thanks to Nebula for

http://dovecot.org/releases/dovecot-1.0.rc20.tar.gz http://dovecot.org/releases/dovecot-1.0.rc20.tar.gz.sig So, rc19 was somewhat broken. How about this version? + dovecot: Added --log-error command line option to log an error, so the error log is easily found. + Added mail_log_max_lines_per_sec setting. Change it to avoid log throttling with mail_log plugin. - Changing message flags

http://dovecot.org/releases/dovecot-1.0.rc20.tar.gz http://dovecot.org/releases/dovecot-1.0.rc20.tar.gz.sig So, rc19 was somewhat broken. How about this version? + dovecot: Added --log-error command line option to log an error, so the error log is easily found. + Added mail_log_max_lines_per_sec setting. Change it to avoid log throttling with mail_log plugin. - Changing message flags

After v1.0 is released, I can finally get back to sane version numbers. But any comments on which one is better: a) Postfix-style: "1.1.UNSTABLE.YYYYMMDD" -> 1.1.0 (stable) b) Odd-even numbering: 1.1.x (unstable) -> 1.2.0 (stable) With a) style the releases could be done by simply copying a nightly snapshot to releases/ directory and announcing the changes since the last

http://dovecot.org/nightly/dovecot-latest.tar.gz Would be nice to get some testing before the actual release. I've now finally gone through all the "TODO" mails in this list and my INBOX and fixed pretty much every problem I know of. There are still some mbox bugs, but I can't really get them fixed unless someone figures out how to reproduce them