| 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 |
My customer receives mail from MEMO but cannot send mail from VMSmail.
The Message Router Delivery notification message is as follows:
RE Message ID: Memo from VAX
Generated by node: MEMO/Gateway
UA content ID: Memo from VAX
Attempted delivery to:
External DDA type : MRMRLP
External DDA value : 1
Route : @MDA85
Route : @MEMO
Userid : SYLEN
Arrival date : 8-April-1991 12:00
This delivery failed. Failure reason was "unable to transfer".
Diagnotic was "invalid syntax for Gateway addressing".
The syntax for the message was
TO: MRGATE::"MEMO::SYLEN"
He is sitting on the MRMEMO machine. What other addressing can he use?
They do not have any DDS validations enabled. Also the MEMO sender never
gets a status that his message was received. The current MRMEMO parameters
are as follows:
Server Identification:
Node Name: MDA85
Mailbox Name: MEMO
Message Router Password: ****
SNA Session Identification:
Gateway node: MDACAN
Access name:
Circuit name:
Session address: 64
Application name: UTM0MRGT
Logon mode entry: MVXBIND
Related files:
Translation Table: SYS$LIBRARY:MRMEMOTRA.TBL
Log file: MRMEMO$DIR:MRMEMO1.LOG
Accounting file: MRMEMO$DIR:MRMEMOACC1.DAT
Options:
Accounting: Enabled
Timestamp: Enabled
Header in text: Enabled
Request Notifications: Disabled
Send Notifications: Disabled
Cluster alias addresses: Disabled
Addresses translation: Disabled
MEMO address: SN_ATTRIBUTES
DDS validation:
MR to MEMO sender: Disabled
MEMO to MR sender: Disabled
MEMO to MR recipient: Disabled
MR to MEMO recipient: Disabled
Distribution list: End
Prefix: VAX.
Replace Strings: ..=@
Console logging: None
Clock tick interval: 0 00:00:30.00
MEMO line length: 75
Wrap/truncation string:
Wrapping of long lines: Enabled
Word wrap margin: Disabled
Hyphenation string:
Hours to GMT: 0
If anybody has any clues as to why this is not working, please let me
know. Thanks,
Tracey
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 79.1 | Use Full MEMO-ID | STKOFF::SPERSSON | Pas de Probleme | Tue Apr 09 1991 09:32 | 48 |
Hi Tracey,
The MEMO address should consist of a Distribution Group Name (DGN) and
a Distribution Element Name (DEN), separated by a dot. Thus, by only
specifying one item (SYLEN), this rule is violated. Presumably SYLEN is
a Username (DEN), but the user must have a DGN as well (say, ABC). The
full MEMO-ID would then be:
ABC.SYLEN
and the MRGATE address:
MRGATE::"MEMO::ABC.SYLEN"
If the full MEMO-ID really is only SYLEN, then your customer has a
weird MEMO configuration indeed. I always thought that such ID's were
illegal.
About status messages; this is an art of science in itself, but
briefly: If you enable the MRMEMO server switch
REQUEST_NOTIFICATIONS you'll get delivery notifications from the
Message Router. This is reflected for the MEMO user in the way that if
he chooses the EXPAND option on his MEMO menu, the status text
"Delivery Not Yet Confirmed" will disappear. Read Receipts are never
generated by VMSmail. This means that the MEMO user won't see the
status of his message changed from "SENT TO" to "SELECTED BY".
so what you need to do is
$ MC MRMMAN DEFINE/REQUEST_NOTIFICATIONS
...don't forget to restart the Server.
It deserves mention here that the new X.400 conformant product set,
ALL-IN-1 MAIL, interoperates much better with MRMEMO as far as
service/status messages are concerned. Read receipts will work although
there are restrictions. These are described in 52.1
cheers,
Stefan
| |||||