I think your example should work.. it's incoming non-stateful connections that should be blocked, so outgoing port 25 to anywhere should work out well. But, who knows.
But, in the end, I'm on Shaw, and not Telus, because I've had more luck on their network, and a few architectural decisions on the network give me better bandwidth..
But, I agree with the bottom line you had there, if you want to host something, get a connection with a good Service Level Agreement, or a good co-locate server.
BTW, that might have been me on the phone that told you that, I think I've used that line a few times..
On Aug 27, 2004, at 11:15 AM, Shawn Grover wrote:
So if they turn off ALL ports, and hey, why not even connection to the Internet, wouldn't they save even MORE bandwidth? The more bandwidth you can save, the more money you can save.....
Sorry Pual, I don't mean to be a jerk here, but if they are going to offer the bandwidth, then they need to allow reasonable use of it. I agree that hosting a server with a Telus home account is outside the acceptable use policies, but to blindly turn off port 25? So, let's say I configure my laptop to send and receive mail from my corporate mail server, and travel a lot. The way they have handled this is that I cannot forward my mail to my SMTP server without going through their SMTP server. Oh, btw, that only works if you're on the Telus network - if you're in a hotel room halfway around the world, the SMTP traffic would be rejected because they don't relay mail. They need to take another look at how and why the servers are setup the way they are - someone forgot to turn on SMTP authentication, which would have allieviated a HUGE amount of the problems they are seeing. They also could have offered an alterative plan for those who know what they are doing, without having to switch to a business level connection.
On the other hand, I was on a Telus network up to the end of June. We changed to Shaw only because we moved into a new house and haven't bothered having a land line brought in. Up to the move, my email server was working perfectly fine receiving and sending mail, and allowing remote connections. I believe the port blocking started in November - so did they just miss my neighborhood? Was my traffic low volume enough that they weren't concerned? How is it that I didn't see any problems, yet so many others did? (just curious)
The bottom line is that if you are looking to run a server, YOU have to check that your ISP will allow it. If it is only written policy that you "shouldn't" run a server on their networks, but you decide to anyways (I did), then you have a responsibility to monitor your bandwidth and prevent abuse (IMHO).
My thoughts...
Shawn
(ps. I once had a telus tech tell me that he didn't want to hear if I was running a web server, but mentioned that there would be no bandwidth cap or shut down of SSH traffic. Is there anyway to set up public SMTP over SSH? <grins>)
-----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Paul Greidanus Sent: Friday, August 27, 2004 10:54 AM To: CLUG General Subject: Re: [clug-talk] Don't use Telus they block your ports
They're weighing the good of the many vs the needs of the few. A little misguided in their approach, but if they can save, 5% on bandwidth by turning off those ports, that turns into a huge savings in bandwidth as well..
_______________________________________________ clug-talk mailing list [EMAIL PROTECTED] http://clug.ca/mailman/listinfo/clug-talk_clug.ca
_______________________________________________ clug-talk mailing list [EMAIL PROTECTED] http://clug.ca/mailman/listinfo/clug-talk_clug.ca
_______________________________________________ clug-talk mailing list [EMAIL PROTECTED] http://clug.ca/mailman/listinfo/clug-talk_clug.ca
