From: Robert Pluim <rpluim@gmail.com>
To: ding@gnus.org
Subject: Re: nnimap-fetch-partial-articles does not seem to work with forwarded articles
Date: Sun, 02 Jan 2011 20:42:28 +0100 [thread overview]
Message-ID: <pknd3ofytwb.fsf@this.is.really.invalid> (raw)
In-Reply-To: <m3d3oferl9.fsf@quimbies.gnus.org>
Lars Magne Ingebrigtsen <larsi@gnus.org> writes:
> Robert Pluim <rpluim@gmail.com> writes:
>
>> Debugger entered--Lisp error: (wrong-type-argument
>> number-char-or-marker-p nil)
>> nnimap-convert-partial-article((("text" "plain" ("charset"
>> "us-ascii") nil nil "quoted-printable" 0 0 nil "1" nil nil)
>> ("message" "rfc822" nil nil nil "7bit" 1638 ("tue, 21 dec 2010
>> 09:10:16 -0500" "re: nmc + e-cscf" ... nil nil ... nil nil
>> "<pknei9bi7f6.fsf@this.is.really.invalid>"
>> "<8ccdd3219a5a4d43a6d3b43d9764774b960a4ae0@mailbox1.company.com>")
>> ("text" "plain" ... nil nil "quoted-printable" 658 25 nil nil
>> "en-us" nil) "2" nil nil nil nil) "mixed" ("boundary"
>> "_002_pkn39pri4stfsfthisisreallyinvalid_") nil "en-us"))
>
> Your backtrace data has been truncated, so I can't really reproduce this
> bug. I think setting print-length and print-level to nil should
> probably fix this, but I'm not sure how your version of XEmacs does this
> exactly.
Hmm, they're both set to nil, so something has gone wrong. Anyway, I
edebug'd nnimap-convert-partial-article, and it's failing because
(while (looking-at ".*BODY\\[\\([.0-9]+\\)\\]")
(setq id (match-string 1)
bytes (nnimap-get-length)) <== this is returning NIL.
If I've understood the code, this should be parsing the BODY response,
which is
BODY[1] NIL UID 49140)
at this point. I'm not terribly familiar with IMAP, but I guess you're
expecting something a little more descriptive of the body than 'NIL' ;)
Trying to understand the relevant section of the RFC has given me a
headache, so I'll leave it to you to decide if this is a bug in Gnus or
in the Exchange server I'm talking to :)
Regards
Robert
next prev parent reply other threads:[~2011-01-02 19:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-21 15:58 Robert Pluim
2011-01-02 6:40 ` Lars Magne Ingebrigtsen
2011-01-02 19:42 ` Robert Pluim [this message]
2011-01-04 0:27 ` Lars Magne Ingebrigtsen
2011-01-04 9:11 ` Robert Pluim
2011-01-11 19:28 ` Lars Magne Ingebrigtsen
2011-01-12 1:31 ` Robert Pluim
2011-01-22 19:19 ` Lars Ingebrigtsen
2011-01-23 10:34 ` Robert Pluim
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=pknd3ofytwb.fsf@this.is.really.invalid \
--to=rpluim@gmail.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).