Gnus development mailing list
 help / color / mirror / Atom feed
From: Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann)
Cc: Niklas Morberg <niklas.morberg@axis.com>, <ding@gnus.org>
Subject: Re: Not downloading attachments over IMAP
Date: Thu, 29 Nov 2001 09:23:38 +0100	[thread overview]
Message-ID: <vafsnayt27p.fsf@INBOX.auto.gnus.tok.lucy.cs.uni-dortmund.de> (raw)
In-Reply-To: <Pine.LNX.4.33.0111281810210.6786-100000@slipsten.extundo.com> (Simon Josefsson's message of "Wed, 28 Nov 2001 18:12:06 +0100 (CET)")

Simon Josefsson <jas@extundo.com> writes:

> On Wed, 28 Nov 2001, Kai Großjohann wrote:
>
>> Couldn't nnimap fetch the message structure and rewrite the `large'
>> parts into external bodies?  Isn't there a MIME type where one stores
>> a reference to the real part, rather than the data itself, in the
>> message?
>
> Yup.  multipart/external.  But isn't it kind of gross to have the backend
> change the contents of a message?  I wouldn't want that.  But I guess it 
> could be useful.  Hm.

Maybe the real solution is for Gnus to provide a way to fetch the
MIME tree for a message from the backend.  But I think that so far,
there is only one backend which allows for retrieval of the MIME
tree: nnimap.

Maybe rewriting nnimap to do what I suggested would also help in
devising a good interface for retrieving the MIME tree, and then the
nnimap functions can be moved into the Gnus proper, more or less: you
have nnchoke-retrieve-mime-tree which returns a useful data
structure, and the Gnus proper then decides what to do with it.
You'll also need nnchoke-retrieve-mime-part, of course.

How about that?

I wish I had time to work on this.

kai
-- 
Simplification good!  Oversimplification bad!  (Larry Wall)



  reply	other threads:[~2001-11-29  8:23 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-28 15:01 Niklas Morberg
2001-11-28 15:11 ` Simon Josefsson
2001-11-28 15:49   ` Kai Großjohann
2001-11-28 17:12     ` Simon Josefsson
2001-11-29  8:23       ` Kai Großjohann [this message]
2001-11-29 10:41         ` Simon Josefsson
2001-11-29 10:53           ` Kai Großjohann
2001-11-28 18:59     ` William M. Perry
2001-11-28 17:08   ` William M. Perry

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=vafsnayt27p.fsf@INBOX.auto.gnus.tok.lucy.cs.uni-dortmund.de \
    --to=kai.grossjohann@cs.uni-dortmund.de \
    --cc=ding@gnus.org \
    --cc=niklas.morberg@axis.com \
    /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).