Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!samsung!think!snorkelwacker!ira.uka.de!smurf!smurf.ira.uka.de From: urlichs@smurf.ira.uka.de (Matthias Urlichs) Newsgroups: comp.protocols.appletalk Subject: Re: Mail for the mac and smtp Message-ID: <1482@smurf.ira.uka.de> Date: 5 Feb 90 16:24:00 GMT References: <9002021644.AA25000@icarus.cns.syr.EDU> Sender: news@smurf.ira.uka.de Organization: University of Karlsruhe, FRG Lines: 33 Comp.protocols.appletalk, from demarsee@ICARUS.CNS.SYR.EDU (Darryl E. Marsee): < >My point of view is that not everyone wants/can afford these < >commercial systems. It would be nice if /usr/ucb/mail was rehosted < >to the Macintosh (with a mac like interface) and sendmail so that < >real RULES could be used. I know this may be easier said than done, < >but I thought I would bring it up. < < I'd like to put my vote in for Stanford's MacMH program, which < uses a Unix system as a revised POP server. We use it campus-wide < here, and it works great. < < Advantages: [ many [omitted ]] < Disadvantages: Requires Macs to connect to IP network (either directly < or through a Kinetics/Gatorbox gateway) Major disadvantage: MacIP and MacMH don't yet work with Apple's MacTCP. (At least last time I asked them, they didn't.) NB: With some trickery, you don't have to have an account for each user. (Some of this is included with the MMDF MTA.) Right now, we try to use HyperCard to interface our Macs to the Unix boxes. Advantage: Flexibility. For instance, the latest version of MacMH we have (I think it's 2.0) didn't allow for user-specific headers, didn't create a Date: header (which is a problem with mmdf's SMTP implementation, since it does not add this header), and a bunch of other problems. Major disadvantage: Reliability. HyperTCP still seems somewhat flakey. Getting updates distributed is also a bit of a hassle, although I am giong to get this organized... < Disclaimer: People here are also using HyperCard to read News and to FTP stuff.