From: Steinar Bang <sb@metis.no>
Subject: Re: IMAP + MIME + pGnus...
Date: 21 Apr 1999 09:32:10 +0200 [thread overview]
Message-ID: <whu2uabf9h.fsf@viffer.oslo.metis.no> (raw)
In-Reply-To: wmperry@aventail.com's message of "20 Apr 1999 09:35:48 -0500"
>>>>> wmperry@aventail.com (William M. Perry):
> Has any progress been made recently in allowing Gnus to delay
> retrieval of MIME parts? I was just pondering how to do this and
> thought that it would not be too hard to have nnimap spoof the
> delayed portions with a content type of
> application/x-gnus-external-imap with a location header that looks
> like a Netscape IMAP-ish URL.[1]
There is an RFC defining a URL MIME External-Body Access-Type:
http://www.isi.edu/in-notes/rfc2017.txt
> Or if there is an `imap' URL standard somewhere, that would be even
> better.
Voilá!
http://www.isi.edu/in-notes/rfc2192.txt
> Could the message/external-body content-type be abused this way?
Probably. See the top URL.
> I would _really_ love to switch to IMAP, but without delaying
> attachments, the appeal over and above POP is not compelling. :)
What's holding me back right now, is lack of article editing
possiblities,... and I'm sortof addicted to reparenting... I also
like to hack MIME types from application/octet-stream (which
MSMail/MSExchange and Lotus Notes put on everything) into something
more meaningful.
next prev parent reply other threads:[~1999-04-21 7:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-04-20 14:35 William M. Perry
1999-04-20 14:50 ` Simon Josefsson
1999-04-21 7:33 ` Steinar Bang
1999-04-23 15:47 ` William M. Perry
1999-06-12 2:26 ` Lars Magne Ingebrigtsen
1999-04-21 7:32 ` Steinar Bang [this message]
1999-04-21 7:43 ` Kai.Grossjohann
1999-04-22 12:59 ` Steinar Bang
1999-04-22 14:59 ` Kai.Grossjohann
1999-04-22 15:51 ` Simon Josefsson
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=whu2uabf9h.fsf@viffer.oslo.metis.no \
--to=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).