On Tue, May 06, 2008 at 05:31:49AM -0700, Gregory Hicks wrote:
> > I think a better way to do this is to cause the archives to expose
> > the relevant headers. This would provide the same URL and would
> > help train people to look in the headers for List-Id, List-Archive, etc.
>
> This is mail user agent (mail reader) behaviour. My mailer (Solaris
> based) hides all headers except Date, From, To, Subject and Cc. If I
> need to see headers, then I can unhide all of any hidden.
Right, I know it's MUA behavior -- I use mutt and have it set up to
display a similar set of headers by default as well as a secondary
set (RFC 2369) on request (and in a different color so that it grabs
my attention even when bleary-eyed).
What I'm suggesting is that in an archive, which presumably people are
viewing with a web browser and not a MUA, that exposing those headers
(and making the links live) will serve the purpose of easily directing
people to the relevant URLs and will also gradually condition them that
those headers exist, and that they (not subject-line tags) should be
used for filtering/sorting, as in:
:0:
* ^List-Id:.*<nanog-futures.nanog.org>
nanog-futures
which is a procmail recipe that works for this list.
Aside: a quick check of the mailing lists I'm on indicates that 70%
use List-Id, 10% use Mailing-List, 6% use X-Mailing-List, and the rest
don't appear to use anything that deliberately tags messages (although
"Sender:" is often reliable enough for filtering).
I'll freely admit that I have an agenda here: I'd like to see these headers
used universally, and I'd like to see them fully supported in MUAs. As that
happens, I hope that use of message-body headers and footers will diminish,
as those often wind up being repeatedly, uselessly included by top-posting,
full-quoting email newbies, often with gratuitous HTML markup.
---Rsk
_______________________________________________
Nanog-futures mailing list
Nanog-futures@nanog.org
http://mailman.nanog.org/mailman/listinfo/nanog-futures
