similar to: v2.0.17 released

http://dovecot.org/releases/2.1/rc/dovecot-2.1.rc1.tar.gz http://dovecot.org/releases/2.1/rc/dovecot-2.1.rc1.tar.gz.sig I'll probably release v2.1.0 pretty soon, unless people report some new bugs. I know v2.1 is already being used to serve mails to tens (or hundreds?) of thousands of users, so it should be pretty stable. Most of the changes since v2.1.beta1 have been for rather small

http://dovecot.org/releases/2.1/rc/dovecot-2.1.rc1.tar.gz http://dovecot.org/releases/2.1/rc/dovecot-2.1.rc1.tar.gz.sig I'll probably release v2.1.0 pretty soon, unless people report some new bugs. I know v2.1 is already being used to serve mails to tens (or hundreds?) of thousands of users, so it should be pretty stable. Most of the changes since v2.1.beta1 have been for rather small

Dovecot users list, I started having problems with Outlook not syncing with Dovecot a public imap folder upon issuing a send/receive in the client; eventually Outlook timed out, and I received the following error in the Dovecot log. Jan 23 09:20:23 imap(user at mydom.com): Error: FETCH [] for mailbox projects.myfolder UID 120 got too little data: 7744 vs 7759 Jan 23 09:20:23 imap(user at

Hello! I'm having two issues building dovecot, one is with dbox storage, and another building gnutls as the SSL backend (builds fine with openssl). Software versions are Dovecot v2.0.0, GnuTLS 2.8.6 and OpenSSL 1.0.0a Configure: ./configure --prefix=/usr --sysconfdir=/etc/dovecot --localstatedir=/var --libexecdir=/usr/lib --with-moduledir=/usr/lib/dovecot/modules --with-zlib

http://dovecot.org/releases/2.0/dovecot-2.0.4.tar.gz http://dovecot.org/releases/2.0/dovecot-2.0.4.tar.gz.sig multi-dbox users: Be careful about the INDEX change. Maildir users: I hope v2.0 is now finally stable. * multi-dbox: If :INDEX=path is specified, keep storage/dovecot.map.index* files also in the index path rather than in the main storage directory. WARNING: if you specified

http://dovecot.org/releases/2.0/dovecot-2.0.4.tar.gz http://dovecot.org/releases/2.0/dovecot-2.0.4.tar.gz.sig multi-dbox users: Be careful about the INDEX change. Maildir users: I hope v2.0 is now finally stable. * multi-dbox: If :INDEX=path is specified, keep storage/dovecot.map.index* files also in the index path rather than in the main storage directory. WARNING: if you specified

Dear all, I have compiled dovecot.When i use dovecot --build-options , i receive following messages: ------------------------------------------------ debian:/home/mohsen# dovecot --build-options Build options: ioloop=epoll notify=inotify ipv6 openssl Mail storages: maildir mbox dbox cydir raw SQL drivers: Passdb: checkpassword vpopmail Userdb: prefetch static vpopmail

I've been using Dovecot in some fresh installs lately and have found it fairly easy to configure. However I'm starting on a migration that involves moving from some very old software (ancient vpopmail, qmail and Courier). On the Courier front, I've reviewed the migration page in the wiki, and it looks like the main concerns are just matching the namespace and then using the migration

http://dovecot.org/releases/2.0/dovecot-2.0.16.tar.gz http://dovecot.org/releases/2.0/dovecot-2.0.16.tar.gz.sig I only now noticed that the VSZ limits weren't being enforced with earlier v2.0.x releases (or they were set 1024 times too high). So if a Dovecot process was leaking memory, it wasn't being killed by kernel. Now that this enforcing is done, some installations will probably

http://dovecot.org/releases/2.0/dovecot-2.0.16.tar.gz http://dovecot.org/releases/2.0/dovecot-2.0.16.tar.gz.sig I only now noticed that the VSZ limits weren't being enforced with earlier v2.0.x releases (or they were set 1024 times too high). So if a Dovecot process was leaking memory, it wasn't being killed by kernel. Now that this enforcing is done, some installations will probably

Hello I'm attempting to configure Dovecot with mysql support so I'm able to have a single database of users and point both postfix and dovecot to this db. I currently have an rpm src that I have download and placed in my RPMBUILDROOT of my linux box. Next I configured the .spec file and attempted to run a rpmbuild -bb Near the end of the install phase I receive an error which has me

Hi, I have a DELL PE R610 (32GB RAM 2x Six Core CPU and about 1,4 TB RAID 10) running with 20.000 Mailaccounts behind 2 Dovecot IMAP/POP3 Proxies on a Debian Lenny. The Server was running about 1 year without any problems. 15Min Load was between 0,5 and max 8. No high IOWAIT. CPU Idletime about 98%. But since yesterday morning the Systemload on the Server has been increased over 500. I Think

Hello, Currently I have a qmail server with vpopmail+courierImap. I want setup a new server in DMZ for proxy IMAP connections and I have a doubt with authentication method. I've read that dovecot can use a vpopmail driver for authentication. As my user database/password is stored by vpopmail, I think that this would be the best method for check the auth logins against dovecot. But I've

http://dovecot.org/releases/2.1/dovecot-2.1.6.tar.gz http://dovecot.org/releases/2.1/dovecot-2.1.6.tar.gz.sig * Session ID is now included by default in auth and login process log lines. It can be added to mail processes also by adding %{session} to mail_log_prefix. + Added ssl_require_crl setting, which specifies if CRL check must be successful when

http://dovecot.org/releases/2.1/dovecot-2.1.6.tar.gz http://dovecot.org/releases/2.1/dovecot-2.1.6.tar.gz.sig * Session ID is now included by default in auth and login process log lines. It can be added to mail processes also by adding %{session} to mail_log_prefix. + Added ssl_require_crl setting, which specifies if CRL check must be successful when

Timo, I nervously ran rc6 plus the patch: http://dovecot.org/tmp/ssl-proxy-openssl.c on my Solaris 9 box, in production, this morning. My dovecot.conf file is attached. Like similar reports for BSD, rc6 fell over after an hour and a half. The final syslog message was: dovecot: [ID 920869 mail.error] Login process died too early - shutting down I rolled back to rc2 for production. BTW,

http://dovecot.org/releases/2.1/dovecot-2.1.7.tar.gz http://dovecot.org/releases/2.1/dovecot-2.1.7.tar.gz.sig * Session ID is now included by default in auth and login process log lines. It can be added to mail processes also by adding %{session} to mail_log_prefix. + Added ssl_require_crl setting, which specifies if CRL check must be successful when verifying client certificates. +

http://dovecot.org/releases/2.1/dovecot-2.1.7.tar.gz http://dovecot.org/releases/2.1/dovecot-2.1.7.tar.gz.sig * Session ID is now included by default in auth and login process log lines. It can be added to mail processes also by adding %{session} to mail_log_prefix. + Added ssl_require_crl setting, which specifies if CRL check must be successful when verifying client certificates. +

How do I configure dovecot-2.0.x to present a client SSL certificate when proxying? If dovecot on server1.example.com has: passdb { driver = static args = proxy=y host=server2.example.com nopassword=y ssl=yes } and dovecot on server2.example.com has: ssl_verify_client_cert = yes auth_ssl_require_client_cert = yes then when a client connects to server1 and authenticates, a connection is

I have apache 1.3 with mod_ssl in front of mongrel/rails. Apache is setup to require client certification, and I''m trying to figure out how to pass the ssl env variables to mongrel. Here is the apache config to proxy requests to mongrel. I haven''t tried to pass env variables like this before so I''m not sure if it''s the apache config I have wrong, if mongrel