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.

   JAMNNTPD      Support for the JAMNNTPD software client      2,630 messages   

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

   Message 1,629 of 2,630   
   Rick Christian to mark lewis   
   Bug Ticket #6   
   09 Nov 16 20:53:47   
   
      Hello mark!   
      
   09 Nov 16 10:19, you wrote to me:   
      
    ml> because the lack of the CAPABILITIES is enough to tell them that it is   
    ml> not a mode switching server...   
      
   Rergardless of if JamNNTPd is a mode switching server...   
      
   Clients that follow the RFC and the way the server is to respond is that MODE   
   READER should be sent.. 200... LIST...   
      
   The way I've read this is that INN etc.. have settings probably IP or FQDN   
   that would indidcate to them that the connection is another server...and lets   
   say a client connected from that IP/FQDN to tell the server to not limit thins   
   to say IHAVE or XOVER (that is a guess) issue MODE READER then LIST etc. would   
   be available.   
      
   Again...there are clients that insist on this to operate... I use 2 of them..   
   I've fixed it.. hackish right now... I've found a more complete code idea..   
   I'll have to play with it... along with some other things...   
      
    ml> interesting... i've never looked but t-bird is one of the news readers   
    ml> i use to test my news server with...   
      
   The debug mode helped to find out what was coming in.. with out setting up   
   wireshark or something else to tee the ports off ...or even more hackish   
   dumping vars, still had to resort to that for the way it parses stuff now...   
      
    ml> seems that more than one news reader has it wrong, then... or maybe   
    ml> t-bird has it right and the others are wrong for terminating...   
      
   Well PAN, insists they follow the RFC to the letter... I don't know that..   
   that is the spin/rhetoric/hyperbole they put out...and it current maintiner is   
   not willing to deviate from the RFC to solve something.. ie: this issue.   
      
      
    ml> the RFC can't be wrong... the RFC is what the rules are... software   
    ml> has to comply with the RFCs it supports...   
      
   I am not saying the RFC is wrong... I am saying that client(s) that IGNORE a   
   500 response to mode reader and issue LIST anyway.. ie: thunderturkey, are   
   probably wrong, and thunderturkey did this to solve this issue...   
      
   Rick   
      
   ... Vote Trump 2016 and Make America Great Again!   
   --- GoldED+/LNX 1.1.5-b20160322   
    * Origin: Vina's Talos Moon Base Alpha (1:135/377)   

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


(c) 1994,  bbs@darkrealms.ca