Re: [Mutt] #3000: Deleting >50k messages from IMAP boxes fails with
#3000: Deleting >50k messages from IMAP boxes fails with Fatal error:
---------------------+------------------------------------------------------
Reporter: myon | Owner: brendan
Type: defect | Status: reopened
Priority: minor | Milestone: 1.6
Component: IMAP | Version: 1.5.17
Resolution: | Keywords:
---------------------+------------------------------------------------------
Comment(by John Hawkinson):
{{{
Mutt <fleas@xxxxxxxx> wrote on Sun, 31 Aug 2008
at 17:34:48 -0000 in <045.d33d7e2d3e34dcd5d768e7ce30a83901@xxxxxxxx>:
Well, it takes 30+ minutes to open this imap mailbox, and things
are a bit interesting.
First observation is I tried to delete 5k messages before the initial
crash, and it looks like it managed to sync almost all of the delete
flags to the server.
Hitting '$','n' returns instantly and doesn't crash (no surprise).
Hitting '$','y', it starts to expunge, and fails with a bogus Kerberos
error:
{{{
Updating progress: 207300
5> a0010 EXPUNGE
5< * 17 EXPUNGE
Handling EXPUNGE
5< * 17 EXPUNGE
Handling EXPUNGE
5< * 200 EXPUNGE
...
5< * 122570 EXPUNGE
Handling EXPUNGE
SASL: Time is out of bounds (krb_rd_req)
SASL decode failed: generic failure
imap_cmd_step: Error reading server response.
mutt_free_body: Not unlinking EmailMessage.pdf.
mutt_free_body: Not unlinking Documentation.pdf.
mutt_free_body: Not unlinking Certification.pdf.
mutt_free_body: Not unlinking information.pdf.
mutt_free_body: Not unlinking information.pdf.
mutt_free_body: Not unlinking clientcare.pdf.
mutt_free_body: Not unlinking clientcare.pdf.
mutt_free_body: Not unlinking clientcare.pdf.
Mailbox closed
mutt_socket_close: Attempt to close closed connection.
imap_exec: command failed: * 122583 EXPU
imap_sync_mailbox: EXPUNGE failed [* 122583 EXPU]
No mailbox is open.
}}}
Normally "Time is out of bounds (krb_rd_req)" means one of the server
or the client's clock was off by 300 seconds. Both the client and
server are ntp synced and neither experienced any strange events
during this period, so as far as I can tell the error is completely
bogus. (Also, generally you only get this error at the beginning of a
Kerberos authentiation, when tickets are presented, not later on.)
I hope figuring this out won't involve digging down into the SASL
layerr.
Reopening the mailbox now (another 30+ minutes), I'll try deleting
another 1k messages or so and see if we can trigger the original
(the core dump earlier today) bug.
--jhawk
}}}
--
Ticket URL: <http://dev.mutt.org/trac/ticket/3000#comment:>
Mutt <http://www.mutt.org/>
The Mutt mail user agent