-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Curtis Sloan wrote: > On Thursday 29 June 2006 14:37, Gustin Johnson wrote: > >> The problem is that when I send email, I do so directly from my mail >> server. I use SMTP Auth secured with TLS. I do this because I make use >> of SPI for a number of the domains I host. I also avoid issues with my >> ISP's mail system (Shaw has a long history of unexplained mail delays). >> > <snip> >> Of course, this discussion would be far different if the ISPs blocked >> the default ssh port, how many here would support that? > > They're not blocking outbound SMTP, they're proxying it. Yes, it would be > disturbing if they did the same thing with SSH. I would rather not have SMTP > or SSH handled in this way. However, I believe Shaw's ToS explicitly says > they do not allow these types of servers. It's more Shaw turning a "blind > eye" that allowed it to date. If you don't like it... >
Actually the servers themselves are run on commercial pipes whose ToS is written for servers. What Shaw has done is prevent an end user from using a mail server other than their own. - From the end user point of view, Shaw has blocked outgoing because security is a concern for a number of my clients (the lawyers in particular) I have the TLS only option checked, which Shaw does not support. Thus the proxied connection fails. Because I don't like it, you may have noticed the other thread I started today :) > Which brings us to the point that Shawn brought up. How about making an ISP > that would allow this by letter of the law? I can foresee some legal > difficulties with that, but I have to admit the idea is still enticing. > It is an idea I have had for years as well, since I used to work at an ISP many moons ago. There was a similar ISP in the US, they didn't offer NNTP, nor end-user support (basically if the connection was working the rest was not their problem). It was geared towards technical people who could take care of themselves. I am not sure how well they faired, but the idea seemed a good one. > My 2 cents, > Curtis S. > -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.2 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFEpESlwRXgH3rKGfMRAgFiAJoC3gtIsZnCqPaqVRkUJQheb/Eq5wCgiNaY kF5EmYmM5WiDqsEPWMGITZM= =FNMH -----END PGP SIGNATURE----- _______________________________________________ clug-talk mailing list [email protected] http://clug.ca/mailman/listinfo/clug-talk_clug.ca Mailing List Guidelines (http://clug.ca/ml_guidelines.php) **Please remove these lines when replying
