ftp.wwiv.com/ftp.wwiv.com.zip/ftp.wwiv.com/pub/BBS/WG042894.ZIP/UPDATE.DOC

Text File | 1994-04-28 | 14KB | 355 lines

 │ New Features WaterGate Release 0.10.0428
 │ 28/04/1993
 │
 │

 . Import function      (added   28/04)
 . Signatures           (added   19/03)
 . Address Mapping      (revised 19/03)
 . ListServer
 . Gateway restrictions

 Once again some additions not mentioned in the manual, i'll promise to
 update the manual sometime soon; (not to soon of course ;-)

 '|' before a line means that it that part of the documentation was updated
 since the last release.

 Each of the 3 programs (Wtrgate,WtrUtil & WtrConf) can be started with a
 -? as an command line switch, explaining all possible commandline options.

 ============================================================================
 Import function
 ============================================================================

 Because the program now supports multiple netmail areas, you probably
 want to store messages for certain AKA's in different netmail directory's.
 WaterGate itself will store all received netmail in the main *.MSG (!)
 netmail directory. Using WtrUtil you can then move them to different bases.

 For example: You are using 80:100/1 as your Ghostnet aka, and you
 want to store all of your messages for that AKA in the 'GHOST_NET'
 base.

    C:>WTRUTIL IMPORT GHOST_NET 80:100/1

 Will do the trick, but then, all those messages in the original
 directory are removed. Add '-NOKILL' to keep them.

 ===========================================================================
 Signature's
 ===========================================================================

 When converting a message from Fido->UUCP the program will look if there
 is a signature file defined for the sending user or system. A signature
 is an small signoff message put at the end of the actual message. Make
 sure that it isn't too long, 3-5 lines should suffice.

 For example:

 ,----------------------------------------.--------------------------------.
 | Martijn Dijksterhuis                   | Kids! Bringing about           |
 | [e-mail]             | Armageddon can be dangerous.   |
 | [e-mail]                   | Do not attempt it in your home |
 `----------------------------------------.--------------------------------'

 To add a signature for a person or a system add a 'SIGNATURE' command
 to the ROUTE.TDB file.

 Format:

 SIGNATURE <filepath> <address> [<UserName>]

 You need to specify a filename, an address and optional a user name.

 Example:

  SIGNATURE C:\SIGS\DIJK.SIG   2:280/802.6  Martijn Dijksterhuis
  SIGNATURE C:\SIGS\BBS.SIG    2:280/802
  SIGNATURE C:\SIGS\MARK.SIG   2:280/802    Mark Groeneveld

 To a message originating from the BBS at 2:280/802, the file 'BBS.SIG'
 is added at the end, except when 'Mark Groeneveld' writes a message
 since he has his own signature defined.

 ===========================================================================
 Address Mapping
 ===========================================================================

 As an extension to the normal routing of mail and netmail messages,
 WaterGate is now also capable of routing messages for certain users.
 All of the described commands must be added to your ROUTE.TDB file in
 the WaterGate system directory.

 Mapping Fido Addresses
 ----------------------

 WaterGate is capable of mapping Fido netmail messages for users at your
 system to :

                 a) another user at your system
                 b) another users at another system
                 c) a user at a Usenet system

  Examples :

  MAP-FIDO  "Joep Meloen"       "Jaap Aap"

 In this example all received netmail messages for "Joep Meloen" at YOUR system,
 are actualy transported to "Jaap Aap".

   MAP-FIDO "Joep Meloen"       "Jaap Aap"%2:280/[e-mail]

 In this example, not only the message is resend to another username but also
 to another system. (Note the '%' in the last part, it MUST be present)

   MAP-FIDO "Joep Meloen"       [e-mail]

 Here the received netmail messages is converted into Usenet format and
 resend to "[e-mail]".

 Mapping Usenet Addresses
 ------------------------

 WaterGate is capable of mapping received Usenet mail messages to :

                    a) another usenet address
                    b) a fido user at your system
                    c) a fido user at another fido system
|
|                   e) a system, to another system
|                   f) a system, to user at another system
|                   g) a system, to a fido system
|
| The program is now also capable of using the MAP statements to
| build user definable Fido->Usenet addresses. By default every Usenet->
| Fido MAP statement is now also used when converting messages from
| Fido->Usenet.
|

   Examples:

   MAP-UUCP [e-mail]        [e-mail]
   MAP-UUCP [e-mail]     [e-mail]

  All messages for "[e-mail]" are detoured to "[e-mail]"
  This option is also handy if you use multiple names on the network and
  want to route them to one username which you use to read your mail.

    MAP-UUCP [e-mail]        "Joep Meloen"
    MAP-UUCP [e-mail]        "Joep Meloen"%2:280/802.134
|   MAP-UUCP [e-mail]        2:280/802.134

  In this example, all messages for Joep are converted into Fido netmail
  messages for "Joep Meloen", at your system. In the second example they
  are also send to another system.

| When Joep writes a message himself, the program will make it apear
| that the message was sent by '[e-mail]' instead of using
| the default mapping of '[e-mail]'.
|
| Since it is possible to use multiple mappings to one fido address,
| this may not always be the prefered action. You can select whether
| you want to use UUCP<>FIDO , UUCP>FIDO or UUCP<FIDO mapping of
| an address. To do this, you can add the options '-UF' for UUCP>FIDO
| mapping only, or '-FU' for UUCP<FIDO mapping only directly behind
| the MAP-UUCP command. The default operation is to allow mapping
| in both directions (UUCP<>FIDO).
|
| Example:
|
| MAP-UUCP -UF [e-mail]    "Joep Meloen"%2:280/802.134
| MAP-UUCP -FU [e-mail]  "Joep Meloen"%2:280/802.134
|
| The first statement is used to map messages for 'Joep@Melon..' to
| his fido address. The second is used when Joep writes a messages
| himself to make it appear that 'Meloen@Melon..' wrote the message.
| The last one would possible be more correct if it was used as :
|
| MAP-UUCP [e-mail]  "Joep Meloen"%2:280/802.134
|
| To ensure that reply's to his messages are correctly mapped to
| his fido address.

| It is possible to forward messages from one system to another, for
| example, the system 'wildlife' went down, but you want all messages
| for that system to be sent to the system 'backup' instead.
|
| MAP-UUCP wildlife.network.nl   backup.network.nl
| MAP-UUCP dungeon.network.nl    2:280/802
|
| A message for 'user@wildlife..' is now forwarded to 'user@backup..'
| Messages for 'dungeon.network.nl' are mapped to the fido system
| 2:280/802, the default routine for converting usernames to fido is used.
|
| You can send map all messages for a system to one user :
|
| MAP-UUCP wildlife.network.nl   [e-mail]
| MAP-UUCP wildlife.network.nl   "Sysop"%2:280/802

 ============================================================================
 List Server
 ============================================================================

 Added to this release of WaterGate is a list server, and a
 list server robot to process remote connection requests.

 What is a mailing-list ?
 ------------------------

 You can see a mailing-list as a more private echo/news area. Messages
 for all users connected to it are send by (net-) mail, so there is
 no need for all intermediate systems to define a separate echo/news group.

 If a user wants to post a message to the mailing list, he or she simply
 sends it to a system that takes care of the distributing of messages
 to all the participants.

 How does it work ?
 ------------------

 Use the configuration program (WtrConf) to setup a mailing-list.
 For example :

                    ┌─────────────────────────────────────┐
                    │ Listname    : Waterland             │
                    │ Description : Discussion Group      │
                    │ Allow Remote: YES no                │
                    │ Only Known  : yes NO                │
                    │ Active      : YES no                │
                    │ AKA         : 2:280/[e-mail] │
                    │                                     │
                    │ Subscribers : <Enter to Edit>       │
                    └─────────────────────────────────────┘

 First select a name for the new mailing list, the name must be unique
 at your system (make sure you don't have any users with the same name!)

 The description gives some information what this list is about, it is
 shown to users requesting a 'LIST' from the mailing list robot (see below).

 The "Allow Remote" option defines whether people can connect to the list
 using the Mailing list robot, or that all maintenance to the list has to
 be done by the System Operator.

 The "Only Known" option restricts the group of people capable of connecting
 to the list using the robot, only users directly defined at your system
 can connect to the list.

 The "Active" option decides if this list is currently active. A disabled
 list is completely ignored by your system.

 Select an Fido AKA for messages send into fidonet, this AKA is used as
 a From address for all messages send by this list.


 Subscribers
 -----------

 Select "subscribers" to add Fido or Usenet users to a list. For a
 Fidonet user a full name & address is needed, for usenet users only
 a full domain address is needed.

 Make sure you add YOURSELF to the list of subscribers if you want to
 post/read messages in the mailing list.

 How to send messages to a mailing list
 --------------------------------------

 If someone wants to send a message to everyone connected to a mailing
 list, he or she must address the message to that mailing list.
 For example, when posting a message to the mailing list "Waterland" :

    For Fido users :  (netmail)

    From: Joep Meloen      2:200/401
    To  : Waterland        2:280/802
    Subj: New features

    For Usenet User : (mail)

    From: [e-mail]
    To  : [e-mail]
    Subj: New Features

 WaterGate will recognize the message as addressed to one of its mailing lists,
 and copies it to everyone connected to the list.

 How to connect to a list
 ------------------------

 Besides its mailing lists, WaterGate will also treat messages to 'ListServer'
 as special. The listserver is a robot capable of connecting and disconnecting
 users from a mailing list. This robot knows a limited number of commands :


   CONNECT     listname           Connects the sender to a list
   DISCONNECT  listname           Removes the sender from a list
   HELP                           Sends information on how to use the robot
   LIST                           Sends a list of all mailing lists

 Note: Besides CONNECT and DISCONNECT, SUBSCRIBE and UNSUBSCRIBE are also
       valid.

 Simply write a message to the listserver, containing one or more of
 the commands listed above.

   For Fido users :   (netmail)

   From: Martijn Dijksterhuis  2:280/803
   To  : ListServer            2:280/802
   Subj:
   -------------------------------------------------------
   LIST
   CONNECT Waterland
   DISCONNECT Babbel


   For Usenet users : (mail)

   From: [e-mail]
   To  : [e-mail]
   Subj:
   ------------------------------------------------------
   LIST
   CONNECT Waterland
   DISCONNECT Babbel


 When a user requests for "HELP", WaterGate will search its system directory
 for a file named "LISTHELP.TXT", if none is found a standard reply is mailed.

 When a list request is received, WaterGate will try give the listing a
 a header and footer, by searching for the files "LISTHDR.TXT" and "LISTFTR.TXT"
 when none are found, standard settings are used.

 ===========================================================================
 Gateway Restrictions
 ===========================================================================

 Acting as a public gateway may be a really rewarding thing for your soul,
 and a great thing for mankind; but it's not going to pay your monthly
 phonebills. By default WaterGate will allow everyone to gate messages
 between a fido and a usenet network.

 Add the following command to your ROUTE.TDB file :

  FORBID-FIDO *

 And nobody, including yourself is now allowed to use the gateway;
 probably not exactly what you intended. To give some people
 access rights :

  ALLOW-FIDO  2:280/*
  ALLOW-FIDO  2:281/*
  ALLOW-FIDO  2:280/802                 Maarten User
  ALLOW-FIDO  2:280/802                 Sysop
  ALLOW-FIDO  2:280/18.*
  FORBID-FIDO 2:280/18                  Jaap User

 This allows everyone within the nets 280 & 281 to use the gateway,
 2:280/18 and its points, and "Maarten User" and "Sysop" at the system
 2:280/802. Also a special case, "Jaap User" at 2:280/18 is not allowed
 to use the gateway.