Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Posting-Version: version B 2.10.2 9/18/84; site watdcsu.UUCP Path: utzoo!watmath!water!watdcsu!herbie From: herbie@watdcsu.UUCP (Herb Chong [DCS]) Newsgroups: net.unix,net.unix-wizards Subject: Re: mail encryption/decryption Message-ID: <1514@watdcsu.UUCP> Date: Fri, 5-Jul-85 11:22:49 EDT Article-I.D.: watdcsu.1514 Posted: Fri Jul 5 11:22:49 1985 Date-Received: Sat, 6-Jul-85 09:37:02 EDT References: <518@dicomed.UUCP> <142@whuts.UUCP> <455@bu-cs.UUCP> Reply-To: herbie@watdcsu.UUCP (Herb Chong [DCS]) Organization: U of Waterloo Lines: 23 Xref: watmath net.unix:4969 net.unix-wizards:13730 Summary: In article <455@bu-cs.UUCP> root@bu-cs.UUCP (Barry Shein) writes: >It also keeps the records short (I >think 45 chars by default) which is useful if you have to forward over >some routes, especially BITNET spools, some of which will chop at 80 >(punch spools ya know.) I even moved it to our IBM3081 to aid using SMTP >as a 'poor person's FTP' (yes we have a license...geeez!) tho there are >limits to ascii->ebcdic conversions. uuencoded files have problems in BITNET file transfers if you don't send in PUNCH or PRINT format because trailing blanks are stripped and need to be replaced before uudecodeing. also, UREP allows each site to define their own ASCII-EBCDIC translation tables (yes, there's more than one valid translation). both these problems have bitten me before when sending data to other Unix systems via BITNET. Herb Chong... I'm user-friendly -- I don't byte, I nybble.... UUCP: {decvax|utzoo|ihnp4|allegra|clyde}!watmath!water!watdcsu!herbie CSNET: herbie%watdcsu@waterloo.csnet ARPA: herbie%watdcsu%waterloo.csnet@csnet-relay.arpa NETNORTH, BITNET, EARN: herbie@watdcs, herbie@watdcsu