Re: Handling large attachments

RANDY@mpa15ab.mv.unisys.com Tue, 21 May 1996 00:01 UTC

Errors-To: owner-imap@cac.washington.edu
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: RANDY@mpa15ab.mv.unisys.com
Date: Mon, 20 May 1996 16:16:00 -0000
To: chrisn+%CMU.EDU@mvdns1.mv.unisys.com, imap%cac.washington.edu@mvdns1.mv.unisys.com
MMDF-Warning: Parse error in original version of preceding line at CNRI.Reston.VA.US
Subject: Re: Handling large attachments
In-Reply-To: Your message of "20 May 1996 18:23:49 -0400"
References: <832631029.19231.0@nifty.andrew.cmu.edu>, <Mailstrom.1.05.64507.1101.treister@networking.stanford.edu> <EGWP15112B024D@MPA15AB>
Message-Id: <EGWS14114A524D@MPA15AB>

On 20 May 1996 18:23:49 -0400, Chris Newman <chrisn+@CMU.EDU> wrote:

> I strongly oppose bloating IMAP, IMSP/ACAP or kludging SMTP CHUNKING
> to support this.
>
> If you really want to do this, here's what I'd suggest:
>
> Design an authenticated, clean, MIME-aware mail submission protocol
> which supports references to IMAP stores (server, folder, uid,
> mime-part).  Whether the mail submission server gets the parts via
> IMAP proxy or pulling them directly out of the IMAP mailstore would be
> an implementation detail.

This is a nice idea.  I wonder how much interest there would be for it?
It doesn't handle attaching arbitrary server files or saving attachments
as server files, but it would handle the essential business of forwarding
and so on.

--
|Randall Gellens             |                    randy@mv.unisys.com|
|(714) 380-6350              | fax (714)597-8053 can add ,,,,,,,,6350|
|Mail Stop MV 237            |                        Net**2 656-6350|
|Opinions are personal;  facts are suspect;   I speak only for myself|

                  Randomly selected tag:

"If I had my life to live over, I'd live over a delicatessen."
  -- Unknown

Re: Handling large attachments RANDY
Re: Handling large attachments RANDY