Richard Ozer wrote:
Philip,
Methinks that's a very silly policy. You're aren't hurting Comcast an
iota; but you sure are penalizing yourself, your users, and their
email contacts. A properly configured SA box will block spam from
Comcast subscribers as well as from anyone else so I don't see what
you are trying to accomplish.
I am my users, for the most part.
I run a small start-up company and run the mail server here.
I have no regular correspondents that are Comcast subscribers, outside
of the occasional respondent from a mailing list such as Matt.
As for properly configured SA... Well, maybe I'm lacking technical
competence and going for the low-hanging fruit, then.
Spam does occasionally get in, and I will report it to the provider if I
believe for an instant that they will investigate it in good faith.
Yes, I block Comcast. I also block ALL of these Japanese, Thai,
Chinese (Chicom only), Korean, Singaporean, New Zealander,
Romanian, Italian, Polish, ... (get the idea) network addresses that I
was able to deduce through CIDR block inferences.
I.e. any provider or country that doesn't have an institutional policy
of prosecuting spam senders...
BTW: A finer point is that I block Comcast USER IP addresses. If
Comcast has mail servers that have a separate address block (and most
ISP's do) and users send their outgoing email through their provider's
relay, then I will happily accept those messages. I will not accept email
coming from the subscriber IP address blocks, however.
IMHO, blocking entire ISP domains makes you part of the problem and
not part of the solution...
I'm not generating spam, so I fail to see the equivalence. Nor am I
providing a relay
or other "safe haven" for spammers.
It's a nice platitude, but doesn't bear up to scrutiny.
It smacks of a sort of "us" and "them" mentality. In addition to "us"
and "them",
there's also "everyone else".
Then again.. you might be the only user on your system; in which case
... who cares!
Exactly. You've come around to my point of view.
-Philip
RO
