From:	CRDGW2::CRDGW2::MRGATE::"SMTP::DECWRL.DEC.COM::SIMPACT!JEH" 19-OCT-1989 18:24
To:	MRGATE::"ARISIA::EVERHART"
Subj:	new checkaddr to test rewrite rules

Message-Id: <8910191939.AA06171@decwrl.dec.com>
Received: from decwrl.dec.com by DRYCAS.CLUB.CC.CMU.EDU; Thu, 19 Oct 89 15:42
 EDT
Received: by decwrl.dec.com; id AA06171; Thu, 19 Oct 89 12:39:32 -0700
Received: by simpact.com (DECUS UUCP w/Smail); Thu, 19 Oct 89 12:01:45 PDT
Date: Thu, 19 Oct 89 12:01:45 PDT
From: Jamie Hanrahan <jeh@simpact.com>
Subject: new checkaddr to test rewrite rules
To: vmsnet@DRYCAS.CLUB.CC.CMU.EDU

Partly in response to Tom Wallis's query, I am about to send to the mailing
list a new version of the checkaddr program (courtesy of Mark Pizzolato) which
will check rewrite rules.  This posting will be a VMS_SHARE'd, MFTU'd, BACKUP
saveset.  Hence the restoration process will consist of

1.  Concatenate the two messages and removing leading headers (up to the 
"cut between these lines" comment)  (headers intervening between the two
pieces are okay)

2.  Save the result and execute it as a .COM file (this will produce 
CA.BKP_MFT)

3.  Decode the result with MFTU;

	$ run uucp_bin:mftu
	mftu> decode ca.bkp_mft

This will produce CA.BKP, a backup saveset.  

4.  Restore the backup saveset, producing checkaddr.exe and corresponding
sources and documentation.  If you are cautious, inspect the source changes
for Trojan Horses and rebuild it on your own system (which you can't do unless
you have the C compiler, but....)

5.  Define a DCL foreign command to invoke it, something like

	$ ca == uucp_bin:checkaddr

(I believe that in 1.1 as distributed there may have been a symbol `uupath' 
which was defined this way)

This new checkaddr will optionally look at rewrite rules tables based on command
line options.  For example,

	$ ca "user@dom.ain.com"

will just look at PATHS. , but

	$ ca -inbound-to "user@mydomain.company.com"

will look at the inbound-to rewrite rules set.  For outbound-to, checkaddr
will look at the rewrite rules and then PATHS., unless the rewritten address
contains !'s, which implies to the routing mechanism that the rewrite rule
is there to *override* PATHS.   This is exactly the same behavior as the 
mailer.

More problems with rewrite rules can occur if you don't have a correct 
uuxqt_dcl.com , which I will ship in yet another subsequent posting (this
one will be a plain vms_shared version of the file).

	--- Jamie Hanrahan, Simpact Associates, San Diego CA
Chair, VMSnet [DECUS uucp] and Internals Working Groups, DECUS VAX Systems SIG 
Internet:  jeh@simpact.com, or if that fails, jeh@crash.cts.com
Uucp:  ...{crash,scubed,decwrl}!simpact!jeh