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:39:05 -0400	[thread overview]
Message-ID: <m3ej9ddba7.fsf@lugabout.jhcloos.org> (raw)
In-Reply-To: <76myo1zutf.fsf@dev-d01.ppllc.com> (Jake Colman's message of "Thu, 10 Apr 2008 09:46:36 -0400")

>>>>> "Jake" == Jake Colman <colman@ppllc.com> writes:

Jake> Is there something I can do to tell Gnus to avoid the problematic email?

I didn't discover one.  And it is an insidious bug; when it hits not
only does that email not show up in the *Summary* buffer, but nothing
that the server sent in its FETCH reply which is after the first rfc/822
mail will show up either.

The best I managed was to log in in parallel with mutt, delete the
offending mail and re-enter the group in gnus.  Since I have procmail in
between postfix and my imap store anyway, filtering those out to a
folder where gnus can handle them was the easiest option.

(I did post a bug report, but never saw any replies, and my attempts to
debug it didn't elucidate the actual cause....)

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



  parent reply	other threads:[~2008-04-10 14:39 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
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 [this message]
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=m3ej9ddba7.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).