Gnus development mailing list
 help / color / mirror / Atom feed
From: Ted Zlatanov <tzz@lifelogs.com>
To: James Cloos <cloos@jhcloos.com>
Cc: Jake Colman <colman@ppllc.com>,  ding@gnus.org
Subject: Re: error In imap-parse-body 2 (Exchange 2007)
Date: Wed, 16 Apr 2008 15:21:54 -0500	[thread overview]
Message-ID: <86ej95lfdp.fsf@lifelogs.com> (raw)
In-Reply-To: <86lk3lwmr0.fsf@lifelogs.com> (Ted Zlatanov's message of "Thu, 10 Apr 2008 14:09:07 -0500")

On Thu, 10 Apr 2008 14:09:07 -0500 Ted Zlatanov <tzz@lifelogs.com> wrote: 

TZ> On Thu, 10 Apr 2008 10:46:25 -0400 James Cloos <cloos@jhcloos.com> wrote: 
>>>>>>> "Jake" == Jake Colman <colman@ppllc.com> writes:
Jake> Actually, even more important in the short-term, is there a way to
Jake> force Gnus to keep going if it encounters this error?

JC> I tried commenting the assert out but that didn't help.  At that point
JC> gnus is too confused about how to parse the FETCH reply.

JC> I *think* what gnus would need to do is to forget that message, skip
JC> past the next end-of-line and if that looks like the start of the next
JC> message's data to continue parsing there as if the offending message
JC> were not included in the reply.

JC> It would take me a while -- perhaps a few hours -- to figure out how to
JC> do that in elisp.  My only exposure to parsing in elisp has been trying
JC> to debug this problem, and that was weeks (maybe months by now) ago.

TZ> I tried to duplicate this bug but couldn't.  Can each of you please
TZ> forward a message that shows the problem to me, and tell me what IMAP
TZ> server you use when you see the bug?

I spent time putting the exact message that's causing you trouble into
my IMAP server (tried Exchange and Courier) and didn't have any luck
triggering the assert.  You'll have to spend more time trying to trigger
and fix this, unfortunately.  As a first step, apply this patch so the
assert call will tell us where in the IMAP buffer we are and what's
around us.  This will be a LARGE debug statement so do it right after
you start Gnus, to diminish the amount of data that's getting sent out,
and then don't use it anymore (remove it and restart Gnus).

As an aside, I am doing C-x C-e to redefine imap-parse-body and it's not
taking effect.  Anyone know why that would happen?

Thanks
Ted

Index: imap.el
===================================================================
RCS file: /usr/local/cvsroot/gnus/lisp/imap.el,v
retrieving revision 7.45
diff -r7.45 imap.el
2903,2904c2903,2904
< 
<       (assert (eq (char-after) ?\)) nil "In imap-parse-body 2")
---
>       
>       (assert (eq (char-after) ?\)) nil "position %d in %s" (point) (buffer-string))



  reply	other threads:[~2008-04-16 20:21 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-03 16:51 Jake Colman
2008-04-03 18:31 ` James Cloos
2008-04-03 20:51   ` Jake Colman
2008-04-10 13:46   ` Jake Colman
2008-04-10 13:58     ` Jake Colman
2008-04-10 14:46       ` James Cloos
2008-04-10 18:15         ` Jake Colman
2008-04-10 19:09         ` Ted Zlatanov
2008-04-16 20:21           ` Ted Zlatanov [this message]
2008-04-24 14:54             ` Jake Colman
2008-04-25  8:54               ` James Cloos
2008-04-25 16:23               ` Ted Zlatanov
2008-04-10 14:39     ` James Cloos
2008-04-10 18:17       ` Jake Colman

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=86ej95lfdp.fsf@lifelogs.com \
    --to=tzz@lifelogs.com \
    --cc=cloos@jhcloos.com \
    --cc=colman@ppllc.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).