From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.comp.tex.context/951 Path: main.gmane.org!not-for-mail From: Matthew Baker Newsgroups: gmane.comp.tex.context Subject: Re: searchable mail archives Date: Thu, 30 Sep 1999 10:23:09 +0200 Sender: owner-ntg-context@let.uu.nl Message-ID: References: <37F32A3C.F373F9EF@wxs.nl> Reply-To: Matthew.Baker@gmd.de NNTP-Posting-Host: coloc-standby.netfonds.no Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Trace: main.gmane.org 1035391791 28540 80.91.224.250 (23 Oct 2002 16:49:51 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Wed, 23 Oct 2002 16:49:51 +0000 (UTC) Original-To: Context List In-Reply-To: <37F32A3C.F373F9EF@wxs.nl> Xref: main.gmane.org gmane.comp.tex.context:951 X-Report-Spam: http://spam.gmane.org/gmane.comp.tex.context:951 On Thu, 30 Sep 1999, Hans Hagen wrote: > I have no objections. One advantage is that new users can easily spot > users that are located in the same country. Is it possible to split the > email addres? That way, programs cannot easily detect them but users can > compose them. > > something: pragma@wxs.nl then becomes pragma @ wxs nl i.e. strip the > . and ad spaces around @ Programs won't be able to access the messages anyway because they are in an SQL database which can be accessed only through a CGI script, ie they are not static HTML. Unless, of course, someone writes a bot that passes search information to the CGI script. But if they can do that, they can decode an altered Email address I guess. - Matt -- Dr. Matthew Baker matthew.baker@gmd.de GMD - FIT.MMK http://fit.gmd.de/hci/pages/matthew.baker.html