🚀 go-pugleaf

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

>>    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.
>
>You can also end up severing your newsfeed so that some groups are
>attached to one server and the others to another (nntp.dat).

    Yes and no... I have exclusive ng polled from only one server, but
it's not reliable. I don't recieve all articles, or recieve them with a
delay. Example: this demon.ip.support.atari. It's a demon specific group,
but I can have it thru news.compuserve.com... but with only a 1/10 of the
daily articles! (trafic is under 1 article/day there).

    For more worldwide groups like comp.sys.atari.st, I can poll
compuserve and get there say 50 articles a day. Then I poll zippo, and get
another 50 more, for the same period (zippo is not working this week??).
So why not get c.s.a.st from zippo only? First because compuserve is
faster for me, second... because zippo dont have some articles cis has.
Someone said me that Usenet and NNTP were reliable techniques... as
opposed to the fidonet echomail technology... Yes, but...

    For the history file problem, I wrote a little program to discard the
doubled lines, make a backup, and cut the 2000 last lines. And if the file
is cuted to 1000 lines (done an expire group in Oasis) fills to 2000 from
backup. Just have to think to execute it manually after each session.


>> - the loose-last-line in articles bug
>
>Another dead annoying one. Anybody want to write a decent batch.txt
>bodger? I don't think Oasis takes the byte count after rnews into
>account either.

    Right, Oasis seems to go from "#! rnews xxxxxx" line to another, not
counting the bytes... Just tested it. So we can add/sub lines, chars,
words, and so on to the batch.txt before unbatch. Have to write a little
proggy to add a CR/LF just at the end of each article, and perhaps convert
the charset from iso to atari, discard it if there is a rnews 0000000000
line, and... and what? Aaaaaahhh! kill sigs!


>> - the hide-last-line in window bug
>
>Is this the same as the loose-last-line? I haven't the inclination to
>check.

    Related, but only a little annoying, you can unhide this line quite
easely, just by scrolling it down the window, then back up. The last line
only disapears when you <shift>up/down page by page... or at the beginning
when Oasis shows you the article, before you scroll or else.


>> - the Organi[sz]ation: header bug

    This one is corrected, as you can see in the headers, just a little
xxedit in OASIS.PRG. It was annoying, because compuserve used to add his
own organiZation line in my headers when I had an organiSation line or
ommited it.

>> - the edit previously written article bug (edit xx.TXT.TXT)
>
>Use an external editor - it may have something to do with the
>messagebase blank screens and bombs - maybe a dumb strcat() stuffing
>some vital storage?

    But I use an external editor! Had the same bug with Oasis-ed, and have
it with Everest 3.5


>95aed504 looks like a machine address so maybe it's got into the UDP
>or TCP code and dying there?

    Yes, its the address of this moment mail.compuserve.com, but behind
this name are hidden 7 or 8 real machines, with different ip addy...

>Why is it resolving the gateway? Does it have to? The demon gateway is
>specified as an address. Is mail.compuserve.com actually a gateway?

    It resolves the gateway even if I just ask the ip address of it,
typing "smtp gateway": Nos resolves the name as setted in my startup.nos,
then print the IP. And puts a line like that one in NOS.LOG

>Try circumventing this by sending direct. What does "smtp wait 60" do?
>Does it still crash immediately or does it wait the 60 seconds then
>crash?

    It always bombs immediatly when I type "smtp kick". I tried smtp wait
0, tried 1, tried 120, etc... tried almost every idea that comes to mind,
but I'm not familiar with smtp concepts, so perhaps just missed something
__

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