Mike Fern wrote:
Hi Bill,
Isn't it possible to put the smtp server's ip address into the
RBL/DNSBL and automatically reject all incoming mails?
In the meantime, maybe it's time for the bayesian filter to wake up
from perennial sleep and take action.
Cheers,
Mike
Its more deeper and sinister than that or else spam would have been
fixed up way back in the early 90's. Ive contacted ICANN on the matters
before, they don't care as long as they get their 50 cents per domain
and spam filter companies get their licensing profits, just like
anti-virus apps.
Ive tried again and again to tackle these things at the core, but my
suggestions are usually ignored. In my investigations, these people are
able to bulk register their domains and dns domains under false yahoo
email addresses, this means their details are able to be falsified when
registering. They will usually use a server where they encourage these
activites like china and russia.
now firstly if ICANN actually did what they are being paid to do, they
would enforce spam reporting systems on all registrars. Alot don't have
any, or you have to be a customer to contact support and takes you hours
to contact them. Alot like ICANN bump you off to the hosting people so
its a back and forth game, many won't take you seriouslly to pull the
domain down and as before tell you to contact the hosts instead. On the
host front they won't listen to you either especially in places like
Poland for instance, when I tracked down a Trac comment spammer, so they
are harbouring spammers.
Now if it was quite a bit of red tape to register domains to begin with,
with above said policies, it would be impossible for these people to
have websites to begin with or have them up for too long to bother to
spam. When they spam its always about selling their product and a link
to their site. So no site no reason to be spamming. The more issue with
the problem is that I only started getting spam when I started
subscribing to publically archivable mailing lists so search engines are
to blame too :)
Therefore filtering, is just ignoring the problem instead of tackleing
it head on, its quite a serious matter especially with phishing emails
for those who are not technically savvy. The other problem with Surbl,
even though your private email domain A record if used is different to
your MX record, and you are on a shared host. If that A record ip is
blocked in surbl, most filters will not care that your MX is different
to the A record so it will be blocked, as I experienced on the PHP list
servers so its quite crippling.
Its a pain in the side in terms of how the internet goes, they really
need to re spec how email and email servers work aswell I guess.
Internet V2 17 years too late or something like that :)
