On Mon, Apr 27, 2009 at 04:55:29PM -0400, Dennis Boone wrote: > Subject: tin incorrectly reports posting is not allowed > Package: tin > Version: 1:1.9.4-1 > Severity: normal > > *** Please type your report below this line *** > After authenticating to giganews, tin reports: > > *** Posting not allowed *** > > Followup and Write then refuse to allow posting. If I allow the
this is due giganews not announcing reader, mode-reader or post (and till two weeks ago not even which auth methods are available) _before_ autheticating. this has been discussed in news.software.readers and IMHO is a missinterpretation of RFC 3977 on the giganews side, but I have fixed tins source to try auth if only auth is advertized (this is what giganews now sends). IOW there is a workaround in the next snapshot/minor release even if this giganews fault. (giganews violates the RFC on some other points too, i.e.. decrementing the low watermark or exceeding the 2^31-1 articlenumber limit). > connection to time out and then enter a group, tin reconnects, and > is subsequently willing to post. > > Looking at network traces, gn lists these capabilities: > > VERSION 2 > READER > POST > LIST OVERVIEW.FMT ACTIVE ACTIVE.TIMES NEWSGROUPS > XFEATURE 1 > XFEATURE-COMPRESS GZIP TERMINATOR > XFEATURE-METADATA BYTES > XFEATURES 1 this is after authetication (which happens on reconnect). urs -- "Only whimps use tape backup: _real_ men just upload their important stuff on ftp, and let the rest of the world mirror it ;)" - Linus -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
