You also lose some email from those of us who got rather tired of this
cumbersome system putting the burden on senders... :-)
I rarely bother with these sort of challenge-response systems anymore.
If you're not getting my emails, and they are important (to you)
you'll add me once you figure out you're not getting them.
If not, oh well, guess you didn't want my email info that badly anyway.
So, just be aware, that the jaded among us won't click through that
usage barrier.
If you want contact via your site, a FORM page in PHP takes only an
hour or so, and you can put all kinds of restrictions on usage in
terms of volume of email from/to or based on user IP/Agent/heuristics
guessing if it's the "same" user or only if they are willing to turn
on and accept cookies...
All of which is ALSO easily beat by a determined attacker, but
probably less likely to be subverted in automated fashion than the
simplistic HTTP/HTML char substitution.
Though, as I said, the bad guys are catching SO MANY fish every time
they try to harvest, it seems like so far the simplest obfuscation is
"enough" I think Netcraft (?) did a field-test on this awhile back...
On Mon, November 20, 2006 8:11 am, Jeff wrote:
> I am running my own email server software - and it has whats called
> Challenge Response.
>
> Basically, when you get an email from someone for the first time, it
> auto
> replies with a link they have to click on, and enter in some text into
> a box
> to authorize themself. They have 2 weeks to enter in the digits or
> else they
> are on the block list.
> Once they enter in the number to authorize, the email is sent through
> to
> your inbox (It basically just sits on the server, you don't know it's
> there
> until they auth.)
>
> Also, if you email someone, it automatically puts them on your allow
> list,
> so when they reply they do not need to authorize themself.
>
> It's pretty neat, I would also get about 50 emails a day, now I get
> zero!
>
> Jeff
> ----- Original Message -----
> From: "Frank Arensmeier" <frank.arensmeier@xxxxxxxxxxxxxxxxx>
> To: "clive" <clive@xxxxxxxxxx>
> Cc: "PHP List" <php-general@xxxxxxxxxxxxx>
> Sent: Monday, November 20, 2006 8:21 AM
> Subject: Re: Little script that might help against some
> email-/webcrawlers
>
>
>>I totally agree. And I haven't said that this would be 100%
>> bulletproof. I
>>get about 50 - 60 spam mails per day (maybe not much, but I think
>> it's
>>enough). And if this is preventing only some of the email spiders to
>> suck
>>out my email adress from the contact pages, well, why not.
>>
>> I mean, if you want to have 100% protection - don't have email
>> adresses
>> on your pages at all. However, I think that it is more important
>> for my
>> visitors to be able to contact me, than to start a never ending
>> fight
>> against email spiders.
>>
>> /frank
>>
>> 20 nov 2006 kl. 14.09 skrev clive:
>>
>>> Frank Arensmeier wrote:
>>>
>>>> Call the function e.g. by:
>>>> <a href="mailto:<?php echo encode_email ("me@xxxxxxxxxx" ); ?
>>>> >">Mail me!<a/>
>>>
>>> nice - but don't you think spammers might be able to test for
>>> ascii and
>>> convert it for there use?
>>>
>>> clive
>>>
>>> --
>>> PHP General Mailing List (http://www.php.net/)
>>> To unsubscribe, visit: http://www.php.net/unsub.php
>>>
>>>
>>
>> --
>> PHP General Mailing List (http://www.php.net/)
>> To unsubscribe, visit: http://www.php.net/unsub.php
>>
>
> --
> PHP General Mailing List (http://www.php.net/)
> To unsubscribe, visit: http://www.php.net/unsub.php
>
>
--
Some people have a "gift" link here.
Know what I want?
I want you to buy a CD from some starving artist.
http://cdbaby.com/browse/from/lynch
Yeah, I get a buck. So?
--
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php
