Your message dated Mon, 24 Aug 2009 11:38:27 +0200
with message-id <[email protected]>
and subject line Re: Bug#538952: dovecot-imapd: 'sort' command generates a 
traceback
has caused the Debian Bug report #538952,
regarding dovecot-imapd: 'sort' command generates a traceback
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
538952: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=538952
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: dovecot-imapd
Version: 1:1.1.13-2~bpo50+1
Severity: important

Hello,
when sending a 'sort' command, dovecot disconnects the client and
generates a traceback in the log:

[session]
$ telnet <host> 143
Connected to <host>
Escape character is '^]'.
* OK Dovecot ready.
a login <username> <password>
a OK Logged in.
a select inbox
* FLAGS (\Answered \Flagged \Deleted \Seen \Draft $MDNSent)
* OK [PERMANENTFLAGS (\Answered \Flagged \Deleted \Seen \Draft $MDNSent
\*)] Flags permitted.
* 42 EXISTS
* 0 RECENT
* OK [UNSEEN 16] First unseen.
* OK [UIDVALIDITY 1243421055] UIDs valid
* OK [UIDNEXT 333] Predicted next UID
a OK [READ-WRITE] Select completed.
a sort (from) iso-8859-1 all
Connection closed by foreign host.

[log]
dovecot: 2009-07-28 08:12:59 Panic: IMAP(<username>): file
index-sort-string.c: line 168 (index_sort_node_add): assertion failed:
(ctx->lowest_nonexpunged_zero == 0 || ctx->lowest_nonexpunged_zero >
node->seq)
dovecot: 2009-07-28 08:12:59 Error: IMAP(<username>): Raw backtrace:
imap [0x80d8c81] -> imap [0x80d8d02] -> imap [0x80d8689] -> imap
[0x80a1501] -> imap(index_sort_list_add_string+0x43) [0x80a1653] ->
imap(index_storage_search_next_nonblock+0xc1) [0x809e7e1] ->
imap(mailbox_search_next+0x2a) [0x80a685a] -> imap(imap_sort+0xdc)
[0x806901c] -> imap(cmd_sort+0x24c) [0x806166c] -> imap [0x8062cdc] ->
imap [0x8062d73] -> imap [0x806332d] -> imap(client_input+0x5e)
[0x80637ae] -> imap(io_loop_handler_run+0xe0) [0x80e0c70] ->
imap(io_loop_run+0x20) [0x80e00e0] -> imap(main+0x472) [0x806b9b2] ->
/lib/i686/cmov/libc.so.6(__libc_start_main+0xe5) [0xb7db4455] -> imap
[0x805cd61]

Let us know if we can support you in any way, since it's really
important to us to get this fixed asap.

Regards,
Sandro

-- System Information:
Debian Release: 5.0.2
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: i386 (i686)

Kernel: Linux 2.6.26-2-686-bigmem (SMP w/8 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/bash

Versions of packages dovecot-imapd depends on:
ii  dovecot-common        1:1.1.13-2~bpo50+1 secure mail server that
supports m
ii  libc6                 2.7-18             GNU C Library: Shared libraries
ii  libssl0.9.8           0.9.8g-15+lenny1   SSL shared libraries

dovecot-imapd recommends no packages.

dovecot-imapd suggests no packages.

-- no debconf information



--- End Message ---
--- Begin Message ---
Version: 1:1.1.16-1

Timo Sirainen wrote:
> On Fri, 2009-08-07 at 16:34 -0400, Timo Sirainen wrote:
>   
>> On Mon, 2009-08-03 at 14:05 +0200, Sandro Tosi wrote:
>>     
>>>> This should help: http://hg.dovecot.org/dovecot-1.1/rev/12670c6d0c10
>>>>   
>>>>         
>>> Hi Timo,
>>> as Joel pointed out (privately) the patch you reference above is already
>>> included in 1.1.3 (released on Mar 2009, while the patch is from Sep '08).
>>>       
>> 1.1.13 you mean. And actually I checked that before giving the link, but
>> looks like I also looked at 1.1.3 release date instead of 1.1.13 :)
>>
>> Anyway, can you reproduce this easily with some mailbox? Could you send
>> me such mailbox's dovecot.index, dovecot.index.log and dovecot-uidlist
>> files? None of them contain anything sensitive about the mailbox. After
>> that you can just delete dovecot.index* files and it should work again
>> (until it reaches the same buggy condition again).
>>     
>
> I looked at it a bit more closely. I don't think that condition should
> ever happen normally. Anyway I changed the code so that it'll reset the
> sort indexes automatically instead of crashing:
> http://hg.dovecot.org/dovecot-1.1/rev/fd48a9c61b6c
>   
Hi Timo,
thanks for your interest and the proposed patch, and sorry for the late
reply (holiday).

We have fixed the problem upgrading to 1.1.16, hence closing this report.

Regards,
Sandro


--- End Message ---

Reply via email to