[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference forty2::mailbus

Title:MAILBUS - Message Router and its Gateways
Notice:Kit Copy Utility - 100.1, Problems - 5.*, Kit Support - 103.1
Moderator:FORTY2::YUILLE
Created:Thu Jun 11 1992
Last Modified:Thu Jun 05 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:3209
Total number of notes:7125

3195.0. "Can I replace SYS$SHARE:MRAPPSHAR.EXE? " by 21272::RP_SATO () Wed Apr 16 1997 21:22

    Hi,
    
    My customer is implementing MBLINK (from Amadeus Systems, in Viena VA)
    that is a gateway to provide access of Message Router world to
    MS-Exchange world. 
    
    This gateway is being configured in a Message Router v3.2 environment.
    Everything works fine here. Problem is that one of their sites have 
    Message Router v3.3 and this gateway is not being able to receive
    message from there. In order to fix this problem, the person from this
    company suggested to copy images sys$share:mrappshar.exe and
    sys$message:mrappmsg.exe from v3.3 to the site (v3.2) where MBLINK is
    being installed and then re-configure the gateway.
    
    Don't you think this copy would damage something in Message Router v3.2
    environment ? I mean, if I replace v3.2 images by those from v3.3 ?
    
    Regards,
    Armando
T.RTitleUserPersonal
Name		DateLines
3195.1ACISS2::LENNIGDave (N8JCX), MIG, @CYOThu Apr 17 1997 13:0813
    If they suspect some version related problems, the best solution 
    would be to upgrade the old (unsupported) V3.2 systems to V3.3A.
    
    I'm curious as to what the actual problem is they are experiencing.
    MR V3.3 supports talking to V3.2 nodes. MRIF (ie mrappshar) isn't
    involved in this process. Perhaps they are simply running into some
    old MRIF bug that we fixed in the later version? (I recall there was
    a problem with V3.2 MRIF disassembling receipt notification messages)
    
    The MRIF component of MR is basically standalone (think about systems
    using remote MR), so copying them over shouldn't 'damage' anything.
    
    Dave
3195.2Other products use those images ?21272::RP_SATOThu Apr 17 1997 21:3718
    Hi Dave,
    
    Thanks for your answer.
    I think there is something in MRIF v3.2 used to build this MBLINK
    gateway that is causing some problem to receive messages from MRv3.3.
    Send/Receive messages from MRv3.2 is not a problem.
    
    >>The MRIF component of MR is basically standalone (think about systems
    >>using remote MR), so copying them over shouldn't 'damage' anything.
    
    Those images I mentioned in .0 are not used by other gateways ? MRGATE
    for example ? Replace them would not cause any problem for other
    products ? I mean, the code of those images are incorporated to
    gateway's code during link time or they are activated at run-time ?
    
    Hope you can help me a little bit more.
    Thanks
    Armando
3195.3Steer clear of Amadeus and MBLINK30753::WIEGLEBLast day is May 2. Farewell!Fri Apr 18 1997 23:0011
    From previous experience, I would recommend using something (anything) 
    other than MBLINK as part of your messaging infrastructure.  What I
    saw was a poorly implemented point-solution and not something I would
    want as part of any credible messaging solution.  Also, their company
    was extremely uncooperative (bordering on hostile) in resolving the
    myriad of problems we encountered with their products.
    
    A much better approach would be to look at standards-based
    interconnection using Innosoft PMDF.
    
    - Dave