On 2005-02-07 14:32:47 +0100, Urs Janßen wrote: > LIST EXTENSION isn't specified by an RFC and it looks like that it > will never be officially implemented (CAPABILITIES might be it's > "replacement"). so officiall we can't blame the netscape server, but > usualy INN is regarded as reference implementation so I'd say that > expecting an 202 answer is the right thing and the server is > 'buggy'. there is still tins problem with unexpected multiline > responses and getting out of sync...
OK. However, in the absence of a specification by an RFC, tin should support the Netscape answer. > > Tin will try to use XHDR XREF instead (slows down things a bit). > > Reading keymap file... > > Reading input history file... > > Reading mail active file... > > Try and save newsrc file again? (Y/n) Y > > > > Then tin freezes. > > for me (but this is with the lastest spanshot) it still accepts the > 'n' answer. I didn't had a closer look at the code why it doesn't > accept 'Y' here. Yes, it accepts the 'n', but in this case, it quits immediately. Not very useful. :( Regards, -- Vincent Lefèvre <[EMAIL PROTECTED]> - Web: <http://www.vinc17.org/> 100% accessible validated (X)HTML - Blog: <http://www.vinc17.org/blog/> Work: CR INRIA - computer arithmetic / SPACES project at LORIA -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
