Sunlink DNI and dnimail question

[dennett at kodak.com]

I have a sun 3/280 running 4.0.3 and also Sunlink DNI 6.0.  A couple of
years ago I had the same combination on a 3/260.  At that time I installed
dnimail (a DECnet mail interface) 2.0.  I recall that the modifications to
the sendmail.cf file as specified in the installation instructions didn't
quite work.  I inquired on the net and got some corrected rewriting rules
to add to the sendmail.cf file.  They worked great.  At the time the VAX I
was interested in was running VMS 4.something and I do not recall any
problems.  

The last few days I've been installing dnimail on the 3/280.  It works,
but I do have one strange problem.  I went back to the original 3/260 and
sure enough it also had the same problem.  I do not recall this problem in
the past.  The VAXs in question are now running VMS 5.3.  Nothing on the
Sun's as far as I can tell has changed.

I have any mail for me that arrives on the VAX sent to my Sun account via
the DECnet/DNI/dnimail link.  If someone on the VAX sends mail to my
account on the VAX it comes down to my Sun with no problems.  However, in
testing the link I was sending mail from the Sun to my account on the VAX.
Of course, the VAX in turn forwarded it down to my Sun.  It arrived but
the From and the From: line generated when the mail came back down from
the vax appear strange.  I've included a complete test message below.
Both these lines appear as ACADIA::@DISNEY.  ACADIA is the name of the sun
running DNI and dnimail and DISNEY is the name of the VAX (Actually it is
the name of the VAX Cluster but tests with an individual machine give the
same result.)  If I try to reply to this message it wants to go to this
bad address.  

I've included along with the test message an excerpt from the sendmail.cf
file.  It's a vanilla sunsidiary cf file with the dni hacks added.  As far
as I can tell, dnimail 2.0 is still the latest version.  At least it's the
latest version I can find on the net.  If anyone else has seen this
problem, knows a better dnimail interface, or knows of a better way to
hack the sendmail.cf file I'll be glad to hear it.  If you need more info,
just ask.

Thanks,

Charlie Dennett          | Rochester Distributed Computer Services
Mail Stop 01816          | Internet: dennett at Kodak.COM
Eastman Kodak Company    | System Manager - Imaging Science Lab
Rochester, NY 14650-1816 | 

--------  Sample test message

 From ACADIA::@DISNEY  Tue Mar 26 19:04:32 1991
 Return-Path: <ACADIA::@DISNEY>
 Received: by acadia.Kodak.COM (4.0/SMI-4.0)
	id AA26183; Tue, 26 Mar 91 19:04:32 EST
 Date: Tue, 26 Mar 91 19:04:32 EST
 From: ACADIA::@DISNEY
 Message-Id: <9103270004.AA26183 at acadia.Kodak.COM>
 Received: by DniMail (v2.0); Tue Mar 26 19:04:29 1991 EDT
 To: DENNETT
 Subject: test
 Status: R

 Received: by DniMail (v2.0); Tue Mar 26 19:04:29 1991 EDT
 Received: by acadia.Kodak.COM (4.0/SMI-4.0)
	id AA26175; Tue, 26 Mar 91 19:04:21 EST
 From: dennett (Charlie Dennett)
 To: dennett at disney
 Subject: test

 hello
 bye

 ------ sendmail.cf excerpts

#Major DECNet relay (relayed by ether) (commented out on actual dnihost)
#DSdnihost

# major relay mailer
DMether

# major relay host
DRmailhost
CRmailhost

#get list of decnet machines we want to be able to send mail to.
FS /usr/sunlink/dni/dnihosts
.
.
.
###   Trusted users
T root daemon uucp dni
.
.
.
###   Format of headers 
H?P?Return-Path: <$g>
HReceived: $?sfrom $s $.by $j ($v/$V)
	id $i; $b
H?D?Resent-Date: $a
H?D?Date: $a
H?F?Resent-From: $q
H?F?From: $q
H?x?Full-Name: $x
HSubject:
H?M?Resent-Message-Id: <$t.$i@$j>
H?M?Message-Id: <$t.$i@$j>
HErrors-To:
.
.
.
#####		RULESET ZERO PREAMBLE
.
.
.
################################################
###  Machine dependent part of ruleset zero  ###
################################################

# resolve names we can handle locally
R<@$=V.uucp>:$+		$:$>9 $1			First clean up, then...
R<@$=V.uucp>:$+		$#uucp  $@$1 $:$2		@host.uucp:...
R$+<@$=V.uucp>		$#uucp  $@$2 $:$1		user at host.uucp

#################################################
#  If $S (decnet gateway) is defined, then forward to $S, else
#  resolve to dni mailer.
#################################################
R$+<@$=S>		$?S $#ether $@$S $:$2!$1 $| $#dni $@$2 $:$1 $.
R$+<@$=S.uucp>		$?S $#ether $@$S $:$2!$1 $| $#dni $@$2 $:$1 $.

# optimize names of known ethernet hosts
R$*<@$%y.LOCAL>$*	$#ether $@$2 $:$1<@$2>$3	user at host.here
.
.
.
# Special DECnet syntax (node::user)
R$=S::$+		$?S $#ether $@$S $:$1!$2 $| $#dni $@$1 $:$2 $.
R$%y::$+		$#ether $@$1 $:$2@$1


# everything else is a local name
R$+			$#local $:$1			local names


###################################################################
###################################################################
#####
#####                 DECnet Mailer Specification
#####
#####  Messages processed by this configuration are assumed to leave
#####  the internet domail.  Hence, they may not necessarily correspond
#####  to RFC822 in all details.
#####
###################################################################
###################################################################

Mdni,	P=/usr/sunlink/dni/dnimail, F=mnSF, S=14, R=24,
	A=dnimail -f $f -n $h $u

S14
# none needed
S24
#none needed