Index: [Article Count Order] [Thread]

Date:  Tue, 10 Mar 2009 11:57:27 -0400
From:  "Darrell D. Mobley" <dmobley (at mark) uhostme.com>
Subject:  [coba-e:15271] Re: Enable additional SMTP port
To:  <coba-e (at mark) bluequartz.org>
Message-Id:  <CB5FED80826841A084083A247622DDED@HP9925NR>
In-Reply-To:  <1d4c951a0903100816y38b0ac31gc08e1d55164ec34a (at mark) mail.gmail.com>
References:  <1d4c951a0903041137s30d532b2sf298df6d57b52a8a (at mark) mail.gmail.com> <A270D97D576B42CDB28F4B71B43B9F14 (at mark) MALAPTOP> <1d4c951a0903042306h56105b71h937c7cc024d975f0 (at mark) mail.gmail.com> <1d4c951a0903100816y38b0ac31gc08e1d55164ec34a (at mark) mail.gmail.com>
X-Mail-Count: 15271

I take it all you had to do was enable it and set the mail client to port
465?

 

  _____  

From: Jeff Keller [mailto:jeff (at mark) datatune.com] 
Sent: Tuesday, March 10, 2009 11:17 AM
To: coba-e (at mark) bluequartz.org
Subject: [coba-e:15268] Re: Enable additional SMTP port

 

Just a belated update to let you know that enabling SMTPS solved the
issue--no hacks required.  Thank you Rickard.

JK

On Thu, Mar 5, 2009 at 12:06 AM, Jeff Keller <jeff (at mark) datatune.com> wrote:

Thank you Michael.  Thank you Rickard.  I'll try each solution and I suspect
that one of them will satisfy my needs.  Hope this helps others as well!

JK

 

On Wed, Mar 4, 2009 at 1:47 PM, Michael Aronoff <ma (at mark) ciic.com> wrote:

I use a linux program called portfwd to take all traffic from any specified
port and route it to another local port.  Below if a how-to I wrote a long
time ago but it should still be the same. I chose this method because it was
the easiest way to do what I needed, without touching Sendmail one bit and
it also allows very simple changes if you need to change the port you use.

Original How-to below.

If you host sites for clients than you have probably run into Port 25
blocking. Most ISP's block all port 25 traffic on their networks except for
to their own SMTP servers. They do this to reduce spam zombies and the like
which I applaud. However it also blocks users with legitimate outside mail
services. Portfwd was a tool I found out about from the old Cobalt Users
List almost 9 years ago, and it solves this problem easily and elegantly
while not compromising security in any way. Once the program is installed
you can tell blocked clients to simply change the SMTP port in their mail
program to the one you specify and they will be good to go.

As usual your mileage may vary so please test yourself. I will not be held
responsible if you mess something up. That being said this is a long but
simple install.

Quote:
cd /home/installations
mkdir portfwd
cd portfwd
wget
http://easynews.dl.sourceforge.net/sourceforge/portfwd/portfwd-0.29.tar.gz
tar zxfv portfwd-0.29.tar.gz
cd portfwd-0.29
./configure
make
make install


Install is now complete. Time to configure your ports.
I forward all trafiic from port 999 to port 25 so that clients whose
ISP does port 25 blocking can set their mail program to use port 999
and use their own SMTP server. For a setup like that we need to make a
portfwd.cfg file.
I use nano for my text editor but simply change that to your text editor as
needed in the instructions that follow.

Quote:
cd /usr/local/sbin
nano -w portfwd.cfg


paste the following in the portfwd.cfg file
(make sure to change the IP to your servers)

(Just compy the line below, nothing else, then save the file):
tcp { 999 { => your.ip.goes.here:25 } }


Now we need to make an init.d script to stop, start, etc.

Quote:
cd /etc/rc.d/init.d/
nano -w portfwd


paste the following exactly as is between the <start copy> and <stop copy>
marks.
Quote:
<start copy>
#!/bin/sh
#
# portfwd Shell script to start and stop portfwd utility
#
# Location: /etc/rc.d/init.d/
#
# Version: 1.1 (02/16/05)
#
# Author: mikey <mikey (at mark) biosearchtech.com>
# for Biosearch Technologies, Inc.
#

# Source function library.
. /etc/rc.d/init.d/functions

# if no config filename is given, then use portfwd.cfg
if [ "$2" = "" ]
then
configfile="portfwd.cfg"
else
configfile=$2
fi

# See how we were called.
case "$1" in
start)
# if config file exists, then start portfwd, else give error message
if [ -f /usr/local/sbin/$configfile ]
then
echo "Starting portfwd utility..."
/usr/local/sbin/portfwd -c /usr/local/sbin/$configfile
touch /var/lock/subsys/portfwd
echo "Done."
else
echo "Config file \"$configfile\" is missing, cannot start portfwd."
exit 1
fi
;;
stop)
echo "Shutting down portfwd utility..."
killproc portfwd
rm -f /var/lock/subsys/portfwd
echo "Done."
;;
status)
status portfwd
;;
restart)
echo "Restarting portfwd utility..."
$0 stop
$0 start $2
echo "Done."
;;
*)
echo "Usage: portfwd {start|stop|restart|status} {configfile.cfg}"
exit 1

esac

exit 0
<stop copy>


save and exit that file, then make it executable

Quote:
chmod 755 portfwd


now to make it start on boot

Quote:
nano -w /etc/rc.d/rc.local


go to the bottom of the file and paste the following

Quote:
/etc/rc.d/init.d/portfwd start portfwd.cfg


save and exit. You are done. You can now reboot to test or you can manually
run it as follows.

Quote:
/etc/rc.d/init.d/portfwd start portfwd.cfg


you can check status with

Quote:
/etc/rc.d/init.d/portfwd status


Ok, I hope that was clear and easy enough. Let me know if you have any
questions. I was careful in the init.d script to use all spaces and not tabs
so I hope it copies and pastes easily for you. Good Luck.

For more info check out the portfwd sorceforge page at
http://portfwd.sourceforge.net/

M Aronoff Out
Calabasas, CA







 

 


	

15271_2.html (attatchment)(tag is disabled)