From: Lars Magne Ingebrigtsen <larsi@gnus.org>
To: ding@gnus.org
Subject: Re: New IMAP mail parsing bug
Date: Mon, 11 Oct 2010 20:31:50 +0200 [thread overview]
Message-ID: <m3bp70d1ih.fsf@quimbies.gnus.org> (raw)
In-Reply-To: <87aamkptdl.fsf@maru.md5i.com>
Michael Welsh Duggan <md5i@md5i.com> writes:
> The nil comes from second nnimap-get-length call. The first one returns
> 2272 as expected, but the forward char only skips to the line containing
> the "BODY[1] NIL)" bit. I expect that the NIL is the problem. The
> attached file may or may not be missing the carriage returns at the end
> of each line.
I think the problem is that the message has no body. I'm not able to
test this myself, but I think the fix I just checked in might fix the
problem.
--
(domestic pets only, the antidote for overdose, milk.)
larsi@gnus.org * Lars Magne Ingebrigtsen
next prev parent reply other threads:[~2010-10-11 18:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-11 16:49 Michael Welsh Duggan
2010-10-11 18:31 ` Lars Magne Ingebrigtsen [this message]
2010-10-11 20:17 ` Michael Welsh Duggan
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=m3bp70d1ih.fsf@quimbies.gnus.org \
--to=larsi@gnus.org \
--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).