-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I have always heard good things about them. I just wish I could get DSL in my neighborhood so I could hook up with them. I'm a Cognigen rep and we sell Speakeasy and I would love to use them but... I'm too far from my local central office so my line fails all DSL related loop tests! So for the time being, it's Cox Cable with their port blocking <sigh>. On Thu, Feb 17, 2005 at 11:56:21AM -0500, Janina Sajka wrote: > Others may disagree, but I cannot countenance any ISP blocking ports on > my account. I would regard this as a kind of denail of service and take > my money to an isp that didn't engage in such parental practices. > > So, I will sing the praises of my isp, Speakeasy: > http://www.speakeasy.net. No blocking, outbound or in. National service, > dialup and DSL. Never a problem, in the years I've been a customer. > > As a matter of fact, I usually forget I even have an isp, until I see > the charges in my monthly statement. That's my yardstick for judging an > isp. > > Speakeasy doesn't care if you run a server--in fact they encourage you > to do it. Want to resell your broadband to your neighbors over wireless? > They encourage that too. > > So, with posts such as we've had the last few days, I have to ask: Is > your isp cheating you? > > Steve Holmes writes: > > -----BEGIN PGP SIGNED MESSAGE----- > > Hash: SHA1 > > > > Speaking of port blockage, I know of at least three ISP's in my area > > that do this; more specifically, they intercept all traffic on port 25 > > and if it isn't destined to their own mail server, it gets bounced > > back as undeliverable. They even include a specific message telling > > you that it must be sent through their MTA. Cox high speed internet, > > the only high speed internet provider in my immediate area does this. > > I have several linux and windows machines at my house on a LAN, they > > all route mail to my internal mail host which runx Exim and I have > > Exim configured to smart host all outgoing mail to Cox and it all > > works well so far. Cox blocks even more inbound ports - namely FTP, > > HTTP, Telnet and 25 SMTP. They don't seem to block ssh port 22 though:). > > - -- > > HolmesGrown Solutions > > The best solutions for the best price! > > http://ld.net/?holmesgrown > > -----BEGIN PGP SIGNATURE----- > > Version: GnuPG v1.2.4 (GNU/Linux) > > > > iD8DBQFCE8l+WSjv55S0LfERAtQLAKCaNy62264Ai3XrzWZokO+ALhTokACg2G0C > > IYU/5XRcAAQGM8ILdnz7a/Q= > > =RgTp > > -----END PGP SIGNATURE----- > > > > _______________________________________________ > > Speakup mailing list > > Speakup at braille.uwo.ca > > http://speech.braille.uwo.ca/mailman/listinfo/speakup > > -- > > Janina Sajka Phone: +1.202.494.7040 > Partner, Capital Accessibility LLC http://www.CapitalAccessibility.Com > > Chair, Accessibility Workgroup Free Standards Group (FSG) > janina at freestandards.org http://a11y.org > > If Linux can't solve your computing problem, you need a different problem. > > > _______________________________________________ > Speakup mailing list > Speakup at braille.uwo.ca > http://speech.braille.uwo.ca/mailman/listinfo/speakup > > - -- HolmesGrown Solutions The best solutions for the best price! http://ld.net/?holmesgrown -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFCFRAXWSjv55S0LfERAu7wAKDFcerH83d9IhqzztrPGrb5rEi6IgCePr0r xHPBO6fc8arMYdUpnYV9CcE= =AXDs -----END PGP SIGNATURE-----
