Conference virke::mrmemo

    
    Hi Patrick,
    
    Maybe you should clarify what you want to do. Below is an explanation
    which may or may not be relevant to your question :-)
    
    There is a one-to-one relationship between a configured MRMEMO<->MEMO
    connection and a Prefix. For the MEMO user, the prefix corresponds to a
    DGN that points to a MEMO/Gateway connection. Each configured MRMEMO
    server is defined with exactly one Prefix. This obviously means that
    unless you define more than one MRMEMO server, the MEMO users will only
    have one Server Prefix/DGN that points to MRMEMO/Mailbus.
    
    You can define several MRMEMO connections to one MEMO system. The
    maximum number of servers on *one* MRMEMO node is 9. If you do
    define more than one MRMEMO server and want to use DDS to lookup MR
    users, this is perfectly possible as long as you map the MR users to
    the correct DGN/prefix. This means that the DDS field SNLOCATION must
    equal the prefix value. If you want to divide your MR users into
    groups like this, then fine. Beware though that you have to use
    separate MR mailboxes for each MRMEMO server, and that might confuse
    things.
    
    It is not however possible to have *all* DDS records match *any* DGN
    value, if this is what you want to do. I hope not.
    
    Finally a tip: Use Address translation, not DDS validation (ie to
    lookup MR users. If you want to lookup MEMO users as well, DDS
    validation is the only option)
    
           cheers,
    
    		Stefan

Hello Stefan,

Thank-you for your patience and explanation.  However, I would like to go 
around one more time to be sure I understand your explanation.

My customer is a government service provider organization with 12 separate 
user agents tied together through a central MAILbus "hub" via MR/P, MR/X, 
PMDF, MRGATE, & the EMS Synchronizer.  There DDS contains over 30 thousand 
entries, which the customer wants accessable to the MEMO users.  Currently, 
all entries have PR attributes set against them using one of a possible 18 
PR_Location values (& expanding).  The customer would like MAILgate for MEMO 
to use the existing PR attributes and standard MEMO addressing format, when 
addressing to non-MEMO users.  I interpret your explanation to mean that I 
would require 18 VAX MAILgate for MEMO server processes running, matching 
each DGN to a server PREFIX - is this correct ?  


My apologies if I have missed the point if your explanation.


Regards,
Patrick.

    
> I interpret your explanation to mean that I 
> would require 18 VAX MAILgate for MEMO server processes running, matching 
> each DGN to a server PREFIX - is this correct ?
    
    Yes, this is correct. Since the max number of servers on a node is 9,
    this obviously means that you will require two MRMEMO systems on
    two different nodes, and for the 19th PR_Location you would need
    another one.
    
    One more thing that I realise I should have mentioned in my previous
    reply; your MR users would have to know exactly which Message Router
    mailbox is tied to "their" particular MRMEMO server, and the addressing
    would differ. Only if they send the message through their own gateway
    would their sender address be presented in the correct way, otherwise
    the sender address presented would be: 
    
    <actual server prefix>.<PR_Username from DDS>
    
    (sorry, this is the way it works, and I wouldn't even call it a bug)
    
    Example of correct adressing: two MR users from different PR_Locations
    (ABC and DEF), tied to MR mailboxes MEMO1@VAX1 and MEMO2@VAX2
    respectively, each send a message to one MEMO user, MEMO.SMITH
    
    1) MEMO.SMITH@MEMO1@VAX1
    2) MEMO.SMITH@MEMO2@VAX2
    
    So one user within the network has different addresses depending on who
    the sender is. This is devastating if you want to lookup your MEMO
    users in DDS!
    
    I have never heard of any other MRMEMO installation where they use more
    than a couple of servers (most often functionally split between DDS
    Validation/NoDDS Validation).
    
    I think we have a case of customization requirements here. There might
    be other things you need that I can't think of off hand, but I can
    identify two changes that you will almost certainly need:
    
    a) When sending messages to MEMO, present the sender with his actual
    Location+Username as registered in DDS instead of defaulting to the
    server prefix . This way you can send your message through any MRMMO
    server
    b) Allow more than 9 Servers on one node (99?) (Mind you, each MRMEMO
    server will use up a lot of memory, so there may be a pragmatic limit
    somewhere. The management of 18+ concurrent MRMEMO servers might also
    require some extra consideration)
    
    Remember that any change to MRMEMO is available at a price, which
    should reflect:
    
    1) the time spent on the development
    2) the added value for the customer
    
    In this case 1) should be very moderate, 2) should be significant
    
    Mail (copy my mgr Tobias Malmgren@Soo) or phone (DTN 876-8168) if you
    want to dicuss this.
    
    	cheers,
    
    		Stefan