From: spamtrap@koldfront.dk (Adam Sjøgren)
Subject: Re: How to get information about your system and network for setting up gnus email
Date: Mon, 16 Sep 2002 14:35:51 +0200 [thread overview]
Message-ID: <87bs6yw1qw.fsf@virgil.koldfront.dk> (raw)
In-Reply-To: <y44lm62gmr8.fsf@nestle.ai.mit.edu>
On 16 Sep 2002 08:08:43 -0400, Don Saklad wrote:
> I've seen people with expertise do this to their delight ! It just
> doesn't make any sense that the information isn't available except
> by oral accounts.
The people that have impressed you so much by doing this have
undoubtly been guessing.
The reason that they have been successful is probably that there are
de-facto standards for what mailservers are called. Usually people
call them "mail.[domain]", "smtp.[domain", "pop.[domain]" or similar.
Guessing, for instance, that pop.ai.mit.edu is a mailserver serving
mail via POP for ai.mit.edu is not a far out guess, because
pop.ai.mit.edu exists. Same thing goes for news.ai.mit.edu and
mail.ai.mit.edu.
Incidently those three guesses might be appropriate for your specific
setup at ai.mit.edu.
But I must stress: These are *guesses*. The only authoritative way to
get the *correct* answer is to get the information for the people
responsible for the news and mailservers you need to use.
> The question is what are some of those files or commands?....
If you want to know whether your guess on a hostname is a name
associated with a machine, you can look it up in the Domain Name
System, DNS.
On most unix machines you can use the command "host" to do this.
For instance:
$ host mail.ai.mit.edu
mail.ai.mit.edu CNAME life.ai.mit.edu
life.ai.mit.edu A 128.52.32.80
$
tells you that there is actually a machine that is supposed to respond
to the name "mail.ai.mit.edu".
If, on the other hand, you try to look up a non-existing machine with
the "host" command, you get something similar to this:
$ host donsbox.ai.mit.edu
donsbox.ai.mit.edu A record currently not present
$
That way one can educate ones guesses. But they're still nothing more
than guesses.
Best regards,
--
"Så har den første snøen falt Adam Sjøgren
men det er ikkje derfor det er kaldt" asjo@koldfront.dk
next prev parent reply other threads:[~2002-09-16 12:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <y44r8fugvs1.fsf@nestle.ai.mit.edu>
2002-09-16 10:00 ` John Paul Wallington
2002-09-16 10:19 ` Kai Großjohann
[not found] ` <wtnbs6yi94z.fsf@licia.dtek.chalmers.se>
2002-09-16 12:08 ` Don Saklad
2002-09-16 12:35 ` Adam Sjøgren [this message]
[not found] ` <y44y9a13dhw.fsf@nestle.ai.mit.edu>
2002-09-17 0:04 ` RL
[not found] ` <8765x5zmrn.fsf@virgil.koldfront.dk>
[not found] ` <y44admhk3ry.fsf@nestle.ai.mit.edu>
2002-09-17 12:20 ` How to get informational details " Josh Huber
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87bs6yw1qw.fsf@virgil.koldfront.dk \
--to=spamtrap@koldfront.dk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).