« CCA client doesn't work with slipstreamed Windows | Another CCA client workaround program » |
I now have proof (as if that was really necessary, people in the know have known that for a long time...) that CCA doesn't do its job in preventing hijacked computers on the network.
The situation: I tried sending an email from this computer within UCI's on-campus residential housing network to one of my off-campus email accounts. The registrar that provides the email service for that off-campus account is very good with respect to spam prevention (one of the reasons I use them.)
The email got rejected by their email server, with this line:
Remote host said: 553 Dynamic pool 128.195.105.207. <http://unblock.secureserver.net/?ip=128.195.105.*>
The only conclusion is that at IP address 128.195.105.207, there is or was a zombied machine sending out spam that resulted in the whole subnet being entered into the registrar's blacklist (which, btw, is standard operating procedure in the spam-fighter community, with escalation if the netblock owner doesn't stop the spam.)
One of the oh-so-highly touted "features" of CCA is that such hijacked machines would automatically be put into quarantine. From the listing above, it is obvious that that didn't happen.
Conclusion: Yet more proof that CCA is faulty and needs to be abolished.
Update: While the block was gone shortly after I put this post up, it is back again, with the same IP address. Indeed, CCA isn't worth a buck, much less it's $50K+ price tag, if it can't prevent such issues. It really needs to be scrapped.