From: Matt Armstrong <matta@geoworks.com>
Subject: Re: Unique? Message-Id generation by Gnus
Date: 13 Mar 1998 11:14:40 -0800 [thread overview]
Message-ID: <uvhtixv1b.fsf@geoworks.com> (raw)
In-Reply-To: Stainless Steel Rat's message of "12 Mar 1998 20:42:48 -0500"
Stainless Steel Rat <ratinox@peorth.gweep.net> writes:
> -----BEGIN PGP SIGNED MESSAGE-----
>
> >>>>> "MA" == Matt Armstrong <matta@geoworks.com> writes:
>
> MA> Why does Gnus add a Message-Id header instead of letting the news/mail
> MA> server do it?
>
> Because it is strongly recomended that Message-Id strings be
> generated by the MUA, rather than the MTA. The reason...<snip>
I'll accept that at face value.
> MA> With people setting user-mail-address to the base domain name of
> MA> their company/ISP/mail-forwarder, it is possible to get a lot of
> MA> <blahblah.fsf@domain.com> message ids even though the logic that
> MA> generates the "blahblah" part doesn't necessarily guarantee
> MA> uniqueness.
>
> Actually, it does. The "blahblah" part is a hash (sort of) derrived
> from your login name and the current system time. As it is
> practically impossible for you (that is, your login) to generate two
> distinct messages at *exactly* the same time, the hash is
> effectively guaranteed to be unique.
It actually defaults to using the UID, not the text of the user's
login. This doesn't work under NT -- message.el/message-unique-id
should probably add 'windows-nt to the list of system types for which
the UID is not a good thing to use.
I realize now that this is really a worry of mine over
message-unique-id's use of user-mail-address to get the domain name of
the machine. Say all my messages are of the form:
From: matt_armstrong@bigfoot.com
Sender: matta@quark.geoworks.com
The Message-Id should be generated from what is in the Sender: field,
not the user-mail-address. My UID isn't guaranteed to be unique under
the bigfoot.com domain.
--
matta
next prev parent reply other threads:[~1998-03-13 19:14 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 [this message]
1998-03-13 21:47 ` Hallvard B Furuseth
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=uvhtixv1b.fsf@geoworks.com \
--to=matta@geoworks.com \
/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).