protecting list archives
Bernie Cosell
> You should never show addresses in a publicly accessible mailing list
> archive if you can help it. Leave the names (where possible) but hide the
> addresses. You can even do this in message bodies if you want to try to
> protect signatures.
Hmm... Hard to do in message bodies, per se, I'd think, because there
are lots of legitimate reasons why someone would include an email address
in their message and so just looking for mailto URLs in the body and
removing them might cripple some otherwise useful articles.
But as for signatures, would just filtering off after "--<space>" be
sufficient, or is that not widely-enough accepted as a "my .sig begins
here" convention to use for this purpose [and/or are too many list
members probably not clueful enough to be able to get that set up
properly in any event...]
/Bernie\
--
Bernie Cosell Fantasy Farm Fibers
mailto:ber...@fantasyfarm.com Pearisburg, VA
--> Too many people, too few sheep <--
Peter Losher
> You can even do this in message bodies if you want to try to
> protect signatures.
Just how? Don't forget the usual 'On <date>, <email address> wrote:' as
well, as .sig's. We had thought about munging/eliminating anything that
had a '@' in it. but since a lot of code runs thru our lists, that was
considered impratical.
> I would also warn people joining the support list that their postings will
> be archived for public view, and that they should watch what they post, or
> use a spamproofed email account, or both.
We already do that, and we support X-no-archive (although that defeats the
purpose of an archive if everyone has X-no-archive in their messages)...
-Peter
---
Peter Losher <Peter....@nominum.com>
Systems Admin. - Nominum, Inc. PGP Key available on request