From: Ted Zlatanov <tzz@lifelogs.com>
To: Jake Colman <colman@ppllc.com>
Cc: James Cloos <cloos@jhcloos.com>, ding@gnus.org
Subject: Re: error In imap-parse-body 2 (Exchange 2007)
Date: Fri, 25 Apr 2008 11:23:15 -0500 [thread overview]
Message-ID: <86zlrhvr7w.fsf@lifelogs.com> (raw)
In-Reply-To: <764p9r9ucj.fsf@dev-d01.ppllc.com> (Jake Colman's message of "Thu, 24 Apr 2008 10:54:20 -0400")
On Thu, 24 Apr 2008 10:54:20 -0400 Jake Colman <colman@ppllc.com> wrote:
>>>>>> "TZ" == Ted Zlatanov <tzz@lifelogs.com> writes:
TZ> I spent time putting the exact message that's causing you trouble into
TZ> my IMAP server (tried Exchange and Courier) and didn't have any luck
TZ> triggering the assert. You'll have to spend more time trying to trigger
TZ> and fix this, unfortunately. As a first step, apply this patch so the
TZ> assert call will tell us where in the IMAP buffer we are and what's
TZ> around us. This will be a LARGE debug statement so do it right after
TZ> you start Gnus, to diminish the amount of data that's getting sent out,
TZ> and then don't use it anymore (remove it and restart Gnus).
Jake> 1) Forward an email that you have received but with a gcc-self.
Jake> 2) In the folder that is the target of the gcc-self, you will get a copy
Jake> of the forwarded email. This email should be formatted as an
Jake> attachment.
Jake> 3) Try reading that email.
Jake> This sequence of steps will always trigger the problem on my Exchange
Jake> 2007 server.
It doesn't do it for me. Very strange.
Ted
next prev parent reply other threads:[~2008-04-25 16:23 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 [this message]
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=86zlrhvr7w.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).