Path: utzoo!attcan!uunet!snorkelwacker!usc!zaphod.mps.ohio-state.edu!pacific.mps.ohio-state.edu!ohstpy!miavx1!pemurray From: pemurray@miavx1.acs.muohio.edu (Peter Murray) Newsgroups: comp.protocols.tcp-ip.ibmpc Subject: Re: EMAIL for IBM PC's - SMTP Ethernet service Message-ID: <1817.26a4462f@miavx1.acs.muohio.edu> Date: 18 Jul 90 16:21:19 GMT References: <1990Jul16.204030.4818@naitc.uucp> Lines: 80 In article <1990Jul16.204030.4818@naitc.uucp>, karl@naitc.uucp (Karl Denninger) writes: > We're looking for a PC-based SMTP Email package for MSDOS. > > Requirements: > 1) Must coexist with PC/NFS or something similar (we're willing > to look at other packages for file service as well). We run PC/NFS in our department. Our PCs use an implementation of the POP (*P*ost *O*ffice *P*rotocol) to send and receive mail. The PC client program is called Lifeline Mail, and it may come with PC/NFS (I'm not sure on this point). > 2) Should allow for keeping of the mail on the SERVER. We definately > do not want each PC to have a local copy of the email! Mail is stored on the server machine and can be picked up from any machine in the office. > 3) Can either use a "daemon pickup" type of outgoing mail capability > (where the client puts the mail in an "outbox" and a daemon > processes it for delivery), or a direct SMTP connection to the > server. Either is acceptable. A POP client will connect to a POP server when the mail is sent for delivery. When it reaches a POP server, it is fed into the normal mailing program (SENDMAIL in our case.) > 4) Must be full-screen and "windowey". No line-oriented packages need > apply. The are many client implementations of POP. I'm sure you can find one to meet your needs. > 5) Must co-exist with Unix accounts on the same machine; that is, > if can't "steal" email from existing Unix accounts unless the user > specifies so (or an administrator does). In our implementation, the user does have an account on the Unix box. When the POP client makes a connection with the server, all mail in the Unix mailbox is transfered to the PC and then deleted from the UNIX box. You may be able to change this. > 6) Should be reasonable to acquire; we're looking at perhaps 100 copies > or more, and if it's too expensive I'll just write it myself! POP itself is an RFC (can't remember the number right now). There are many commercial and free distributions of the client programs. You can find them for PCs, MACs, and just about any other kind of computer. > 7) Should not be a TSR. It >is< acceptable for the client to read > the mail off a net USE'd drive; in fact, that may be preferrable. > For outgoing transmission an SMTP connection would appear to be > ideal. It is not a TSR. The mail is received and sent while the client program is running. (A daemon always runs on the server.) > 8) Ease of use is a must; folder support and the like is a big plus. This depends on what implementation you choose. > Commercial and free packages welcome. If we can't find one, we'll have to > write it from scratch. Whatever is recommended has to be usable in a > commercial environment; we definately will be doing that. > > Thanks in advance! I would say definitely don't write something from scratch. POP works really well for us. I apologize that I don't have a listing of software or FTP sites that have POP clients, but they should be rather easy to find. Good luck! Peter -- Peter Murray Neat UNIX Stunts #4: pemurray@miavx1.bitnet 215 Foxfire Dr #308 csh> \(- murrayp@apsvax.aps.muohio.edu Oxford, OH 45056 NeXT Mail: pmurray@next4.acs.muohio.edu 513/523-5994