similar to: rc18->rc19: read/unread/reply flags broken

Displaying 20 results from an estimated 1000 matches similar to: "rc18->rc19: read/unread/reply flags broken"

2007 Jan 31
1
Query: LSUB "" "*" still on rc19
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,
2007 Jan 23
2
imap core dump with rc18
Hi, I had a core dump while using rc18. Here are the backtraces: Jan 23 01:01:44 rouge dovecot: IMAP(user): file mail-index-view.c: line 386 (_view_lookup_uid_range): assertion failed: (*last_seq_r >= *first_seq_r) Jan 23 01:01:44 rouge dovecot: IMAP(user): Raw backtrace: [0x47f25b00000000] Jan 23 01:01:44 rouge dovecot: child 24319 (imap) killed with signal 6 Core was generated by
2007 Jan 31
1
read/unread flags broken in rc19 ?
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
2007 Jan 30
0
mail_plugins = mail_log (pop3) crashing 1.0.rc18 and rc19
Hello Thank for adding mail_log plugin in Dovecot POP3/IMAP server. But when I am use "mail_log" in pop3 secction Dovecot getting the following log message: ... Jan 26 15:34:11 rtr dovecot: pop3-login: Login: user=<gk2>, method=PLAIN, rip=8x.xx.xx.xx, lip=8x.xx.xx.xxx Jan 26 15:34:11 rtr dovecot: POP3(gk2): dlopen(/opt/dovecot/v1.0rc19/lib/dovecot/pop3/lib20_mail_log_plugin.so)
2007 Jan 23
1
dovecot-acl file location in rc18
Hi, I'm trying to use ACL with dovecot rc18 but I don't understand where to store per-mailbox dovecot-acl file. In dovecot.conf I have mail_location = maildir:/var/vmail/%u/ and I do not use namespaces. I have some "testuser" maildir with subdir ".test". When I put dovecot-acl file to the .test directory I get this error in my log file: Error: IMAP(testuser):
2007 Jan 22
1
1.0.rc18 released
http://dovecot.org/releases/dovecot-1.0.rc18.tar.gz http://dovecot.org/releases/dovecot-1.0.rc18.tar.gz.sig I think we're quite near v1.0 now. * ACL plugin + Maildir: Moved dovecot-acl file from control directory to maildir. To prevent accidents caused by this change, Dovecot kills itself if it finds dovecot-acl file from the control directory. * When opening a maildir, check if
2007 Jan 22
1
1.0.rc18 released
http://dovecot.org/releases/dovecot-1.0.rc18.tar.gz http://dovecot.org/releases/dovecot-1.0.rc18.tar.gz.sig I think we're quite near v1.0 now. * ACL plugin + Maildir: Moved dovecot-acl file from control directory to maildir. To prevent accidents caused by this change, Dovecot kills itself if it finds dovecot-acl file from the control directory. * When opening a maildir, check if
2007 Jan 23
1
1.0.rc19 released
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
2007 Jan 23
1
1.0.rc19 released
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
2007 Feb 02
2
1.0.rc20 released
http://dovecot.org/releases/dovecot-1.0.rc20.tar.gz http://dovecot.org/releases/dovecot-1.0.rc20.tar.gz.sig So, rc19 was somewhat broken. How about this version? + dovecot: Added --log-error command line option to log an error, so the error log is easily found. + Added mail_log_max_lines_per_sec setting. Change it to avoid log throttling with mail_log plugin. - Changing message flags
2007 Feb 02
2
1.0.rc20 released
http://dovecot.org/releases/dovecot-1.0.rc20.tar.gz http://dovecot.org/releases/dovecot-1.0.rc20.tar.gz.sig So, rc19 was somewhat broken. How about this version? + dovecot: Added --log-error command line option to log an error, so the error log is easily found. + Added mail_log_max_lines_per_sec setting. Change it to avoid log throttling with mail_log plugin. - Changing message flags
2007 Feb 05
2
Nitpicking: rc21 startup banner says rc19
> [jhg at helios RPMS]$ rpm -q dovecot > dovecot-1.0-1_42.rc21.fc5.at but: > dovecot: Feb 05 10:49:21 Info: Dovecot v1.0.rc19 starting up
2007 Jan 26
3
imap-login crash with RC19
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
2007 Feb 23
1
rc19 - (_view_lookup_uid_range): assertion failed
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:
2007 Feb 01
0
Mail Answered status flag in pine stopped working in rc19
The Flag indicating that a message has been Answered does not work in pine. The status flags for New and Deleted work as always. The Answered flag worked properly in dovecot 0.99, but after upgrading to 1.0rc19 it stopped working. Interestingly, mail that was answered before upgrading to rc19 still shows the proper flag. I have tried with mbox_dirty_syncs turned on and off and I have tried
2007 Jan 22
1
RC18 core dumps
Still seeing a few core dumps via the deliver process and corrupted transaction log files with RC18: Jan 22 10:46:36 zahara deliver(user at host.com): Corrupted transaction log file /data/mail/host.com/us/user at home.com/dovecot.index.log: start_offset (71680) > file size (71520) Jan 22 10:46:36 zahara deliver(user at host.com): seq = 6, rec->uid = 0, first_new_seq = 6, records = 5 Jan 22
2007 Feb 02
4
1.0.rc21 released
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:
2007 Feb 02
4
1.0.rc21 released
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:
2007 Jan 29
2
lda sieve broken after upgrade
upgraded to rc19. using maildirs. solaris 9/cc. removed all modules from pop/imap/lda subdirs and first upgraded dovecot to rc19 and then used dovecot-sieve-1.0.1 sources to build against the dovecot source directory ( everything now builds nicely on Solaris, thank you Timo ). added "cmusieve" to the list of plugins used by lda. ail_plugins = cmusieve now getting this:
2007 Jan 25
1
X-UID gaps cause Dovecot/IMAP to hang
Hi, When the Dovecot 1.0.rc19 IMAP server encounters X-UID headers with gaps in them, it hangs indefinitely. I've attached a sample mailbox (in mbox format) which repeatably exhibits this behavior. The mbox contains only three messages with the following X-UIDs in order: 774, 785, 787. If I remove the X-UID headers from each message, Dovecot handles the mailbox without any problems. UW-IMAP