🚀 go-pugleaf

 In article <832967208_OASIS_@swampdog.demon.co.uk>
  guy@swampdog.demon.co.uk (Guy Harrison) said:-

>Not too sure about this but I think there are a couple of different
>ways newservers can behave. It sounds like this one doesn't implement
>NEWNEWS and is sending headers for clients to pick which they want
>perhaps?

    This command is listed in the HELP of the server (connected to the
server thru telnet on port 119), and works good appart of this date
problem... It even complains if you give a bad format date...

    I wonder if it's a bug of the unoff versions of INN 1.4... but just
yesterday I found a new public server, running official INN 1.4, and the
NENEWS command suffers the same bug, it sends messageIDs of all articles
in requested groups, not only this one received after date/time given. But
I know perfectly the behaviour of INN 1.4 server, as it's the program on
the compuserve newsserver. And the NEWNEWS command works on it.

    I dont remember if I stated this, but the server is set to the correct
time, in GMT, the problem dont come from this. It's perhaps a config
problem in INN?

>I thought the Nos history file was truncated at 1000 articles?

    No, only with NOS it's never truncated. Oasis truncates the file when
you expire a group. If you backup it before expiring then restore it, you
can have a bigger history file. And I always backup it, because Oasis
corrupts history when unbatching... well not exactly corrupts, but set
each line twice, if you do nothing you end with a 1000 line file where
only 500 are usefull.
__

	/* Bruno Kozlowski 100710.1360@compuserve.com */
	/* -==- A happy Falcon owner from france -==- */