Article View: comp.mail.misc
Article #3558Re: BITFTP grief! (UUNET email-ftp?)
From: CSSE LAN Test Account
Date: Wed, 22 May 1991 17:40
Date: Wed, 22 May 1991 17:40
19 lines
1387 bytes
1387 bytes
In article <1991May22.081251.1026@uunet.uu.net> asp@uunet.uu.net (Andrew Partan) writes: | If someone can write some software that can distinguish between | customer!customer-node!user | and | customer!non-customer-node!user | for all customers w/o us having to keep a database of interior customer | nodes, then we will consider running it. Wasn't this sort of distinction the reason for the domainizing of the mail system? It seems that the way to do it would be to define a domain for your customers (perhaps "uu.net" ;-), and only send things to machines in that domain. Am I missing something? Of course, enforcing the domain's boundaries might be an interesting research problem. Then again, maybe it'd just be an interesting legal problem.
Technical Details
Message-ID:
<22842@shlump.lkg.dec.com>Path:
arc1-ca.pugleaf.net!utzoo!utgpu!news-server.csri.toronto.edu!rpi!dali.cs.montana.edu!uakari.primate.wisc.edu!zaphod.mps.ohio-state.edu!swrinde!elroy.jpl.nasa.gov!decwrl!deccrl!news.crl.dec.com!nntpd.lkg.dec.com!netrix.nac.dec.com!lan_csseReferences:
<81678@bu.edu> <4068@island.COM> <1991May22.081251.1026@uunet.uu.net>Show Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!utzoo!utgpu!news-server.csri.toronto.edu!rpi!dali.cs.montana.edu!uakari.primate.wisc.edu!zaphod.mps.ohio-state.edu!swrinde!elroy.jpl.nasa.gov!decwrl!deccrl!news.crl.dec.com!nntpd.lkg.dec.com!netrix.nac.dec.com!lan_csse From: lan_csse@netrix.nac.dec.com (CSSE LAN Test Account) Newsgroups: comp.mail.misc Subject: Re: BITFTP grief! (UUNET email-ftp?) Message-ID: <22842@shlump.lkg.dec.com> Date: 22 May 91 17:40:36 GMT References: <81678@bu.edu> <4068@island.COM> <1991May22.081251.1026@uunet.uu.net> Sender: news@shlump.lkg.dec.com Distribution: na Organization: Digital Equipment Lines: 19