From: Jake Colman <colman@ppllc.com>
To: ding@gnus.org
Subject: Re: error In imap-parse-body 2 (Exchange 2007)
Date: Thu, 10 Apr 2008 14:17:58 -0400 [thread overview]
Message-ID: <76myo160bt.fsf@dev-d01.ppllc.com> (raw)
In-Reply-To: <m3ej9ddba7.fsf@lugabout.jhcloos.org>
>>>>> "JC" == James Cloos <cloos@jhcloos.com> writes:
>>>>> "Jake" == Jake Colman <colman@ppllc.com> writes:
Jake> Is there something I can do to tell Gnus to avoid the
Jake> problematic email?
JC> I didn't discover one. And it is an insidious bug; when it hits
JC> not only does that email not show up in the *Summary* buffer, but
JC> nothing that the server sent in its FETCH reply which is after
JC> the first rfc/822 mail will show up either.
JC> The best I managed was to log in in parallel with mutt, delete
JC> the offending mail and re-enter the group in gnus. Since I have
JC> procmail in between postfix and my imap store anyway, filtering
JC> those out to a folder where gnus can handle them was the easiest
JC> option.
JC> (I did post a bug report, but never saw any replies, and my
JC> attempts to debug it didn't elucidate the actual cause....)
That's pretty much what I've been doing as well. I have Outlook up and
running on my PC and I manually delete any messages that Gnus cannot
handle.
--
Jake Colman
Director of Software Development
Principia Partners LLC
101 West Elm Street
Suite 620
Conshohocken, PA 19428
+1 (610) 755-9786
www.principiapartners.com
prev parent reply other threads:[~2008-04-10 18:17 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
2008-04-10 18:17 ` Jake Colman [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=76myo160bt.fsf@dev-d01.ppllc.com \
--to=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).