[TriLUG] Re: Need a Stupid Sendmail trick

[Jon Carnes]

I like the ssh tunnel method mentioned earlier, but for years I've setup
a simple port relay out of xinetd that simply moves one of the higher
connection ports to port 25 locally.  Then you simply set your email
client to attach to the higher port.

service 4225
{
        socket_type             = stream
        wait                    = no
        user                    = root
        log_on_success  += HOST DURATION
        log_on_failure  += HOST
        redirect = localhost 25
        disable                 = no
}


This has the added advantage of making the connection seem as though it
is via localhost - so it bypasses a lot of local relaying rules.
Caution, be sure to monitor the use of this port to make sure you don't
become a known open relay.

Good Luck - Jon Carnes

On Wed, 2004-05-26 at 18:24, Dave Sorenson wrote:
> Thanks I'll take a look and give you a holler if I hit a wall.
> 
> Dave 
> 
> -----Original Message-----
> From: trilug-bounces at trilug.org [mailto:trilug-bounces at trilug.org] On Behalf
> Of Lance A. Brown
> Sent: Wednesday, May 26, 2004 5:01 PM
> To: Triangle Linux Users Group discussion list
> Subject: [TriLUG] Re: Need a Stupid Sendmail trick
> 
> If you are using a recent version of sendmail, this should be easy. 
> Port 587 is designated as a submission port for email clients unable to
> access port 25 for whatever reason.  On recent Red Hat systems you just need
> to uncomment the correct line in /etc/mail/sendmail.mc and remake the
> sendmail.cf file.  I've been using this feature to support email submission
> using STARTTLS on my server at home for quite a while.
> 
> Lemme know if you need more pointers/assistance.
> 
> --[Lance]
> 
> 
> Dave Sorenson wrote:
> > OK, need help from the Sendmail gods.. I need to reconfigure sendmail 
> > to listen for incoming request on a port other than 25. I know this 
> > will break a number of things, but it may also help me end-run 
> > Bellsouth's asinine block of outgoing (I can understand this somewhat) 
> > AND incoming (completely whacked IMHO) 25 traffic garbage.
> > 
> > What I need to do is to use my mail server for outgoing SMTP traffic. 
> > I can configure my client to send on alternate ports so that is not an 
> > issue. Mail will leave my laptop, travel to my mail server (on an 
> > unblocked port) sender
> > (me) will get verified and then out through Bellsouth's SMTP via the 
> > smarthost relay (that's the only thing they did not break when I
> "Upgraded"
> > my DSL). That way I don't need to keep changing my mail client 
> > settings depending on what network I happened to be on...
> > 
> > I know this breaks incoming to my server, thats not an issue. I'm 
> > using a pop account on a server outside of the Bellsouth network for
> incoming mail.
> > My biggest problem for the moment is to not have to mess with the 
> > client settings every time I change locations and networks.
> > 
> > Please don't tell me to change providers, I'm going to when I move in 
> > with the fiancé at the end of my lease.. I just need to end-run BS 
> > stupidity for a few months.
> > 
> > TIA
> > 
> > Dave S
> > 
> 
> --
>   Celebrate The Circle: http://www.celebratethecircle.org/
>   Carolina Spirit Quest:  http://www.carolinaspiritquest.org/
>   My LiveJournal: http://www.livejournal.com/users/labrown/
>   GPG Fingerprint: 409B A409 A38D 92BF 15D9 6EEE 9A82 F2AC 69AC 07B9
> -- 
> TriLUG mailing list        : http://www.trilug.org/mailman/listinfo/trilug
> TriLUG Organizational FAQ  : http://trilug.org/faq/ TriLUG Member Services
> FAQ : http://members.trilug.org/services_faq/
> TriLUG PGP Keyring         : http://trilug.org/~chrish/trilug.asc