From: Harry Tabak <[EMAIL PROTECTED]>
This is so crazy I had to respond.
Are you one of those people, that blames a car owner for not havingMy tiny x/29 block is sub-allocated from my DSL provider's x/23 block. The DSL provider's block is a sub-allocation from Inflow.com's 188.8.131.52/17 block. Spambouncer doesn't like Inflow. While they have a right to their opinions, they don't have a right to publicly tar me because of my neighbors.
an alarm system when his car gets stolen, instead of blaming the
It's simple. Inflow is blocked for a reason. You can whine all you
want, but spam filters never add default blocks unless an ISP has
spammed, and refused to anything about it. Therefore, Inflow had to
do at least 2 things:
2. Refuse to stop spamming after being contacted about it.
I, personally, fully support their decision. There really needs to
be some accountability on the Internet.
Here's what you _should_ do:
1. Contact Inflow and raise a stink about how their poor policies are
2. Find another provider.
3. Send a letter to the BBB complaining about Inflow's policies
Even if you don't agree with me, I'll say that you're unlikely to have
the FreeBSD people do anything? Have you emailed all the Linux distros
as well and told them that there's an RPM out there that they should
boycott? Are you now going to email every ISP on the planet and suggest
that they boycott all FreeNIXes because they can use this anti-spam
software? You're driving the wrong way on a "the other way" street, if
you really want to accomplish anything.
Put the pressure on the people who are doing wrong, not on the people
trying to stop it. You shouldn't even have to contact the anti-spam
developers, Inflow should contact them once they've improved their
policy and demand that they be removed!
MSN 8 helps eliminate e-mail viruses. Get 3 months FREE*. http://join.msn.com/?page=features/virus&xAPID=42&PS=47575&PI=7324&DI=7474&SU= http://www.hotmail.msn.com/cgi-bin/getmsg&HL=1216hotmailtaglines_virusprotection_3mf
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-questions" in the body of the message