From: Michael Shields <shields@msrl.com>
Subject: Re: Why article numbers?
Date: Sun, 23 Feb 2003 05:03:14 +0000 [thread overview]
Message-ID: <873cmf8u7h.fsf@mulligatwani.msrl.com> (raw)
In-Reply-To: <m3lm08xa74.fsf@multivac.cwru.edu> (prj@po.cwru.edu's message of "Sat, 22 Feb 2003 16:43:37 -0500")
In article <m3lm08xa74.fsf@multivac.cwru.edu>,
prj@po.cwru.edu (Paul Jarc) wrote:
> I think I should point out that Kai and I seem to be advocating
> slightly different things. Kai's suggestion, AIUI, is to use
> Message-ID header fields as article IDs everywhere.
One wrinkle with this is that it's possible for messages to have no
message-ID. This never happens in news or with most MTAs, but it's
legal in mail. One way it can happen is when using `G f' to read an
mbox-format archive that has incomplete headers.
It's also possible, and not uncommon, for the same mail message to be
delivered twice -- because you receive it both directly and via a
mailing list, or theoretically because an SMTP connection was dropped
after the "." but before the acknowledgment.
> My suggestion is
> to let backends decide how to identify articles, with the only
> requirement being that identifiers should be eq if they are supposed
> to identify the same article. (This includes the possibility of
> symbols whose names are Message-IDs, but does not require that.)
That seems reasonable, especially sine it lets the conversion be done
one backend at a time, or not at all for some backends.
For mail with no message-ID, fake ones could be generated; I seem to
remember VM doing this (with "@toto.iv"). I'm not sure what is the
best way to handle duplicates.
Message-IDs are fine identifiers for news.
--
Shields.
next prev parent reply other threads:[~2003-02-23 5:03 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-07 21:55 Kai Großjohann
2003-02-08 20:38 ` Lars Magne Ingebrigtsen
2003-02-08 23:44 ` Paul Jarc
2003-02-08 23:49 ` Lars Magne Ingebrigtsen
2003-02-09 14:59 ` Kai Großjohann
2003-02-10 18:40 ` Paul Jarc
2003-02-22 20:24 ` Lars Magne Ingebrigtsen
2003-02-22 21:11 ` Kai Großjohann
2003-02-22 21:24 ` Lars Magne Ingebrigtsen
2003-02-22 21:37 ` Kai Großjohann
2003-02-22 21:44 ` Lars Magne Ingebrigtsen
2003-02-23 9:51 ` Kai Großjohann
2003-02-22 22:33 ` Simon Josefsson
2003-02-23 9:52 ` Kai Großjohann
2003-02-23 11:04 ` Simon Josefsson
2003-02-23 13:33 ` Kai Großjohann
2003-02-23 16:56 ` Simon Josefsson
2003-02-23 17:23 ` Kai Großjohann
2003-02-23 11:34 ` Lars Magne Ingebrigtsen
2003-02-23 16:56 ` Michael Shields
2003-02-22 21:43 ` Paul Jarc
2003-02-23 5:03 ` Michael Shields [this message]
2003-02-23 10:28 ` Kai Großjohann
2003-02-23 11:38 ` Lars Magne Ingebrigtsen
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=873cmf8u7h.fsf@mulligatwani.msrl.com \
--to=shields@msrl.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).