Date: Wed,  2 Jan 2002 17:50:51 EST
From: COMSAT@ITS.SVENSSON.ORG
Subject: Msg of Wednesday, 2 January 2002 17:50-EST
To: CSTACY@ITS.SVENSSON.ORG
Message-ID: <723838.020102@ITS.SVENSSON.ORG>

============ A copy of your message is being returned, because: ============
"SV" at ITS.SVENSSON.ORG is an unknown recipient.
	Will try sending to the file "COMMON;SV MAIL".
============ Failed message follows: ============
Date: Wed,  2 Jan 2002 17:50:51 EST
From: CSTACY@ITS.SVENSSON.ORG
To: SV@ITS.SVENSSON.ORG
Message-ID: <723837.020102.CSTACY@ITS.SVENSSON.ORG>

If you would like to try a version of INQUPD that probably works,
install CSTACY;INQUPD BIN as INQUIR;INQUPD BIN.
I'll be releaseing the real thing eventually, but I wouldn't mind
if you tried out this one.   It works on my system.

I restored the LISP directory (only) on my system, and that's
what makes INQUIR work there.  Is that all you did on your sysetm?
(Donald Fisk doesn't think that worked on his system.)

Chris

Date: Wed,  2 Jan 2002 17:48:36 EST
From: CSTACY@ITS.SVENSSON.ORG
To: CSTACY@ITS.SVENSSON.ORG
Message-ID: <723836.020102.CSTACY@ITS.SVENSSON.ORG>

Does mail work?

Date: Sun, 23 Dec 2001 11:10:53 EST
From: PAUL@ITS.SVENSSON.ORG
Subject: Msg of Tuesday, 4 December 2001 16:36-EST
To: CSTACY@ITS.SVENSSON.ORG
Message-ID: <723786.011223.PAUL@ITS.SVENSSON.ORG>

While I was tweaking my smtp server on the linux side,
trying to get it to log the SMTP commands from SV,
I accidentally bounced all incoming mail for a while.

Here's one of the things that came lose:

    Date: Sun, 23 Dec 2001 10:58:47 EST
    From: COMSAT@ITS.SVENSSON.ORG

    FAILED: cstacy@spacy.Boston.MA.US at [216.155.41.65]; Recipient name apparently rejected.
    	Last reply was: {553 no way from 216.155.41.76 to cstacy@spacy.Boston.MA.US}
     Failed message follows:
    -------
    Date: Tue,  4 Dec 2001 16:36:59 EST
    From: PAUL@ITS.SVENSSON.ORG
    Subject:  Re: Odds and ends 
    To: "cstacy@spacy.Boston.MA.US"@[216.155.41.65]
    Message-ID: <723687.011204.PAUL@ITS.SVENSSON.ORG>

    Good morning Chris,

    Since DQ is one of the two top items on my list of things
    to bring ITS up to speed with the modern world (the other
    is PWORD support in FTPS), I'm going to bug you about it again.

    On Wed, 28 Nov 2001, you wrote:

    >Lacking source code, I just patched the binary for DQ;
    >simply NOP out the gratuitous instructions that I mentioned
    >in my previous message, and the DQ program works:

    Maybe I missed your previous message, or failed to understad it;
    I haven't been able to identify these instructions you're refering to.
    Would you mind trying another shot at enlightening me ?

    >So I assembled a new [DQDEV] from the distributed source.

    The source I have, from the PI image, is DQDEV 182, dated 5/1/86.
    I'm assuming this is what you call the "distributed source" ?
    It contains a referece to SRI-NIV.ARPA, which I suppose needs
    to be replaced with a more modern root server.  Is there anything
    else I need to tweak to get it to work ?  I've tried it here;
    I can initialize and print out the database, but when I try to
    look something up, all I get is a "DEVICE NOT READY" error.

    >This works well enough to do a DNS resolution, update the cache,
    >and print out the resource records in ASCII.  That's about as far
    >as I remember it ever getting (although I may have gotten further
    >with the binary API than I remember.)  As I indicated a few weeks
    >ago when someone asked: there are a lot of things left to do to
    >finish this project.  If I get some time this weekend, maybe I'll
    >start doing that.

    As far as I can tell, the only program currently using the DQ 
    device is COMSAT -- does that mean that it's finished enough
    to make COMSAT happy, or what is needed for that ? 

    You're welcome to have a look at SV if you like; you can reach
    it at its.svensson.org with finger, smtp, telnet, ftp, http, ...

    	/Paul