Conference forty2::mailbus

    Bjarne,
    
    	You won't be able to simply make a change local to MRX - the MTA
    definitions for the MTAs MRX connects to (e.g. Your ADMD) will have to 
    be updated also.  To show MRXs' MTA definitions type;
    
    	$ mc mrxman
    	MRXMAN> show mta /full
    
    	The "PRMD substitution", or 'target aliasing' should be done on the 
    remote MTA(s); Obviously, this depends upon how many MTAs you have defined
    - with a bit of luck you may have only your ADMD defined, and would 
    therefore only have to get one MTA to 'fiddle' their MTA definition.  
    	The possible implementation of this would be MTA specific - I
    couldn't say how you could do this with your ADMD/MTAs, but I do know 
    MAILbus400 can do this with the syntax;
    
    	ncl> create mts <x> oraddr <y> type alias, alias target <z>   
    
    
    
    Or I guess you could set up another MRX and run the two in parallel ...
    
    
    	Antony.    

    Hi Antony!
    
    Thanks for your reply!!
    
    The necessary changes have been made at the remote MTA (or whatever) -
    that is our national X.400 service provider.  As far as I know they
    have made two equal ADMD entries apart from the fact that one would
    route mail addressed to the old PRMD name (NTA, I think) and the other
    one would route mail addressed to the same recipients with the new PRMD
    (NPT) instead.
    
    Unfortunately, I'm not currently able to log into the customers system
    but I did send a test mail to a valid X.400 recipient using the new
    PRMD name instead of the old one.   The mail got past the service
    provider but was rejected by customers MRX with something like 
    "unrecognized orname" (I forgot to write it down ....).  I presume it 
    was rejected because no alteration to the PRMD entry has been done at 
    the customer site -> MRXMAN> Show param   gives the PRMD name as the 
    old one.  The new PRMD has not yet been defined anywhere at customer
    site.   Problem is that I only seem able to change the PRMD name, not to
    add an "alternate PRMD" or something like that.   Customer would like
    their users to be able to receive mail addressed using both new and old
    PRMD name.
    
    So, bottom line of my inquiries are:
    
    How do I ensure that mail sent to the customers recipients, using either 
    new or old PRMD name would be validated by customers MRX?
    
    In worst case I guess I could try to set up an "alternate_mbx" for mail
    messages which was not validated to be forwarded to an MailWorks
    account with an autoreply set up - saying that "you need to change PRMD
    in the address to NPT" or something, but I don't know if this would
    work either.   Also, another possibility may be to add doulble
    subscriber entries in DDS for every subscriber, but this would not be a
    very easy or elegant solution - and again - I don't know if it would
    work.
    
    All further help is much appreciated!!!
    
    
    Thanks,
    
    	Bjarne  :-)
              

    Bjarne,
    
    You can't set up an MRX with alternative PRMD attributes. Life just
    isn't meant to be that easy.
    
    As I understand it your ADMD has two definitions for you, one with the
    old (NTA ?) PRMD, one with the new (NPT) PRMD.  Both have identical
    Network addresses.
    
    *If* your ADMD supports this functionality (e.g. If it is MAILbus400), it
    may be possible to set up not two MTA definitions as is set up currently,
    but only one MTA definition with a PRMD attribute of "NPT".  Your ADMD 
    would also have a 'target alias' set up which would substitute the new
    domain "2=ADMDNAME;3=NPT" wherever it found the old domain of
    "2=ADMDNAME;3=NTA".  Any mail coming through your ADMD would therefore
    be 're-addressed' to your updated MRX PRMD.
    This means you would only have to change the PRMD attribute on MRX, i.e.; 
    
    	MRXMAN> modify param /prmd=NPT 
    
    
    > How do I ensure that mail sent to the customers recipients, using
    > either new or old PRMD name would be validated by customers MRX?
    
    All incoming and outgoing mail would be going through the one (and
    only) MRX that you already have up and running. All you would need to
    do is stop MRX, modify the PRMD parameter, then restart MRX.  You would
    be able to receive mail addressed to the old PRMD - it would just be
    altered by the ADMD to point to the new PRMD.   All outbound mail would
    contain the new PRMD address.
       
    I guess the thing to do would be to find out if the ADMD is MAILbus400,
    and failing that, if it supports the described functionality.
    
    
    
    	Regards,
    
    	Antony.	
    

    Antony,
    
    I have just spoken to the ADMD service provider tech support and they
    say they are not using MB400 and that their product is not capable of 
    such a "target alias substitute" functionality as you describe.
    
    I'm instead going to try to persuade the customer to have the ADMD
    provider set up an autoreply (saying please change you PRMD name
    to ....) for any message coming in which is addressed to the customers
    old PRMD.  Hopefully this will suffice .....
    
    
    Thanks,
    
    	Bjarne  :-)