On Friday 20 May 2005 10:19, Nick W wrote: > > I attempted to email you through my MX which is on a Shaw business package. > I got: > > �The Postfix program > > <[EMAIL PROTECTED]>: host mail.zoneedit.com[209.152.174.160] said: 554 > � � Service unavailable; Client host [68.147.28.194] blocked using > � � l1.spews.dnsbl.sorbs.net; ! [1] shawcable, see > � � http://spews.org/ask.cgi?S3163 (in reply to RCPT TO command) > > If you go to the URL you find out they've blocked every Shaw IP, even the > static ones. Worse, there's no way to request to be un-blocked, even though > I have SASL running on my MX, so it's unlikely it's being used for SPAM. > [Plus it would show up in the logs and the LAN activity would tip me off, > the box isn't all that busy.] > > So, Shaw is dumb for not blocking port 25, and SPEWS has a system that > screws me over, telling me to either switch ISPs or get Shaw to block port > 25. That's equally stupid. Alternatively, I could remove all the spam bots > from every idiots windows box in western canada.... > > Nick
Interesting - a royal pain for sure. I wonder how many complaints Shaw gets about this? I see that according to http://spews.org/html/S3163.html they say: <quote> Spam ignorant. Poster child of how not to run a broadband network company when it comes to dealing with abuse. </quote> Certainly Shaw could block 25 as does Telus. I suppose I could update my zoneedit entry and set up a SASL MX server instead of forwarding through zoneedit, but, alas, the clock ticks forward with other projects... :-) _______________________________________________ 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
