Gnus development mailing list
 help / color / mirror / Atom feed
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: Tue, 04 Jan 2011 10:11:24 +0100	[thread overview]
Message-ID: <pkn8vz1owxv.fsf@this.is.really.invalid> (raw)
In-Reply-To: <m38vz1eco3.fsf@quimbies.gnus.org>

Lars Magne Ingebrigtsen <larsi@gnus.org> writes:

> Robert Pluim <rpluim@gmail.com> writes:
>
>>     (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.
>
> The length thing is a {foo} at the end of the line.
>
> Could you send the complete contents of the IMAP buffer when this
> happens?
>

Here's the nnimap buffer I get when attempting to read your reply
forwarded to myself (how's that for circularity :) )

* 556 FETCH (BODY[HEADER] {1063}
MIME-Version: 1.0
Received: from RPluim.mycompany.com (192.168.15.1) by mail.mycompany.com
 (192.168.1.2) with Microsoft SMTP Server (TLS) id 8.2.254.0; Tue, 4 Jan 2011
 03:42:31 -0500
From: Robert Pluim <rpluim@mycompany.com>
To: Robert Pluim <rpluim@mycompany.com>
Date: Tue, 4 Jan 2011 03:42:10 -0500
Subject: [gmane.emacs.gnus.general] Re: nnimap-fetch-partial-articles does
 not seem to work with forwarded articles
Thread-Topic: [gmane.emacs.gnus.general] Re: nnimap-fetch-partial-articles
 does not seem to work with forwarded articles
Thread-Index: Acur61OjR7l3bzSaRjyLTsv29CTRUw==
Message-ID: <pknipy5m55p.fsf@this.is.really.invalid>
Accept-Language: en-US
Content-Language: en-US
X-MS-Exchange-Organization-AuthAs: Internal
X-MS-Exchange-Organization-AuthMechanism: 06
X-MS-Exchange-Organization-AuthSource: mail.mycompany.com
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
user-agent: Gnus/5.110011 (No Gnus v0.11) XEmacs/21.5-b29 (cygwin32)
Content-Type: multipart/mixed;
	boundary="_002_pknipy5m55pfsfthisisreallyinvalid_"

 BODY[1] NIL UID 49311)
127 OK FETCH completed.


Imap log contains:

09:51:32 126 UID FETCH 49311 (BODYSTRUCTURE)
09:51:40 127 UID FETCH 49311 (BODY.PEEK[HEADER] BODY.PEEK[1])

Regards

Robert




  reply	other threads:[~2011-01-04  9:11 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
2011-01-04  0:27     ` Lars Magne Ingebrigtsen
2011-01-04  9:11       ` Robert Pluim [this message]
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=pkn8vz1owxv.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).