Path: utzoo!attcan!uunet!husc6!mailrus!ukma!david From: david@ms.uky.edu (David Herron -- One of the vertebrae) Newsgroups: comp.sys.next Subject: Re: NeXT mail system // CMU Andrew System // "groupware" software Message-ID: <10426@s.ms.uky.edu> Date: 24 Oct 88 22:57:58 GMT References: <2463@hplabsz.HPL.HP.COM> Reply-To: david@ms.uky.edu (David Herron -- One of the vertebrae) Organization: U of Kentucky, Mathematical Sciences Lines: 30 In article <2463@hplabsz.HPL.HP.COM> mayer@hplabsz.UUCP (Niels Mayer) writes: > >Could someone who has used the NeXT mailer comment on it's >functionality. While I haven't used their mailer I think I'm qualified to make some educated guesses :-) Voice/picture type stuff is usually in some binary format. There's no reason to suspect that this would be any different here. BUT, in order for it to be part of e-mail it has to be in printable ASCII. No funny characters, and some limits on what you can assume about tabs and/or end-of-line markers. Now, where to store it? It'll have to be part of the message somewhere. Putting it down in the body would be "inappropriate" because the system isn't really supposed to interpret things in the body, and also this is more an "envelope" type thing. A better place (er.. more appropriate) would be in the header somewhere. BUT, I can see a problem that this'd lead to large headers ... and I won't gaurantee that all systems or user-agents will be able to handle a header that's on the order of 4 or 5 Kbytes. (That's a bit beyond the norm for headers). What *I* am curious about is which mailer is at the transport level? -- <-- David Herron; an MMDF guy <-- ska: David le casse\*' {rutgers,uunet}!ukma!david, david@UKMA.BITNET <-- <-- Controlled anarchy -- the essence of the net.