Re: Fwd: email problems with charter

[Eric Lathrop <eslathro@xxxxxxx>]

Very useful. I was gonna look into how to do that until I found out 2525
was open.

> Eric,
> 
> Oh and another thing to check out.
> 
> SSH tunnels!  :)
> 
> Example: here is the exec command in my script:
> ssh -L 25:email.mtu.edu:25 pbschou@xxxxxxxxxxxxxx -N
> 
> Note: to bind to port 25 will require this command to be executed as
> root and in nsa patched kernel you have the perms setup to allow it to
> bind.
> 
> (hint: use perl's stdin to send your password, then you can init.d it,
> but make sure if you are not the only on on your system you have chmod
> 600 to keep your password safe)
> 
> you can do the same from any command prompt and then type you password
> when it requsts for it from your university login server.
> 
> - Paul Schou
> 
> 
> On Sun, 2 Nov 2003, Eric Lathrop wrote:
> 
> >
> > > * Raphael Mudge (rsmudge@xxxxxxx) wrote:
> > > > In case anyone is experiencing the same problems I was.
> > >
> > > I just have my smtp server(postfix) relay the mail to
> > > "mail.chartermi.net". Works just fine for me. Thats how this email
> > > was sent.
> >
> > Yeah, but I don't want to send my mail through charters server becase
> > they blocked all outgoing mail not through their server. I dont
> > remember any part of my user-agreement that said they can block
> > whatever ports they want. I trust MTU's server over charter's any day.