SCOUG-HELP Mailing List Archives

>> Next Message >>

Date:	Tue, 11 Mar 2003 05:41:40 PST8
From:	Harry Chris Motin <hmotin@attglobal.net >
Reply-To:	scoug-help@scoug.com
To:	scoug-help@scoug.com
Subject:	SCOUG-Help: LAN, TCPIP and Router Setup

Content Type: text/plain

=====================================================
If you are responding to someone asking for help who
may not be a member of this list, be sure to use the
REPLY TO ALL feature of your email program.
=====================================================

Peter Skye wrote:
> I wrote a Rexx program similar to Junk Spy for Rocky a couple of years
> ago. It was intended to handle ...,

I would like to talk to you some more about this. The more I know about
TCPIP the better.
HCM

__________________________________________________________________________________

Peter Skye wrote:
>
> =====================================================
> If you are responding to someone asking for help who
> may not be a member of this list, be sure to use the
> REPLY TO ALL feature of your email program.
> =====================================================
>
> Harry Chris Motin wrote:
> >
> > The order of the 2 does not appear to make much difference
> > on my machine. Right now I have them switched to:
> > dhcpstrt -i lan0
> > ...
> > ifconfig lo 127.0.0.1
> > my router still does not register this computer
> >
> > The trick in getting the DSL and JunkSpy both to work was
> > not the order of "dhcpstrt" and "ifconfig". Instead, it
> > was the use of DHCP, instead of a fixed IP device (so that
> > router could issue and the computer could accept a dynamic
> > address) and the removal of all routes in the TCPIP config
> > notebook (so JunkSpy would work with DHCP activated).
>
> Glad you have it working, Harry.
>
> Junk Spy is sort of an "intermediate server". Your email program talks
> to it instead of directly to the email (POP3) server, and Junk Spy takes
> the request that it receives from your email program and then contacts
> the email server and gets the messages. Since Junk Spy is on the same
> machine as your email program, the default setup is to use 127.0.0.1
> (the "loopback address") as the IP address for Junk Spy. Thus, your
> email program asks 127.0.0.1 for email messages, and Junk Spy is using
> 127.0.0.1 so it gets that request; Junk Spy then asks your "real" email
> server for the messages, checks them to see if they are spam/junk, and
> sends them back to your email program over the 127.0.0.1 link. If
> IFCONFIG hasn't set up the local loopback (or if DHCPSTRT has trashed
> it), there isn't any 127.0.0.1 connection available so your email
> program can't communicate with Junk Spy.
>
> I wrote a Rexx program similar to Junk Spy for Rocky a couple of years
> ago. It was intended to handle logins between his older email program
> and his ISP's email server which used an authentication that the older
> email program didn't know. The program worked as far as connecting, but
> I never got around to getting an account with Rocky's ISP (Orange County
> Online) and testing the authentication. It worked fine with my own ISP
> (which just needs USER and PASS). I was somewhat surprised that I could
> write TCP/IP stuff in Rexx.
>
> - Peter
>
> =====================================================
>
> To unsubscribe from this list, send an email message
> to "steward@scoug.com". In the body of the message,
> put the command "unsubscribe scoug-help".
>
> For problems, contact the list owner at
> "rollin@scoug.com".
>
> =====================================================

=====================================================

To unsubscribe from this list, send an email message
to "steward@scoug.com". In the body of the message,
put the command "unsubscribe scoug-help".

For problems, contact the list owner at
"rollin@scoug.com".

=====================================================

Return to [ 11 | March | 2003 ]

SCOUG, Warp Expo West, and Warpfest are trademarks of the Southern California OS/2 User Group. OS/2, Workplace Shell, and IBM are registered trademarks of International Business Machines Corporation. All other trademarks remain the property of their respective owners.