|
|
Posted by boclair on 05/24/07 09:37
Schraalhans Keukenmeester wrote:
> One of my customers' site has been 'discovered' by the spammers community.
> What else is new.
>
> None of the messages they posted sofar ended up showing in the guestbook,
> since they fail to pass the correct verification string. (yes, available
> in written text and audio for the visually impaired)
>
> Yet the volume and size of unsuccesful posts is increasing to a point
> where they may become a burden on server and bandwith.
>
> I added some logic to the scripts blocking spammer ip adresses via
> .htaccess, but this proves pretty useless, and might block the innocent.
> Their addresses may be spoofed, their systems unknowingly abused by
> others.
>
> Given the fact I have rather limited freedom on this client's host, what
> would be your recommended means of preventing spam submission in the first
> place, if possible? Of course, anything taking up as much or more
> resources than my current solution wouldn't really improve things.
Prevent unacceptable submissions being written to the dat file, database
table. One way is to apply substr_count() as a condition of the record
being inserted. eg
if (
($message)
AND ((substr_count($message, 'porn')==0))
AND ((substr_count($message, 'sex')==0))
)
{insert record}
Louise
Navigation:
[Reply to this message]
|