High Voltage Shareware/high1.zip/high1/DIR3/KA9Q212.ZIP/TODO

Text File | 1993-07-15 | 18KB | 417 lines

KA9Q "to do" list as at 15 Jul 93.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1) Line drops whilst NNTP or SMTP are active leave lock files lying
around.

2) New style KA9Q with runtime loadable modules.

3) Add a "rename" command to FTP.

4) 386MAX reports system integrity violation.

5) Write carrier detect and carrier loss event logs.

6) Make the CLI case insensitive (configurable option).

7) Allow the current drive to be changed.

8) Make the telnet chat receive routine do split screen chat so that I
can understand what fis is saying.

9) Add command line history.

10) Remove the "From" line in KA9Q generated mail messages.  Viz:

>From  Sun Oct 18 12:35:08 1992
>Date: Sun, 18 Oct 92 12:35:08 GMT
>Message-Id: <[e-mail]>
>From: [e-mail] (Mail Delivery Subsystem)
>To: [e-mail]
>Subject: Failed mail
>
>  ===== transcript follows =====

11) A user found the following problem:

He managed to create a mail message in PCELM without a To: entry.
When he tried to send it he got "smtp - too many processes".

Also, if the file names in ~/spool/mqueue are changed from *.txt to *
then the same error occurs.

12) NNTP client: deal with "400" response from server.

13) Fix "finger" so that "net -d \nos" works ok.

14) tn3270 client.

15) "ping <target> 10 600 1" no longer produces output on the ping
session screen.

16) > If I start it up from the command line as:
>
>        net -d p:/usr/curdrugs
>
> It works OK & does mail & news.
>
> If I start it up instead as:
>
>        net autoexec.net -d p:/usr/curdrugs
>
> It gives the nntp lock file failure message I posted earlier.

The syntax is actually "net <options> [<autoexec file>]".  Nevertheless,
KA9Q should fail more gracefully in this instance.

17) > I was getting a long (1.5MB) file archive and decided to send some mail while
> this was going on - something I have done many times when using NOS over
> packet radio.  Rather than invoking the shell, just in case this might have an
> adverse effect on the file transfer, I telnetted myself.  After login, I got
> a MAILER BUSY message.  On Retrying, everything seemed OK.  Typed Send with
> the address, got the Subject header through and then the machine hung up.
> I have had to restart the file transfer as unfortunately there is no way
> of just extracting the .zip files I didn't get from the main archive (.zip) file
> Any ideas as to why this happened would be welcomed (how about a Christmas refun
> refund for my long-distance phone call wasted?...).

18) Add an "ftp.rc" file capability to allow presetting of FTP defaults.

19) Add receive hardware handshake to the async routines.

20) >Is there some way to reduce the noise the dialer puts in the NOS log -
>I can't find a configuration parameter.....

21) > I am playing with rlogin in net 2.02a. In it's self it appears to
> work very well, zmodem included, but if you turn capture on, the
> captured sessions has a) at least one if not two extra CR's at the
> end of every line; b) captures the byte counts in zmodem.

22) >Could we have a log entry made whenever the idle timer expires and shuts
>down the line?  This would occasionally help in diagnosing problems.

>Can we also have line mode and pager settings for telnet?
>
>Can we also have a scrollback buffer so I can see what's gone off the
>top of the screen?  Also in FTP for directory listings...  Setting pager
>on works, but I still end up wasting time by having to get another
>directory listing to find the next file I want.

23) Background ping sessions cause bad frees on exit?  Investigate.

24) Dialer - line drop after login prompt.  Hangs dialer.

25) > Another one...
>
> to allow DIS.EXE/NET.EXE to cope with the case where London is long
> distance (and needs the LD code) and Warrington is a local call, for the
> case "Prefer Warrington".

26) Use 450 error in response to RCPT command in SMTP server if mailbox
is locked.

27) Modify KA9Q's SMTP server to process incoming messages as per the
recommendations of RFC 1047.

28) >For KA9Q, a suggestion: some way of slowing down the speed at which
>modem commands are sent (eg. a 1ms delay between sent characters). Some
>modems' command interpreters can't always keep up at 9600bps (eg. mine).
>This is most often found with v22bis modems. (I must upgrade to v32bis
>some day, but I paid 300 quid for my present 3 year old modem -- I doubt
>I'd get 50 quid for it now. Anyone with a second-hand HST DS+ to sell? 8-)

29) >Received: from post.demon.co.uk by nowster.demon.co.uk with SMTP
>        id AA797 ; Tue, 27 Apr 93 19:15:23 GMT
>
>The time given here was the "local time" (ie. BST), but was flagged with
>"GMT". This is in NET.EXE (2.11) and I've the TZ variable set up as you
>recommend.

30) > This morning, at about 0625 I got a whole batch of illegal pointer
> messages from ka9q 2.03. pc=2206 16db & 2206 16ce.
>
> The error appeared to be in smtp. I had sent a set of 5 messages (long) to
> the same recipient. One of them bounced, why I don't know, since I
> regularly send to the same alias name, and one mail file was truncated
> to zero length in mqueue. The mail log shows nothing, apart from one
> incomplete line.
>
>
> Thu Apr 22 06:02:14 1993 - NOS was started at Thu Apr 22 06:02:14 1993
> Thu Apr 22 06:02:15 1993 - NOS load information: CS=0x1d71 DS=0x6448
> Thu Apr 22 06:02:15 1993 - ax1 dialer: init "ATZ\r"
> Thu Apr 22 06:02:16 1993 - ax1 dialer: dial_cmd "ATB1DT"
> Thu Apr 22 06:02:16 1993 - ax1 dialer: ld_code ""
> Thu Apr 22 06:02:16 1993 - ax1 dialer: number "0813434848"
> Thu Apr 22 06:02:17 1993 - ax1 dialer: retries 10
> Thu Apr 22 06:02:18 1993 - ax1 dialer: control down
> Thu Apr 22 06:02:18 1993 - ax1 dialer: wait 2000
> Thu Apr 22 06:02:21 1993 - ax1 dialer: control up
> Thu Apr 22 06:02:21 1993 - ax1 dialer: wait 2000
> Thu Apr 22 06:02:23 1993 - ax1 dialer: init
> Thu Apr 22 06:02:24 1993 - ax1 dialer: wait 3000 "OK"
> Thu Apr 22 06:02:24 1993 - ax1 dialer: dial
> Thu Apr 22 06:02:25 1993 - ax1 dialer: cwait 45000 "CONNECT" "BUSY" "NO CARRIER" "NONE"
> Thu Apr 22 06:02:39 1993 - ax1 dialer: wait 60000 "ogin:"
> Thu Apr 22 06:02:41 1993 - ax1 dialer: wait 1000
> Thu Apr 22 06:02:42 1993 - ax1 dialer: send "panache\r"
> Thu Apr 22 06:02:42 1993 - ax1 dialer: wait 60000 "word:"
> Thu Apr 22 06:02:43 1993 - ax1 dialer: send "11celarent\r"
> Thu Apr 22 06:02:44 1993 - ax1 dialer: wait 60000 "HELLO"
> Thu Apr 22 06:03:07 1993 - update Domain.txt initiated
> Thu Apr 22 06:03:46 1993 - PC clock adjusted by 19 at Thu Apr 22 06:03:46 1993 (server 158.152.1.65)
> Thu Apr 22 06:09:53 1993 158.152.1.65:25 - SMTP sent job 655 To: [e-mail] From: [e-mail]
> Thu Apr 22 06:14:02 1993 - update Domain.txt
> Thu Apr 22 06:14:54 1993 - update Domain.txt finished
> Thu Apr 22 06:15:16 1993 136.170.129.1:25 - SMTP sent job 654 To: [e-mail] From: [e-mail]
> Thu Apr 22 06:23:01 1993 158.152.1.65:25 - SMTP sent job 656 To: [e-mail] From: [e-mail]
> Thu Apr 22 06:24:28 1993 - free: WARNING! invalid pointer (0xaa55aa55) pc = 0x2206 169f proc smtp_send
>
> Thu Apr 22 06:24:28 1993 - free: WARNING! invalid pointer (0x2616752e) pc = 0x2206 16ce proc smtp_send
>
> Thu Apr 22 06:24:29 1993 - free: WARNING! invalid pointer (0x38353655) pc = 0x2206 16db proc smtp_send
>
> Thu Apr 22 06:24:29 1993 - free: WARNING! invalid pointer (0xb0a468b) pc = 0x2206 16ce proc smtp_send
>
> Thu Apr 22 06:24:29 1993 - free: WARNING! invalid pointer (0x473b261c) pc = 0x2206 16db proc smtp_send
>
> Thu Apr 22 06:24:30 1993 - free: WARNING! invalid pointer (0x341c0674) pc = 0x2206 16ce proc smtp_send
>
> Thu Apr 22 06:24:31 1993 - free: WARNING! invalid pointer (0x4478826) pc = 0x2206 16db proc smtp_send
>
> Thu Apr 22 06:24:31 1993 - free: WARNING! invalid pointer (0x160100e9) pc = 0x2206 16ce proc smtp_send
>
> Thu Apr 22 06:24:32 1993 - free: WARNING! invalid pointer (0x1a70424d) pc = 0x2206 16db proc smtp_send
>
> Thu Apr 22 06:24:32 1993 - free: WARNING! invalid pointer (0x75c00be8) pc = 0x2206 16ce proc smtp_send
>
> Thu Apr 22 06:24:32 1993 - free: WARNING! invalid pointer (0x375e040) pc = 0x2206 16db proc smtp_send
>
> Thu Apr 22 06:24:32 1993 - free: WARNING! invalid pointer (0x76fffa76) pc = 0x2206 16ce proc smtp_send
>
> Thu Apr 22 06:24:33 1993 - free: WARNING! invalid pointer (0x468906c4) pc = 0x2206 16db proc smtp_send
>
> Thu Apr 22 06:24:33 1993 - free: WARNING! invalid pointer (0x45c72605) pc = 0x2206 16ce proc smtp_send
>
> Thu Apr 22 06:24:34 1993 - free: WARNING! invalid pointer (0xff5098e9) pc = 0x2206 16db proc smtp_send
>
> Thu Apr 22 06:24:34 1993 - free: WARNING! invalid pointer (0xff5250c0) pc = 0x2206 16ce proc smtp_send
>
> Thu Apr 22 06:24:34 1993 - free: WARNING! invalid pointer (0x3a3ec436) pc = 0x2206 16db proc smtp_send
>
> Thu Apr 22 06:24:34 1993 - free: WARNING! invalid pointer (0x868d1650) pc = 0x2206 16ce proc smtp_send
>
> Thu Apr 22 06:24:35 1993 - free: WARNING! invalid pointer (0x33064689) pc = 0x2206 16db proc smtp_send
>
> Thu Apr 22 06:24:35 1993 - free: WARNING! invalid pointer (0xffff00cb) pc = 0x2206 16ce proc smtp_send
>
> Thu Apr 22 06:24:36 1993 - free: WARNING! invalid pointer (0x80b8f0) pc = 0x2206 16db proc smtp_send
>
> Thu Apr 22 06:24:36 1993 - free: WARNING! invalid pointer (0xc626e88b) pc = 0x2206 16ce proc smtp_send
>
> Thu Apr 22 06:24:36 1993 - free: WARNING! invalid pointer (0xca00c9) pc = 0x2206 16db proc smtp_send
>
> Thu Apr 22 06:24:36 1993 - free: WARNING! invalid pointer (0xf472019b) pc = 0x2206 16db proc smtp_send
>
> Thu Apr 22 06:24:49 1993 158.152.1.69:119 - NNTP Receive error
> Thu Apr 22 06:24:51 1993 158.152.1.69:119 - News summary: 160 articles (304063 bytes) in 1092 sec (278 bytes/sec)
> Thu Apr 22 06:24:51 1993 158.152.1.69:119 - New articles: 62 duplicate, 0 unavailable, 0 headers, 160 complete
> Thu Apr 22 06:24:52 1993 158.152.1.69:119 - History file: 2563 entries, 3 complete scans
> Thu Apr 22 06:24:52 1993 158.152.1.69:119 - Throughput  : 332431/375194 bytes in 1092/1280 sec (304/292 bytes/sec)
> Thu Apr 22 06:24:53 1993 - NOS was stopped at Thu Apr 22 06:24:53 1993
>
> ------------------
> When I tried to log in again to send you this message, I  found that
> the server was down. It was presumably this that caused the errors at
> my end. Nevertheless, ka9q should not have generated pointer faults,
> so ...

31) >NOS (PC, 2.03) seems to die if the message becomes unavailable between NNTP
>deciding it wants the article & actually fetching the article.  (Giles or
>Grahame, could you note this problem please?)

32) >On the original subject (downloading files with silly names) many FTP
>programs have a pattern match/replace facility like
>
>pattern *.ps.Z $1.psz
>
>meaning "if the file name looks like '<anything>.ps.Z', change it to
>'<anything>.psz'.  Any chance of this being incorporated?

33) >>In my rewrite file, I've got a single line saying:
>>
>>    *@zombie.demon.co.uk [e-mail]
>>
>>So why is it, that if mail bounces, it doesn't get put in the right
>>mailbox? Doesn't mail when bouncing look at the rewrite file?
>
>I just checked the source.... the SMTP client in ka9q will return
>undeliverable email to the sender or if present the target of an
>'Errors-To:' line.
>
>It currently ignores the rewrite file, but does use the alias file.
>The change to make it also use the rewrite file is trivial, but we
>are currently consolidating rather than developing.

34) >I managed to crash my PC just now by doing the following from in dis:
>
>ftp ftp
><ftp refused to respond after a couple of minutes>
>F10
>disconnect
>ftp <Another site>
><Logged in okay to other site>
>F10
>se 1
><Returned to first (failed) ftp attempt, to "press key to continue" or
> whatever it says after disconnect>
><Pressed key as requested>
>
><Pressed enter, expecting to go back to se 2, but system hung>
>
>Hope that lot made sense; what does it mean?

gate's ftpd was banjaxed.  Now fixed.  It shouldn't have crashed KA9Q
though.  Hmm...

35) >Using KA9Q 2.03 with demand dialling enabled, I sometimes find that
>when the ppp timeout drops the line and the dialler kicks back in,
>one or more FTP sessions get garbaged screens, then NOS gives an
>error message when I exit from it. I said I would get some exact error
>messages when it happened again, and of course it then stopped
>happening.
>
>Well, it finally reared its head. The message when leaving KA9Q was :-
>  "free: warning: invalid pointer (0x78D30008) pc = 0x4904 28C
>   proc killer"
>The load info from KA9Qs log was
>  "CS = 0x1589 DS = 0x5C60"

36) >Perhaps he means "as soon as I have got my news, exit"  which assumes that
>by this time you will have received all mail.  A more precise way of getting
>mail and news ("blinking") would be handy - it benefits the user and us
>because there isn't any idle timeouts to rely on/wait for.

37) >Often I find that newer mail files in the MQUEUE directory are blocked
>from sending by older files which are waiting for the response from a
>nameserver, whilst the newer files are to addresses cached in
>DOMAIN.TXT.
>
>I'd have thought that up to "smtp maxclients" would be tried at one go,
>but this appears not to be the case.

38) > On my last connect, I had four '[beep] new mail for ...', but
> only three received items in the mailbox, three events in mail.log
> and no trace of a fourth anywhere. (How about writing these new mail
> for lines to the nos log file Giles ?)
>
> One of the items was the 'I'm mailing your article for
> demon.ip.pc.announce' to the mod.
>
> The headers an this look most peculiar, in fact I can't see how it
> reached *my* mailbox - malcolm.txt as I dont have a default deliver
> or default anything in my 'bouncing' file. (I intend mail to any user
> I don't recognise to bounce)
>
> I suspect the fourth beep was this article bouncing around somewhere
> locally via ka9q.
>
> The GMT-60:00 is a little unusual as well isn't it ?
>
> This is the header...
>
> >From @demon.co.uk:[e-mail] Sat May 15 23:32:21 1993
> Received: from post.demon.co.uk by muir.demon.co.uk with SMTP
>     id AA2676 ; Sat, 15 May 93 23:32:19 GMT
> Received: from demon.demon.co.uk by post.demon.co.uk id aa17957;
>               15 May 93 19:50 BST
> Received: from dis.demon.co.uk by demon.demon.co.uk id ab05961;
>           15 May 93 19:50 BST
> To: [e-mail]
> Subject: Output of your News Posting
> Date: Sat, 15 May 93 19:40:11 GMT-60:00
> From: [e-mail]
> Sender: [e-mail]
> Message-ID:  <[e-mail]>

39) >Please could the KA9Q finger command be given an option to do a 'finger -l'
>(long format finger) ? For instance, 'finger -l user@host' should send
>the text '/w user' to port 79 on host. This is useful for some finger
>daemons which otherwise default to the short format listing.

40) >  > >What modems are you all using?  Is there any pattern to the ttys you log
>  > >in to?  What PoP are you dialling in to?
>  >
>  > It happened to me, too - the first time in 6 months (at least) - this
>  > morning (93.05.25 @ 06:20).  Sorry, no tty (it was off the screen
>  > because there were a load of mail jobs queued), but other details:
>
> Passing thought Giles, how about capturing the tty line in the dialer
> code of ka9q and putting it in the log file ?

41) >With a little help from Cliff, a bug found :
>(using NET.EXE v2.11)
>
>If you have a newsgroup entry in NNTP.DAT longer than 32 characters, it
>can cause problems under as-yet-unfathomed circumstances.
>
>If your news pickup crashes out while collecting the headers, check this out !

42) ftp "pager on" - allow break from display.

43) > I think I have found a bug in ka9q, the one where I keep noting that
> I get 'n' You Have Mail messages / beeps, but 'n-1' mail messages
> appear.
>
> I have noticed a few mail messages in my 'malcolm.txt' file that are
> a result of bounces where I have tried to send to a misspelled
> address. That is they were locally bounced when trying to do a lookup
> at demon's name resolution failed.
>
> The 'From ' line (the first one without the colon) is missing the
> site address and reads simply:
>
> >From  Fri Jun 11 21:04:08 1993
>
> instead of
>
> >From  [e-mail] Fri Jun 11 21:04:08 1993
>
> My mailers do not show this message, hand editiing the mail file
> cures the problem.
>
> Also for the wish list...
>
> Can the Mail for line the appears on the screen as mail is received
> also say who it is from ?

44) > I've noticed what appears to be a bug in KA9Q while playing various MU*s,
> not on this account I may add but on my home account (sweat!). If you try
> entering more than about 256 characters without a c/r, KA9Q bleeps at you
> and hangs. I can cope with the bleeping, its the hanging which is annoying as
> its three fingered salute time....

45) > There seems to be a bug in the NET211 DNS server (I use it for writing
> TCP/IP software, using it 'back-to-back'.  It seems that if the client
> asks for the same name more than once in succession, the returned packet
> with the name resolution gets more and more copies of that name in it.
>
> Request:    keris.demon.co.uk
> Receive:    keris.demon.co.uk
>
> Request:    keris.demon.co.uk
> Receive:    keris.demon.co.uk
>             keris.demon.co.uk
>
> Request:    keris.demon.co.uk
> Receive:    keris.demon.co.uk
>             keris.demon.co.uk
>             keris.demon.co.uk
>
> etc.  This may be a fault of my setup, but it's slightly annoying (i.e.
> it makes trace files bigger).
>
> Note that this is getting the host (keris) address - I haven't tried the
> zone file method, as I didn't understand it (I still don't - if anyone
> could mail me their named.boo and zone files, I'd be grateful).  The
> instructions in the documentation are not very helpful...