|
.0> If one of the MEMO users does not exist, and this user is somewhere in
.0> the middle of the dist list, the non-delivery receipt returned contains
.0> the user name of the next user in list. Example:
.0>
.0> MRM.user1
.0> MRM.user2
.0> MRM.usern
.0> MRM.user4 is the dist list
.0>
.0> usern does not exist.
.0> Nondelivery receipt contains: user4 does not exist.
Is this a new customer or has the problem suddenly appeared?
What versions of MEMO and MRMEMO?
Is DDS in use, what options?
My initial guess is that MEMO is doing something wrong. There was a
related problem in this area in MEMO version 3.1.something.
Could you get a trace of this? Either with
1) SNATRACE
or
2) DEFINE/SYSTEM MRMEMO$LOGMASK 20 to get a trace of the message
sent to MEMO (the trace appears in the MRMEMO log file).
The non-delivery from MEMO can't be traced in any nice way with
MRMEMO, so the best way is to use MRNBSDMP on the non-delivery
MR message that MRMEMO creates.
Anders
|
| Hello Anders,
this is a new customer to me, but with all the changes around...
It is Degussa and as far as I know they have MRMEMO for a while.
I have seen the same problem at Bosch already, so it is not totally
new.
Degussa has MRMEMO 2.1 (no patches)
and MEMO V.4.xx .
I am not sure about DDS validation, but I will ask.
SNATRACE ? I have to ask them, if they can do it, but they are very
nice...
I' ll gice more info shortly
Ute
|
| Hello Anders,
no chance to get a trace until 6th of july (that is when I am onsite).
They do not use DDS .
I have tried the same thing at BOSCH, but it worked there (they use DDS validation MR Sender -> MEMO).
But theyhave patches as well.
I will try to give you more info soon.
Ciao
Ute
|