similar to: IMAP threading - the THREAD command

Hi all, $ sudo dovecot --version 1.2.beta3 I just started using Dovecot a few weeks ago, and my client is also using the X-REFERENCES2 thread algorithm. The client is misbehaving when trying to list messages in my INBOX, but only when a threaded message exists. I have tracked it down to the thread index that Dovecot is returning, but the problem is only extant when using the X-REFERENCES2

/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.

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 #

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.

>>> Hi all >>> >>> Thanks to Milan I am able to get further with xen and reiser4 >>> >>> - In swap line 6 and 7 status_flags.c >>> >>> #include <linux/bio.h> >>> #include <linux/page-flags.h> >>> >>> >>> - PACKED is redefined, but the definitions are the same, so the gcc >>>

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.

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

First off I just want to pass on a big thank you to everyone who has worked on the win32 packages, they have helped me numerous times. But (of course you knew it had to be coming :-)... I have just started doing some work with win32-service -- I was creating a wrapper around it and daemon.rb, so I could write one body of code that depending upon platform would provide a reasonable interface for

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

Hi Jim, Thanks for putting in the effort here. It's never a good situation to have to moderate, but sometimes it is necessary. >From my perspective, this kind of thing happens far more often than the current example, though maybe not with such intensity. This situation forces me to evaluate if replying to any message on this list is going to be worth the headache of the inevitable noise

Hi, The thread titled "Another Fedora Decision" is rapidly turning into a political and opinion driven flame fest that is unsuited for the CentOS mailing list. This list should try and remain focused on CentOS, what we have and keep the area sane for new users as well as old hands to participate in a fair and thoughtful conversation around the CentOS Linux platform and the CentOS

Hi all, I have a strange problem and rigth now I can't figure out a solution. Trying to calculate an ANOVA with one between subject factor (group) and one within (hemisphere). My dependent variable is source localization (data). My N = 25. My data.frame looks like this: > ML.dist.stack subj group hemisphere data 1 1 tin left 0.7460840 2 2 tin left

I don''t know whether this is a bug or feature, and I don''t know whether this belongs to Gmailer (http://rubyforge.org/projects/gmailutils) in specific or Rails/Ruby in general. I have an instance method in an ActiveRecord model, that upon a web request using WEBrick, spawns off a thread, in which it invokes Gmailer to perform some processing. What fails is that simply

server: ms 2003 with ads client: debian 3.1/samba 3.0.14 smb.conf: .. [global] workgroup = SP-GRUPPE password server = 10.85.117.150 realm = SP-GRUPPE.DE encrypt passwords = no server string = %h server (Samba %v) obey pam restrictions = yes passdb backend = tdbsam, guest passwd program = /usr/bin/passwd %u passwd chat = *Enter\snew\sUNIX\spassword:* %n\n *Retype\snew\sUNIX\spassword:* %n\n .

Hello I'm looking for a way to manually break threads apart when independent threads are mixed up, mostly by users which aren't aware that they should not be replying to existing threads when starting a new one. Since Thunderbird afaik does the threading itself, it would require a solution that actually changes the In-Reply-To header (and maybe also that other (non-standard?) header