From: gdt@work.lexort.com
Cc: ding@gnus.org
Subject: Re: problem asserts in nnimap
Date: Thu, 01 Jun 2006 16:05:34 -0400 [thread overview]
Message-ID: <smuac8w4p69.fsf@linuxpal.mit.edu> (raw)
In-Reply-To: <m3verxfbhj.fsf@kurono.home> (joakim@verona.se's message of "Tue, 23 May 2006 09:26:16 +0200")
I've been losing with "imap-parse-body 2" for a while, and believe
I've tracked down what sorts of messages cause it.
Basically, entering a group with g, or rescanning with M-g causes an
assert to fail in imap-parse-body. Messages which have a
message/rfc822 part seem to all trigger the problem when in INBOX, and
I searched for the messages by using 100 M-G and then 102 M-g to
binary search for most recent problem message. I then used
Thunderbird to move messages to a "Trouble" IMAP folder, since Gnus
won't put them in the summary. One prevented even getting a summary
buffer. Messages with other parts, such as attached pdf, and PGP/MIME
seems fine.
I can look at the Trouble folder just fine with gnus. But the same
messages in INBOX hit the assert.
It would be nice if the assert included the UID, but I don't see how
to do that.
I'm using
NetBSD/i386 -current
emacs 21.4
up-to-date CVS Gnus
dovecot
With the same IMAP server, I have no issues when using Thunderbird
(other than that my wrists will hurt from using the mouse).
--
Greg Troxel <gdt@work.lexort.com>
prev parent reply other threads:[~2006-06-01 20:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-22 19:29 joakim
2006-05-23 2:07 ` gdt
2006-05-23 7:26 ` joakim
2006-06-01 20:05 ` gdt [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=smuac8w4p69.fsf@linuxpal.mit.edu \
--to=gdt@work.lexort.com \
--cc=ding@gnus.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).