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 347 of 484   
   Marc Lewis to Digital Man   
   RE: Problem with legacy tosser (Squish)    
   01 Dec 20 09:17:32   
   
   MSGID: 1:396/45.0 fc65c956   
   REPLY: 43034.syncprog@1:103/705 242b9ecf   
   CHRS: IBMPC 2   
   * Copied (from: SYNC_PROGRAMMING) by Marc Lewis using timEd/2 1.10.y2k+.   
      
   Hello Digital.   
      
      
      
    > Of late, my old Squish tosser (OS/2) is having an insurmountable problem   
    > with NetMails containing data other than the Node number and the time/date   
    > code. Here is an example:   
   [snip]   
    >    
    > That apparent message number followed by the @ symbol in the MSGID line   
    > completely throws Squish for a loop as far as the Zone number is   
    > concerned. Both the from and to address are Zone 1 addresses but for    
    > some reason Squish cannot fathom the xxxx@ in the MSGID line.   
   [snip]   
    > I am at a complete loss.  Your help will be very much appreciated!   
      
    DM> It sounds like Squish is trying to parse the source address from   
    DM> the MSGID? It definitely should not be doing that. Squish is open   
    DM> source, do you have the means to recompile it if somewhere were to   
    DM> supply a source code fix/patch for it?   
      
   First, thanks for taking a look at my message and for your suggestion. I would   
   indeed be interested in a re-compilation of the Squish executable, but have   
   absolutely no method of accomplishing that.  I should note that on occasion I   
   run the DOS version of the executable (though not very often) so both the OS/2   
   and the DOS versions would need to be re-compiled.   
      
   Next I need to ask about the @MSGID line itself. (I am still digging to find   
   the FidoNet technical spec that covers it.) I was told *years* back that the   
   only thing that was supposed to be in that line were the originating Node   
   number and the hex date/time code - nothing else. Perhaps the person telling   
   me this (long deceased) may have misinterpreted something... So let me ask   
   you; what's the spec for that line?     
      
   As I mentioned before, and there's absolutely no disrespect intended,   
   Synchronet's NetMail messages are the ONLY ones that cause Squish to go   
   nuts... In fact, only a couple years ago or so, Squish had zero problems with   
   NetMail messages from Synchronet... Until the apparent message numbers started   
   appearing in that line.  What prompted the change in that line's format?   
      
   Also, if there's someone you know of that can re-compile Squish's executable   
   with the recommended changes, please let me know. If you prefer to do it   
   outside of EchoMail, e-mail me at marc.lewis@sursum-corda.com or   
   marc.w@marclewis.org.   
      
   Many thanks.   
      
   Best regards,   
   Marc   
      
   --- timEd/2 1.10.y2k+   
    * Origin: Sursum Corda! BBS-Huntsville,AL-bbs.sursum-corda.com (1:396/45)   
   SEEN-BY: 1/123 18/200 19/33 90/1 105/81 106/633 987 120/340 123/131   
   SEEN-BY: 124/5014 5016 130/803 203/0 221/0 226/30 227/114 702 229/101   
   SEEN-BY: 229/424 426 550 664 1016 240/2100 5138 5411 5832 5853 249/206   
   SEEN-BY: 249/317 400 261/38 280/464 5003 292/854 8125 317/3 322/757   
   SEEN-BY: 342/200 387/25 396/45 633/280 2432/390 2454/119   
   PATH: 396/45 280/464 240/5832 229/426   
      

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


(c) 1994,  bbs@darkrealms.ca