In article <op.tkworcxbm9g4qz-EMAIL REMOVED>, William T***o <usenet> wrote:
>preventing spam is the tricky part. For my part I like to keep things
>simple (I have not the resources to be an avenging angel) so the ip that
>connects to servers in my control is the ip that gets blocked.
I don't understand that. It's not because those who claim to be avenging
angels of spam are sad posuers, but that blocking all IP addresses can't
be right. Maybe the idea is to block previous senders of spam. But
blacklisting IP addresses that have sent spam in the past is often good,
but often need to be de-listed eventually. A bigger problem is that
unless you are running AOL, you are unlikely to have enough traffic to
blacklist IP addresses quickly enough, and so need to use other tactics.
Even Spamhaus advocates more defenses against spam than DNSBLs against
SMTP client IP addresses, such as checking URLs in message bodies.
Disclaimer: some people might think my views of good spam defenses are
biased by my own enterprises.
>> But of course anyone who competent to have written the world's easiest
>> PHP form to email script ...
>
>Frankly, I thought the case was well made until the personal attacks came
>in.
>
>Oh well.
The possibility that the other person might share significant responsible
for the floods of PHP spam seen until recently seems relevant to his
defense of the innocense of his customers. Even if his code is not
what I suspect, his defense of his competitors' customers use of his
competitors' malware cannot be seen as disinterested.
To be more explicit and personal, someone who feels no shame
advertising as a major claim to fame something as trivial as a
form-to-email PHP script is unlikely to be the most competent hack
I've encountered. Even if his PHP form-to-email script is now safe,
I have dark suspicions of its past.
(I see a lot less PHP spam lately, and have the impression that others
see the same.)
Vernon Schryver
EMAIL REMOVED