Path: utzoo!attcan!uunet!wuarchive!zaphod.mps.ohio-state.edu!pacific.mps.ohio-state.edu!ohstpy!miavx1!miamiu!js05staf
From: JS05STAF@MIAMIU.BITNET (Joe Simpson)
Newsgroups: comp.protocols.appletalk
Subject: Re: MAC MS-MAIL to SMTP gateway?
Message-ID: <90281.090712JS05STAF@MIAMIU.BITNET>
Date: 8 Oct 90 14:07:12 GMT
References: <34162@cup.portal.com> <26FE4E59.1748@intercon.com> <546@fciva.FRANKLIN.COM> <2707782A.6C5@intercon.com> <14017@slice.ooc.uva.nl> <1990Oct5.072457.17013@news.arc.nasa.gov> <1990Oct5.211803.11653@ux1.cso.uiuc.edu>
Organization: Miami University - Academic Computer Service
Lines: 14

uuencode is a much older, and more universal, binary->text tranformation
standard.  Implementations exist for many computer systems.  MacBinary
is the new kid on the block.
 
The troubling part for me is that I belive MacBinary performs services
beyone simply binary->text transformation.  It does this in support of the
Mac's unique file structure.  If this is so, one would have to stuffit
(or compressit or ...) before sending to obtain a flat binary file in the
data fork. This would be necessary for all mac applications.
Many applications write fiat binary files in the data fork.  Thus Excell
spreadsheets would transfer easily.
 
We are evaluating GatorMail-Q now.  I'll let the net know if my suspicions
are correct.  Unless, of course, someone beats me too it!  :-)