similar to: Virtual plugin - [SERVERBUG] BUG: Unknown internal error

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

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

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.

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.

I'm trying to follow the guide at https://wiki.dovecot.org/Plugins/Virtual for the 'Conversation' style virtual mailbox, but with a small change. I'd like the virtual mailboxes to be 'top level', which I found while searching through this list is accomplishable by putting the dovecot-virtual file in the root of the namespace location. My issue is this works perfectly

I merged all the new features and latest v1.1 changes under one tree: http://hg.dovecot.org/dovecot-1.2/ The changeset order is kind of weird though. The timestamps jump all around. Wonder if there's a way to reorder them so that it looks more sane.. The status of the new features: 1. CONDSTORE extension is probably the largest change. It adds new "modification sequences" for

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

Hello, I am using the antispam plugin of Dovecot with SpamAssassin and in some cases when users move back mails from the Spam folder to their INBOX (false positive) they get the following error message: [SERVERBUG] failed to send mail Does anyone have an idea what could be the issue here? It is quite annoying as the mail then stays in the Spam folder and can not been re-learnt has ham. Best

Hi all, Long story short, I'd like to configure a folder containing: INBOX (some other folders) -> unseen emails from these folders + all other emails (also seen) from the same thread -> seen emails from these folders, but only the recent ones + all other emails from the same thread I tried: # inthread refs (or (or recent unseen) recent ) inthread refs unseen # inthread

Hehe sure. Here would be the output of dovecot -n on my maibox server: # 2.1.7: /etc/dovecot/dovecot.conf # OS: Linux 3.2.0-4-amd64 x86_64 Debian 7.8 ext4 auth_master_user_separator = * auth_mechanisms = plain login cram-md5 disable_plaintext_auth = no first_valid_uid = 150 last_valid_uid = 150 login_trusted_networks = X.Y.Z.X mail_location = maildir:/var/vmail/%d/%n/Maildir mail_plugins = quota

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

Hello, I had an Inbox with 975,604 emails on ext3 filesystem. I keept getting dropped on the comand "copy 1:2000 inbox2", the syslog gave me an error message indicating "out of memory" problems. This despite the fact that the server has 800MB of ram free. Anyways, I asked if I could manuanlly move the files at the filesystem level or if that would mess up dovecot (break the

Thank you for your helpful hints on debugging this issue. I wanted first to get the mail which generates this error but unfortunately the user already deleted it as well from his trash. Now I got another hint and it looks like this mail had a big attachment to it. Is it possible that spamc generated this error due to the size of the mail? Regards ML On Thursday, January 15, 2015 8:29 AM,

Been experimenting with virtual mailbox and have a question :- I have defined 2 virtual mailboxes 'all' and 'combined' as follows ... virtual/all/dovecot-virtual virtual/combined inthread refs x-mailbox INBOX virtual/combined/dovecot-virtual !INBOX INBOX/Sent INBOX/Drafts all When new mail comes I would assume that both virtual mailboxes should actually see the message

Hello, Timo: on Oct 29th I wrote ---- with latest 2.0.6 (601065674f74), the following virtual mailbox is not behaving correctly. I'm quite sure that the problem has not existed in some earlier 2.0.x (maybe only INBOX as mailbox then though): ~user/Maildir/virtual/.week/dovecot-virtual contains INBOX INBOX.* -INBOX.Trash inthread refs younger 604800 This works as expected for the first

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