home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!haven.umd.edu!darwin.sura.net!dtix!mimsy!nocusuhs!nmrdc1!rdc30
- From: rdc30@nmrdc1.nmrdc.nnmc.navy.mil (Code-03 LCDR Michael E. Dobson)
- Newsgroups: comp.mail.sendmail
- Subject: Re: Replacing UUCP with SMTP in this age...
- Message-ID: <1992Sep10.153316.17758@nmrdc1.nmrdc.nnmc.navy.mil>
- Date: 10 Sep 92 15:33:16 GMT
- References: <1992Sep9.220304.5690@tigger.jvnc.net> <CKD.92Sep9194820@loiosh.eff.org>
- Organization: Naval Medical Research & Development Command
- Lines: 26
-
- In article <CKD.92Sep9194820@loiosh.eff.org> ckd@eff.org (Christopher Davis) writes:
- >VA> == Vikas Aggarwal <aggarwal@tigger.jvnc.net>
- >
- > VA> More and more people are moving to dialup IP protocols like SLIP, CSLIP
- > VA> and PPP. IN all of these 'dialup' cases, mail has to be typically stored
- > VA> on another system and transferred when the dialup system connects.
- >
- > VA> Typically, UUCP provides a very good store and transfer mechanism.
- > VA> What I need (and I think is needed by a lot in this community), is
- > VA> a similar functionality using IP instead of UUCP.
- >
- >Options I've seen used include the old standby UUCP-over-TCP, a "finger
- >trigger" where fingering the 'server' causes it to flush the queue for
- >that client, and there's always the TURN command in SMTP, if anyone ever
- >implemented it ;-)
-
- Another option is the use of POP clients and servers. We do that here,
- especially for DOS users, over SLIP. This does require an account for each
- user on the server and doesn't help for dial-up machines with multiple users.
- It does work quite well, especially for those users who travel a lot and
- want their e-mail on their laptops.
- --
- LCDR Mike Dobson, Sys Admin for | Internet: rdc30@nmrdc1.nmrdc.nnmc.navy.mil
- nmrdc1.nmrdc.nnmc.navy.mil | UUCP: ...uunet!mimsy!nmrdc1!rdc30
- AT&T 3B2/600G Sys V R 3.2.3 | BITNET: dobson@usuhsb or nrd0mxd@vmnmdsc
- WIN/TCP for 3B2 R3.2 | MCI-Mail: 377-2719 or 0003772719@mcimail.com
-