home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Usenet 1994 October
/
usenetsourcesnewsgroupsinfomagicoctober1994disk2.iso
/
misc
/
volume3
/
dnamail
/
dnamail.doc
< prev
next >
Wrap
Text File
|
1989-02-03
|
9KB
|
232 lines
1) Intro
Dnamail and dnamaild allow a Sun computer with the Sunlink/DNI software
to send and receive mail from VMS computers (may work with other DECnet
computers, but hasn't been tested).
These programs cooperate with the sendmail program, so that users
do not need to use any special commands to send and receive mail.
This means that 'mailtool' may be used to read and compose messages.
Dnamail may also be used independently of sendmail, although message
editing is lacking.
2) Installation
>> The DNI software has a bug that needs to be fixed before
>> dnamail will work. The bug is related to failure to read/write
>> zero-length records. You can get the patch from Sun
>> (bug #1007228), and possibly from the sun archives at rice.edu.
>> You could possibly get them from me, but save this as a last resort.
Look over 'Makefile' and 'dnamail.h'. If you want to have dnamaild
run 'standalone', then uncomment the STANDALONE definition in
dnamail.h. When dnamaild is compiled with the STANDALONE option, then
it will not automatically be called from dnaserver, but must be run
before you expect any mail to show up. It will handle one mail connection
and then exit. Obviously, this option is not too useful, but it helps
if you are trying to debug.
Do 'make all'. This should make the executables 'dnamail' and 'dnamaild'.
Put the executables into /usr/sunlink/dna, or use a symbolic link.
Add the following line to /usr/sunlink/dna/dnaserver.reg (if you want
to run dnamaild 'standalone', then you shouldn't do this):
27 MAIL /usr/sunlink/dna/dnamaild
Modify sendmail.cf appropriately and restart sendmail.
Test... Before making sendmail.cf changes, you can try
running dnamail directly - just type /usr/sunlink/dna/dnamail.
After making the sendmail.cf changes, you can test by just sending
mail.
3) Sendmail.cf changes
In order to have dnamail and dnamaild cooperate with sendmail, changes
must be made to /usr/lib/sendmail.cf.
>> If you have made changes to sendmail.cf before, or no someone
>> who has, then the modifications will be relatively straightforward.
>> If you don't fit into the above category, then I suggest that you
>> read the 'Sendmail Installation and Operation' tutorial in the
>> Sun system administrators guide to familiarize yourself with
>> sendmail.
On the Sun installation tape(s), sendmail.cf came in two forms,
sendmail.main.cf and sendmail.subsidiary.cf. With dnamail, there
are four combinations - main, subsidiary, sub_decnet, and main_decnet.
Remember to make a symbolic link to the correct file on each machine
(see the Sun system administrators manual).
'diff' output is included in this distribution showing the changes to
be made to the original sendmail.main.cf and sendmail.subsidiary.cf
so that they will handle DECnet. If you have not changed your
original .cf much from the original SMI-3.2 version, then the patches
may work as is. If not, then use the patches and the following
instructions as a guide. Even if patch works, you still need
to read these instructions (two other files need changing).
Briefly - use patch to create new version of the .cf files. Then for
every Sun that runs DNI, uncomment the 'DSdnahost' line for it (use
a private copy!).
REMEMBER: Make backups of the original .cf files!! It also helps
to comment each of the lines you changed.
Here are the basic changes. Anything that looks like multiple spaces
should actually be a tab.
- in /etc/hosts, add 'dnahost' as an alternate name for the machine
you want to be the DECnet relay. For example, my site has:
192.9.200.1 nova dnahost
If you have more than one machine running Sunlink/DNI, then pick
one machine to be the relay for machines without Sunlink/DNI.
- Edit a file called "/usr/sunlink/dna/dnahosts" to contain a list of
all VMS/DECnet nodes you want to send mail to, one node per line.
You do not need to have ALL the VMS machines listed, just the ones
you want to send mail to (a listed machine can deliver mail to a machine
that you didn't list).
- Add the following lines somewhere near the beginning of sendmail.main.cf
and sendmail.subsidiary.cf.
# Major decnet relay (relayed by #ether)
DSdnahost
# get list of decnet machines we want to be able to send mail to
FS/usr/sunlink/dna/dnahosts
The DS line defines a macro, $S, to be the name of the machine that will
actually connect to DECnet. Any machine that can't handle DECnet mail
will forward any DECnet mail to this machine to handle it instead.
If all your machines are on DECnet, then you don't need to do this.
If you already have a $S macro (search for ^DS in vi), then choose an
unused macro instead.
The FS line defines a class, $S, that defines the VMS nodes
we can send mail to with dnamail.
- Add 'dna' as a trusted user. Look for the following lines in
sendmail.main.cf and sendmail.subsidiary.cf:
Troot
Tdaemon
Tuucp
and add the following line to these:
Tdna
- In sendmail.main.cf (only), look for the following lines (in ruleset 0):
# resolve UUCP domain
R<@$-.uucp>:$+ $#uucp $@$1 $:$2 @host.uucp:...
and add these next lines BEFORE them:
####################################################
# If $S (decnet gateway) is defined, then forward to $S, else
# resolve to dna mailer.
####################################################
R$+<@$=S> $?S $#ether $@$S $:$2!$1 $| $#dna $@$2 $:$1 $.
R$+<@$=S.uucp> $?S $#ether $@$S $:$2!$1 $| $#dna $@$2 $:$1 $.
(If you aren't using 'S' as the macro for 'dnahost', then subsitute
in the macro letter you are using).
- In sendmail.subsidiary.cf (only), look for the following lines
(in ruleset 0):
# optimize names of known ethernet hosts
R$*<@$*$%y.LOCAL>$* $#ether $@$3 $:$1<@$2$3>$4 user@host.here
and add these next lines BEFORE them:
####################################################
# If $S (decnet gateway) is defined, then forward to $S, else
# resolve to dna mailer.
####################################################
R$+<@$=S> $?S $#ether $@$S $:$2!$1 $| $#dna $@$2 $:$1 $.
R$+<@$=S.uucp> $?S $#ether $@$S $:$2!$1 $| $#dna $@$2 $:$1 $.
(If you aren't using 'S' as the macro for 'dnahost', then subsitute
in the macro letter you are using).
- Add the following lines to sendmail.main.cf and sendmail.subsidiary.cf
(at the end of the file, or grouped with the other mailer definitions):
############################################################
############################################################
#####
##### DECnet Mailer specification
#####
##### Messages processed by this configuration are assumed to leave
##### the internet domain. Hence, they may not necessarily correspond
##### to RFC822 in all details.
#####
############################################################
############################################################
Mdna, P=/usr/sunlink/dna/dnamail, F=mnSF, S=14, R=24,
A=dnamail -f $f -n $h $u
S14
# none needed
S24
# none needed
- Now copy sendmail.main.cf to sendmail.main_decnet.cf. Also copy
sendmail.subsidiary.cf to sendmail.sub_decnet.cf. Edit both of
these new files and change the following line:
DSdnahost
to:
# DSdnahost
(this comments the line out). This one line should be the only change.
Now for each machine that is a valid DECnet node, make a link from
sendmail.cf (in /private/usr/lib for standard installations) to
sendmail.main_decnet.cf or sendmail.sub_decnet.cf. Depending upon
whether the machine is a main mail machine or not, use one of the
following commands:
ln -s /usr/lib/sendmail.main_decnet.cf /private/usr/lib/sendmail.cf
or
ln -s /usr/lib/sendmail.sub_decnet.cf /private/usr/lib/sendmail.cf
That's it!! After making the changes, you need to restart sendmail.
Since sendmail does not have the capability of 're-reading' the
configuration file, you will have to stop the currently running
sendmail, and then run it again (as root) with the same parameters
as the old invocation (usually, /usr/lib/sendmail -bd -q1h).
4) Usage
If the installation has gone smoothly, everything should
be nearly transparent to users.
To send mail from Sun to VAX, use an address like:
vmsnode!user
To send mail fromt VAX to Sun, use an address like:
SUNNODE::"user"
The quotes (") are necessary so that VMS mail does not convert
everything to uppercase. Longer addresses are just as easy:
SUNNODE::"node1!node2!..."
(In this case, leaving off the quotes causes the '!' to be treated as
comment characters). To set mail to be forwarded from the vax, you will
have to use 3 quotes instead of one:
SET FORWARD SOMESUN::"""someuser"""