🚀 go-pugleaf

    Is there a list of bugs of the Oasis package, and known cures? It
would be interesting to make one, helping new users... Or a sort of FAQ.

    I just found one, Oasis corrupts the history file when unbatching...
exactly not corrupts, but adds double lines, with Message-IDs of unbatched
articles... but NOS made this history file with the same IDs before. This
results in a more than twice as long file as it must be, or if you prefer,
in a 1000 ID list (Oasis cuts the last 1000 when you expire a group), only
max 500 lines are usable.

    If you poll more than one server, this can result in a certain amount
of articles downloaded twice, NOS remembering only the last 500... and
different servers recieving the same article at different dates. With my
setup I would need +-2000 IDs in history to be sure.

    Other bugs?
 - the post percent bug (NOS bug actually)
 - the post (not on demon) bug (NOS update is the cure)
 - the slow clock corruption (+-2 seconds each time you start the prg)
 - the loose-last-line in articles bug
 - the hide-last-line in window bug
 - the unbatch bombs
 - no use of the Reply-to: header
 - no use of the "Followup-to: poster" header
 - no use of the "Followup-to:" header at all
 - now this "doubled lines" in history file bug
 - the lines more than 255 chars cutted bug
 - the Organi[sz]ation: header bug
 - sometimes a disk-operation while reading messagebase bombs
 - no cross-posting when replying to a crosspost
 - the yellow-pages cuts too long email addresses
 - the edit previously written article bug (edit xx.TXT.TXT)
 - the "501 newsgroup usage" error related bug

    I think it's all the problems I know of, if you know another one or
have a cure against one of this bugs...

    By the way, not Oasis but NOS: I dont know why, but absolutly cant
send (nor recieve) smtp mail... I tried 7845 different startup.noses, and
have always a bad crash (2 bombs with Falcon locked, reset necessary)
immediatly when I type "smtp kick" (or wait for autokicks) even if there
is NO mail to send... the last lines in the NOS.LOG file are "dogateway:
resolve gateway = 95aed504" and "smtpkick: resolve addr = 0". I'd be
gratefull if someone could help... actually it's perhaps not the better
group to ask this, as I'm using the smtp server mail.compuserve.com... and
the problem might be from there.
__

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