Gnus development mailing list
 help / color / mirror / Atom feed
From: wmperry@aventail.com (William M. Perry)
Cc: Steinar Bang <sb@metis.no>, ding@gnus.org
Subject: Re: nnimap URLs? (Was: What now?)
Date: Fri, 10 Dec 1999 11:07:43 -0500	[thread overview]
Message-ID: <199912101607.LAA11361@localhost.localdomain> (raw)
In-Reply-To: Simon Josefsson's message of "08 Dec 1999 18:26:33 +0100"

Simon Josefsson <jas@pdc.kth.se> writes:

> Steinar Bang <sb@metis.no> writes:
> 
> > They could be a good start towards an infrastructure for doing delayed
> > loading of attachments in nnimap mail groups.  nnimap could replace
> > the attachment MIME parts with an URL external body message part
> > 	http://www.landfield.com/rfcs/rfc2017.html
> > and when opening the part, the contents of the URL would be fetched
> > and inserted inline (that is, if Simon hasn't already fixed this in a
> > different way and I haven't been paying attention...:-) ).
> 
> I haven't, but I'm sort-of against the idea of modifying an article in
> the backend. You'd never really now what the article actually looked
> like in the long run...

`C-u g' should of course get the entire message.  I think this would be
sufficient.

> Unless someone want to implement automatic external-body access-type
> stuff in nnimap.

They would just have to implement it in the mm-* routines I would think.
Then any message could have external body parts, and nnimap would just take
advantage of it.

-Bill P.


  reply	other threads:[~1999-12-10 16:07 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-11-24  0:06 Forwarding Mail Messages Brian May
1999-12-01 19:47 ` Lars Magne Ingebrigtsen
1999-12-02  0:42   ` Nevin Kapur
1999-12-02  1:19     ` What now? (was: Forwarding Mail Messages) Lars Magne Ingebrigtsen
1999-12-02  2:59       ` What now? Brian May
1999-12-02 16:23         ` Colin Marquardt
1999-12-02 16:56         ` Jody M. Klymak
1999-12-06  4:26           ` Lars Magne Ingebrigtsen
1999-12-06  5:31             ` Brian May
1999-12-07  5:36               ` William M. Perry
1999-12-07  5:59                 ` Brian May
1999-12-07 16:09                   ` William M. Perry
1999-12-08  8:02                     ` nnimap URLs? (Was: What now?) Steinar Bang
1999-12-08 16:08                       ` William M. Perry
1999-12-08 18:02                         ` Simon Josefsson
1999-12-08 18:23                           ` William M. Perry
1999-12-08 17:26                       ` Simon Josefsson
1999-12-10 16:07                         ` William M. Perry [this message]
1999-12-08 22:51                     ` What now? Brian May
1999-12-06 17:36             ` Jody M. Klymak
1999-12-06 20:34               ` Bruce Stephens
1999-12-06 22:38               ` Kai Großjohann
1999-12-03 19:12       ` What now? (was: Forwarding Mail Messages) Jody M. Klymak
1999-12-04 17:05         ` Hrvoje Niksic
1999-12-04 22:53           ` Jody M. Klymak
2000-04-21 21:13         ` Lars Magne Ingebrigtsen
2000-04-21 21:05           ` William M. Perry
2000-04-21 21:16             ` Arcady Genkin
2000-04-21 23:32               ` William M. Perry
2000-04-22  9:36             ` Hans de Graaff
1999-12-05 21:46       ` Kai Großjohann
1999-12-05 21:51       ` Kai Großjohann
1999-12-06  1:27       ` Richard Hoskins
1999-12-02  1:48   ` Forwarding Mail Messages Brian May
1999-12-06  4:12     ` Lars Magne Ingebrigtsen

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=199912101607.LAA11361@localhost.localdomain \
    --to=wmperry@aventail.com \
    --cc=ding@gnus.org \
    --cc=sb@metis.no \
    /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).