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.

   ELIST      [ADM] ELIST Conference      7,279 messages   

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

   Message 5,091 of 7,279   
   Vincent Coen to Sean Dennis   
   Testing   
   21 Apr 22 16:00:10   
   
   REPLY: 1:18/200 6260de0e   
   MSGID: 2:250/1@fidonet 626173d1   
   CHRS: UTF-8 2   
   TZUTC: 0100   
   TID: MBSE-FIDO 1.0.8 (Linux-x86_64)   
   Hello Sean!   
      
   Thursday April 21 2022 00:29, you wrote to me:   
      
    > Hello Vincent,   
      
    > 21 Apr 22 01:27, you wrote to All:   
      
    VC>> Remember all file submissions MUST go through 2:25/21.   
      
    > So in MBSE, I have 2:25/21 as one of your AKAs.  Do I need to set up a   
    >  separate node for you now?  I just put all of my files into your   
    > filebox here and MBSE fires it off to you; it's all automated.   
      
   All submissions MUST go to 2:25/21 as it is now a different computer that   
   handles it, so yes sorry you will have to create one if you cannot just send   
   files direct and in mbse you can do that - see mbfido a and used as a set up   
   via a script say via a cron job every 11-12 months.   
      
   For other bbs system I do not know but all the one's I used in the past I    
   think   
   you could do the same even without using a netmail attach method (and if that   
   is used do NOT have text within the netmail as empty netmails are deleted by   
   the system as far as I remember.   
      
   Sending to 250/1 will just stay there as I have not set up any method to   
   transmit them to the correct system - assuming there is a way of doing so in   
   mbse but I do not think there is a way as files have not addressing info with   
   them and I would have to manually use mbfido a to send each one, one at a time   
   as there is no group attach method available at least in a automated way.   
      
      
   The whole idea of moving the elist system service onto a different system, in   
   this case a Raspberry Pi is so that if I become ill or die etc the system can   
   be boxed up and posted to a new maintainer that is some what younger than   
   myself. Will only require some minir setting changes and away it will go and    
   it   
   has low power needs.   
      
   Vincent   
      
   --- Mageia Linux v8 X64/Mbse v1.0.8/GoldED+/LNX 1.1.5-b20180707   
    * Origin: The Elist Maintainer (2:250/1)   
   SEEN-BY: 1/123 15/0 18/200 25/0 90/1 105/81 106/201 120/340 123/131   
   SEEN-BY: 129/305 330 331 153/7715 218/700 221/1 226/30 227/114 229/110   
   SEEN-BY: 229/111 206 317 400 424 426 428 470 664 700 250/0 1 3 4 5   
   SEEN-BY: 250/7 8 10 11 263/0 266/512 282/1038 292/854 301/1 317/3   
   SEEN-BY: 320/219 322/757 342/200 396/45 460/58 633/280 712/848 3634/12   
   PATH: 250/1 292/854 229/426   
      

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


(c) 1994,  bbs@darkrealms.ca