Conference virke::mrmemo

74.0. "From MRMEMO via MRX, Mail sent but not received" by SWTHOM::GRAMAIN (G�ronimo) Mon Feb 25 1991 14:54

                         Hi

 Our customer is ALCATEL and our contact is Jonatan Davis (Jonatan worked in 	
In DIGITAL Basingstok, and now works in France on a Mailbus project)

here is the messaging topology:



   --------                        --------
   !      !		           !      !
   !      ! _______________________!      !------------------------ (ATLAS)
   --------                        --------                       administratif
 node NSFDM2                      node NSFDM1                        domain

 MESSAGE_ROUTER 3.1-B            MESSAGE-ROUTER 3.1-B
 MRGATE 3.1-B                    MRGATE 3.1-B
 DDS end node                    DDS World search node
 VMS 5.3-2                       VMS 5.3-2
 MR_MEMO V 2.0                   MRX 2.1-B
 ALL-IN-1 2.3                    VOTS 2.0 + patches
                                 PSI 4.2

     ^
     |
     |
     |
     |
     |
   ---------
   ! IBM   ! with MEMO
   _________
   




  In the DDS world search node there's 3 subscribers (It's very few but a
  little complicate ...)

  subs1: surname DAVIS ,     reverse lookup add ==>  DAVIS@MRGATE@NSFDM1 
  subs2: surname A1DAVIS ,   reverse lookup add ==>  A1DAVIS@A1@NSFDM2
  subs3: surname MEMODAVIES, reverse lookup add ==>  ANSFM.DAVIES1@MEMO@NSFDM2 

  MEMODAVIES have a MEMO account on the IBM and he is abble to send  mail
  to A1DAVIES or to DAVIES via MAILBUS. 

  from Memo on the MEMODAVIES account on the IBM, to DAVIES on VMSMAIL, the
  address used is:  V.DAVIES..MRGATE  (V is the memo name of the vax NSFDM2)

  from MEMODAVIES to A1DAVIES the address used is: V.A1DAVIES..A1  


  Now our customer want to send X400 mail from MEMODAVIES via MRX400. 
  He try the following addresses from IBM memo:

    V.DAVIES..3=private_domain..ATLAS_MB 
and V."DAVIES..3=private_domain"..ATLAS_MB

 the X400 mail is correctly send to the administrative domain ATLAS but 
 when ATLAS try to route the mail to the private domain ALCANET, the 
 receiver information are not found in the X409 envelloppe and the VMSMAIL 
 user DAVIES never receive the X400 mail . 

 The private domain name, the receiver ORNAME0 and ORNAME3 aren't found in the 
 received X409 mail. I think that there's a problem in NBS file created 
 with MRMEMO. I think that this NBS file doesn't store the X400 receiver
 information like MRGATE or All-in-1 . So the X409 file created is also 
 not correct and this mail never reach his destination. 

 Is there an error in my memo addressing syntax ?
 Is there some customer who used MRMEMO and MRX ?
 Is this problem a known problem ?
 Does any body interested with the MRNBSDMP and the MRXTBED of a mail coming 
 from MRMEMO and a mail coming from MRGATE ? 

                            Thank's for any help 


 Here is a MRX log of a tranfert from Memo to vmsmail via MRX

  
File Name : DUA0:[MB$.MRX]MRX$LOG.LOG;29
  
21FEB91 17:26:42.81 E001 1_NSFDM1_000000A3 %MRX-I-RTSMRFETC,  has fetched from
                         message router mailbox ATLAS_MB into file
                         DUA0:[MB$.MRX]625.NBS
21FEB91 17:26:44.53 E001 1_NSFDM1_000000A3 %MRX-I-STAMSGTRN, Started message
                         translation
21FEB91 17:27:53.06 E001 1_NSFDM1_000000A3 %MRX-I-MSGID, Message id:
                         country=FR, admin=ATLAS, private=ALCANET,
                         mpduid=51727112201991/6264@NSFDM2
                         File=DUA0:[MB$.MRX]625.X409 Message Size=682 bytes
21FEB91 17:27:54.60 E001 1_NSFDM1_000000A3 %MRX-I-MSGCLASS8, Message file:
                         DUA0:[MB$.MRX]625.X409 Class: OUTBOUND message
21FEB91 17:27:55.07 E001 1_NSFDM1_000000A3 %MRX-I-ORNAME0, Originator ORname::
                         Country: FR, Admin: ATLAS, Private: ALCANET
21FEB91 17:27:55.33 E001 1_NSFDM1_000000A3 %MRX-I-ORNAME3, Originator ORname::
                         Personal Name: Surname: MEMODAVIES, Given name:
                         JONATHAN
21FEB91 17:27:55.58 E001 1_NSFDM1_000000A3 %MRX-I-CPLMSGTRN, Completed message
                         translation
21FEB91 17:28:06.65 0229 1_NSFDM1_000000A3 %MRX-I-RTSNEWCON, New connection
                         SCI: ALCA400910221162806Z29 to admin domain:ATLAS,
                         private domain:, network
                         address:.X400.X25_ALCANET%193242420, connection
                         attempt 1 of 40
21FEB91 17:28:12.94 0229 1_NSFDM1_000000A3 %MRX-I-RTSACTSEN,
                         ALCA400910221162806Z29 activity 020101000000 sending
                         X.400 message file DUA0:[MB$.MRX]625.X409
21FEB91 17:28:14.96 0229 1_NSFDM1_000000A3 %MRX-I-RTSACTTRA,
                         ALCA400910221162806Z29 X400 message file
                         DUA0:[MB$.MRX]625.X409 transmission ended, 682 bytes
21FEB91 17:28:16.23 0229 1_NSFDM1_000000A3 %MRX-I-RTSDISCON,
                         ALCA400910221162806Z29 waiting 1 minutes before
                         disconnection
21FEB91 17:28:19.33 OSAK 1_NSFDM1_000000A3 %MRX-I-RTSCONACP,
                         =ATLAS910221172825Z new connection from admin
                         domain:ATLAS, private domain:, network
                         address:..X25_ALCANET%193242420, is accepted
21FEB91 17:28:19.95 OSAK 1_NSFDM1_000000A3 %MRX-I-RTSOSIWAI, ALCA400 - Session
                         waiting for incoming connections
21FEB91 17:28:22.25 0230 1_NSFDM1_000000A3 %MRX-I-RTSACTCRE,
                         =ATLAS910221172825Z activity 020101000000 creating
                         X.400 message file DUA0:[MB$.MRX]627.X409
21FEB91 17:28:23.27 0230 1_NSFDM1_000000A3 %MRX-I-RTSACTRCV,
                         =ATLAS910221172825Z X400 message file
                         DUA0:[MB$.MRX]627.X409 created, 266 bytes received
21FEB91 17:28:25.41 0230 1_NSFDM1_000000A3 %MRX-I-RTSSESREL,
                         =ATLAS910221172825Z has been disconnected
21FEB91 17:28:27.21 D001 1_NSFDM1_000000A3 %MRX-I-STAX409R, Started X.409
                         relay message check
21FEB91 17:28:29.45 D001 1_NSFDM1_000000A3 %MRX-I-STAMSGTRN, Started message
                         translation
21FEB91 17:28:51.86 D001 1_NSFDM1_000000A3 %MRX-I-MSGID, Message id:
                         country=FR, admin=ATLAS, private=,
                         mpduid=21/02/01194387 File=DUA0:[MB$.MRX]627.X409
                         Message Size=266 bytes
21FEB91 17:28:52.08 D001 1_NSFDM1_000000A3 %MRX-I-MSGCLASS5, Message file:
                         DUA0:[MB$.MRX]627.X409 Class: INBOUND delivery report
                         for delivery
21FEB91 17:28:52.26 D001 1_NSFDM1_000000A3 %MRX-I-ORNAME0, Originator ORname::
21FEB91 17:28:52.45 D001 1_NSFDM1_000000A3 %MRX-I-ORNAME3, Originator ORname::
                         Personal Name:
21FEB91 17:28:52.63 D001 1_NSFDM1_000000A3 %MRX-I-CPLMSGTRN, Completed message
                         translation
21FEB91 17:28:52.88 D001 1_NSFDM1_000000A3 %MRX-I-CPLX409R, Completed X.409
                         relay message check
21FEB91 17:28:59.05 D001 1_NSFDM1_000000A3 %MRX-I-RTSMRPOST,
                         =ATLAS910221172825Z posted DUA0:[MB$.MRX]627.NBS at
                         MR-mailbox ATLAS_MB as 21/02/01194387
21FEB91 17:29:33.61 0229 1_NSFDM1_000000A3 %MRX-I-RTSSESREL,
                         ALCA400910221162806Z29 has been disconnected





    

    
    (in reply to both 73 and 74)
    
    Before we do anything else I suggest upgrading to MRMEMO V2.1 (see 3.3
    and 3.4 for info on how to obtain it through the Assets library)
    
    74 will almost certainly be fixed by this, 73 not for sure but there's
    a fair chance.
    
    Stefan