This is my attempt at listing some Frequently Asked Questions for the
newsgroup comp.os.os2.networking.tcp-ip, which is where IBM tells us
all to look for support and exchange information about OS/2 Warp when
running the Internet Access Kit.

DISCLAIMER:  The information contained within this document was mostly
extracted from posts made to comp.os.os2.networking.tcp-ip and thus
has only the credibility of the original poster, which can range
anywhere from "propagator of ill-founded rumors," right on up to the
"official words of IBM," or even higher. ;-)

     THIS DOCUMENT IS PROVIDED "AS-IS" AND ANY USE HEREOF IS AT THE
     RISK OF THE USER.  ABSOLUTELY NO REPRESENTATION IS MADE AS TO
     THE COMPLETENESS, ACCURACY, TRUTHFULNESS, USABILITY, OR OTHER
     CHARACTERISTIC OF THE INFORMATION CONTAINED HEREIN.  FURTHER,
     ABSOLUTELY NO REPRESENTATION IS MADE AS TO THE OWNERSHIP OF
     ANY RIGHTS TO ANY OF THE INFORMATION CONTAINED HEREIN.  IF YOU
     NEED SOMEONE TO EXPLAIN TO YOU THAT YOU USE THE INFORMATION
     CONTAINED HEREIN AT YOUR OWN RISK, THEN YOU ARE EXPLICITLY
     PROHIBITED FROM USING ANY INFORMATION CONTAINED HEREIN.

All information contained herein is copyright by the various authors
thereof, and on their behalf, I am demanding a royalty of $1,000 per
use for any use by Microsoft Network.  Any such usage is deemed to be
consent to this royalty agreement, and payment shall be immediately
remitted to:

     William A. Schultz          guru@deltanet.com (Bill Schultz)
     P. O. Box 18732
     Irvine, CA  92713-8732

I am actively soliciting comments, clarifications, and requests for
changes to this FAQ.  Either questions, answers, or both may be
submitted.  Of course, the bulk of the information contained herein
has been, and will continue to be, extracted from the newsgroup
discussion threads in comp.os.os2.networking.tcp-ip as time goes by.

This is file number 12 of 12.  It contains the fourth part of some
long information which would not easily fit within parts 1 through 8.

TABLE OF CONTENTS:

     FAQ PART ONE:

          1.0  GENERAL QUESTIONS
          2.0  GENERAL IBM QUESTIONS
          3.0  GENERAL OS/2 QUESTIONS
          4.0  OS/2 INTERNET ACCESS KIT (IAK) QUESTIONS
          4.1  GENERAL IAK QUESTIONS
          4.2  GENERAL PROXY SERVER QUESTIONS
          4.3  DIAL OTHER PROVIDER QUESTIONS
          4.3.1  GENERAL DIAL OTHER PROVIDER QUESTIONS

     FAQ PART TWO:

          4.3.2  SLIP SPECIFIC QUESTIONS

     FAQ PART THREE:

          4.3.3  PPP SPECIFIC QUESTIONS

     FAQ PART FOUR:

          4.3.4  TIA SPECIFIC QUESTIONS
          4.4  ULTIMAIL/LITE QUESTIONS
          4.5  NEWS READER/2 QUESTIONS
          4.6  SENDMAIL QUESTIONS

     FAQ PART FIVE:

          4.7  WEB EXPLORER QUESTIONS
          4.8  FTP QUESTIONS
          4.9  GOPHER QUESTIONS
          4.10  RETRIEVE SOFTWARE UPDATES QUESTIONS
          4.11  OTHER IAK SOFTWARE QUESTIONS
          4.12  WINDOWS TCP/IP WITH IAK SOFTWARE QUESTIONS

     FAQ PART SIX:

          5.0  OS/2 TCP/IP QUESTIONS

     FAQ PART SEVEN:

          5.0  OS/2 TCP/IP QUESTIONS (Continued)
          6.0  OTHER BONUS PACK SOFTWARE QUESTIONS
          7.0  IBM RESOURCES
          8.0  THIRD PARTY SOFTWARE QUESTIONS
          9.0  OTHER RESOURCES

     FAQ PART EIGHT:

          9.0  OTHER RESOURCES (Continued)

     FAQ PART NINE:

          APPENDIX A - INSTRUCTIONS FOR INSTALLING FIXPACK 5

     FAQ PART TEN:

          APPENDIX B - SLIP CONFIGURATION EXAMPLE

     FAQ PART ELEVEN:

          APPENDIX C - PPP CONFIGURATION EXAMPLE

     FAQ PART TWELVE:

          APPENDIX D - ABBREVIATED SENDMAIL DOCUMENTATION

EDITOR'S NOTE:  This document is very much a work in process.  In fact,
I have not yet completed editing it.  However, because there is so
much useful information available herein, I have decided to go ahead
and post it anyway.  This should result in some comments from all of
you which might save me the trouble of editing this further. (i.e., if
nobody thinks this is a good idea, or that it is way too long. ;-)

APPENDIX D - ABBREVIATED SENDMAIL DOCUMENTATION

Newsgroups: comp.os.os2.networking.tcp-ip
From: forester@netcom.com (Mike Forester)
Subject: Re: sendmail
Message-ID: <foresterD6G5ED.57o@netcom.com>
References: <3la74v$984@solaris.cc.vt.edu>
Date: Mon, 3 Apr 1995 06:44:36 GMT

Jim Hendry (jhendry@vt.edu) wrote:
: Does anyone know the command line parameters for SENDMAIL.EXE.  I 
have the 
: IAK and would like to bypass the flaky UMail interface.  Please send 
me mail 
: or post to this group.


: 					Thanks in Advance,

: 					Jim

  --------------------------------------------------------------------
  15. SendMail Server and Client


     SendMail can be used in one of two modes, as a server or as
     a client.  The server mode is used for receiving mail, and
     the client mode is used for sending mail.

  --------------------------
  15.1 Server

     If both modes of SendMail are needed (which normally is the case),
     the SendMail server must always be started first.

     Following are examples of commands to start the SendMail server:

       sendmail -bd                start the SendMail server
       sendmail -q30m -bd          start the SendMail server and
                                   process the mail queue every 30
                                   minutes
       sendmail -d1.1 -q30m -bd    start the SendMail server, process
                                   the mail queue every 30 minutes, and
                                   log connections in the SENDMAIL.LOG
                                   file
       Note:  The SENDMAIL.LOG is not a message file.  You should use
              the -d1.1 parameter only for debugging purposes, because
              it records all details of the client-server handshaking
              procedure (as described in RFC 821) in the SENDMAIL.LOG.

     The SendMail server functions as follows:

        1. The command with a -bd flag starts a SendMail server which
           sets up the SendMail environment, copies the SENDMAIL.CF 
file
           to a shared memory and then waits for requests from SendMail
           clients to establish connections and to deliver mail.

        2. When a request for connection arrives, the server initiates
           another instance of SendMail (a SendMail child process) 
which
           initializes itself from the configuration information in the
           shared memory, and then services the connection and receives
           mail.

        3. Once the mail has been received and properly delivered to 
its
           destination, the SendMail child process closes the 
connection
           and exits.

     The number of SendMail child processes that can run at any one 
time
     is controlled by a Load Limiting variable which by default is 6,
     but can be changed by the OX option in the SENDMAIL.CF file.

  --------------------------
  15.2 Client

     The SENDMAIL client command now has additional parameters.  The
     SendMail client mode is usually started by a User Mail Agent, but
     can also be started from an OS/2 Command line.

     SYNTAX

     >>--sendmail--.-----.--.------.--.----------------.---------------
>
                   '- -q-'  '- -bt-'  '- -Cmyconfig.CF-'

     >-- -af filename--.- -f user@localhost user@remotehost-.----------
>
                       '- -t--------------------------------'

     >--.--------.----------------------------------------------------
><
        |- -d1.1-|
        '- -d----'


     -q         Instructs SendMail to process the mail queue.  If you
                include other parameters, SENDMAIL will ignore them.

     -bt        Instructs SendMail to run in rule-testing mode.  You 
can
                use this parameter to test changes to rules in the
                configuration file.  In rule-testing mode, SendMail
                prompts you to enter a rule-set number and address, and
                then displays how the rule-set causes the address to be
                rewritten.  SendMail Version 1.3.0 always calls
                rule-set 3 first and then the entered rule-set number.
                In rule-testing mode, SendMail does not deliver any 
mail.
                This parameter cannot be used with any other parameter.

     -Cmyconfig.CF
                Specifies the name of a configuration file to use 
instead
                of SENDMAIL.CF.

     -af filename
                Specifies the name of the file that contains the mail
                message.

     -f user@localhost
                Identifies the user and host name of the sender.

     user@remotehost
                Identifies the user and host name of the receiver (or
                destination).

                NOTE:  OS/2 is not a multiuser operating system.  The
                user field of an address in an item of mail sent to an
                OS/2 system is not significant; however, it is 
required.
                The significant part of the address is the host name,
                with the domain name expansion if domain names are 
used.

     -t         Specifies that SENDMAIL retrieves the to and from
                information for the mail from the body of the file 
rather
                than from the command line.

     -d1.1      Creates only the SENDMAIL.LOG file.  The SENDMAIL.LOG
                file is placed in the ETC directory.

                NOTE:  The SENDMAIL.LOG is not designed to keep track 
of
                messages you send and receive.  You should use the -
d1.1
                parameter only for debugging purposes, because it 
records
                all details of the client-server handshaking procedure
                (as described in RFC 821) in the SENDMAIL.LOG.

     -d         Writes detailed debugging information to the SENDMAIL
                console and creates a SENDMAIL.LOG file.

                NOTE:  The -d parameter produces a great deal of
                       information, and for performance reasons, should
                       be used only for debugging.

     Examples of the SendMail client startup command are:

            sendmail -af file -f sender recipient
                                            (Send a message using the
                                            SendMail client)

            sendmail -d1.1 -af file -f sender recipient
                                            (Send a message using
                                            the SendMail client
                                            and log the connection
                                            in the SENDMAIL.LOG file)

            sendmail -Cmyconfig.cf -af file -f sender recipient
                                            (Send a message using the
                                            SendMail client and also
                                            using MYCONFIG.CF instead
                                            of SENDMAIL.CF)

     The SendMail client also uses shared memory for Configuration
     information, if present, otherwise it gets this information by
     reading the SENDMAIL.CF file.

  --------------------------
  15.3 Considerations

     If SendMail is used for sending a message to several recipients on
     the same workstation, the number of recipients should be limited
     to 150.  A message for 150 recipients will be received as several
     files with lesser number of recipients in each (the number of
     recipients is limited by the header buffer space; recipients would
     be added to a header until that header ran out of room, then the
     process would begin again with a new header).

     If sending a message to 30 or fewer recipients, the whole file may
     be transmitted in one transaction.

     The processing time for sending a message to several recipients is
     much longer than that for a single recipient.  Potentially, the
     processing time may exceed the time-out of the client.  Time-out 
is
     determined by the idle time on the socket, and is typically 
measured
     from the last activity on the socket.  On a UNIX system, the 
client
     time-out is usually 2 minutes;  on an OS/2 system, it is usually 5
     minutes.

     If a client times out, the connection is not closed properly, and
     SendMail is not made aware of the completion status of the 
message.
     Sending a message to more than 150 recipients can cause the 
network
     connection to time out.  Therefore, the number of recipients for a
     given message should be limited to 150.

     On a busy server handling multiple transactions, you run the risk
     of not servicing a given connection fast enough, thereby allowing
     the client that established the connection to time out.  The 
client,
     not aware of the completion status of the message, then requeues 
the
     message for later delivery even though it may have been delivered
     already.  At a later time, the client delivers the same message
     again, and if the connection times-out again, the client requeues
     the message again.

     To prevent this undesirable looping, a network connection cannot 
be
     allowed to time out.  It is, therefore, imperative to use a server
     that has sufficient processing capability to handle the mail
     delivery load.  To send mail to large numbers of recipients, the
     minimum size of machine you should consider is a 33 Megahertz
     machine with 16 MB RAM, HPFS and DISKCACHE to enhance the disk
     performance.


-----------------------------------------------------------------------
-

***********  END OF PART TWELVE OF TWELVE PART WARP/IAK FAQ  **********
