3. Installing FEddi

3.1 User installation fido.

We'll install fido as a mail user, but you can give it another name.

If you see ~/ in this document, we refer to the user's home directory.

• file /etc/passwd Include the following line:

  fido::2004:300::/home/fido:/bin/bash
  

• file /etc/group Include the following line:

  fido::300:uucp,fido,root
  

3.2 Necessary packages

You'll need:

• perl, do

  ls /usr/bin/perl
  

  If not found, install it from disk-set D (Slackware)
• ncurses, do

  ls /usr/lib/libncurses.a
  

  If not found, install it from disk-set D (Slackware)

3.3 mailer installation/configuration.

Change to the directory /FEddi-0.9pl5

1. Edit the file Makefile, put for variable SRCDIR your fonts' path, e.g.:

   SRCDIR=/root/trabajo/mailer/FEddi-dev
   

2. Add to the beginning of the line NODEPRG =: nlfunct.o else it won't compile.
3. make
4. If you get the following error:

   ncurses.h: No such file or directory
   

   Do:

   ln -s /usr/include/ncurses/curses.h /usr/include/ncurses/ncurses.h
   

5. su root
   make install
   exit
   

6. It seems that the install utility doesn't copy all of the utilities; do the following:

   cp utils/* ~/fnet/utility
   

7. A few files need modification:
   • File printmsg

     
     #!/bin/sh
     cat | $HOME/fnet/utility/formatmsg | lpr
     

   • File exportmsg

     
     #!/bin/sh
     if test $1 = "new"
       then
             cat | $HOME/fnet/utility/formatmsg > "$2"
       else
             cat | $HOME/fnet/utility/formatmsg >> "$2"
     fi
     

8. The fnet directory has the following contents:

   ./outbound
   ./msgbase
   ./copy
   ./log
   ./inbound
   ./utility
   ./nodelist
   

   Create these directories and do the following:

   chown -R fido.fido fnet
   

9. Configuration file ~/.feddirc:
   • Permissions 644
   • User/group fido.uucp

   ;
   ; This .feddirc was automatically created with config.user
   ;
   ; Profile Section
   ;
   PROFILE Manuel Soriano
   2:346/207.punto net_name the_passwd outbound 2:*
   25:946/100.punto other_net_name the_passwd outbound 25:*
   93:346/101.punto other_net_name the_passwd outbound 93:*
   END
   ; The first line is your main address, the following are subnets, the routing
   ; fro 25: to 93: is done by means of 2:
   ;
   ;
   ;
   ; Paths
   ;
   MsgBasePath  ~/fnet/msgbase/
   InboundPath  ~/fnet/inbound/
   OutboundPath ~/fnet/
   UtilityPath  ~/fnet/utility
   Log          ~/fnet/log/feddi.log 200
   CopyPath     ~/fnet/copy/
   NodelistPath ~/fnet/nodelist/
   ;
   ; Misc
   ;
   Packer       /usr/bin/zip -q -m -k -j %s %s
   ; Editor       /usr/bin/vi %s
   Beep         Yes
   AutoDelEmpty Yes
   KeepPKT      No
   KeepNL       Yes
   KeepBackups  No
   ShowAllAddr  Yes
   MaxMsgLength 64k
   QuoteLength 70
   ReplySubject No
   AskForOrigName Yes
   AutoNextFolder Yes
   ;
   ; End of .feddirc
   ;
   

   You may base your configuration on this file, as it works for me without troubles.
10. File ~/fnet/nodelist/fnlcrc

    dial    34-6-   3
    dial    34-6    
    dial    *       
    
    pointlist       ptlstr34
    pointlist       eu_point
    
    nodelist        region34
    nodelist        eu_nodes
    

    dial : According to your zone 34-6 (Valencia), 34-1 (Madrid), 34-3 (Barcelona), etc... As pointlist, the different lists of points, you may use the point lists that come from the bbs, without modification. As nodelist, the different lists of nodes, you may use the node lists that come from the bbs, without modification. That's it.
11. Compiling the nodelist/pointlist I'm using the following scripts. They are simple and work.
    • file ~/fnet/nodelist/compila0 permissions 777

      #!/bin/bash
      unzip lista.zip
      mv EU_NODOS* eu_nodos
      mv EU_PUNTO* eu_punto
      mv PTLSTR34* ptlstr34
      mv REGION34* region34
      mv SNETLIST* snetlist
      mv SUBPTLST* subptlst
      

    • file ~/fnet/nodelist/compila1 permissions 777

      #!/bin/bash
      rm fnlc.*
      fnlc
      

    This will compile the lists. If you run into troubles, certainly it's about permissions. Check four files, normally the binaries go to /usr/bin

3.4 Check and usage.

Check your mail. Look for a mail package you might have for MS/DOS. Put it into the directory ~/fnet/inbound and do

ftoss ; futility pack ; futility link

This will always be the way to handle your incoming mail. ftoss will create automatically the folder according to your areas.

fmbedit

If everything went well you'll see the mail of that package on your screen :-)

The editor is quite simple and well documented. It looks somewhat like the fmail's editor.

Create a message in an area or two and do the following:

fscan

This will always be the way to handle your outgoing mail.