I'm only skimming the thread, so may not have seen the important parts,
but...
If he is on a Shaw residential service, then he is NOT paying for the
right to host servers. Which the scripts in question kinda are. An
argument could be made that he is paying for the right of using standard
IP protocols and ports though. But Shaw has the right to fight spam by
not allowing non-business accounts from sending bulk emails.
Working around this is trivial - just configure the mail client to send
on another port, or through a mail relay.
What I haven't seen is any discussion of the configuration of the
current/previous system which would give us a hint what configurations
need to be changed or how. The initial question seems to be asking for
a way to port forward all outgoing packets on port 25 to some other
address or port. This is what firewalls/routers are for. I think that
approach is error prone though - what happens when you *really* want to
connect to a server on port 25?
My thoughts.
Shawn
On 11-03-27 02:33 PM, t...@terralogic.net wrote:
A better idea is for him to tell Shaw to take a hike. This is real dirty on
Shaw's part. He paid for the service.
On Sun, Mar 27, 2011 at 12:00:55PM -0600, Royce Souther wrote:
I have a client that runs his business from home, he runs a number crunching
program that takes a few days to produce results. I wrote a bunch of wrapper
scrits to automatically send him email notifications as it competes jobs but
Shaw has now turned off his direct port 25 access. Now all the scripts have
to be changed so that the mail command will use the alternet SMTP server for
Shaw.
Is there any way to change some configuration file in /etc that will make
the mail command always use the Shaw SMTP so that I do not have to change
dozens of scripts?
I am looking for a global solution.
--
Easy, fast GUI development.
http://PerlQt.wikidot.com
_______________________________________________
clug-talk mailing list
clug-talk@clug.ca
http://clug.ca/mailman/listinfo/clug-talk_clug.ca
Mailing List Guidelines (http://clug.ca/ml_guidelines.php)
**Please remove these lines when replying
_______________________________________________
clug-talk mailing list
clug-talk@clug.ca
http://clug.ca/mailman/listinfo/clug-talk_clug.ca
Mailing List Guidelines (http://clug.ca/ml_guidelines.php)
**Please remove these lines when replying
_______________________________________________
clug-talk mailing list
clug-talk@clug.ca
http://clug.ca/mailman/listinfo/clug-talk_clug.ca
Mailing List Guidelines (http://clug.ca/ml_guidelines.php)
**Please remove these lines when replying
