| Title: | VAX MAILGATE for MEMO | 
| Moderator: | STKHLM::OLSSON | 
| Created: | Sat Feb 25 1989 | 
| Last Modified: | Tue May 14 1996 | 
| Last Successful Update: | Fri Jun 06 1997 | 
| Number of topics: | 216 | 
| Total number of notes: | 933 | 
    
    Hey !
    
    One customer to me told, they had following kind of a problem
    when sending mail from MEMO to X.400 via MRMEMO.
    They are using the old 2.0 version of the MRMEMO server SW.
    
    They have done DEFINE/REPLACE for characters @ (VAX) --> .. (MEMO)
    and ' ' (VAX) --> + (MEMO).
    It works alright for the name part of the addresses but if the
    X.400 organization part for example includes a two part name
    then it doesn't work.
    
    E.g. @org=NOKIA DATA (from memo NOKIA+DATA)
    The + character will be forwarded to X.400, which will followingly not
    find this organization.
    
    Has somebody noticed this kind of a problem ? Does the MRMEMO
    software support this type of double names in X.400 PRMD and ORG fields
    ?
    
    Thanks in advance
    
    		Jan-Erik Aladin 
                               
| T.R | Title | User | Personal Name | Date | Lines | 
|---|---|---|---|---|---|
| 50.1 | Wait for V2.1 | STKHLM::OLSSON | Anders Olsson, LEG Sweden | Mon Sep 17 1990 13:24 | 20 | 
|     Hello Jan-Erik!
    You say:
.0> They are using the old 2.0 version of the MRMEMO server SW.
    and
.0> It works alright for the name part of the addresses...
    Is it really 2.0 they are using? It shouldn't work even in the name part
    in 2.0 but it was fixed in 2.0A (see note 48.*).
    Unfortunately, the fix in V2.0A only affected freeform names immediately
    following the server prefix. When spaces (i.e. a replacement sequence)
    occur in other places, it doesn't work until MRMEMO V2.1. In V2.1,
    replacement sequence handling will be improved to avoid this kind of
    problems.
    Anders
 | |||||
| 50.2 | Yes, they are using 2.0A | EEMELI::ALADIN | Mon Sep 17 1990 19:30 | 13 | |
|     
    HEY !
    	Yes, you are sure right, that they are using v 2.0A.
    	All because my collegue is away from the office I'm not
    	totally aware of the version numbers that our customer are using.
    
    	Thank's for the quick answer! Sorry to bother you, I should have
        seen  the answer in note 48.
    
    	Bye
    		Jan-Erik
    
    	
 | |||||