SCOUG Logo


Next Meeting: Sat, TBD
Meeting Directions


Be a Member
Join SCOUG

Navigation:


Help with Searching

20 Most Recent Documents
Search Archives
Index by date, title, author, category.


Features:

Mr. Know-It-All
Ink
Download!










SCOUG:

Home

Email Lists

SIGs (Internet, General Interest, Programming, Network, more..)

Online Chats

Business

Past Presentations

Credits

Submissions

Contact SCOUG

Copyright SCOUG



warp expowest
Pictures from Sept. 1999

The views expressed in articles on this site are those of their authors.

warptech
SCOUG was there!


Copyright 1998-2024, Southern California OS/2 User Group. ALL RIGHTS RESERVED.

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.

The Southern California OS/2 User Group
USA

SCOUG-Programming Mailing List Archives

Return to [ 02 | March | 2000 ]

<< Previous Message << >> Next Message >>


Date: Thu, 2 Mar 2000 13:42:36 PST
From: "Steven Levine" <steve53@earthlink.net >
Reply-To: scoug-programming@scoug.com
To: scoug-programming@scoug.com
Subject: SCOUG-Programming: TCP/IP socket programming ?

In <38BE04DD.39C0@peterskye.com>, on 03/01/00
at 10:06 PM, Peter Skye said:

>I want the email program (NS202) to connect to my monitoring module,
>which will watch all email traffic in both directions, and then the
>monitoring module will communicate with whatever the email software
>normally communicates with.

This sounds like you want to implement the same type of functionality
that's built into Junkspy, but with different procession logic.

Rollin is much better versed the details and the gotcha, but I can give
you the basics.

>I know how to open a socket and connect it to a server so I can send the
>server some commands and then "listen" for a response. What I don't know
>is how to open a socket so it will "listen" for a command from the email
>software. How do I do this? (What setting do I have to change in the
>email software to get it to send a command to the monitoring module? How
>does the monitoring module tell TCP/IP that it is indeed the module that
>the email software is looking for?)

You do it the other way about. You tell NS to talk to your module by
telling it to talk to your IP address (192.168.x.x). You then set your
module up to listen for requests addressed to the SMTP and POP3 ports at
this address. Since you are the only module at your address listening to
these ports your will get all the traffic. The store and forward details
are where it gets interesting and really depend on what you really mean by
monitor.

>the modules together in a certain sequence? I presume I have to give
>unique names to each module and have each module tell TCP/IP what the
>name of the other module is that it is to link to - how do I do this?

Nope. You will have to string them together by port addresses.

Steven

--
----------------------------------------------------------------
"Steven Levine" MR2/ICE 2.08 #10183 Warp4/FP11
----------------------------------------------------------------

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

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

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

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


<< Previous Message << >> Next Message >>

Return to [ 02 | March | 2000 ]



The Southern California OS/2 User Group
P.O. Box 26904
Santa Ana, CA 92799-6904, USA

Copyright 2001 the Southern California OS/2 User Group. ALL RIGHTS RESERVED.

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.