-=> Daryl Stout wrote to DIGITAL MAN on 06-13-17 17:58 <=-   
      
      
    DM> > When I run SBBSECHO -LINF, it complains "unrecognized internal code,   
   ssu   
    DM> > passthrough".   
      
    DS>   I've gotten the same thing. I was told the other day that SBBSECHO   
    DS> 3.00 was a FLO mailer ONLY, and that the Attach option did not work   
    DS> right...so, I went in, and made changes. I gather the syntax is -LINF   
    DS> for exporting, and -LESR! for importing, correct??   
      
   You no longer need to use the 'options'. Just use sbbsecho alone.  One   
   suggestion.  If you're running htick, you're going to have to use the -d   
   option.  This will prevent the deletion of incoming netmail as to allow it to   
   process any filefix requests.     
      
    DS>   What I did with the AREAS.BBS (in c:\sbbs\data) was set up an   
    DS> internal tag for all the FIDONet style areas, since some of the "tags"   
    DS> from other networks are identical. So, in mine, it looks like this   
    DS> (I'll use the FIDONet Region 19 Sysops echo as an example):   
      
    DS> FIDONET-R19SYSOP   R19SYSOP  1:261/38   
      
   In the Fidonet Group box, what did you put in for the Internal Code? In order   
   for the above to work, FIDONET- would be needed and in the Sub Group, under   
   'Short Name', R19SYSOP. When you export to your areas.bbs file, just tell it   
   your uplink, in this case Janis and either overwrite or append. Personally, for   
   my Internal Code, each network has a #. Fidonet is #1 so my areas.bbs entry   
   would look like this...   
      
   Internal   ShortName  Uplink   
   ----------------------------	   
   1R19SYSOP   R19SYSOP  1:261/38   
      
      
    DS>   Yet in checking the log file, it seemed that SBBSECHO wasn't   
    DS> processing outgoing packets right, if it had the internal tag, specific   
    DS> to the BBS...and I thought I'd need 2 different AREAS.BBS files, but   
    DS> that doesn't seem necessary. In other words, the first entry and the   
    DS> second entry were identical...but as of now, they look like what I   
    DS> noted above.   
      
    DS>   Also, I tried using the ZIP and UNZIP, but was getting messages that   
    DS> they didn't know how to handle the packets (I assume done with   
    DS> PKZIP/PKUNZIP). Along that line, I have registered copies of 2.04g and   
    DS> 2.50 -- which would be better?? I also disabled the other archivers for   
    DS> now, but I could put them back in, below ZIP, if it's necessary.   
      
   Do you have ZIP and UNZIP in your ../sbbs/exec folder or in your PATH   
   tatement?   
      
      
      
      
   --   
      
   Bill   
      
   Telnet: tequilamockingbirdonline.net   
   Web: bbs.tequilamockingbirdonline.net   
   FTP: ftp.tequilamockingbirdonline.net:2121   
   IRC: irc.tequilamockingbirdonline.net Ports: 6661-6670 SSL: +6697   
   Radio: radio.tequilamockingbirdonline.net:8010/live   
      
      
   ... Look Twice... Save a Life!!! Motorcycles are Everywhere!!!   
   --- MultiMail/Win32 v0.50   
    * Origin: TequilaMockingbird Online - Toms River, NJ (1:266/404)