similar to: Outlook 2007 & 2010 hangs in v2.2?

http://dovecot.org/releases/2.2/beta/dovecot-2.2.beta2.tar.gz http://dovecot.org/releases/2.2/beta/dovecot-2.2.beta2.tar.gz.sig A ton of fixes since beta1. Especially the new dsync and the replication server related to that should really work now. It also works correctly now for shared mailboxes with private \Seen flags. And the replication server uses incremental syncing after the initial full

http://dovecot.org/releases/2.2/beta/dovecot-2.2.beta2.tar.gz http://dovecot.org/releases/2.2/beta/dovecot-2.2.beta2.tar.gz.sig A ton of fixes since beta1. Especially the new dsync and the replication server related to that should really work now. It also works correctly now for shared mailboxes with private \Seen flags. And the replication server uses incremental syncing after the initial full

Hi everyone, While examining dovecot versions v2.1 and v2.2 for their lucene search performances, I have noticed a huge difference in the index sizes created by them. Both versions were compiled on same system, against same libclucene, same configure options and were used with same dovecot.conf during run-time. I deleted the lucene-indexes folder and dovecot* files in the Maildir prior to

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, I'm using a postgres dict for ACL, when when use deleteacl or setacl I get a "not connected" error and (v2.2) Panic: file driver-pgsql.c: line 84 (driver_pgsql_set_state): assertion failed: (state == SQL_DB_STATE_BUSY || db->cur_result == NULL) and a rawdump eventually. You can trigger the error with the "dict"

Hi Timo http://hg.dovecot.org/dovecot-2.2/rev/1f3f21081ee5 : man pages: Updated v2.1 -> v2.2 dovecot.1.in now references a inexistent "LGPLv2.2" instead of "LGPLv2.1"

http://dovecot.org/releases/2.2/alpha/dovecot-2.2.alpha1.tar.gz http://dovecot.org/releases/2.2/alpha/dovecot-2.2.alpha1.tar.gz.sig I wanted to start stabilizing v2.2 release some months ago already, but I somehow got stuck adding more and more features. Now it looks like all of the necessary API changes are done, so everything I'm planning on near future can still be added to v2.2 without

http://dovecot.org/releases/2.2/alpha/dovecot-2.2.alpha1.tar.gz http://dovecot.org/releases/2.2/alpha/dovecot-2.2.alpha1.tar.gz.sig I wanted to start stabilizing v2.2 release some months ago already, but I somehow got stuck adding more and more features. Now it looks like all of the necessary API changes are done, so everything I'm planning on near future can still be added to v2.2 without

Here's a list of things I've been thinking about implementing for Dovecot v2.2. Probably not all of them will make it, but I'm at least interested in working on these if I have time. Previously I've mostly been working on things that different companies were paying me to work on. This is the first time I have my own company, but the prioritization still works pretty much the same

I've been planning on adding these for years. Maybe it's about time soon. I guess they could be added already to v2.2, but enabled only by a new setting because it requires file format changes that old Dovecots can't then read. I could probably patch v2.1 also so it is able to at least read the new format without failing. For v2.3 this new format could then be made the default. And

My understanding of the man page description of --exclude vs. --include is that the list of these is kept in order, and file names are searched against these parameters in that order for the first that matches and that one makes the decision. It doesn't seem to be working exactly as expected. But there is a factor involved that's making it unclear, which is whether or not *'s should

http://dovecot.org/releases/2.1/dovecot-2.1.9.tar.gz http://dovecot.org/releases/2.1/dovecot-2.1.9.tar.gz.sig I've again mostly finished reading and answering most of the mails in Dovecot mailing list. There are a couple annoyingly difficult / time consuming bugreport mails that I haven't replied to yet, but if anyone thinks I should have replied to something already feel free to resend

http://dovecot.org/releases/2.1/dovecot-2.1.9.tar.gz http://dovecot.org/releases/2.1/dovecot-2.1.9.tar.gz.sig I've again mostly finished reading and answering most of the mails in Dovecot mailing list. There are a couple annoyingly difficult / time consuming bugreport mails that I haven't replied to yet, but if anyone thinks I should have replied to something already feel free to resend

Hi all, We have put together a firmware for a range of inexpensive routers. It has been configured to provide optimum VoIP performance. We have internally tested it for number of months and it looks very good. You should be able to run it easily with 20+ phones on local network ( we still did not hit the upper limit ) assuming that you have bandwidth. Your VoIP will get prioritized over other

Hello all, Long time, no write :-) I am building a spanking, wonderful new mail server. I am very excited about this, since I am going to use the new dovecot v2.2.12 !! However, last time I did this (and documented it), I was working with v1.2. I consulted my notes and it seems there are huge differences between v1.2 and v2.2. So my question is, would anyone know if there's a "quick

Hi, For our testing enthusiasts I've created new automatic Debian repositories for Dovecot v2.2. Repositories are available for Debian oldstable, stable and testing, on both i386 and am64. Read the following wiki item for more information: http://wiki2.dovecot.org/PrebuiltBinaries#Automatically_Built_Packages The repository for Dovecot v1.2 has been defunct for a few months now and is

Hi Function imap_envelope_parse return incorrect result for addresses with groups due to error in imap_address_arg_append because of with ", " is added after group name and before first mailbox. Patch for dovecot v2.1 in attach. -------------- next part -------------- A non-text attachment was scrubbed... Name: imap-envelope.patch Type: application/octet-stream Size: 1455 bytes Desc:

Currently if user is 1MB under quota and someone tries to deliver mail that is over 1MB, Dovecot rejects the mail. But smaller mails aren't rejected probably for days. So user might not even realize that they didn't receive one of the mails. Also having a user "almost over quota" is a rather strange state I think. So what do you think about v2.2 allowing delivery of one last

http://dovecot.org/releases/2.2/rc/dovecot-2.2.rc1.tar.gz http://dovecot.org/releases/2.2/rc/dovecot-2.2.rc1.tar.gz.sig A few fixes since beta2. Also added tcp and tcps (=tcp+ssl) targets for dsync, where the destination needs to be a doveadm-server listener. I'm planning on releasing v2.2.0 in 1-2 weeks if no major problems are found. Please test and report any bugs found. BTW. I've

http://dovecot.org/releases/2.2/rc/dovecot-2.2.rc1.tar.gz http://dovecot.org/releases/2.2/rc/dovecot-2.2.rc1.tar.gz.sig A few fixes since beta2. Also added tcp and tcps (=tcp+ssl) targets for dsync, where the destination needs to be a doveadm-server listener. I'm planning on releasing v2.2.0 in 1-2 weeks if no major problems are found. Please test and report any bugs found. BTW. I've

http://dovecot.org/releases/2.2/beta/dovecot-2.2.beta1.tar.gz http://dovecot.org/releases/2.2/beta/dovecot-2.2.beta1.tar.gz.sig Lots of fixes since 2.2.alpha1, especially related to dsync. Also dsync now supports syncing private message flags when INDEXPVT is used. Here's again the list of all the major changes in v2.2: * When creating home directories, the permissions are copied from the