dovecot.org/releases/2.2/beta/dovecot-2.2.beta2.tar.gz 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 sync, so it should be pretty efficient also. I've only two things left to do before v2.2.rc1: 1. Implement dsync to work via TCP and TCP+SSL sockets. This is pretty easy to do actually, since it can use the existing doveadm-server to start up. 2. Read up all the pending mails from Dovecot mailing list and fix up the reported issues. Actually I guess most of those are for v2.1, but still I should get around to it. :) There shouldn't be any major bugs left, so I'm expecting v2.2.rc1 out in maybe a week or so, hopefully followed by the final v2.2.0 soon afterwards. Please test and report any bugs found!
I've been running 2.2beta1 in production since it got out and I haven't had any issues. However, my setup is simply IMAP/POP3 without any complicated configurations. This is on FreeBSD 8.3-STABLE with about 100 users. I've just updated to 2.2b2... On 21 February 2013 18:34, Timo Sirainen <tss at iki.fi> wrote:> dovecot.org/releases/2.2/beta/dovecot-2.2.beta2.tar.gz > 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 sync, so it should be > pretty efficient also. > > I've only two things left to do before v2.2.rc1: > > 1. Implement dsync to work via TCP and TCP+SSL sockets. This is pretty > easy to do actually, since it can use the existing doveadm-server to start > up. > > 2. Read up all the pending mails from Dovecot mailing list and fix up the > reported issues. Actually I guess most of those are for v2.1, but still I > should get around to it. :) > > There shouldn't be any major bugs left, so I'm expecting v2.2.rc1 out in > maybe a week or so, hopefully followed by the final v2.2.0 soon afterwards. > Please test and report any bugs found! > >-- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254733744121/+254722743223 _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ I can't hear you -- I'm using the scrambler.
On 21.02.2013, at 16:34, Timo Sirainen <tss at iki.fi> wrote:> A ton of fixes since beta1. Especially the new dsync and the replication server related to that should really work now.I am running v2.2beta1 for almost a week now (handful of users, ~1000 mails/day). And yes, I can confirm that replication works ...> Please test and report any bugs found!... there is only a "feature request" left: I did run a lot of stress tests as mentioned before (simultaneously injected local mail). Whenever I do run those tests with a delay of 1 second between every injection, I do observe, that not all mails injected become visible in my MUAs (Mail.app and Roundcube), immediately. All "get new mail" functionality or MUA restarts fails to fetch those missing messages from both servers. But, if I do restart any one of both dovecot servers involved, those remaining missing messages are fetched instantaneously. It seems to me, as if those missing messages were kept in the "replicator queue" and not delivered to the partner server, and as if that queue became flushed during restart. After restart all injected and replicated messages are accessible by the MUAs. I never waited longer then 10 minutes before restarting dovecot, thus I do not know if I didn't wait long enough. But I can say that an additionally injected local mail shows up in both MUAs but doesn't become replicated. Thus, if I am not mistaken that something like a "flushing" really takes place, I wonder if there is a "doveadm flush replicator-queue" functionality is available already (that I might have over-seen), and if not, would that be a big deal to implement? JFTR and with kind regards, Michael
Il 21/02/2013 16:34, Timo Sirainen ha scritto:> Please test and report any bugs found!Hi, I'm running dovecot 2.2b2 , for the first time, with vpopmail-auth and works fine. But I found this bug, also present in 2.1.15. When I enable dict quota with mysql and in dovecot DB there is no entry for the user, dovecot waits 3 minutes and 30 seconds before create the entry and close telnet session: Feb 22 11:45:26 demo-vpop dovecot: pop3-login: Login: user=<test at alessio.com>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, mpid=18132, secured, session=<6R6m403WlAB/AAAB> Feb 22 11:45:32 demo-vpop dovecot: pop3(test at alessio.com): Disconnected: Logged out top=0/0, retr=0/0, del=1/21, size=9828 Feb 22 11:45:32 demo-vpop dovecot: dict: mysql(localhost): Connected to database dovecot Feb 22 11:46:02 demo-vpop dovecot: pop3(test at alessio.com): Error: read(/usr/local/dovecot-2.2/var/run/dovecot/dict) failed: Timeout after 30 seconds Feb 22 11:46:32 demo-vpop dovecot: pop3(test at alessio.com): Error: read(/usr/local/dovecot-2.2/var/run/dovecot/dict) failed: Timeout after 30 seconds Feb 22 11:47:02 demo-vpop dovecot: pop3(test at alessio.com): Error: read(/usr/local/dovecot-2.2/var/run/dovecot/dict) failed: Timeout after 30 seconds Feb 22 11:47:32 demo-vpop dovecot: pop3(test at alessio.com): Error: read(/usr/local/dovecot-2.2/var/run/dovecot/dict) failed: Timeout after 30 seconds Feb 22 11:48:02 demo-vpop dovecot: pop3(test at alessio.com): Error: read(/usr/local/dovecot-2.2/var/run/dovecot/dict) failed: Timeout after 30 seconds Feb 22 11:48:32 demo-vpop dovecot: pop3(test at alessio.com): Error: read(/usr/local/dovecot-2.2/var/run/dovecot/dict) failed: Timeout after 30 seconds Feb 22 11:49:02 demo-vpop dovecot: pop3(test at alessio.com): Error: read(/usr/local/dovecot-2.2/var/run/dovecot/dict) failed: Timeout after 30 seconds # telnet 0 110 Trying 0.0.0.0... Connected to 0. Escape character is '^]'. +OK Dovecot ready. user test at alessio.com +OK pass ciao +OK Logged in. [...] 21 468 . dele 21 +OK Marked to be deleted. quit +OK Logging out, messages deleted. [ here is waiting for logout 3 minutes] Connection closed by foreign host. LDA as the same problem: Feb 22 12:09:00 demo-vpop dovecot: master: Dovecot v2.2.beta2 starting up (core dumps disabled) Feb 22 12:09:02 demo-vpop dovecot: lda(test at alessio.com): msgid=<20130222110902.20244.qmail at demo-vpop.alessio.com>: saved mail to INBOX Feb 22 12:09:02 demo-vpop dovecot: dict: mysql(localhost): Connected to database dovecot Feb 22 12:09:32 demo-vpop dovecot: lda(test at alessio.com): Error: read(/usr/local/dovecot-2.2/var/run/dovecot/dict) failed: Timeout after 30 seconds Feb 22 12:10:02 demo-vpop dovecot: lda(ale at alessio.it): Error: read(/usr/local/dovecot-2.2/var/run/dovecot/dict) failed: Timeout after 30 seconds Feb 22 12:10:32 demo-vpop dovecot: lda(ale at alessio.it): Error: read(/usr/local/dovecot-2.2/var/run/dovecot/dict) failed: Timeout after 30 second Here is my configuration: # dovecot -n # 2.2.beta2: /usr/local/dovecot-2.2/etc/dovecot/dovecot.conf # OS: Linux 2.6.32-5-amd64 x86_64 Debian 6.0.6 default_login_user = dovecot dict { quota = mysql:/usr/local/dovecot-2.2/etc/dovecot/dovecot-dict-sql.conf.ext } first_valid_gid = 89 first_valid_uid = 89 last_valid_gid = 89 last_valid_uid = 89 mail_location = maildir:~/Maildir mail_plugins = quota managesieve_notify_capability = mailto managesieve_sieve_capability = fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date ihave namespace inbox { inbox = yes location mailbox Drafts { special_use = \Drafts } mailbox Junk { special_use = \Junk } mailbox Sent { special_use = \Sent } mailbox "Sent Messages" { special_use = \Sent } mailbox Trash { special_use = \Trash } prefix } passdb { driver = vpopmail } plugin { quota = maildir:User quota quota2 = dict:User dict::proxy::quota sieve = ~/.dovecot.sieve sieve_dir = ~/sieve } service auth { unix_listener auth-userdb { group = vchkpw mode = 0660 user = vpopmail } } service dict { unix_listener dict { group = vchkpw mode = 0600 user = vpopmail } } ssl_cert = </etc/ssl/certs/dovecot.pem ssl_key = </etc/ssl/private/dovecot.pem userdb { args = quota_template=quota_rule=*:backend=%q driver = vpopmail } protocol imap { mail_plugins = quota imap_quota } I hope can be fixed. Thanks -- Alessio Cecchi is: @ ILS -> linux.it/~alessice on LinkedIn -> linkedin.com/in/alessice Assistenza Sistemi GNU/Linux -> cecchi.biz @ PLUG -> ex-Presidente, adesso senatore a vita, prato.linux.it