Conference iosg::all-in-1_v30

    Hi,
    
    Is that really the address? Because it begins with an @ I think
    ALL-IN-1 will be fooled into thinking it's a Distribution List.
    
    I suspect that the address is really:
    
    1=DK@2=DK400@3=DENET@*RFC-822\CLAUS(A)TUBBE.UVM.MIN.DK@UNIC_MRX
    
    If so then Nicknames will not work because of the embedded parentheses,
    but you can work round this by inventing a pretty name, so that the
    nickname address is:
    
    Claus (1=DK@2=DK400@3=DENET@*RFC-822\CLAUS(A)TUBBE.UVM.MIN.DK@UNIC_MRX)
    
    Cheers
    
    Stuart

    to correct Stuart only slightly (:==:)
    
    An X.400 address should start
    
    term@1=DK@2=....
    
    so you are missing the term to the left of the first @
    
    Regards,
    
    Andrew.D.Wicks

The problem was the use of brackets, and I understand .2 like this:
Put the whole mailaddress into brackets and put any string in front
(preferably a non-insulting name for the adressee).

Below are some examples:

 > 1     EA                     blablabla(a)bla@xxx
   2     EB                     Kingkong  (blablabla(a)bla@xxx)
   3     EC                     Tarzan in the treetops (blablabla(a)bla@xxx)

And below are the same nicknames used in a mail header:

TIL: blablabla                            ( a)bla@xx )
TIL: Kingkong                             ( blablabla(a)bla@xxx )
TIL: Tarzan in the treetops               ( blablabla(a)bla@xxx )

As you can see, EA gets slit up, while EB and EC get treated correctly.

Thanks for your help!

Elin

			... I understand .2 like this ...
should have been 	... I understand .1 like this ...

Elin

      <<< Note 2745.2 by AIMTEC::WICKS_A "Alphatraz - Coming Summer 93" >>>
                       -< Something missing on the left >-

>    An X.400 address should start
>    
>    term@1=DK@2=....
>    
>    so you are missing the term to the left of the first @
    
Well, as the problem's fixed I'm sure Graham will allow us to waste some space 
in his conference!

Why do you need 'term' at the beginning? What's it supposed to be as part of 
an X.400 address? In the example in this note, all of the info is in the 
keyword=value pairs and the DDA - easily enough for MRX to construct a valid 
o/r address.

grahame

    GASh,
    
    well I defer to you as mail expert in residence but i thought that the
    left most term was the person's name or at least that's how i read the
    comments in X400.CMU....
    
    Elin,
    
    EA doesn't work because there's no space character before the ( which
    confuses the mail code which puts the ( ) almost together, gets to the
    end of the address realises it has finished and adds a closing ) at
    which point you have mismatched ( )
    ( all the above subject to whatever GASH says next of course (:==:) )
    
    Regards,
    
    Andrew.D.Wicks

>      <<< Note 2745.6 by AIMTEC::WICKS_A "Alphatraz - Coming Summer 93" >>>
    
>    well I defer to you as mail expert in residence but i thought that the

And quite right too!!

No, seriously, it's an optional field (as it says in the .CMU), and if it's 
present when MRX gets it I think MRX will try and split it into a personal 
name: Given, last, Initials. It's only in the CMU to allow users of the X.400 
form to specify a friendly name - and leave MRX with the problem of sorting it 
into X.400 values!

If the user does what Elin's user does i.e. type in the full 'TFS' address on 
form EMC, then it's sent straight to MRX as is, and the .CMU will never see it 
of course.

(And on the subject of how address validation works, I defer to absolutely 
everyone!)

Now back to normal business,

g

>> Tarzan in the treetops

I didn't know we'd sold him an ALL-IN-1 system :-)

Scott