similar to: hangup with corrupted indexes

Hello everyone, Since the upgrade to 1.0.alpha3 I experience a strange problem with plaintext authentication. I successfully login first few (2-5) times after the dovecot restart, and then on a reason I cannot login any more (both via POP3 and IMAP). I tried to find out what could be the reason for this but I failed. Nothing is changed inside the user's home directory or

Hello Timo, What was the reason to remove ssl_parameters_file setting? Is it possible to restore it? We really need it, and I can see no reason to remove this useful setting. -- Sergey Redin

Hi! I should report yet another problem with dovecot index files. Suppose we have a user with his filesystem disk quota exceeded. He logins via POP3 or IMAP to remove some mail messages and fix this problem. When he logins for the first time, everything works fine, and he can read and remove something. But if his disk quota is still exceeded when he logs out, he cannot login any more.

On October 11, Mark Farmer reported a problem about not being able to see new mails. I'm running into the same issue. Even though cur/ and new/ contain messages, Dovecot reports that there aren't any. This problem seemed to start happening in alpha3 (and persists in alpha4). When I revert back to alpha2, the messages show up again. It looks like a problem with the dovecot.index*

Hello Dovecot users, Since the first release of the new Sieve implementation, not that many bugs were reported. This is probably due to the fact that it is not tried yet by that many people. In the mean time, I did find and fix some more bugs myself, I adapted to changes in Dovecot, wrote some more documentation and started work on the enotify extension. Both Sieve and ManageSieve were changed

Hello Dovecot users, Since the first release of the new Sieve implementation, not that many bugs were reported. This is probably due to the fact that it is not tried yet by that many people. In the mean time, I did find and fix some more bugs myself, I adapted to changes in Dovecot, wrote some more documentation and started work on the enotify extension. Both Sieve and ManageSieve were

I've been simultaneously learning about dovecot and experimenting with the 1.2.alpha4. To start I built an rpm under CentOS 5.2 from: dovecot-1.2.alpha4.tar.gz dovecot-1.2-managesieve-0.11.2.tar.gz dovecot-1.2.alpha4-managesieve-0.11.2.diff.gz dovecot-1.2.alpha4.tar.gz dovecot-1.2-sieve-0.1.2.tar.gz and then setup with mysql to use virtual users. Mail-wise, it all works. :)

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello I'm currently running dovecot-1.0.alpha4-1 on my production system, dovecot-1.0.alpha4-1where I am making use of namespaces. I have downloaded 1.0-beta3 and have installed it on a test system. I have customised the configuration for local use, however when I inserted the namespace settings into my configuration file dovecot refuses to

From: Ben Skeggs <bskeggs at redhat.com> [ Upstream commit 13d03e9daf70dab032c03dc172e75bb98ad899c4 ] Where possible, we want the failsafe link configuration (one which won't hang the OR during modeset because of not enough bandwidth for the mode) to also be supported by the sink. This prevents "link rate unsupported by sink" messages when link training fails.

From: Ben Skeggs <bskeggs at redhat.com> [ Upstream commit 13d03e9daf70dab032c03dc172e75bb98ad899c4 ] Where possible, we want the failsafe link configuration (one which won't hang the OR during modeset because of not enough bandwidth for the mode) to also be supported by the sink. This prevents "link rate unsupported by sink" messages when link training fails.

From: Ben Skeggs <bskeggs at redhat.com> [ Upstream commit 13d03e9daf70dab032c03dc172e75bb98ad899c4 ] Where possible, we want the failsafe link configuration (one which won't hang the OR during modeset because of not enough bandwidth for the mode) to also be supported by the sink. This prevents "link rate unsupported by sink" messages when link training fails.

From: Ben Skeggs <bskeggs at redhat.com> [ Upstream commit 13d03e9daf70dab032c03dc172e75bb98ad899c4 ] Where possible, we want the failsafe link configuration (one which won't hang the OR during modeset because of not enough bandwidth for the mode) to also be supported by the sink. This prevents "link rate unsupported by sink" messages when link training fails.

Hi, i have 2 dovecot imap server running on solaris 10 The primary server with dovecot 1.0.alpha4 is running with best performance on Sun Sparc E4k5 with 8x 450MHz The secondary with rc10 has ugly performanceproblems on Sun E450 wth 4x 450MHz. Every new imap process takes permanent 25% cpu usage List the folder and fetch message are both slowy! Both servers are configred with ldap backend

For the mailing list archive and for anyone else interested. A few years ago we needed to automatically run a second AGI if the first AGI failed i.e. a "failsafe" setup. Mainly because I'm not a very good programmer. 8-| The code below is very similar to what we use in production. This code is also at http://pastebin.com/LBaLhdfJ for a while. "sm" stands for Switch

We are proud to a announce a forth alpha release of Samba 4. What's new in Samba 4 alpha4 ============================ Samba 4 is the ambitious next version of the Samba suite that is being developed in parallel to the stable 3.0 series. The main emphasis in this branch is support for the Active Directory logon protocols used by Windows 2000 and above. Samba 4 is currently not yet in a

I get this error every single time some of my users log in: Error: POP3(${user}): Corrupted index cache file /${userdir}/dovecot.index.cache: invalid record size The named file seems to be deleted as soon as corruption is found. This only affects some users. I thought the affected users had in common that they are using POP3 in "leave-messages-on-server" mode, and that their mailboxes

http://dovecot.org/releases/1.2/alpha/dovecot-1.2.alpha4.tar.gz http://dovecot.org/releases/1.2/alpha/dovecot-1.2.alpha4.tar.gz.sig Note that there are significant changes in this release from alpha3 and I haven't tested everything extensively. Be careful. The next release will hopefully be v1.2.beta1 with a feature freeze. Most importantly shared mailboxes and IMAP ACLs are finally

Please try if http://dovecot.org/nightly/dovecot-latest.tar.gz (or the CVS directly) works with you. I made a lot of changes to dovecot-auth, so I wouldn't want to make alpha4 release without some more testing in different environments. I'll release alpha4 in a few days, but it'll be basically same as this unless more bugs get fixed. Some of the changes include: - IMAP: We might

The actual alpha4 release this time. With a few changes since the pre-release. The important changes again: - Default lock_method changed to flock instead of the old fcntl. Solaris users will need to set it back to fcntl. This makes sure that Dovecot's indexes aren't accidentally used with NFS. - IMAP: We might have sent extra EXPUNGE messages when output buffer got full. This could

Howdy, Forgive me if this issue has been more recently addressed in CVS, but a quick scan of the archives didn't turn up any other reports. There appears to be a small typo in src/lib/ioloop-select.c: --- dovecot-1.0.alpha4/src/lib/ioloop-select.c.orig 2005-11-06 22:06:53.000000000 -0800 +++ dovecot-1.0.alpha4/src/lib/ioloop-select.c 2005-11-06 22:07:13.000000000 -0 800 @@ -113,7