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.

   FMAIL_HELP      Fmail support      2,396 messages   

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

   Message 1,706 of 2,396   
   Paul Quinn to Wilfred van Velzen   
   FMail-lnx32-2.1.0.18-Beta20170905 netmai   
   10 Jan 18 12:25:18   
   
   Hi! Wilfred,   
      
   A funny thing happened yesterday.  I finally tested FMail's "ping" function,   
   from my other point...   
      
   > 09 Jan 18 09:03:21 FMAIL  Processing 87479A7C.PKT from 3:640/384 to   
   > 3:640/1384   
   > 09 Jan 18 09:03:21 FMAIL  Pkt info: FastEcho 1.46, Type 2+, 415,   
   > 2018-01-09 08:51:06, Pwd, Sec   
   > 09 Jan 18 09:03:21 FMAIL  Processed PING request message from   
   > 3:640/384.125 to 3:640/1384   
   > 09 Jan 18 09:03:21 FMAIL  Deleted: /opt/ftn/fido/inbound/87479A7C.PKT   
      
   That worked beautifully.  OTOH, the pack manager's handling of FMAil's   
   response caught me by surprise, with...   
      
   > 09 Jan 18 09:03:21 FMAIL  FMail-lnx32-2.1.0.18-Beta20170905 - Pack -C   
   > 09 Jan 18 09:03:21 FMAIL  Warning: Node 3:640/384.125 is not defined in   
   > the node manager   
   > 09 Jan 18 09:03:21 FMAIL  Message #1 : 3:640/1384 -> 3:640/384.125   
   > 09 Jan 18 09:03:21 FMAIL  Create   
   > /opt/ftn/fido/outbound/02800180.pnt/0000007d.flo   
   > 09 Jan 18 09:03:21 FMAIL  Sending new mail from 3:640/1384 to   
   > 3:640/384.125   
   > 09 Jan 18 09:03:21 FMAIL  Netmail: 1,  Personal: 0,  Hudson: 0,  JAMbase:   
   > 0   
   > 09 Jan 18 09:03:21 FMAIL  Msgbase net: 0, echo: 0, dup: 0, bad: 0   
   > 09 Jan 18 09:03:21 FMAIL  Pack Active: 0.0062 sec.   
      
   Since I didn't have a 'node' setting in binkD for the point, it meant the mail   
   packet just got hung up (the default binkD ~binkp.net addressing wouldn't work   
   as it's a point, and therefore not available from the WAN side).   
      
   To my way of thinking it shouldn't have happened.  The pack manager's routing   
   is defined as...   
      
     9.   3:640/* via 3:640/384   
    10.   1:* 2:* 3:* 4:* 5:* 6:* via 3:640/384   
      
   (The other 8 entries deal with other zones & regions.)   
      
   So, I'm wondering what I might need to add to the routing table in the event   
   of further "ping" queries, especially from other 'unknown' nodes?  Did the   
   "Pack -C" statement have any bearing?   
      
   Do you have time to help, please?   
      
   Cheers,   
   Paul.   
      
   ... Bad command.  Bad, bad command!  Sit!  Stay!  Staaay...   
   --- GoldED+/LNX 1.1.5-b20110213   
    * Origin: Quinn's Rock - Live from Paul's Xubuntu desktop! (3:640/1384)   

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


(c) 1994,  bbs@darkrealms.ca