similar to: PATCH: Advertise X-REFERENCES2

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

Hi Timo - hope things are well :) Playing around with the CONDSTORE (RFC 4551) stuff while testing the IMAP lib I am writing and I think I have found a bug in Dovecot 1.2. RFC 4551 [4] identifies the FETCH response to a MODSEQ request as follows: fetch-mod-resp = "MODSEQ" SP "(" permsg-modsequence ")" with 'permsg-modsequence' defined as:

Been seeing these occasionally for the last few weeks. Only way to fix is to remove cache files in the affected mailbox. Reproduced with both 1.2.5 and 1.2.6. IMAP transaction: ----------------- * PREAUTH [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE SORT THREAD=REFERENCES THREAD=REFS MULTIAPPEND UNSELECT IDLE CHILDREN NAMESPACE UIDPLUS LIST-EXTENDED I18NLEVEL=1

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

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

>From /opt/src/dovecot-2.2.19/doc/wiki/PasswordDatabase.ExtraFields.Host.txt > Login referrals are an IMAP extension specified by RFC 2221 > [http://www.apps.ietf.org/rfc/rfc2221.html]. They're not supported by many > clients, so you probably don't want to use them normally. Right. > The following clients are known to support login referrals: > > * Pine > *

On 12/03/2015 01:46 PM, sb wrote: > From /opt/src/dovecot-2.2.19/doc/wiki/PasswordDatabase.ExtraFields.Host.txt >> Login referrals are an IMAP extension specified by RFC 2221 >> [http://www.apps.ietf.org/rfc/rfc2221.html]. They're not supported by >> many >> clients, so you probably don't want to use them normally. > Right. >> The following clients are

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

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 {

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

Hello Dovecot community, Below please find a patch that adds support to dovecot-1.2.11 for: - RFC 4467 - IMAP URLAUTH Extension - RFC 4468 - Submission BURL - RFC 4469 - IMAP CATENATE Extension URLAUTH URLAUTH is added as a plugin so it can be disabled to satisfy site security requirements. Each user's URLAUTH keys for all mailboxes are stored in a file named

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

I'm seeing this: 1 UID FETCH 31734 (ENVELOPE) * 23 FETCH (UID 31734 ENVELOPE ("Fri, 2 Mar 2012 19:05:24 -0500 (EST)" "XXXXXX" (({22} XXXXX \"X-XX\" XXXXXX NIL "XXXXXXX" "XXXXXXXXX.XXX")) (({22} XXXXX \"X-XX\" XXXXXX NIL "XXXXXXX" "XXXXXXXXX.XXXXXX.XXX")) ((NIL NIL "XXXXXXX"

An architecture may restrict host access to guest memory. Provide a new Kconfig entry the architecture can select, CONFIG_ARCH_HAS_RESTRICTED_VIRTIO_MEMORY_ACCESS, when it provides the arch_has_restricted_virtio_memory_access callback to advertise VIRTIO common code when the architecture restricts memory access from the host. Signed-off-by: Pierre Morel <pmorel at linux.ibm.com> ---

An architecture may restrict host access to guest memory, e.g. IBM s390 Secure Execution or AMD SEV. Provide a new Kconfig entry the architecture can select, CONFIG_ARCH_HAS_RESTRICTED_VIRTIO_MEMORY_ACCESS, when it provides the arch_has_restricted_virtio_memory_access callback to advertise to VIRTIO common code when the architecture restricts memory access from the host. The common code can then