similar to: THREAD X-REFERENCES2 index bug?

Don't see any reason why X-REFERENCES2 should not be advertised in the CAPABILITY string - the wiki indicates this is a new addition for 1.2, and RFC 5256 explicitly states that the THREAD= is to be used for upwards-compatible extensions. # HG changeset patch # User root at bigworm.curecanti.org # Date 1225057043 21600 # Branch HEAD # Node ID 1f082281f8d4e3d364b85c08ec329cf1be7ba61f #

/etc/dovecot/virtual/Inbox2/dovecot-virtual * -Trash -Trash/* -Deleted* -Junk* inthread x-references2 x-mailbox INBOX Using php to connect o {host}virtual/Inbox2 gives me [SERVERBUG] BUG: Unknown internal error. If I connect to virtual/Allmail which has "all" instead of the inthread line it works.

Hi folks, there's an extension [1] to IMAP specifying the THREAD command to return list of message sequence numbers grouped to indicate the threading of them. That draft currently defines two algorithms, one of them based solely on Subjects (which is rather dumb) and the second one, combining Subjects with In-Reply-To (etc) headers. The second method is actually advertised and supported by

First a list of all the new features and their state: 1. http://hg.dovecot.org/dovecot-threadindexes/ THREAD=REFERENCES indexes. Missing NFS flushes, support for mmap_disable=yes, breaks when more than one session modifies at the same time. Not tested much if the replies are really correct at all. Also started THREAD=X-REFERENCES2 but it doesn't work as expected. 2.

http://dovecot.org/releases/1.1/alpha/dovecot-1.1.alpha2.tar.gz http://dovecot.org/releases/1.1/alpha/dovecot-1.1.alpha2.tar.gz.sig Hopefully the next release can be v1.1.beta1. I'm not aware of any major problems and I think I'm pretty much done with new features (except for dbox). The largest changes since alpha1: * Removed THREAD indexing. It's a bit buggy and I think

http://dovecot.org/releases/1.2/rc/dovecot-1.2.rc1.tar.gz http://dovecot.org/releases/1.2/rc/dovecot-1.2.rc1.tar.gz.sig I think it's time to get v1.2.0 out soon. Shared mailbox code is beginning to look like it's working and other features should work fine also. I don't really see any reasons to delay it, so please start testing and let's get the last bugs found and fixed quickly.

http://dovecot.org/releases/1.2/rc/dovecot-1.2.rc1.tar.gz http://dovecot.org/releases/1.2/rc/dovecot-1.2.rc1.tar.gz.sig I think it's time to get v1.2.0 out soon. Shared mailbox code is beginning to look like it's working and other features should work fine also. I don't really see any reasons to delay it, so please start testing and let's get the last bugs found and fixed quickly.

http://dovecot.org/releases/1.2/alpha/dovecot-1.2.alpha1.tar.gz http://dovecot.org/releases/1.2/alpha/dovecot-1.2.alpha1.tar.gz.sig This is the only v1.2.alpha announcement I'm going to send to dovecot-news list. Next announcement will be for either v1.2.beta1 or v1.2.rc1. I'm hoping that v1.2 stabilizes pretty soon. There are no huge changes like there were in 0.99->1.0 or

http://dovecot.org/releases/1.2/alpha/dovecot-1.2.alpha1.tar.gz http://dovecot.org/releases/1.2/alpha/dovecot-1.2.alpha1.tar.gz.sig This is the only v1.2.alpha announcement I'm going to send to dovecot-news list. Next announcement will be for either v1.2.beta1 or v1.2.rc1. I'm hoping that v1.2 stabilizes pretty soon. There are no huge changes like there were in 0.99->1.0 or

http://dovecot.org/releases/1.1/alpha/dovecot-1.1.alpha1.tar.gz http://dovecot.org/releases/1.1/alpha/dovecot-1.1.alpha1.tar.gz.sig This is the first alpha release of Dovecot v1.1. I hope that it stabilizes into final release within a few months. There are a lot of new features since v1.0. The most important ones are listed at the end of this post. This is the only v1.1.alpha announcement I send

http://dovecot.org/releases/1.1/alpha/dovecot-1.1.alpha1.tar.gz http://dovecot.org/releases/1.1/alpha/dovecot-1.1.alpha1.tar.gz.sig This is the first alpha release of Dovecot v1.1. I hope that it stabilizes into final release within a few months. There are a lot of new features since v1.0. The most important ones are listed at the end of this post. This is the only v1.1.alpha announcement I send

Hello, I finally got an INBOX to work, but is virtual mailbox plugin only meant to create a virtual inbox, or should I be able to have an Allmails virtual folder that is viewable in my imap client? if ~/virtual/ is my location, would I create an Allmails directory in the virtual/ or virtual/INBOX/Allmails. Im fairly confused on how this is suppose to work. I was trying to duplicate the gmail-like

Hi, I'm using dovecot 1.2rc2 and I have the following issues with the virtual folder: 1. The virtual folders are flagged with \Noselect and at least thunderbird does not offer to select them. Adding them to the subscriptions file works fine and the folder can be used after that. 2. Two basic virtual work just fine like: $ cat virtual/all/dovecot-virtual INBOX INBOX.Ordner.work.archive.*

Getting these Warning: imap <brandonl at pacwebdev.com>: Timeout leak: 0x461bd0 /etc/dovecot/virtual/Allmail/dovecot-virtual * -Trash -Trash/* all /etc/dovecot/virtual/INBOX/dovecot-virtual virtual/Allmail inthread x-references2 x-mailbox INBOX /etc/dovecot/dovecot.conf namespace private { prefix = "" separator = / list = yes hidden = yes } namespace private {

I think I won't do any actual releases until it's mostly feature complete. Then maybe v1.1.alpha1 or v1.1.beta1. So if you want to test it before then, use CVS or the nightly snapshots. I'm planning on keeping v1.1 almost completely compatible with v1.0. There could be some minor configuration file changes, but for most people v1.0's dovecot.conf should work with v1.1. I want to

v1.1.0 is finally getting closer, so it's time to start planning what happens after it. Below is a list of some of the larger features I'm planning on implementing. I'm not yet sure in which order, so I think it's time to ask again what features companies would be willing to pay for? Sponsoring Dovecot development gets you: - listed in Credits in www.dovecot.org - listed in

Hello all, We currently have a java web utility that allows multi-threaded data analysis using S+. We want to migrate it to R. However, the guy who preceded me here left some documentation indicating that he couldn't implement it because R didn't support threading. Also, he noted that the R-Java interface(org.omegahat.R.Java.REvaluator) wasn't thread safe even if R was. Can

Supermicro X7DWN+, XEON 5410, Centos 5.2, Xen 3.2.1 At what looks like random times network traffic over xen bridge stops working, the only way I found to fix it is a reboot. This sometimes takes 10 min, other times it may be up for 10 days. This happened with default xen that comes with RedHat EL 5.2 as well as a default install of Fedora 8. Any ideas? ><> Nathan Stratton

Hello, What is for you the best GlusterFS scenario in using XenServer (i'm not talking about Xen on a linux but XenServer baremetal) for a web farm (Apache-Tomcat) ? I were thinking of using ZFS as the filesystem for the different nodes. The objectives/needs : * A storage cluster with the capacity equal to at least 1 node(assuming all nodes are the same). * being able to lose/take down any

Hey, we''re currently using shoulda (http://dev.thoughtbot.com/ shoulda/) on a project and I saw some things that would be really nice to see in rspec, namely the should_ methods, and especially the should_be_restful method. Do these go against the rspec goals at all? Or could an ambitious programmer go to town implementing these for rspec_on_rails? Nathan Sutton fowlduck at