Hi, One approach we've been mulling over is using a separate email address @register4less.com, one per account, for each client. Email that would be sent to the clients can then be run through a junk filter.
We're started using X-Spam for filtering, and it's pretty good. Of course something like this would be opt in. This would also more clearly identify to the registrant when they get mail if it's from their whois listing. Downside of course is the potential bandwidth & machine resources of this. Doug. Quoting Swerve <[EMAIL PROTECTED]>: > Hi Derek, > > Do you have any suggestions of how to protect email addresses from being > harvested from the whois by spammers and pseudo opt-in companies? > > thanks, > > Swerve > > > From: "Derek J. Balling" <[EMAIL PROTECTED]> > > Date: Wed, 12 Jun 2002 15:35:04 -0400 > > To: <[EMAIL PROTECTED]> > > Subject: RE: Geektools whois proxy - OpenSRS Whois Results > > > > At 2:56 PM -0400 6/12/02, Ross Wm. Rader wrote: > >> The time pressure really stems from a larger strategy that we are > >> working. Whois is essentially broken. It doesn't give registrants the > >> privacy they need, > > > > I'm still not convinced that the registrant - a tenant of a shared > > namespace - has any NEED of privacy. There does not yet to seem to be > > a demonstrated need for such, thus making this statement as a factual > > statement and not just an opinion would be unwarranted. > > > > D > > > > -- > > > > +---------------------+-----------------------------------------+ > > | [EMAIL PROTECTED] | "Thou art the ruins of the noblest man | > > | Derek J. Balling | That ever lived in the tide of times. | > > | | Woe to the hand that shed this costly | > > | | blood" - Julius Caesar Act 3, Scene 1 | > > +---------------------+-----------------------------------------+ > > >
