On Friday 28 April 2006 06:58, Reza - Asterisk Enthusiast wrote: > This is a painful change, but necessary as per their claim - to prevent
No it's not. There are all kinds of ways to ensure it without a flat-out block. Remember that SPAM only works on volume. Simple rate-limiting will let you stop the SPAM dead without pissing off the small business owner who doesn't want to use Bell's shitty-ass SMTP servers which are a) slow, b) down half the time and c) intermittently successful at sending mail. However rate-limiting costs CPU on the routers, which is something they want to stay away from, so a simple outgoing port 25 block is effective. I recommend powerdsl (full disclosure, I work with someone who resells it and is working on their own L2TP server so they don't have to resell) -- no port 25 block and it's the exact same hardware and network (well, up to the ATM level, then you go off on powerdsl's connection instead of Bell's). And the price is about the same. > I think jumping to another provider is really not necessary. Your Linux > box has amazing capabilities to do what you need to do. Yes, and pissing about trying to work around the idiocy and laziness of a big-name provider isn't something I should have to waste my time and energy on. > server) to act as a smart host, routing ALL my * related email, to my > Sympatico e-mail account, through SMTP authentication (of course). All > e-mail going out, passes through Symaptico mail servers. You cannot > simply relay mail to Sympatico M.S. As long as you get your Linux mail > server, behaving like an e-mail client, connecting to Sym. M.S., your > e-mail will go out. Yes, and then you have all the intermittencies of Bell's SMTP network. They have to put up with all the virused and zombie'd hosts trying to send millions of SPAM messages through their network, and their SMTP system shows it's war-weary. What I do on my laptop is much simpler (at least for me) -- since I have no idea where I'll be hooking up to the 'net from, I configure an ssh port-forward to my colocated server. Then I just make sure this is running: ssh -L 2500:localhost:25 mixdown.ca Since I have an IRC session running there at all times anyway I'm usually on it :-) Any mail I send goes to localhost:2500 and out my SMTP server in the colo facility. No bullshit hoop-jumping or other games. It's fast, I have full control over the mail path and I don't have to worry about any port blocks. I got really sick of other people's mail servers many years ago, which is why I finally just put a box in a colo (it's a virtual box with Xen, actually) and use my own services. Wow... I really am turning into a crotchety old man! :-) -A.
