Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: Lute Kamstra <Lute.Kamstra@cwi.nl>
Subject: Re: Fully Qualified Domain Name
Date: 13 Sep 2002 10:53:58 +0200	[thread overview]
Message-ID: <sgdvg5a46e1.fsf@occarina.pna.cwi.nl> (raw)
In-Reply-To: <844rcujq2u.fsf@tecont.de>

Ralf Muschall <ralf@tecont.de> writes:

> Lute Kamstra <Lute.Kamstra@cwi.nl> writes:
> 
> > "echo $HOSTNAME".  Do you really need to know _your_ domain name?  If
> 
> This just tells you what you types yourself into /etc/HOSTNAME.

I assumed the OP didn't set up his own system.  If he did, he would
probably not ask the questions he is asking.

> It is nontrivial to get the FQDN stuff right for an enduser.  One
> might disable the Message-ID generation in the newsreader.  Then the
> local leafnode will create one.  In order to disable that, one has to
> patch it.  Then the provider's news server will make one, which is
> probably OK.  The problem is that an enduser's computer normally has a
> variable IP and no real name at all ($HOSTNAME is *not* one), since
> it is not DNSed.

Am I missing something?  Why do you need to know, or even have, your
domain name to be able to use Gnus?

> > you want to configure Gnus, you probably only need to know the domain
> > name of your mail server(s) and your news server.  The folks that
> 
> This still does not help perfectly - the thing right of the @ in the
> Message-ID will then be the same as for other users of the same
> provider.  If the provider makes the Message-ID, no problem.  But if
> the left part is made by the users, they might not be unique.

Why do you worry so much about message-ID's?  From the Message manual:

,----
| `Message-ID'
|      This required header will be generated by Message.  A unique ID
|      will be created based on the date, time, user name and system
|      name.  Message will use `system-name' to determine the name of the
|      system.  If this isn't a fully qualified domain name (FQDN),
|      Message will use `mail-host-address' as the FQDN of the machine.
`----

So you don't _need_ to have a FQDN.  What are the chances of the first
part of the ID being the same?  What's the worst that can happen when
the ID's of two different messages are the same?

Lute.

-- 
(spook) => "Centro David John Oates MD5"
(insert-file-contents "~/.signature") => (error "`~/.signature' too rude")


       reply	other threads:[~2002-09-13  8:53 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <y44it1bj9da.fsf@nestle.ai.mit.edu>
     [not found] ` <sgdd6rjotc1.fsf@occarina.pna.cwi.nl>
     [not found]   ` <844rcujq2u.fsf@tecont.de>
2002-09-13  8:53     ` Lute Kamstra [this message]
     [not found]   ` <y447khqfryh.fsf@nestle.ai.mit.edu>
     [not found]     ` <sgdptvia1r6.fsf@occarina.pna.cwi.nl>
2002-09-13 15:10       ` Petr Swedock

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=sgdvg5a46e1.fsf@occarina.pna.cwi.nl \
    --to=lute.kamstra@cwi.nl \
    /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).