Problems sending mail from .mumble
freimer at ctiusa.com
Tue Apr 15 17:34:29 UTC 2008
This wouldn't be a problem if people would use, and applications would
enforce the use of, proper URL's instead of domain names for web
destinations. The proper URL for a file is file://... IIRC. For a web page
it is http://... I understand people are lazy, including me, but the web
browsers can pre-type in http:// whenever you click on the address bar to
make it easier. For CLI-type applications, well, you're using a CLI so
you're supposedly smart enough to figure it out.
Fred Reimer, CISSP, CCNP, CQS-VPN, CQS-ISS
Senior Network Engineer
Coleman Technologies, Inc.
> -----Original Message-----
> From: owner-nanog at merit.edu [mailto:owner-nanog at merit.edu] On Behalf Of
> Robert Bonomi
> Sent: Tuesday, April 15, 2008 12:56 PM
> To: nanog at nanog.org
> Subject: Re: Problems sending mail from .mumble
> > Date: Mon, 14 Apr 2008 16:07:22 -0700 (PDT)
> > From: Duane Wessels <wessels at packet-pushers.com>
> > Subject: Re: Problems sending mail from .mumble
> > FWIW I was able to find one application, the text browser 'links,'
> > which accepts either filename or hostnames as its commandline
> > argument. From what I can tell its algorithm is something like
> > this:
> > - if tld/extension has two letters --> URL
> > - if less than two letters --> File
> > - if tld/extension is in list of known gTLDs --> URL
> > - else --> File
> The web browser "Lynx" does something very similar. One addendum to
> above logic is that if the DNS look-up fails, it tries to use the
> as a local file path.
> Typo the FQDN in a URL to something that returns NXDOMAIN, and you get
> error message to the effect that lynx 'couldn't access start *FILE*
> (emphasis added.)
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 3080 bytes
Desc: not available
More information about the NANOG