Gnus development mailing list
 help / color / mirror / Atom feed
From: James Cloos <cloos@jhcloos.com>
To: Jake Colman <colman@ppllc.com>
Cc: ding@gnus.org
Subject: Re: error In imap-parse-body 2 (Exchange 2007)
Date: Thu, 10 Apr 2008 10:46:25 -0400	[thread overview]
Message-ID: <m38wzldaxz.fsf@lugabout.jhcloos.org> (raw)
In-Reply-To: <76ej9dzu9z.fsf@dev-d01.ppllc.com> (Jake Colman's message of "Thu, 10 Apr 2008 09:58:16 -0400")

>>>>> "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?

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

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

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

-JimC
-- 
James Cloos <cloos@jhcloos.com>         OpenPGP: 1024D/ED7DAEA6



  reply	other threads:[~2008-04-10 14:46 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 [this message]
2008-04-10 18:15         ` Jake Colman
2008-04-10 19:09         ` Ted Zlatanov
2008-04-16 20:21           ` Ted Zlatanov
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=m38wzldaxz.fsf@lugabout.jhcloos.org \
    --to=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).