From: wmperry@aventail.com (William M. Perry)
Cc: ding@gnus.org
Subject: Re: nnimap URLs? (Was: What now?)
Date: 08 Dec 1999 11:08:11 -0500 [thread overview]
Message-ID: <8666y91klw.fsf@localhost.localdomain> (raw)
In-Reply-To: Steinar Bang's message of "08 Dec 1999 09:02:44 +0100"
Steinar Bang <sb@metis.no> writes:
> >>>>> wmperry@aventail.com (William M. Perry):
>
> > This is changed with the new version of URL - I am in the midst of
> > rewriting url-news.el right now.
>
> Will you do IMAP URLs as well?
> http://www.faqs.org/rfcs/rfc2192.html
I'm not sure if I know enough about the guts of 'imap.el' to hack this
together or not. Fortunately, it is easy to add a new URL type. :) If
anyone (simon?) wants to work on this, let me know and I'll concentrate on
getting the documentation on how to do this written tonight. I would LOVE
to see this get written.
It should probably be distributed as part of or along with imap.el - is
this only distributed with gnus now?
> 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...:-) ).
This would kick serious %!@#%!@, I might even gripe about the ridiculously
low quotas on our imap server so I could actually use it. (Pffft, who
needs only 135 megabytes for storing email :)
-Bill P.
next prev parent reply other threads:[~1999-12-08 16:08 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 [this message]
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
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=8666y91klw.fsf@localhost.localdomain \
--to=wmperry@aventail.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).