similar to: Nitpicking: rc21 startup banner says rc19

http://dovecot.org/releases/dovecot-1.0.rc21.tar.gz http://dovecot.org/releases/dovecot-1.0.rc21.tar.gz.sig Just one fix. Maybe the one big thing in Dovecot v2.0.* will be a test suite, which is run before any release. :) - Cache file handling could have crashed rc20 -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type:

http://dovecot.org/releases/dovecot-1.0.rc21.tar.gz http://dovecot.org/releases/dovecot-1.0.rc21.tar.gz.sig Just one fix. Maybe the one big thing in Dovecot v2.0.* will be a test suite, which is run before any release. :) - Cache file handling could have crashed rc20 -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type:

Hi all, ive just upgrade to rc21 ( so i dont know perhaps this report failure is fixed with this release ) i have reports from users that attachments get broken ( with rc19, dont know about before ) with some accounts , which where downloaded via a pop3 service to a exchange server, but in fact nothing is broken when looking with imap to the mailboxes Has anyone an idea, i havent any failure logs

Hi all, I finally got a chance to try out the fix for the LDAP auth_bind=yes issues in production (using rc21). It seems to be working just fine even after 24 hours of severe abuse. Incidentally, I had switched to bsdauth+login_ldap (on OpenBSD) which was often OK, but occasionally I would see Postfix smtpd throttled with SASL errors due to "connection refused" on the Dovecot

http://dovecot.org/releases/dovecot-1.0.rc19.tar.gz http://dovecot.org/releases/dovecot-1.0.rc19.tar.gz.sig Just did a few more fixes to index files. Do they help with anyone's problems? - ACL plugin didn't work unless control dir was separate from maildir - More index file handling fixes -------------- next part -------------- A non-text attachment was scrubbed... Name: not available

http://dovecot.org/releases/dovecot-1.0.rc19.tar.gz http://dovecot.org/releases/dovecot-1.0.rc19.tar.gz.sig Just did a few more fixes to index files. Do they help with anyone's problems? - ACL plugin didn't work unless control dir was separate from maildir - More index file handling fixes -------------- next part -------------- A non-text attachment was scrubbed... Name: not available

Timo, This might be a bit vague, but I have noticed that rc19 seems to have broken the read/unread/reply flags in imap. My officemate has had problems with messages that are read and marked as read then mysteriously get remarked as unread the next time email is checked. I've had problems where I reply to a message and it does not get marked as "answered". We didn't see this

Hi all, We've downgraded to rc17 for the past week or so, as when we upgraded to rc19, this error did go, but came back again. ERROR: Could not complete request. Query: LSUB "" "*" Reason Given: Internal error occurred. Refer to server log for more information. Looks like it never helped us in rc19. Back on rc17 just now, which we still have to restart a few times a day,

I upgraded one server to 1.0rc19 (from rc15) over the weekend, and have since received several reports of dovecot erroneously retrieving older messages as new mail. I've seen this myself intermittently on KMail, and users have reported it on Thunderbird, Squirrelmail, and Outlook. I see some things in the archives that suggest that this was a problem in older 1.0 release candidates, but

Hi Timo, Using RC19, I've have the following crash. If there was a core file, I've got no idea where it's gone... Jan 25 10:35:10 rouge dovecot: imap-login: file client.c: line 528 (client_unref): assertion failed: (client->refcount > 0) Jan 25 10:35:10 rouge dovecot: child 25498 (login) killed with signal 6 Best regards, -- Nico On r?alise qu'une femme est de la dynamite

Apologies if this is an <=rc19 thing, but am waiting for rc24 to come into Debian unstable/testing before upgrading. After purging ~10 messages from INBOX the index's appeared to go into a broken state. Mail client (Outlook express) reported "unable to read message flags". Logged messages: Feb 23 17:34:58 mailget01 dovecot: IMAP(drawkcab at drawkcab.com): file mail-index-view.c:

Hi, I've been trying to get dirsize quotas to work properly with 1.0rc19 and Dovecot consistently crashes when attempting to do file copies once a user is over quota. Dovecot works fine for us for regular mbox based IMAP, but as soon as I add the following two entries in their respective locations in dovecot.conf: mail_plugins = quota imap_quota (in the imap{} section) quota =

Hi, I'm posting to relate that on debian unstable dovecot imap 1.0rc19 I'm experiencing exactly the same as seen on this thread: http://www.dovecot.org/list/dovecot/2007-January/018937.html All mail dating from last sunday (only that day it seems) gets reset to unread after I mark them as read after a period of time. This with thunderbird. Thanks for any help on this topic :) -- St?phane

After upgrading a working system from FC5's beta8 to rc21, one vhost is failing with: > dovecot: Feb 05 09:54:30 Error: POP3(user at mydomain.com): > open(/var/mail/vhosts/mydomain.com/david/user, O_CREAT) failed: Not a > directory > dovecot: Feb 05 09:54:30 Error: POP3(user at mydomain.com): > mkdir_parents(/var/mail/vhosts/mydomain.com/user/.imap/INBOX) failed: > Not a

Hello, For those interested, I have released the NHW v0.3.0-rc21 new version. I continue to fine-tune the nhw_kernel weights.This new version has more precision and a better visual quality. If you don't agree with this new version, do let me know and I'll revert the commit. More at: https://nhwcodec.blogspot.com/ Cheers, Raphael -------------- next part -------------- An HTML

I've finally upgraded to 1.0.rc21. If I run "dovecot --log-error", then dovecot fails to start. The following appears in the log: Feb 5 10:54:00 taurus1 dovecot: Dovecot v1.0.rc21 starting up Feb 5 10:54:00 taurus1 dovecot: This is Dovecot's error log Without --log-error, it will start up fine from command-line. Dovecot still fails to start, as near as I can tell, in the

http://dovecot.org/releases/dovecot-1.0.rc22.tar.gz http://dovecot.org/releases/dovecot-1.0.rc22.tar.gz.sig Found another bad bug in rc19 changes. Wonder why my imaptest catched the bug only in CVS HEAD but not in branch_1_0 even though both had it. Anyway, now the imaptest runs nicely for both, and I'm again optimistic that the bug count is low enough for v1.0 to be released soon :) BTW. My

http://dovecot.org/releases/dovecot-1.0.rc22.tar.gz http://dovecot.org/releases/dovecot-1.0.rc22.tar.gz.sig Found another bad bug in rc19 changes. Wonder why my imaptest catched the bug only in CVS HEAD but not in branch_1_0 even though both had it. Anyway, now the imaptest runs nicely for both, and I'm again optimistic that the bug count is low enough for v1.0 to be released soon :) BTW. My

The following shows up in the "orphaned page" list of the Wiki: http://wiki.dovecot.org/MboxLocking?action=show&redirect=MboxSoftwareLocks Does the description of Dovecot mbox locking still apply to current versions? If yes, it should be linked from the "Troubleshooting" page. -- Jim Garrison (jhg at acm.org) PGP Keys at http://www.jhmg.net RSA 0x04B73B7F DH 0x70738D88

Dovecot 2.0.9 on Centos 6.6 I have some local users and some Postfix virtual mailboxes. The config currently has: > # 2.0.9: /etc/dovecot/dovecot.conf > # OS: Linux 2.6.32-504.12.2.el6.x86_64 x86_64 CentOS release 6.6 (Final) > first_valid_uid = 190 > log_path = /var/log/dovecot.log > mail_access_groups = mail > mail_location = mbox:~/mail:INBOX=/var/mail/%u >