| Title: | VAX MAILGATE for MEMO |
| Moderator: | STKHLM::OLSSON |
| Created: | Sat Feb 25 1989 |
| Last Modified: | Tue May 14 1996 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 216 |
| Total number of notes: | 933 |
When a VMSmail user that resides on a node where MRGATE is not installed
send messages to MRMEMO and DDS validation is used, there can be problems
if the DDS record is not properly set up.
There have been some innovative uses of the addressing fields in DDS that
could work in some situations but to work with MRMEMO DDS validation (MR
to MEMO sender validation and MEMO to MR recipient validation), a DDS
record should be set up as follows.
Let's assume that the user USER uses VMSmail on node USRNOD. There is no
MRGATE available on USRNOD but there is one on MRGNOD. The MRMEMO server
is on node MRMNOD and uses mailbox MEMO.
The DDS record should be setup with:
BUILD|MOD DDS SUB/VMSOR=(ADDR=MRGNOD,VMSNOD=USRNOD,VMSUSER=USER)
which results in:
Reverse lookup : USER@USRNOD@MRGATE@MRGNOD
MHS/VMS address number : 1
MHS/VMS address part : MRGNOD
VMS node name : USRNOD
VMS user name : USER
Note that the information in the MBMAN HELP is WRONG!!!
It says:
o vmsnodename is the name of the DECnet node or
cluster where the nearest Message Router VMSmail
Gateway is located. This only applies to
subscribers who are on nodes where Message Router
is not installed.
In the manual (Message Router Management Reference Manual), however, it
correctly says:
o nodename is the subscriber's VMS node name.
After setting up the DDS record as above, USER can now send messages to
MEMO by sending to
MRGNOD::MRGATE::MRMNOD::MEMO::dgn.den
and MRMEMO DDS validations will work.
Anders
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 18.1 | We are greatful... | EEMELI::MITTS | H�kan Mitts, NET/SWAS/Finland | Mon Nov 06 1989 11:30 | 8 |
Tack Anders, Could you please make a mental note to add this info into the manuals, as this was not to be found in the documentation and all examples etc for VAXmail-users used the MHSORADDRESS syntax. Nice to see such quick response, H�kan | |||||
| 18.2 | Oooops - forgot MEMO to MR rec validation | STKHLM::OLSSON | Anders Olsson | Wed Nov 08 1989 12:51 | 49 |
I'm afraid .0 is not entirely correct. My testing was not complete.
.0> After setting up the DDS record as above, USER can now send messages to
.0> MEMO by sending to
.0>
.0> MRGNOD::MRGATE::MRMNOD::MEMO::dgn.den
.0>
.0> and MRMEMO DDS validations will work.
^
+----- This is NOT correct
Sending to MEMO will work fine when MR to MEMO sender validation is used.
BUT... Sending from MEMO to MR will not work when MEMO to MR recipient
validation is used (without DDS is ok). The MEMO user will get back
a message from Message Router looking like:
----------------------------------------------------------------------
Subject: Message Router VMSmail Gateway nondelivery notification
Delivery of this message through the Gateway had the following results:
USER@USRNOD - invalid address
.
.
.
-----------------------------------------------------------------------
To work around this, the DDS entry for a VMSmail should be set up like
this:
BUILD|MOD DDS SUB/MHSOR=(ADDR=(MRGNOD,MRGATE),MHSMAIL=USRNOD,-
MHSUSER=USER)
which results in:
Reverse lookup : USER@USRNOD@MRGATE@MRGNOD
MHS/VMS address number : 1
MHS/VMS address part : MRGNOD
MHS/VMS address part : MRGATE
MHS mailbox : USRNOD
MHS User identifier : USER
I know it doesn't look very nice to have a node name in the mailbox
field but it works and provides a workaround until MRMEMO is fixed
(in a future version).
Anders
| |||||