From Pierre Phaneuf · 1996-04-11 16:43 · #73159 in FREE25
In reply to How a new nodelist would work..... by Jason Steck
JS> etc. The point is that more than just an IP might be necessary. The JS> e-mail address in the "mapped" section of my nodelist entry would JS> specify that I was able to handle MIME/UUENCODE packets embedded in an JS> RFC-822 e-mail. An FTP address (complete with path) would specify an JS> FTP-accessible inbound area. I think that if sending mail over FTP or in UUENCODEd packets is possible for everyday mail, it is a kludge and is destined to disappear with time... It must be set by hand before the system can accept or export mail, where a nodelist is a list of systems that can be contacted right now... JS> The point is to make the technology of it as flexible as possible to JS> allow for permutations (such as the use of shell accounts and scripts) JS> that we may not think of ahead of time. Every "restriction" we place JS> on it limits its usefulness down the road. If we were to do that, the JS> new technology would just be a re-do of the current limitations that JS> FTS technology imposes. It should not encourage kludges and cruftyness tough... I have yet to envision a nodelist with every script and options to access a system stored in it... Let only purpose-built program be listed in a nodelist, so that nodes can *always* be contacted... I agree with expanding it, but putting in UUENCODEd mail packet and FTPmail as valid crashmail recipient pathways is maybe pushing it a little too far... Both requires quite extensive and custom script-writing to be usable... Pierre phaneuf@absint.login.qc.ca --- FMail/386 1.02 * Origin: Zaphod Beeblebrox for President! (1:167/136.14)