PID: EleBBS/W32 v20130208.d   
   MSGID: 1:340/1101 0123a232   
   REPLY: 122.fe_help@1:154/700 2d0cdecc   
   NOTE: IceEdit 2.35 K96741   
   TID: FastEcho 1.46.1 43288   
      
   * In a message originally to Martin Kazmaier, Nick Boel said:   
      
    > Hey Martin!   
      
    > On Wed, Aug 20 2025 15:06:00 -0500, you wrote:   
      
    > > I can't pack netmail to 30:30/99, only everything else.  That is for   
    > > gated email.  Scan goes before pack.  I'm not sure if I need via or   
    > > just the node number.  A lot of netmail goes to things like 1:40/150   
    > > and is going via 1:229/426.   
      
    > If you can't pack and scan for 30:30/99, then it probably shouldn't even   
    > be in your tosser's configuration. Is this something you're doing with   
    > IREX or some such?   
      
   It needs to be scanned, not packed.   
      
    > I'm fairly sure you should pack your netmail before you try to scan it   
    > out. Although, some tossers (like HPT for example), you can enable a   
    > configuration option "PACKNETMAILONSCAN" so you don't have to use both   
    > commands, but I don't know if FastEcho has that option or not.   
      
   Scan scans the message areas for outbound messages, including netmail.  Then   
   pack sends the netmail.   
      
    > You don't need "via". This is what setting 1:229/426 (1:* 2:* 3:* 4:*)   
    > already does. Any node number in zone 1-4 will go to Nick Andre first. And   
    > if you want to add any direct links for Fidonet, they need to be added   
    > /before/ 1:229/426 in order to work properly.   
      
   Ok, using via and not using via wasn't working, so I tried both.   
      
    > Most tossers read a routing table from top to bottom. So if Nick's entry   
    > is first, no other entries for 1:* 2:* 3:* 4:* will work properly.   
      
    > While it seems like you're ultimately confused as to how your tosser   
    > works, at this point, you should probably start over with Fidonet, and   
    > just have 1:229/426 as a link, and route 1:* 2:* 3:* 4:* through it.   
      
   I'm trying that, but only 1:* is routing, not 2:* or 4:*.   
      
    > Once you've done that, and it works properly, then you can add direct   
    > links and/or other route links one at a time while making sure they work   
    > before moving on to the next. If you don't need direct links or other   
    > routes, then leave it alone with the one Fidonet link, and let Nick's   
    > system send any/all of your echomail and netmail where it needs to go. He   
    > kinds knows what he's doing. ;)   
      
   To work around this, I've got fastecho scanning, then irex sending, then the   
   process waiting to close (it gets put to the background, in which case pack   
   runs immediately, so I run a tasklist | findstr rexw.exe and check the error   
   level.), then packing all of the rest of the netmail. Seems to be working.   
      
   --   
   Shurato, Sysop Shurato's Heavenly Sphere (ssh, telnet, pop3, ftp,nntp,   
   ,wss) (Ports 22,23,110,21,119,999)   
      
      
   ---   
    * Origin: Shurato's Heavenly Sphere telnet://shsbbs.net (1:340/1101)   
   SEEN-BY: 105/81 106/201 128/10 187 129/14 305 153/7715 154/110 218/700   
   SEEN-BY: 226/30 227/114 229/110 114 206 317 400 426 428 470 664 700   
   SEEN-BY: 229/705 266/512 291/111 292/854 300/6 320/219 322/757 340/0   
   SEEN-BY: 340/101 400 800 1100 1101 342/200 396/45 60 460/58 712/848   
   SEEN-BY: 902/26 5075/35   
   PATH: 340/1101 400 128/187 229/426