Re: [Dovecot] A few dovecot 1.1 bugs - sort, flag reset and etc.

2007-08-07 Thread Timo Sirainen
On Sat, 2007-08-04 at 11:25 -0400, wenjie zheng wrote:
 BUG #2: Some flags are reset after they were set a while ago,
 like messages that has been read are randomly becoming unread again.

Fixed: http://hg.dovecot.org/dovecot/rev/65e12fa51d4d



signature.asc
Description: This is a digitally signed message part


Re: [Dovecot] A few dovecot 1.1 bugs - sort, flag reset and etc.

2007-08-06 Thread Timo Sirainen
On Sat, 2007-08-04 at 11:25 -0400, wenjie zheng wrote:
 imap([EMAIL PROTECTED] javascript:void(0);): Panic: file
 mail-cache-lookup.c: line 70: unreached

This should be fixed now in hg.

 BUG #2: Some flags are reset after they were set a while ago,
 like messages that has been read are randomly becoming unread again.

I haven't noticed this myself. When you see this, could you look up the
message's UID and then check with logview program (in libexec/dovecot/)
what flag changes there have been for this UID. The only parameter
logview needs is path to the dovecot.index.log file.

 Bug #3: CRLF in the email file on disk is shown like =0A, which
 causes display problem in wireless access.
 =0A
 =0A
 =0A
 =0A
 =0AHey all,
 =0A=C2=A0

Dovecot doesn't do any line feed conversions, I think that email was
just sent like that?



signature.asc
Description: This is a digitally signed message part


Re: [Dovecot] A few dovecot 1.1 bugs - sort, flag reset and etc.

2007-08-06 Thread Jasper Bryant-Greene
On Aug 06, 2007 17:36:02, Timo Sirainen wrote:
 On Sat, 2007-08-04 at 11:25 -0400, wenjie zheng wrote:
  BUG #2: Some flags are reset after they were set a while ago,
  like messages that has been read are randomly becoming unread again.
 
 I haven't noticed this myself. When you see this, could you look up the
 message's UID and then check with logview program (in libexec/dovecot/)
 what flag changes there have been for this UID. The only parameter
 logview needs is path to the dovecot.index.log file.

I'm seeing this problem too.

Message was marked 'O' in mutt - I believe this means 'seen'. Here's the
logview output when I open the message (which should mark it as 'read'):

record: offset=13532, type=flag-update (ext), size=20
 - 223-223 (flags +0-1f)
record: offset=13552, type=keyword-reset (ext), size=24
 - 228-228, 230-240,
record: offset=13576, type=header-update (ext), size=16
 - offset = 64, size = 4: 1835 (dec=13592)

Let me know if you need anything else.

Cheers,
J