[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[ale]OT It begins...

The Sympa mailing list engine ( www.Sympa.org ) claims to be able to
protect addresses by either the @/" AT " substitution paradigm or
JavaScript mangling.  It can also add an additional level of protection
to web archives of the mailing list by requiring a form-generated cookie
to be eaten by the client before the archive can be seen.

However, I believe we're using Mailman ...

On Tue, Jan 27, 2004 at 03:53:29AM -0600, ChangingLINKS.com wrote:
> I don't think you are correct.
> As I mentioned before, the local Linux group has already implemented such 
> code. I am not *sure* that they overcame the "emails in the body" issue that 
> you raised, but my guess is that they did. I can get more information on how 
> to do it if no one in the ALE knows how.
> -- 
> Wishing you Happiness, Joy and Laughter,
> Drew Brown
> http://www.ChangingLINKS.com
> On Tuesday 27 January 2004 00:26, Jim Popovitch wrote:
> > There is no feasible way to do what you are asking for, short of
> > removing the sender's email address entirely.  Even then... it is
> > ineffective because the body of the email may contain email addresses
> > from a reply or forward, and the diversity of email clients makes it
> > near impossible to determine where a client may inject the original
> > posters email address (headers included).  
> > 
> > Given the use of email addresses in sigs, RFCs, announcements, and code
> > samples (not to mention emails containing valid addresses that posters
> > are trying to share, i.e. Congressmen, etc), it would require human
> > intervention (i.e. a moderator, also not perfect) to scan each email and
> > decide what email addresses should remain. 
> > 
> > If you don't want your address public, get a diff email account for
> > public lists.
> > 
> > -Jim P.
> > 
> > On Mon, 2004-01-26 at 22:32, Robert Reese wrote:
> > > Hash: SHA1
> > > 
> > > I'd love that to, but it isn't quite what I meant.  What I meant was
> > > for the list manager (sorry, I don't know who that is) to change the
> > > behavior of the archives so that the email addresses cannot be
> > > obtained via bots or search engines.  I have seen a good many lists
> > > that offer this protection for the  members.