John Lines wrote:
> I forgot to mention that I had looked at rfc2369 (I remember the discussion
> about it on list-managers in August 1998).
>
> I agree that it would be good if more mailing lists supported this, but
> it does not deal with the problem of lists which move hosts (this is not a
> problem for onelist, as they assume that they will always be hosting the
> list.
But YOU might want to take YOUR list from onelist to topica, for
example. (There might be reasons down the road; I'm not suggesting
that anyone do this or that one is better than the other.)
> I was wanting a header whose sole purpose was to identify the name of the
> list for filtering purposes, but which would be independent of the hosting
> location. (I appreciate that this creates the problem of the non-uniqueness
> of list names - you would still have to do complex filtering if you wanted
> to be subscribed to [EMAIL PROTECTED] and [EMAIL PROTECTED])
There is a "List-Id:" header proposed as well (it's a "work in progress"
which you can find at:
http://www.ietf.org/internet-drafts/draft-chandhok-listid-04.txt
)
This would cover address changes within a domain (i.e., some changes
to the "List-Unsubscribe" header). However, it still uses either
domain name or "localhost". It doesn't seem to me to address what
happens if the list moves to a different domain, or (if the
List-Id can move with the list) then what happens if the domain name
becomes unfunded and re-issued to someone else. I did comment on
these issues to the list-header mailing list some time ago. I agreed
with the consensus there that we don't need YetAnotherRegistryForThings,
but there are ways not to use the domain name directly either.
Cheers,
Stan
