From: Hallvard B Furuseth <h.b.furuseth@usit.uio.no>
Subject: Re: Unique? Message-Id generation by Gnus
Date: 13 Mar 1998 22:47:52 +0100 [thread overview]
Message-ID: <HBF.980313vn9o@bombur2.uio.no> (raw)
In-Reply-To: Matt Armstrong's message of "13 Mar 1998 11:14:40 -0800"
Matt Armstrong <matta@geoworks.com> writes:
> a worry of mine over message-unique-id's use of user-mail-address to
> get the domain name of the machine.
It does that only as a backup.
> The Message-Id should be generated from what is in the Sender: field,
It is, indirectly. The sender field is generated from (system-name).
See (message-make-sender) in message.el. (message-make-fqdn), which
generates the domain part of the message ID, tries:
first (system-name) if that has at least 2 components,
then mail-host-address if that has at least 2 components,
then user-mail-address' domain.
> not the user-mail-address. My UID isn't guaranteed to be unique under
> the bigfoot.com domain.
Note that your message's ID is <uvhtixv1b.fsf@geoworks.com>. It does
not fall through to using mail-user-address.
--
Hallvard
prev parent reply other threads:[~1998-03-13 21:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-03-12 22:45 Matt Armstrong
[not found] ` <x74t138ixz.fsf@peorth.gweep.net>
1998-03-13 19:14 ` Matt Armstrong
1998-03-13 21:47 ` Hallvard B Furuseth [this message]
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=HBF.980313vn9o@bombur2.uio.no \
--to=h.b.furuseth@usit.uio.no \
/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).