similar to: 0.99.10.5 released

http://people.redhat.com/wtogami/temp/dovecot/ dovecot-0.99.10.5 binary packages for FC1 and FC2 are available here. I need feedback from Fedora users with THESE ACTUAL BINARIES before pushing them to official updates. Note: This does not solve the SSL related crash issue. That requires a patch to OpenSSL or kernel. I am still trying to convince the maintainers to patch it. Warren Togami

On Apr 7, 2017, at 11:17 AM, Aki Tuomi <aki.tuomi at dovecot.fi> wrote: >> On April 7, 2017 at 6:00 PM "Daniel J. Luke" <dluke at geeklair.net> wrote: >> On Apr 7, 2017, at 3:01 AM, Aki Tuomi <aki.tuomi at dovecot.fi> wrote: >>>> On April 7, 2017 at 9:38 AM Timo Sirainen <tss at iki.fi> wrote: >>>> On 7 Apr 2017, at 2.25, Daniel

On Apr 7, 2017, at 3:01 AM, Aki Tuomi <aki.tuomi at dovecot.fi> wrote: >> On April 7, 2017 at 9:38 AM Timo Sirainen <tss at iki.fi> wrote: >> On 7 Apr 2017, at 2.25, Daniel J. Luke <dluke at geeklair.net> wrote: >>> >>> On Apr 6, 2017, at 1:33 PM, Timo Sirainen <tss at iki.fi> wrote: >>>> Planning to release v2.2.29 on Monday.

On 7 Apr 2017, at 2.25, Daniel J. Luke <dluke at geeklair.net> wrote: > > On Apr 6, 2017, at 1:33 PM, Timo Sirainen <tss at iki.fi> wrote: >> Planning to release v2.2.29 on Monday. Please find and report any bugs before that. > > I'm seeing still seeing the assert that started showing up for me with 2.2.28

http://dovecot.org/releases/2.2/rc/dovecot-2.2.29.rc1.tar.gz http://dovecot.org/releases/2.2/rc/dovecot-2.2.29.rc1.tar.gz.sig Planning to release v2.2.29 on Monday. Please find and report any bugs before that. * When Dovecot encounters an internal error, it logs the real error and usually logs another line saying what function failed. Previously the second log line's error message was

http://dovecot.org/releases/2.2/rc/dovecot-2.2.29.rc1.tar.gz http://dovecot.org/releases/2.2/rc/dovecot-2.2.29.rc1.tar.gz.sig Planning to release v2.2.29 on Monday. Please find and report any bugs before that. * When Dovecot encounters an internal error, it logs the real error and usually logs another line saying what function failed. Previously the second log line's error message was

http://dovecot.org/releases/2.1/dovecot-2.1.0.tar.gz http://dovecot.org/releases/2.1/dovecot-2.1.0.tar.gz.sig Here's finally the the stable v2.1 release. I expect this release to be quite stable, since it's already being used in several large installations. Changes since rc7: FS layout related crashfix, two man pages added. The biggest changes since v2.0: * Plugins now use UTF-8

http://dovecot.org/releases/2.1/dovecot-2.1.0.tar.gz http://dovecot.org/releases/2.1/dovecot-2.1.0.tar.gz.sig Here's finally the the stable v2.1 release. I expect this release to be quite stable, since it's already being used in several large installations. Changes since rc7: FS layout related crashfix, two man pages added. The biggest changes since v2.0: * Plugins now use UTF-8

Is there anything that can be done so that when users IMAP to their inbox and have reached their filesystem quota, that they can still DELETE their mail? They can login, but when they go to delete/expunge this is the error I get in syslog. I have tried mail_read_mmaped to yes and no, and same result. Mar 25 14:54:27 penguin1 imap(bob): file_set_size() failed with index data file

On Apr 7, 2017, at 11:54 AM, Aki Tuomi <aki.tuomi at dovecot.fi> wrote: > So.. as workaround, you *could* move indexes to separate directory, using INDEXES= parameter. And move the lucene-indexes to this folder. But thank you, this helps a bit. I'm happy to do anything else to test if you'd like. I did go ahead and set INDEXES and can confirm that this does work around the bug.

Is there any good rpm source for latest spamassassin for centos/rhel ? Currently using from dag's, but is is a bit old version nowdays. -- Eero

http://dovecot.org/releases/2.1/dovecot-2.1.2.tar.gz http://dovecot.org/releases/2.1/dovecot-2.1.2.tar.gz.sig There are a ton of proxying related improvements in this release. You should now be able to do pretty much anything you want with Dovecot proxy/director. This release also includes the initial version of dsync-based replication. I'm already successfully using it for @dovecot.fi

http://dovecot.org/releases/2.1/dovecot-2.1.2.tar.gz http://dovecot.org/releases/2.1/dovecot-2.1.2.tar.gz.sig There are a ton of proxying related improvements in this release. You should now be able to do pretty much anything you want with Dovecot proxy/director. This release also includes the initial version of dsync-based replication. I'm already successfully using it for @dovecot.fi

http://dovecot.org/rc/ Thought I'd still make one 0.99.10.x release now that mbox corruption problems are (hopefully) fixed. Please test, if no problems are found this will be the final 0.99.10.5. Changes since .4: + MySQL authentication, patch by Matthew Reimer - mbox: APPEND reversed given \Draft and \Deleted flags - mbox: "LF not found" errors happened sometimes when

http://togami.com/~warren/archive/2003/evolution-1.4.4-crash.mbox I suspect that dovecot-0.99.10 is misserving this message in some way that is confusing some IMAP clients. This behavior causes evolution-1.4.4 to segfault, and squirrelmail-1.4.1 to be unable to read the message. The same message served by uw-imapd works works fine in both evolution and squirrelmail.

> On April 7, 2017 at 6:48 PM "Daniel J. Luke" <dluke at geeklair.net> wrote: > > > On Apr 7, 2017, at 11:17 AM, Aki Tuomi <aki.tuomi at dovecot.fi> wrote: > >> On April 7, 2017 at 6:00 PM "Daniel J. Luke" <dluke at geeklair.net> wrote: > >> On Apr 7, 2017, at 3:01 AM, Aki Tuomi <aki.tuomi at dovecot.fi> wrote: >

greetings, have been google foo for week or so. used to be super easy to upgrade spamassassin on CentOS dist. just grab the tarball and put in right spot and rpmbuild -tb spamassassin-3.somethingsomething.tar.gz then rpm or yum install and done would take just a few minutes. Yet... in regards to EL4 / CentOS 4 and spamassassin, it appears the end of the road for .spec in SA tarball

http://dovecot.org/rc/ Just a few more changes: - --with-moduledir option to configure - compile fix to Solaris 10 - mbox syncing complains if mbox is modified while we have it locked and something goes wrong (lock settings are wrong) - maildir: RENAME xx inbox.xx makes sure INBOX is uppercased. - "RAND_bytes() failed:" SSL "fix" for fedora/redhat -------------- next

> On April 7, 2017 at 6:00 PM "Daniel J. Luke" <dluke at geeklair.net> wrote: > > > On Apr 7, 2017, at 3:01 AM, Aki Tuomi <aki.tuomi at dovecot.fi> wrote: > >> On April 7, 2017 at 9:38 AM Timo Sirainen <tss at iki.fi> wrote: > >> On 7 Apr 2017, at 2.25, Daniel J. Luke <dluke at geeklair.net> wrote: > >>> >

/etc/postfix/main.cf.default: mailbox_delivery_lock = flock, dotlock Is flock equivalent to dovecot's fnctl locking? For mbox what type of locking settings should I be using? (No NFS, only local filesystem.) Warren Togami warren at togami.com