"TC" == Trevor Cordes trevor@tecnopolis.ca writes:
TC> On 17 Nov, Tim Lavoie wrote: >> Second defense: Outbound SMTP has to go through their server, >> not direct from random, unpatched Windows boxes which are >> always on-line.
TC> And not direct from random fully secured linux firewall boxes TC> I manage which are not infected, never have been, and probably TC> never will.
True enough. For outbound SMTP, they provide an option in the mail host that is available. If performance or availability are suffering, that is indeed something they need to fix. Otherwise, it shouldn't be a problem. That's not to say that there are no problems, just that any which do occur should be fixed.
TC> They could make a case for blocking OUTBOUND SMTP, but why on TC> earth do they need to block INBOUND SMTP!!! That has nothing TC> to do with spam. That is a simple cash grab and TC> screw-the-little-guy ploy to make someone running a tiny super TC> low-volume micro-business server pay the exhorbitant static-IP TC> address fees that, strangely, don't have SMTP blocked at all. TC> Does that mean that people who have the dough to buy static TC> IP's are any better at admin'ing their systems and not TC> becoming bot zombies?
I suspect that those who are serious enough to get the static IP should be up to the task. Yes, the market catered to is different, and I would think that expectations of the customer are different as well.
The choice to make IPs dynamic is a business one, not technical. The choice is yours to make as a customer whether that works for you. If not, go elsewhere. Unless you need hands on a physical box, there are tons of hosting setups which are reliable, inexpensive and are aimed at people hosting network applications. Terms of service will vary, but you can read that up front. For virtual servers, it's probably even easier for you to migrate to another provider if you aren't satisfied, since you aren't relying on a cable to a physical address.
TC> The more important point is: today they block outbound SMTP. TC> Then they block inbound SMTP. Tomorrow they block, what? TC> HTTP? SSH? P2P? FTP? VNC? I don't know about you, but I TC> don't want my ISP controlling what traffic I can send. Sure, TC> penalize or drop me if I go over the prescribed GB/month TC> limits, but don't censor me.
Oh, I'm not a censorship fan, and I do appreciate having everything as open as possible. Balance is vital, as always. Services are why customers come to your door. Security is also important, and cost is always a factor. I don't want to be restricted, but I sure wish that some fellow customers would get disconnected for being idiots. :)
Tim