Path: utzoo!attcan!uunet!lll-winken!lll-lcc!ames!amdahl!pyramid!prls!philabs!briar.philips.com!klb
From: klb@briar.philips.com (Ken Bourque;6355;2.34d;$0332)
Newsgroups: comp.os.vms
Subject: Re: Exos Mail.
Message-ID: <31196@philabs.Philips.Com>
Date: 21 Jul 88 16:05:17 GMT
References: <8807160715.AA24007@ucbvax.Berkeley.EDU>
Sender: news@philabs.Philips.Com
Reply-To: klb@briar.philips.com.UUCP (Ken Bourque)
Organization: Philips Laboratories, Briarcliff Manor, NY
Lines: 20

In article <8807160715.AA24007@ucbvax.Berkeley.EDU> "RSVAX::RSVAX::MRGATE::\"A1::BERRY,JOHN\"@gmr.COM" writes:

*
*If a user on any other VAX node attempts to address a workstation (using 
*VAXmail with EXOS% addressing), his process will hang (forever) when he 
*does his final CONTROL-Z to exit and send the message.
*

We use the Excelan stuff all the time and have never seen this.  Next time you
try it have a look at the DECnet server process on the bridge machine and see
if it is running Mail the way it should be.  Check the netserver.log file for
errors.  Also, try sending mail from a DECnet system to the bridge machine
using Exos mail as follows:

<bridge node name>::exos%"<yourself>@<bridge node name>"

That will take the Suns out of the picture and test just DECnet and Exos mail.

Good luck!

Ken Bourque    klb@philabs.philips.com    ...!{uunet,decvax}!philabs!klb