Stan Ryckman wrote:
> John Lines wrote:
> >
> > I would like to see a standard header for all mailing lists, for example:
> >
> > List-name: list-managers
> >
>
> Look for RFC2369, which I think is still Standards Track.
> There's a copy at (among other places):
> http://www.cis.ohio-state.edu/htbin/rfc/rfc2369.html
> "List-Unsubscribe" is the header which would always be present.
> Its contents are the obvious address, and would change only
> if the list moved.
>
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.
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])
> Onelist.com lists now use them:
> List-Unsubscribe: <mailto:[EMAIL PROTECTED]>
> where XXXX is the listname.
>
> As for filtering on it, especially creating folders automatically...
> you'll have to decide how you want your setup to behave when
> somebody forwards/bounces/resends (pick your terminology) a message
> to you, but from a list you aren't subscribed to, and their software
> leaves that header in.
>
A good point - though you would presumably work out what had happened when
you read the message in the new folder.
John Lines
