Conference virke::mrmemo

    Hello Ute,

    Could you give a more detailed description of the enviroment?

    Is it like this?

    IBM                 Node X               Node Y

    MEMO  ------------  MRMEMO  ----------- ALL-IN-1


    in DDS: USER @ A1 @ Y

    An ALL-IN-1 user at node Y sends a message to "memouser @ MEMO @ X".

    Are you saying that this is the situation and that the MEMO recipient
    is seeing the sender address "prefix.USER @ A1 @ X @ Y" ?

    If you do, something is very strange! The last node should be the
    server node. I.e. the MEMO recipient should see the sender address
    "prefix.USER @ A @ Y @ X".

    What kind of DDS validation are we talking about? Since you say:

.0> When MRMEMO looks up in DDS there is no entry with this reverse 
.0> lookup, the message disappears.

    , I assume that it is MEMO to MR recipient validation. When MRMEMO
    looks up "USER @ A @ Y @ X" in DDS, there is no entry with such a reverse
    lookup. This causes MRMEMO to strip off the last route and try again
    (with "USER @ A @ Y"), which should give a match.

    If the lookup fails, the message should definitely not disappear. The
    sender should receive a non-delivery.

    Could you post the server parameters and give a more detailed description
    of the involved nodes (how they hang together)?

    Exactly what address is the ALL-IN-1 user at Y sending to?

    Is the ALL-IN-1 mailbox (A1) located on the same node (Y) as ALL-IN-1.

    Are any Message Router address replacements used (e.g. on node Y to
    translate "MEMO" to "MEMO @ X")?

    If you have additional information and prefer to use FAX, the number is
    +46-8-833552.

    Anders

    hello Anders,
    
    the situation decsribed in .1 is what we experience here.
    
    Mor info for you:
    Server: 	Number 1
    		Name   MEMO2
    		Accounting: 	     Enabled
    		Timestamp,Header in text,Request Notif.,Send Notif. 	Disabled
		Cluster Alias:       Enabled
    		Address translation: Enabled
    			Format:      MEMO
    			Uniqueness:  Disabled
    			Multiaddr.:  Primary
                MEMO addres:	     SN_ATTRIBUTES
    		DDS validation:
    			MR-MEMO sender:	Disabled
    			MEMO-MR sender: Disabled
    	 	        MEMO-MR recip.: Enabled
    			MR-MEMO recip.: Disbaled
    
    The nodes involved look as follows:
    	
    	XNODE ---------- YNODE --------MEMO
    	-----            -----
    	A1, MR           A1, MR,
    			 MRMEMO
    
    	Both A1 systems have local mailboxes.
	
    	On XNODE there is an entry in the MRMAn database:
    	MEMO  /Replace=MEMO2@YNODE
    	
    	On YNODE it's:
    	MEMO /Replace=MEMO2
    	The addressing and answering back works from YNODE to/from MEMO.
    
    	So the users address with : DGN.DEN @ MEMO
    
    	In DDS users are entered as:
    	user@XNODE_A1@XNODE
    	user@YNODE_A1@YNODE
    
    	The from address seen in MEMO is:
    		DEC.user..XNODE_A1..XNODE..YNODE
    
    	If you need more information, please let me know.
    
    	Thanks Ute

    Hello Ute,

    Ok, now I think I've got the configuration clear to me so let's see what 
    we have here...

.2>    	The from address seen in MEMO is:
.2>    		DEC.user..XNODE_A1..XNODE..YNODE

    This clearly shows that MRMEMO did not find "user@XNODE_A1@XNODE" in
    DDS. (The trailing "@YNODE" should not interfere since MRMEMO strips this
    off in the second lookup attempt.)

    I guess you have double (at least :-) checked that user@XNODE_A1@XNODE
    really does exist in DDS.

    If user@XNODE_A1@XNODE does exist in DDS but is not found by MRMEMO, the
    explanation must be that user@XNODE_A1@XNODE is not what MRMEMO looks for!

    I can see that the "Cluster Alias" option in MRMEMO is enabled.
    Are there any cluster aliases involved here, are XNODE and YNODE clusters?
    Is the Transfer Service configured to use Cluster Alias?

    One more thing - what do you mean by:

.0> When MRMEMO looks up in DDS there is no entry with this reverse
.0> lookup, the message disappears.

    What message disappears?
    Doesn't the sender get a non-delivery notification?
    What happens if the MEMO user tries to send a message to
    DEC.user..XNODE_A1..XNODE..YNODE ?

    Could you provide me with:

      - Ansers to the questions above (including those about cluster alias).

      - An MRNBSDMP dump of an NBS file from user@XNODE_A1@XNODE when the
	message has arrived to MRMEMO (when the message is waiting in
	the MEMO2 mailbox).

      - The DDS record (/FULL) for the user that sent this particular
	message.

    There shouldn't be any problems with your setup since it is quite straight
    forward, so I think we'll solve this one soon.

    Anders

    Hello Anders,
    
    after a long time, I came back to this customer and tried to look into
    things and I found the solution.
    
    Problem was, that the DDS entry of the sender had 2 SNUSER and
    SNLOCATIOn fields. I mean it looked like:
    
    Surname:	agkfjhgak
    ...
    SNUSER:	ABCDEFG
    SNUSER:	ABCDEFG
    SNLOCATION:	DEC
    SNLOCATION:	DEC
    ...
    Reverse L.:	abcdefg@a1@node
    
    I have no idea, how this happened, but after deleteing the entry and
    adding it in the right manner everything worked fine.
    
    
    Ciao
    Ute
    
    PS: Thanks for the patience.