@database 101f4aa0-0
@master up:newnet/ARC/newNET/ENGLISH/newNET.guide
@$VER: 1.0
@author "Alfredo Soro"
@(c) "27 Jun 97 - Alfredo Soro"
@index Main
@remark Created with Heddley v1.1 (c) Edd Dumbill 1994

@node "Main" "Bienvenid@ a newNET"
@next "INTRO"




                            @{b}newNET v1.20@{ub}
                        © Alfredo Soro, 1997


          @{"INTRODUCTION" link "INTRO" 0} ................. What is this?
          @{"REQUERIMENTS" link "REQUI" 0} ................. What is needed?
           @{"INSTALATION" link "INSTAL" 0} ................. How is this installed?
          @{"README FIRST" link "RTFM" 0} ................. RTFM
         @{"CONFIGURATION" link "CONFIG" 0} ................. How is this configured?
                 @{"USAGE" link "UTIL" 0} ................. How newNET is used?
               @{"WORKING" link "FUNCI" 0} ................. The newNET secrets
      @{"ACKNOWLEDGEMENTS" link "Agra" 0} ................. Credits and contact address









     Another gate for Echos, Nets, Ticks, etcetera through E-Mail
@endnode

@node "INTRO" "Introduccion a newNET"
@next "REQUI"
@prev "Main"

                           INTRODUCTION

     If you use YamNet, @{b}newNET@{ub} is programed to replace it.

      "newNET"  is  other program to avoid expensive direct phone
     callings  between  points  and BBS of fidonet-like networks.
     Saving  in long-distant calls and using the way more used of
     the moment:  Internet.

      "newNET" allows to phone automaticly to Internet, send FIDO
     "mail"  files in e-mails using SMTP and to get choosing only
     the  files  generated  by  the  program,  via POP3 (E-Mail),
     without the need of use any concrete E-Mail program; decodes
     files and imports it using the user selected "Fido-Mailer".

      "newNET"  can be used by any  user without the need of that
     the  receiver have newNET installed in the system; Receivers
     can  use  any  standard  MIME E-Mail program to deattach the
     mail files to the INBOUND directory of their system.

      "newNET"  converts  configuration  file  of its predecesor,
     YamNet  to  the  most  modern  newNET @{"configuration" link "CONFIG" 0}.

      "newNET"  deletes  old files that are already sent when has
     passed  a  determinated  number  of  days.  Re-send archived
     files if their are requested in the case of decoding error.

    ------------------------------------------------------------
             newNET is @{b}*Freeware*@{ub} © Alfredo Soro, 1997
       The author is not liable about any damage that could be
     done by this software. newNET is NOT tested on animals. :-)
@endnode

@node "REQUI" "Requisitos de newNET"
@next "INSTAL"
@prev "INTRO"

                         REQUERIMENTS

- Name:    MOOS, The ARexx library. (By Rocco Coluccelli)
  Place:   http://wuarchive.wustl.edu/pub/aminet/util/rexx/
  File:    MOOS.lha - 163898 bytes

- Name:    PGPAmiga 2.6.3 international (By Peter Simons) [optional]
  Place:   http://ftp.uni-paderborn.de/pub/aminet/util/crypt/
  File:    PGPAmiga-2.6.3is.lha - 426911 bytes

- Name:    Base64Coders V1.3 (By Edmund Vermeullen)
  Place:   http://wuarchive.wustl.edu/pub/aminet/comm/mail/
  File:    Base64Coders.lha

- Name:    FSCode V37.20 (By Flavio Stanchina)
  Place:   http://wuarchive.wustl.edu/pub/aminet/util/arc/
  File:    FSCode.lha

- Name:    uuInOut103 (By Nicolas Dade)
  Place:   http://wuarchive.wustl.edu/pub/aminet/util/arc/
  File:    uuInOut103.lha

Other:

- Miami or Amitcp - YAM [Optional] - MailManager [Optional] - another
E-Mailers & "fido-Mailers"

Workbench:

 ARexx:

  Waitforport

 AmigaDos:

  Assign
  Execute
  Rename
  Copy
  Delete
  Filenote
  Wait
  Makedir
  Join
  Protect
  Stack

 Residents:

  Echo
  Run
@endnode

@node "INSTAL" "Instalación de newNET"
@next "RTFM"
@prev "REQUI"


                            INSTALATION


     The instalation  of  @{b}newNET@{ub} is quite easy. Only is needed to
    copy the newNET file to your SYS:C/ drawer and the  language
    file s/newNET.ENGLISH to your SYS:S/ drawer @{b}*renaming*@{ub} it as
    newNET.LANG

    If this is very difficult for you or newNET doesn't work  as
    must be waited,   you can use the included  installer script
    @{b}install-newNET@{ub} from its own icon.

     This installer will check that you have correctly installed
    all the files that @{b}newNET@{ub} @{"REQUIRES" link "REQUI" 0} to work.
@endnode

@node "RTFM" "Lee el MANUAL"
@next "CONFIG"
@prev "INSTAL"

                     USING newNET FOR FIRST TIME

     Before the executing of this program like it would be a game
    please, read  carefully the  @{"USAGE" link "UTIL" 0}  and  @{"CONFIGURATION" link "CONFIG" 0}
    instructions.  Thank you.
@endnode

@node "CONFIG" "Configuración de newNET"
@next "UTIL"
@prev "RTFM"

                           CONFIGURATION

     First   time   you  execute  the  program,  if  not  exists
    configuration  file (S:newNET.cfg) the configuration routine
    will  be  activated,  and depending if you have or you don't
    have  a  YamNet  config  file,  S:YamNet.cfg,  more  or less
    questions will be asked to you.

     NOTE:    First  time  you  run  newNET  having  it  or  not
    configured  the program will be really executed like allways
    will   do   depending   of   its   configuration   and   the
    @{"arguments" link "UTIL" 0}  that  you  especify.   IF you have a S:YamNet.cfg
    config  file  (and  you  don't have created the S:newNET.cfg
    config  file) @{b}newNET@{ub} will adapt this configuration to use it
    when  configuration routine is finished encoding the mail of
    your  YamNet configurated nodes from your OUTBOUND using the
    @{b}newNET@{ub}  standard  format  and  with the same method and user
    data configured in YamNet.cfg

     To  modify configuration (or create it if you don't wait to
    use the configuration routine) use a ascii plain-text editor
    to modify a file like this.

                      The S:newNET.cfg file
    -----------------------------------------------------------
    ; newNET.cfg  Format for newNET 1.20
    ; You can leave comments here using semi-colon,
    ; but the speed of execution will be reduced a little (very little)

    INBOUND IN:
    ;INBOUND <directory>
    ;in this case <directory> is the drawer where is stored
    ;all bundles, PKTs and the rest of fidonet-type files.

    OUTBOUND OUT:
    ;OUTBOUND <directory>
    ;in this case <directory> is the drawer where our fidomailer
    ;has the control index files HLO, CLO, PKT or similars addressed
    ;to our links (points or nodes)

    LOG Logs:newNET.log
    ;LOG <file>
    ;<file> will be the name of the file where will be writed the logfile
    ;of the program usage with the actions reported depending of LOGLEVEL.

    TEMP T:
    ;TEMP <directory>
    ;Temporal work directory of newNET (de/encode, create file
    ;headers, etc) Preferably use RAM:
    ;Although if you are very short of memory, best use HD.

    LOGLEVEL 4
    ;LOGLEVEL <level>
    ;<level> indicates the verbosity level of the program.
    ;levels:
    ; 0 = SILENT, SILENT.
    ; 1 = Informs only about important actions, without write in logfile.
    ; 2 = Show more information and also don't write in logfile.
    ; 3 = Show what is doing the program and write the same in logfile.
    ; 4 = Show and write in logfile all posible information about program
    ;     execution.

    DAYS 14
    ;DAYS <days>
    ;In <days> you must to indicate the number of days you want that newNET
    ;wait before delete an archived newNET file.

    GMT +0100
    ;GMT <gmt>
    ;<gmt>  must be adjusted depending of your position respect to
    ;the Grenwitch meridian depending of your time zone.
    ;<gmt> must be five characters:
    ; The first one always be the plus sign + or less sign - and the
    ;other four always will be numbers that indicates hours tenths
    ;(0 or 1), hours units, minutes tenths and at the end a zero.
    ;(minutes) in that order.
    ;In Europe generally is +0100
    ;In american countries the time zone could be something between -0300
    ; and -0800
    ;To more information look in the PREFS program LOCALE

    NODE 2.344.44.0 pflins@rubber.com FidoE-Mail MIME
    NODE 50.500.50.0 brobin@rabbit.org emailred PGP "Michael Knight"
    NODE 2.341.341.0 zoof@uwater.com FidoE-Mail PGP
    NODE 28.91.111.0 zoof@uwater.com CuaE-Mail FSCode
    ;NODE <zone.net.node.point> <email-dest> <name-for-network> <method>
    ; <zone.net.node.point>  must be the 4D address of the node
    ;that you want to send its echo-etc-mails. Is necessary to use
    ;the same format that is used in the OUTBOUND directory by the
    ;fidomailer program. I mean separating zone, net, node, and point
    ;numbers with dots instead of normal signs (x:x/x.x)
    ; <email-dest>  Is the e-mail address that will be used to
    ;send all packets, files, and bundle files destinated to the
    ;node/point.
    ; <name-for-network> Name used by the newNET users.
    ;I use allways this names:
    ;Amiganet: AmigaE-Mail
    ;Fidonet:  FidoE-Mail
    ; In the last field could be used many distinct methods, <method>:
    ;MIME
    ; -The most standard. And this MUST be used if the destination user
    ;don't use newNET. This method is valid for a lot of e-mail programs
    ;of ANY platform or O.S.
    ;FSCODE
    ; -Is a good alternative to the PGP method. Is fast and reliable.
    ;The inconvenient is that if you don't use newNET dificilly you'll
    ;find an E-Mailer that support this method.
    ;X-UUE
    ; -Encoding method of old Unix machines. Still implemented
    ;in some E-Mail programs.
    ;PGP
    ; -Fast and reliable method of PUBLIC encoding.
    ;PGP "User Name"
    ; -Fast, safe, and reliable method of encrypting the files.
    ;This last two methods only works if you have PGP installed and
    ;correctly configured. And this last method, only is valid
    ;if you have the public key of the user in "User Name".

    TCPROG AMITCP
    ;TCPPROG <TCPprogram>
    ;Name of the TCP program you use to connect with internet.
    ;Only two options: MIAMI or AMITCP

    ONLINE Amitcp:bin/internet
    ;ONLINE <dialing script>
    ;<dialing script>  must be the executable or Script that
    ;is used to call internet.
    ;Is important that the file have "S" flag in case of be an Script.
    ;P.E.: You can put the flag "S" using this AmigaDOS command:
    ;protect Amitcp:bin/internet +S

    OFFLINE Amitcp:bin/stopnet
    ;OFFLINE <hang-up script>
    ;<hang-up script> must be the executable or script to hang-up.
    ;Equal to ONLINE keyword if is an script, must have "S" flag.

    EMAIL yself@yourdomain.addr.es
    ;EMAIL <your-EMail-Address>
    ;In <your-EMail-Address>  you must type your only E-Mail address
    ;used for send and receive newNET messages in your system.

    POPSERVER pop3.yourserver.com
    ;POPSERVER <popserver>
    ;<popserver> is the POP3 (Postal Office Protocol) server that
    ;is used to receive E-Mails. If you don't know what is your
    ;POP3 server ask to your internet provider.

    SMTPSERVER smtp.yourserver.com
    ;SMTPSERVER <smtpserver>
    ;<smtpserver>  is the SMTP  (Simple  Mail Transfer Protocol)
    ;server and lets you send E-Mails through internet.
    ;Sometimes is the same name of the POP server.

    USERID yself
    ;USERID <user-id>
    ;<user-id> is generally the string before arroba sign (@)
    ;Is your identificative as electronic mail user.
    ;THIS IS NOT the login-id of TCP conection.
    ;Although could be the same.

    USERPASS idontsaytoyou
    ;USERPASS <E-Mail-password>
    ;<E-Mail-password> is the password configured in your internet
    ;provider for get your electronic mail.
    ;This password normally is the same configured to connect with
    ;internet and is proporcioned to or from your internet server
    ;at time of create your e-mail account.

    FMAILER MM
    ;FMAILER <fido-mailer>
    ;You must replace <fido-mailer> only with one of this arguments:
    ;MM
    ; This is the only argument that works, actually.
    ; Is used for process messages when necessary using MailManager.
    ;THOR
    ; For THOR users, when be implemented in newNET.
    ;SPOT
    ; For SPOT users, when be implemented in newNET.

    ;AUTOIMPORT
    ;Do a PROCESS using the configured fido-mailer  (if supported)
    ;when had been decoded newNET files with bundle files.

    ;AUTOCALL
    ;Call to internet to get and send messages HANGING UP
    ;after the trying of send messages.
        -----------------------------------------------------------
@endnode

@node "UTIL" "Uso del newNET"
@next "FUNCI"
@prev "CONFIG"

                                USAGE

    You can use the following sintax to execute newNET:

    Usable Arguments:

    Connect/S,Days/K,Import/S,Miami/S,Noconnect=NC/S,Noimport/S,
    NoMail/S,Yam/S

  (Type1) @{b}Connect@{ub}  - newNET will try to call internet when the program
                     is ready to receive & send E-Mail messages.  Then
                     newNET will hangup the line after send all newNET
                     messages. (This argument is the same that to have
                     keyword @{"AUTOCALL" link "CONFIG" 184} in a line of  configuration file
                     S:newNET.cfg)

          @{b}Days@{ub}=N  -  In deleting phase, newNET  will  delete all files
          archived in the newNET directory of your OUTBOUND older than
          N  days.   (if  you use this argument newNET will ignore the
          configured days in S:newNET.cfg)

  (Type2) @{b}Import@{ub}  -  newNET execute MailManager, if it  is configured,
          and  will  import  all  bundles and mail packets received if
          newNET has processed it.

  (Type1) @{b}Miami@{ub}  -  newNET will connect to internet using Miami. (only
                   have effect if newNET is @{"configured" link "CONFIG" 119} to use AmiTCP &
                   Miami is installed)

  (Type1) @{b}Noconnect@{ub}
          @{b}NC@{ub}  -  newNET don't hang-up the line after receive and  send
                newNET messages,  newNET neither try to call internet.
                (This is for users that have the keyword "AUTOCALL" in
                @{"configuration" link "CONFIG" 184} & are connected to internet when they go
                to execute newNET)

  (Type2) @{b}Noimport@{ub}  -  Avoid automatic processing of messages with the
                      MailManager  program (if it is @{"configured" link "CONFIG" 169})  This
                      is for users that wants newNET ends its task as
                      soon as possible.

  (Type1) @{b}NoMail@{ub}  -  As NoConnect argument it doesn't call to internet
                    but also don't try to send or receive any  E-Mail.
                    Only encoding, decoding, storing,  processing  and
                    old files deleting routines will be executed.

          @{b}Yam@{ub}  -   Lets to YAM users moving directly to INBOUND   all
         files, decoding  it  from  @{b}newNET@{ub}  messages  that  have been
         received using YAM, without getting it using newNET, before.
         Very  practical when MIME method is NOT used and files can't
         be  easily  dettached  because are encoded in FSCode or PGP.
         @{b}newNET@{ub} will move all files to be detached in inbound.
          newNET  also  will get all E-Mails in your mailbox, putting
         it into the incoming drawer of YAM and filtering it depening
         of your YAM configuration.


     "Type1" arguments are mutually incompatible.   In the  same
     way  that  "Type2" arguments; It can't be combined arguments
     of the same Type.


 
     Arguments have priority over @{"configuration" link "CONFIG" 0}.


    Examples:


    > newNET CONNECT NOIMPORT

    : Creates messages to be send to the @{"nodes" link "CONFIG" 82}  configurated  in
    newNET, Call to internet, receives @{b}newNET@{ub} messages, send the
    prepared messages, hangup, moves and decodes received  files
    to your INBOUND and ends deleting all old archived files.
     If  newNET  is  configured to IMPORT, configuration will be
    ignored.


    > newNET YAM NOMAIL
    
    : Deattachs files received in messages from YAM incoming  to
    the INBOUND without call/hangup internet  and  without send/
    receive any e-mail message.


    > newNET MIAMI IMPORT DAYS = 1

    : newNET calls internet using Miami instead  of  @{"TCP" link "CONFIG" 119} program
    configured, normally AmiTCP, then  after  receive  and  send
    @{b}newNET@{ub} messages, newNET hangs up Miami, deletes all archived
    files  stored  one day ago (Very practical if you have short
    of  Hard  Disk  space)  At  the  end,  @{"Mail  Manager" link "CONFIG" 169} will be
    executed  (if  newNET messages are received) and will import
    all messages.


      This  was  only  examples.  Use the arguments that you
     need more in every moment.
@endnode

@node "FUNCI" "Asi funciona newNET"
@next "Agra"
@prev "UTIL"

                           WORKING


Theese  are  the steps followed by newNET from its execution to the end:


 - PROGRAM BEGINS.

 - Is searched the S:newNET.LANG file that contains all text strings in the
user selected language.

 - If not exists the S:newNET.cfg file, begins the CONFIGURATION routine:
   CONFIGURATION
   -
    All  needed  data  are  asked to make the
configurationconfigurationconfigurationconfigurationconfiguration@{"configur
ation"
   link "CONFIG" 0}.  If exists the S:YamNet.cfg config file it
   is converted and some questions about nodes to use in newNET
   aren't asked.

 - Configuration is read.

 - If not exists a "newNET" drawer in the user OUTBOUND, it's created.

 - If YAM argument is  specified when executing newNET,
   it is tryed to run YAM.
    YAM
    -
     The  program  look  in the YAM's INCOMING drawer for newNET
    specific  E-Mail  messages  and  move it to OUTBOUND:newNET/
    drawer  adding  to  its filenotes that are messages ready to
    Decode, putting the "D" letter at the begining of comment.

 -  OUTBOUND  is examined searching HLO, FLO, CLO, DLO, CUT,
 OUT,  DUT,  HUT  index files for configured nodes in newNET;
 preparing   mailer   files:    echomail/netmail,   TICS   or
 fileattachs.
  All files are stored in OUTBOUND:newNET/ drawer (OUTBOUND:
 could  be  any drawer configured) putting at the begining of
 its filenote the "C" letter (indicating that are files ready
 to enCode)

 - OUTBOUND:newNET/ directory  is examined to see  what files
 are  ready  to be encoded (with a "C" letter at the begining
 of filenote).
  Files  are  encoded  with  configured method,  specified in
 previous step filenote.

   A  standard E-Mail header is created to send every message
 with  encoded file.  The E-Mail message is MIME standard and
 can be processed with any MIME standard E-Mail program.
  Files that previously had "C" letter now have an "A" letter
 ("Archived")  and the new files in E-Mail format ready to be
 send have the letter "E" in its filenote.

 -  If  argument  NOMAIL  isn't used when newNET is executed
 CALLING routine is started:


   CALLING
   -
   If  AUTOCALL  keyword is present in the configuration and NC
   or NOCONNECT argument is not used, or if CONNECT argument is
   used, the routine CALLING2 is started.

  
       CALLING2
       -
       If  argument  MIAMI is not used, the ONLINE script specified
       in newNET configuration is used to connect into internet.
       -
       If  MIAMI  argument was specified, newNET will execute MIAMI
       and will use it to connect into internet.

   -
   If  TCP:  program is working it is tryed conecting to E-Mail
   POP3 server and after that with SMTP server.

      POP3
      -
      Server  is  acceded using username & password.  The messages
      number of the mailbox is checked.
     
      -
      If  YAM  argument  is  used  all  messages  from mailbox are
      retrieved.    Putting   the   specific  newNET  messages  in
      OUTBOUND:newNET/  directory  with "D" letter in filenote (to
      Decode)  The  rest of messages are stored in INCOMING folder
      of YAM and FILTERED using YAM.
     
      -
      If  YAM  argument  is not used only specific newNET messages
      are    retrieved    from   the   mailbox   storing   it   in
      OUTBOUND:newNET/ directory with "D" letter in filenote.

      SMTP
      -
      All  files  in  OUTBOUND:newNET/  with  an "E" letter at the
      begin  of  its  filenote are sended through your SMTP E-Mail
      server and deleted from directory.

   -
   HANGUP is tryed to go OFF LINE but only if AUTOCALL keyword
   is specified in configuration or CONNECT argument is used.

     HANGUP
     -
     If MIAMI argument is used, newNET tryes to go OFF LINE using
     MIAMI.

     -
     If  MIAMI  argument  is  not used, the command configured in
     OFFLINE keyword is used to hangup conection.

 -  OUTBOUND:newNET/ directory is  examined looking for files
 with  "D"  letter  in  filenote  (to Decode).  The files are
 decoded  to INBOUND; If a bundle file exists in INBOUND with
 the same name of decoding file it will be used an equivalent
 new name.
 A  "B" letter is putting in received file if it is correctly
 decoded (indicating that is a file ready to be deleted).  If
 size  doesn't  match  or  file  is  not correctly decoded, a
 message to Request a Resending of the file is prepared.

 -
 Files  with  "B" letter in filenote are deleted and also all
 the  files stored since more than DAYS number configured (or
 specified in arguments).
 The files with "K" letter in filenote that have been created
 since more than a week also be deleted.

 -
 If  exists  files  in  newNET  directory  with "D" letter in
 filenote  that was decoded in INBOUND the PROCESS routine is
 started while IMPORT keyword is configured or argumented and
 don't be used the NOIMPORT argument.

 -
  If  there  are files in newNET drawer of the outbound with
 the 'D' letter in filenote that had decoded in INBOUND, the
 PROCESS  routine  is  started,  while the keyword IMPORT is
 present  in  configuration  and  is  not  used the NOIMPORT
 argument  or  if  the  argument  IMPORT  is especified when
 executing newNET.

   PROCESS
   -
   In case of having configured MailManager as the fidomailer
   (MM)  the program is started, if there wasn't yet, and the
   bundles files of the inbound are processed.

   -
   If you have configured another fidomailer wait
   for a new newNET version for this option works.

 - THE PROGRAM EXITS.



ABOUT FILENOTES:

 All  files  of  newNET  directory  have  a FileNote or File Comment that
could be seen making a LIST of the directory.

This  comments  says  to newNET all necesary information for the files could
be processed adequately.

p.e.: A file with this filenote:

A ted@red.es 9BCA4356.SA0 7525 FidoE-Mail newNET-729554.5 MIME

Informs  to  the program that the file with that filenote is an  already
sent  file  ("Archived")  to  "ted@red.es" that originally  was  named
"9BCA4356.SA0"  with 7525 bytes from network  named  like  "FidoE-Mail"
which origin file has the name  of  "newNET-729554.5"  and was used the MIME
method to send it.

All filenotes use a similar structure.


 The  first  letter  of  filenote  can  be any of theese six letters; and
says to newNET what to do with every file:


"C"  bundle  file  copied  or  moved  from  original drawer.
    (Outbound:bundles  or  so)  Ready  to  enCode.   When is
    created the new encoded file goes to have the "A" letter
    in the filenote.

"A"  Archived file. The file was encoded in a new file  that
    is already created to be sent. This file is  stored  for
    assurance. If is received a Re-Send request (in case  of
    file couldn't be decoded correctly in destination). When
    a determined number of days has passed  the  files  with
    this letter go to use the "B" letter.

"E"  File  ready  to  send  via E-mail.  Is a text in e-mail
    format that includes the encoded file attached. When  is
    sent the file is commented with the "B" letter.

"D"  Received E-Mail file ready to Decode.
    When is decoded in INBOUND directory goes to have the "B"
    letter.

"B"  File ready to para immediate deleting.

"K"  Received file, that couldn't be correctly decoded, that
    is ready for deleting in one week after be received.
 ----------------------------------------------------------
@endnode

@node "Agra" "Agradecimientos"
@prev "FUNCI"

                          ACKNOWLEDGEMENTS

     I  thank  to  the following persons their direct or indirect
    support  to  this  program  that  without  they this program
    couldn't be done.

    Rocco Coluccelli -- For his rexxMOOS.library
    Edmund Vermeulen -- For his Base64coders
    Flavio Stanchina -- For his FSCode
    Peter Simons -- For his PGPAmiga 2.6.3i
    Nicolas Dade -- For his uuOUT & uuIN

    Robert Hofmann -- For his CompressRexx

    Miguel Barnosi -- For his intense BetaTesting
    Ferran Delriu -- For be the best AMIGAn ex-SysOp
    Julio Garcia -- For be the best pcerian SysOp
    Eugenio De Frutos -- For his heavy support

    and  the  rest of sysops and AmigaNET users that enjoy using
    my program.

                                    THANKS


    For any affair you can contact with me in theese addresses:

              Greetings, Alfredo Soro.  Freddy/SOGA
        GSM: +34 29 463594  -@{b}asoro@redestb.es@{ub}-  nyar@geocities.com
     www.redestb.es/personal/asoro   www.geocities.com/Hollywood/6442

     Fidonet   CuaRed[34]  Amiganet    VMail   NavarraNet      RedBBS
     2:344/15   28:94/1    39:194/1  70:344/2   150:20/3   757:1202/1

        SOGA: http://www.geocities.com/SiliconValley/Vista/3266
@endnode

