http://dovecot.org/releases/2.0/beta/dovecot-2.0.beta5.tar.gz http://dovecot.org/releases/2.0/beta/dovecot-2.0.beta5.tar.gz.sig Sorry for being so quiet recently. Unfortunately I think it's still going to last a while longer. I'll be in Italy for next two weeks and immediately after that I'll move to Portugal. I'll probably write something about that later to blog. I had hoped that this beta5 would be almost the same as RC1, but I didn't have time to put everything there yet, and thought beta4 is way too old already. The few things that should still be done: - Change expire-tool to be a plugin for doveadm expunge command - doveadm mailbox * commands should use UTF-8 for mailbox names, not mUTF-7 (and add -7, -8 parameters to switch between them) - THREAD command seems to be crashing - some other bugfixes Some of the changes since beta4: - default_login_user is now "dovenull". You should create this user. - imap, pop3 -u <user> now does userdb lookup + changes privileges if necessary, so it's much easier to start imap/pop3 session for a specific user from command line - doveadm has all kinds of new commands and changes - PostgreSQL supports now multiple connections to backend. Also supports load-balancing / HA by specifying multiple host parameters. MySQL and PostgreSQL now share the same code for that. - probably lots of other things I can't think of right now. h
Timo Sirainen <tss at iki.fi> writes: [...]> - PostgreSQL supports now multiple connections to backend. Also > supports load-balancing / HA by specifying multiple host > parameters. MySQL and PostgreSQL now share the same code for that.You don't really need to wonder that your release cycles 'get longer' when you do major feature changes to something you consider to be 'beta' (and not alpha) code just because you cannot stand the fact that other people need to write code to deal with problems in code written by you. BTW, there is no need to now start the usual 'unwanted outsiders attack' flamewar since I am not going to receive it.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Timo Sirainen said the following on 09/05/10 21:27:> http://dovecot.org/releases/2.0/beta/dovecot-2.0.beta5.tar.gz > http://dovecot.org/releases/2.0/beta/dovecot-2.0.beta5.tar.gz.sigI don't know if it is an issue linked to the 2.0 proctitle or what else because I just enabled ssl feature of Dovecot. That said, I am running 2.0B5 in a CentOS 5.4 64 bit. When I have three IMAP user connected via SSL I have this IMAP processes: 27258 ? S 0:00 dovecot/imap-login [1 connections (1 TLS)] 27259 ? S 0:00 dovecot/imap-login [1 connections (1 TLS)] 27263 ? S 0:00 dovecot/imap [A at A 10.x.x.1 IDLE] 27265 ? S 0:00 dovecot/imap [A at A 10.x.x.1 IDLE] 27266 ? S 0:00 dovecot/imap-login [1 connections (1 TLS)] 27267 ? S 0:00 dovecot/imap [A at A 10.x.x.1] 27717 ? S 0:00 dovecot/imap-login [1 connections (1 TLS)] 27719 ? S 0:00 dovecot/imap [B at B 10.x.x.1 IDLE] 27720 ? S 0:00 dovecot/imap-login [1 connections (1 TLS)] 27721 ? S 0:00 dovecot/imap [B at B 10.x.x.1 IDLE] 27722 ? S 0:00 dovecot/imap-login [1 connections (1 TLS)] 27723 ? S 0:00 dovecot/imap [C at C 10.x.x.1 IDLE] 27726 ? S 0:00 dovecot/imap-login [1 connections (1 TLS)] 27727 ? S 0:00 dovecot/imap [A at A 10.x.x.1 IDLE] 27748 ? S 0:00 dovecot/imap-login [1 connections (1 TLS)] 27749 ? S 0:00 dovecot/imap [B at B 10.x.x.1] 27750 ? S 0:00 dovecot/imap-login [1 connections (1 TLS)] 27751 ? S 0:00 dovecot/imap [B at B 10.x.x.1 IDLE] 27752 ? S 0:00 dovecot/imap-login [1 connections (1 TLS)] 27753 ? S 0:00 dovecot/imap [B at B 10.x.x.1 IDLE] 27754 ? S 0:00 dovecot/imap-login [1 connections (1 TLS)] 27755 ? S 0:00 dovecot/imap [B at B 10.x.x.1 IDLE] 27760 ? S 0:00 dovecot/imap-login [1 connections (1 TLS)] 27761 ? S 0:00 dovecot/imap [C at C 10.x.x.1] 27762 ? S 0:00 dovecot/imap-login [1 connections (1 TLS)] 27763 ? S 0:00 dovecot/imap [C at C 10.x.x.1 IDLE] 27764 ? S 0:00 dovecot/imap-login [1 connections (1 TLS)] 27765 ? S 0:00 dovecot/imap [C at C 10.x.x.1 IDLE] 27779 ? S 0:00 dovecot/imap-login [1 connections (1 TLS)] 27780 ? S 0:00 dovecot/imap [C at C 10.x.x.1 IDLE] Isn't there a way to see if a "dovecot/imap [C at C 10.x.x.1 IDLE]" connection is ssl other that looking at the parent process? Ciao, luigi - -- / +--[Luigi Rosa]-- \ Luke: I don't believe it. Yoda: That is why you fail. --Empire Strikes Back -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkvoOfQACgkQ3kWu7Tfl6ZQmWwCghHgAQC449wqiHJFPpsURzx7v 6dYAnRyLtjEj92unMTbjTsY0HFjnOrXk =+NgJ -----END PGP SIGNATURE-----