Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!pacific.mps.ohio-state.edu!linac!att!pacbell.com!ucsd!ucbvax!THUMPER.BELLCORE.COM!nsb From: nsb@THUMPER.BELLCORE.COM (Nathaniel Borenstein) Newsgroups: comp.mail.multi-media Subject: Re: Multiple Binary Attachments And RFC-822 Mail Message-ID: Date: 28 Mar 91 13:56:41 GMT References: <575@cronos.metaphor.com> Sender: daemon@ucbvax.BERKELEY.EDU Distribution: inet Organization: The Internet Lines: 24 Excerpts from internet.mmm-people: 28-Mar-91 Re: Multiple Binary Attachm.. Phil Fernandez@apple.com (1073) > In article <40567@cup.portal.com> Will@cup.portal.com (Will E Estes) writes: > >Have there been any attempts to define a standard for the transmission > >of multiple binary files inside of an RFC-822 envelope? Is there > >anything about RFC-822 that makes this impossible? It seems to me that > >this capability is going to become very important to companies who > >want to make use of cheap TCP/IP internets and SMTP as the backbone > >for their email networks. > At Metaphor we have done a fair amount of thought-work on this issue, > and have built an effective working prototype for the transmission of > multiple binary attachments in an RFC-822 message transmitted via > SMTP. Actually, there have been DOZENS of prototypes. A lot of the people and organizations who have built such prototypes are now trying, via the IETF-SMTP mailing list, to converge on a standard way of representing multiple body parts. We're currently working towards a third version of a draft RFC, which will (with luck) be posted to the list next week. -- Nathaniel Borenstein