-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Guy Davis wrote: > Maybe I don't understand your post but this seems reasonable to me > now that most receiving mail servers on the Internet will flag mail > coming directly from IPs in the dynamic Shaw IP address block as > spam. > > From about 2000 through 2004 or so, my outgoing email travelled like > this: > > Workstation -> Linux Server under desk -> Receiving SMTP server. > > Around 2004, I noticed that many "receiving" SMTP servers were > flagging my mail as spam since my Linux server was in the Shaw > dynamic IP range. So I added the following line to my > /etc/mail/sendmail.mc file: > > define(`SMART_HOST',`shawmail.cg.shawcable.net') > > Now my outgoing mail travels like so: > > Workstation -> Linux server -> shawmail.cg.shawcable.net -> Receiving > SMTP server. > > All my mail is getting through now as the receiving SMTP server seems > to recognize the shawmail server as an authorized SMTP host for that > IP block. The mail takes a couple more minutes to arrive as Shaw's > server isn't too quick, but at least the Spam blocks at the receiving > end aren't eating my messages. > > On the other hand, maybe I misread your message and Shaw is planning > to firewall off incoming connections to port 25 on its client's > systems? That would be unfortunate... > > Guy > > Gustin Johnson wrote: >> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 >> >> Shaw will be redirecting all outbound connections on port 25 to >> their own mail servers. For the moment there is a small test zone >> downtown (that happens to include 2 of my clients and my apartment) >> that has had this change implemented. >> >> I think this is a bad idea (and so do my clients who were unable to >> send email ). If you also think that this is a bad idea you should >> probably let them know. >> >> The support staff were unaware of this change, so you may wish to >> have them look at Ticket# 11799439. >> >> I may be eating my words in the near future and ordering up a Telus >> DSL connection. > 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).
Also some of my larger clients (100+ employees) have their own mail servers onsite. For employee to employee communication this is more secure than using shaw (or anyone else) for outgoing mail. It was a client who initially reported this to me. Also, my laptop connects to a variety of ISPs in the course of a single day, so having to change my mail client is a bit of a PITA. Of course, this discussion would be far different if the ISPs blocked the default ssh port, how many here would support that? -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.2 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFEpDoVwRXgH3rKGfMRAgNaAJwK0e85MJywe1hPwiFNYOH++rLo5wCcDS3P qHtITHBJOfv8FzxZpQduOAw= =jhjH -----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
