I use openBSD on the firewall and on the servers.  I could just do a redirect.

Your point about pulling the plug on #25 is appropriate if the thing is spewing 
spam.  Usually they just let that through.  Botnets seem to thrive but a guy 
soing legit work?  They are trying to push him into a more expensive package 
and that is just dirty - at least this is what I suspect is going on here.

Something we should ask is why his compute farm isn't in his basement?


There are things which don't add up.







On Sun, Mar 27, 2011 at 02:18:20PM -0600, Gustin Johnson wrote:
> Spam is a real problem, especially from end user machines infected
> from malware.  This policy actually makes sense to me.  If you really
> need direct port 25 access you can get a business package that allows
> it.  IMO you are far better off outsourcing your mail server to
> someone who really knows what they are doing.  I have been hosting
> email for more than 10 years and there are so many companies doing a
> better job for so cheap  that I no longer provide email hosting
> solutions directly.
> 
> There are a couple of choices for the OP.  The first is to change his
> MTA to use a relay host.  How you do this really depends on the MTA
> you are using.  The specific terms to use in google are "smart host
> relay <insert MTA in use>" without the quotes.  Some distros like
> Debian and Ubuntu have semi automated ways of doing this, typically
> with a "dpkg-reconfigure exim" is one example.
> 
> Whatever host you are using as a relay probably supports ports 465
> (smtps) and 587 (submission), the later traditionally used with
> authentication.  Gmail for example supports both ports with
> authentication and TLS on port 587.  Most competent email providers
> will do the same.  If your scripts rely on the local system to send
> mail, all you need to do is configure the local system to use a relay
> (the smart host relay usually refers to SSL and authentication as
> well.  Slightly more tricky to setup depending on your MTA and
> distro).
> 
> Hth,
> 
> On Sun, Mar 27, 2011 at 2: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

_______________________________________________
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

Reply via email to