PID: EleBBS/W32 v20130208.d   
   MSGID: 1:340/1101 01335bc8   
   REPLY: 120.fe_help@1:154/700 2d0b808e   
   NOTE: IceEdit 2.35 K96741   
   TID: FastEcho 1.46.1 43288   
      
   * In a message originally to Martin Kazmaier, Nick Boel said:   
      
    > Hey Martin!   
      
    > On Tue, Aug 19 2025 11:50:00 -0500, you wrote:   
      
    > > Sorry for replying to myself, my software doesn't give the option to   
    > > change the to: field.  Any way, my direct netmails for areafix and   
    > > filefix are working.  Routed mail is not.  I've got the routing set   
    > > properly in fastecho for 1:229/426 (1:* 2:* 3:* 4:*).   Any ideas?   
      
    > If you're trying to route all of your netmail to 1:229/426, then why do   
    > most of your "fastecho pack" commands start with 1:340/400?   
      
      
   Leftovers and fixed...   
      
    > If you take a look at your fastecho logs, you should be able to see where   
    > these netmails are getting packed for. If you're sending them to Rob   
    > Starr, and he's not routing your netmail properly, that's probably your   
    > problem.   
      
    > I also haven't used fastecho in ages, but I don't remember anything about   
    > the 'via' option, so I probably never used it. If every link is setup   
    > correctly, and your routing table is correct, 'fastecho pack' should be   
    > all you need. Maybe even a 'scan' option afterwards to send it over to   
    > your mailer, unless the 'pack' command does both.   
      
   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're trying to route all Fidonet netmail through Nick Andre, then   
    > what you have above is correct. You shouldn't need anything else for   
    > Fidonet. Then, you will need a separate route setting for zone 10 where   
    > 10:* goes there, a separate route setting for zone 21 where 21:* goes   
    > there, and a separate one for every other network you're a part of.   
      
    > If what you are trying to do is route everything through Nick, but have a   
    > separate direct link to Rob, then you would need a separate route setting   
    > for 1:340/400 specifically where you only route 1:340/400.* to him, and it   
    > would have to be listed /before/ Nick's entry (as 1:* 2:* 3:* 4:* is the   
    > "catch all" that is used if and when any direct links are not used.   
      
    > Hope that makes it a bit easier to understand, and hope it helps.   
      
    > Regards, Nick   
      
   --   
   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