Conference iosg::all-in-1_v30

    
    Further investigation shown that it's very likely the ALL-IN-1 sender
    who's translating lowercase addresses to uppercase.
    
    Here're the steps that I've run through :
    
    1. Create a mail with the following TO address the following address :
    
            user @nodea @nodeb
    
    2. Shutdown TS before sending the mail from ALL-IN-1.
    
    3. Released the OAMTISEND job to send the mail from sender queue.
    
    4. Since TS was shut down, we were able to locate two NBS files under
       OA$MTI_DATA.  Using MRNBSDMP.EXE to dump the content of the NBS file
       we could see that the address was still in lowercase.
    
    5. Created a dummy mailbox NODEB using MRMAN and started the TS.
    
    6. Released the OAMTISEND job again.
    
    7. The message got queued in the NODEB mailbox.
    
    8. One NBS file corresponding to the queue message was found in MR$NBS. 
       Using the MRNBSDMP.EXE to dump the content of the message indicated
       that the routing address has been converted to uppercase.
    
    What can be done to get around with this ?  Our customer needs
    lowercase to send mail to ULTRIX environment ?
    
    Please help.
    
    Regards,
    Sang. (China/Hong Kong DSS)
     

>    4. Since TS was shut down, we were able to locate two NBS files under
>       OA$MTI_DATA.  Using MRNBSDMP.EXE to dump the content of the NBS file
>       we could see that the address was still in lowercase.

Whwn you say 'content' do you mean the content of the message? You should be 
looking at the envelope .NBS file. Anyway, if the address is in lowercase at 
this stage it cannot be ALL-IN-1 which is responsible for the uppercasing.
    
>    8. One NBS file corresponding to the queue message was found in MR$NBS. 
>       Using the MRNBSDMP.EXE to dump the content of the message indicated
>       that the routing address has been converted to uppercase.
    
So, during the stage in which Message Router takes the two files and convers 
them into one, the address becomes uppercased. Again, are you sure it's the 
envelope address which has changed? MR will never change the values of content 
fields.

The problem with MR changing addresses into uppercase is known for V3.1 (and 
V3.1b I believe). It should be fixed with MR V3.2 - which version are you 
using?

grahame

This doesn't answer the problem, but is just some info.  In .0 you say "X.400
mail".  The X.400 standards explicitly state that all mail addresses are
case-insensitive.

Therefore if the receiving system is insisting on addresses being lower case,
then it is at fault, not ALL-IN-1.  However, I agree it would be nice if
ALL-IN-1 / MR / MRX / whatever didn't change the case of an address!

Scott

    While Scott is theoretically right (for X.400), in practise there are
    case sensitive mail systems around.
    
    So we fixed all the places (lots!) in ALL-IN-1 where addresses were
    upper-cased. That left, as Grahame said, one remaining piece of code -
    the (antique!) stuff which converts NBS v1 (two files) to NBS v2 (one
    file). That code ships as part of Message Router, and is fixed as
    Grahame says in MR V3.2
    
    Dave.

    .. and in case none of my fellow ex-mail-developers said it explicitily
    you do need to have ALL-IN-1 patched to at least K602 to get all the
    lower-case fixes.
    
    Regards,
    
    Andrew.D.Wicks
                  

    Is this patch only for ALL-IN-1 V3.0? 
    
    My customer has the same problem and running ALL-IN-1 V2.4. They will
    be upgrading, but in the mean time if this patch can be applied to
    V2.4, it will be very helpful.
    
    Yasemin