ken@argus.UUCP (Kenneth Ng) (10/19/86)
In article <755@mtune.UUCP>, jhc@mtune.UUCP (Jonathan Clark) writes: > In article <3000002@cdp> scott@cdp.UUCP writes: > >How can you send binaries in mail. > > You can't. That's why uucp(1) and uuto(1) were invented. Encoding is > cheating. > As long as all the sites on the path are Unix machines you are probably ok. But if it should encounter other machines on the way I wouldn't trust uucp or uuto at all. The worst case is if "smart" mailer routes it over bitnet for speed purposes. I seriously doubt if there will be ANYTHING usable after it goes to bitnet and back. -- Kenneth Ng: Post office: NJIT - CCCC, Newark New Jersey 07102 uucp !ihnp4!allegra!bellcore!argus!ken *** WARNING: NOT ken@bellcore.uucp *** !psuvax1!cmcl2!ciap!andromeda!argus!ken bitnet(prefered) ken@orion.bitnet McCoy: "This won't hurt a bit" Chekov: "That's what you said last time" McCoy: "Did it?" Chekov: "Yes"
levy@ttrdc.UUCP (Daniel R. Levy) (10/19/86)
In article <755@mtune.UUCP>, jhc@mtune.UUCP (Jonathan Clark) writes: >In article <3000002@cdp> scott@cdp.UUCP writes: >>How can you send binaries in mail. >You can't. That's why uucp(1) and uuto(1) were invented. Encoding is >cheating. >You could if /bin/mail supported a logical separation between a letter >and its envelope. As I know nothing about X.400 except that it weighs >more than I care to read, and very little about other mail delivery >systems, let me ask a possibly stupid question: do any other mail >subsystems support this separation so that binaries could be mailed? >Jonathan Clark >[NAC,attmail]!mtune!jhc >My walk has become rather more silly lately. I'd like to pose yet another issue to feed the fire: how would one implement mailing "binaries" on, to, or from systems where, instead of the sensible Unix paradigm of a data file being a continuous stream of bytes, there are about a jillion different file formats, all record-based? I'm talking in particular about our old friend VMS. One would not only have to send the raw data itself but also supplementary data about record boundaries, record attributes, file attributes... etc. This would seem to call for a "neutral" exchange format, if such were even possible. -- ------------------------------- Disclaimer: The views contained herein are | dan levy | yvel nad | my own and are not at all those of my em- | an engihacker @ | ployer or the administrator of any computer | at&t computer systems division | upon which I may hack. | skokie, illinois | -------------------------------- Path: ..!{akgua,homxb,ihnp4,ltuxa,mvuxa, go for it! allegra,ulysses,vax135}!ttrdc!levy
jhc@mtune.UUCP (Jonathan Clark) (10/24/86)
In article <3000002@cdp> scott@cdp.UUCP writes: >How can you send binaries in mail. You can't. That's why uucp(1) and uuto(1) were invented. Encoding is cheating. You could if /bin/mail supported a logical separation between a letter and its envelope. As I know nothing about X.400 except that it weighs more than I care to read, and very little about other mail delivery systems, let me ask a possibly stupid question: do any other mail subsystems support this separation so that binaries could be mailed? -- Jonathan Clark [NAC,attmail]!mtune!jhc My walk has become rather more silly lately.