home bbs files messages ]

Just a sample of the Echomail archive

Cooperative anarchy at its finest, still active today. Darkrealms is the Zone 1 Hub.

   FE_HELP      The FastEcho Mailprocessor Support Confe      381 messages   

[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]

   Message 368 of 381   
   Nick Boel to Martin Kazmaier   
   Re: pack command...   
   20 Aug 25 17:20:06   
   
   TZUTC: -0500   
   MSGID: 120.fe_help@1:154/700 2d0b808e   
   REPLY: 1:340/1101 01321b5c   
   PID: Synchronet 3.21a-Linux master/955e50fea Aug 10 2025 GCC 15.1.1   
   TID: SBBSecho 3.29-Linux master/955e50fea Aug 10 2025 GCC 15.1.1   
   BBSID: PHARCYDE   
   CHRS: UTF-8 4   
   FORMAT: flowed   
   NOTE: Mozilla Thunderbird   
   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?   
      
   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.   
      
   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   
      
   ... Sarcasm, because beating people up is illegal.   
   --- SBBSecho 3.29-Linux   
    * Origin: _thePharcyde telnet://bbs.pharcyde.org (Wisconsin) (1:154/700)   
   SEEN-BY: 50/22 103/705 104/119 105/81 106/201 114/10 124/5016 128/187   
   SEEN-BY: 129/14 305 153/757 7715 154/10 30 50 110 700 203/0 218/700   
   SEEN-BY: 220/20 30 90 221/0 6 226/30 44 50 227/114 229/110 114 206   
   SEEN-BY: 229/310 317 400 426 428 470 664 700 705 240/1120 5832 263/1   
   SEEN-BY: 266/512 280/464 291/111 292/854 8125 301/1 310/31 320/219   
   SEEN-BY: 322/757 341/66 234 342/200 396/45 423/120 460/58 256 1124   
   SEEN-BY: 467/888 633/280 712/848 770/1 902/26 2320/105 3634/12 5020/400   
   SEEN-BY: 5020/8912 5054/30 5075/35   
   PATH: 154/700 10 280/464 460/58 229/426   
      

[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]


(c) 1994,  bbs@darkrealms.ca