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.

   TUB      Squish EchoMail Tosser, Help & Support      484 messages   

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

   Message 372 of 484   
   Rob Swindell to Oli   
   Problem with legacy tosser (Squish) and    
   03 Dec 20 11:12:46   
   
   TZUTC: -0800   
   MSGID: 1892.tub@1:103/705 242e7612   
   REPLY: 2:280/464.47@fidonet 5fc9263a   
   PID: Synchronet 3.18c-Win32  Nov 30 2020 MSC 1927   
   TID: SBBSecho 3.11-Linux r3.179 Nov 30 2020 GCC 8.3.0   
   COLS: 80   
   CHRS: CP437 2   
   NOTE: FSEditor.js v1.104   
     Re: Problem with legacy tosser (Squish) and Sync's MSGID   
     By: Oli to Fred Riccio on Thu Dec 03 2020 05:18 pm   
      
    > 03 Dec 20 08:50, you wrote to Marc Lewis:   
    >   
    >  ML>> I REALLY don't think that Squish is at fault.   
    >   
    >  FR> I think Squish is partially at fault.  When messages tossed to *.Msg   
    >  FR> files, it leaves trash at offset B0 and B2 where the orig & dest zone   
    >  FR> should be.  Same with ofs B4 & B6 where the point number should be.   
    >   
    > The documentation in the Squish Developers Kit (Version 2.00) agrees:   
    >   
    >           Certain message systems, such as the FTSC-0001 *.MSG format,   
    >           do not store zone  information with each message.   When the   
    >           API  encounters such a message  and no zone  is present, the   
    >           specified  zone will  be used  instead.   A 'def_zone'  of 0   
    >           indicates  that nothing  is  to be  inferred about  the zone   
    >           number of a  message, and  in that case,  the API  functions   
    >           will return  0 as the  zone number for  any message with  an   
    >           unknown zone.   
    >   
    > But FTS-0001 defines zone and point fields since 1989.   
      
   The zone and pont header fields only exist for "stored message" (.msg files)   
   and packet headers. The packed message headers themselves do not have   
   provisions for zone and point information. Instead, the zone and point can be   
   found in the INTL/FMPT/TOPT kludges and the "Via" kludge lines (for NetMail),   
   the INTL/FMPT/TOPT kludges being the "correct" method - also mentioned in   
   FTS-1. I'm not sure when the INTL/FMPT/TOPT kludges were added to FTS-1, but   
   it's certainly been a *long* time.   
   --    
                                               digital man   
      
   Rush quote #31:   
   Live for yourself, there's no one else more worth living for   
   Norco, CA WX: 66.6øF, 13.0% humidity, 8 mph NNE wind, 0.00 inches rain/24hrs   
   --- SBBSecho 3.11-Linux   
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)   
   SEEN-BY: 1/123 10/0 1 15/0 18/200 19/10 36 90/1 102/401 103/705 105/81   
   SEEN-BY: 106/201 116/18 110 120/340 123/131 140 1970 124/5016 153/7715   
   SEEN-BY: 203/0 214/22 218/0 1 401 410 700 720 802 820 840 221/0 1   
   SEEN-BY: 221/6 360 222/2 226/30 227/114 702 229/101 424 426 550 664   
   SEEN-BY: 229/1016 230/150 152 240/1120 5832 249/110 206 317 400 250/1   
   SEEN-BY: 261/38 100 1466 266/512 267/155 275/100 280/464 5003 282/1031   
   SEEN-BY: 282/1056 1061 1062 291/100 111 292/854 8125 317/3 320/119   
   SEEN-BY: 320/219 322/757 340/400 900 341/66 342/200 396/45 423/81   
   SEEN-BY: 633/280 640/1114 1115 1138 1321 1384 712/848 801/161 189   
   SEEN-BY: 2320/105 3634/12 5020/715 1042   
   PATH: 103/705 218/700 261/38 640/1321 1384 221/1 280/464 229/101   
   PATH: 229/426   
      

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


(c) 1994,  bbs@darkrealms.ca